The Super IC Playbook: 12 Years of Product Leverage Without Management

Lenny notes that Tal Raviv has spent 12 years as an individual-contributor PM, an unusually long run, and asks why he never moved into management. Tal says he has no career strategy; his strategy is not to have one. For most workdays he asks what will make him excited to wake up and follows that, rather than optimizing for title progression. He has watched managers and product leaders and never looked at their calendars and thought he wanted their days.

Tal also noticed that many colleagues he identifies with move into team-lead or director roles and then insist on returning to IC work. His father, a professor and researcher, modeled a version of this: he loves his work, refuses to retire, and never aspired to be chairman or provost. That example made staying hands-on feel like a legitimate source of joy rather than a failure to advance.

He admits the choice is not frictionless. When peers with similar experience get promoted, he feels an ego twinge and questions everything, then realizes that if he could press a button to swap roles he would not. He keeps returning to the same logic: he does not actually want the manager's life. The decision is deliberate, but it is also repeatedly re-made.

Tal frames the IC path around autonomy, mastery, and purpose. Product management offers unusual agency; the role keeps changing, so mastery can deepen across industries and contexts; purpose matters when you care enough about an outcome to want to be the one making sure it is done well. He notes compensation is the elephant in the room, and that the engineering analogy is useful: ICs should not have to become managers to earn more.

He argues ICs must genuinely believe their work can have large scope and impact, especially as companies flatten and hire senior, hands-on people. Tactically, when a recruiter says the number is too high but promises future management opportunities, Tal says he has no intention of going into management. He points out that the industry traditionally undervalues ICs, so the number needs to be right now. He says this approach works.

For companies, Tal recommends making the IC path visible with titles, levels, and rubrics. Titles like product manager, senior product manager, principal product manager, and occasionally distinguished product manager create the idea that progress exists without management. Clear rubrics show how to grow, and saying it out loud gives ICs the respect and recognition they want.

Lenny connects Tal's experience to the industry shift toward flatter organizations and senior IC PMs. Tal cites Meta's layoffs and preference for IC PMs, Zuckerberg's talk of flattening, and Riverside founders looking for experienced hands-on people; he also hears that more experienced people are competing for the same IC roles. The result is that being a 10x PM is becoming table stakes, and AI is a tailwind.

Tal's concrete example came from a team introducing stricter scrum, which created more PM paperwork. He gave ChatGPT the format for stories and epics, then dictated a natural kickoff explanation about background, intent, and cases, and ChatGPT produced detailed user stories that needed only light editing. He says this would previously have required splitting the team or multiple PMs to keep up, and the next experiment is feeding the recorded kickoff transcript into the model.

The project was a fundamental UX change at Riverside. The high-level why, usability studies, design vision, and kickoff had already been done by Tal, design leadership, and the founder; the hard part was making the work specific enough for testing. The team wanted JIRA user stories in a Gherkin-style given/when/then format, which is useful when small but overwhelming at scale. Tal loaded the template into a ChatGPT thread, told it to act as an expert PM and product owner, then dictated the changes conversationally; a human still decided how to split the huge change into logical engineering-sized stories.

Tal used Whisper dictation inside ChatGPT's desktop and mobile apps, and he praised it as a strong transcription model. The workflow depends on giving the model the template first, confirming it understands, then describing the product changes in plain language. He is still experimenting with using the actual kickoff transcript, which did not work as well on the first try.

Tal separates leverage into managing his own time, energy, and focus, then cultivating team habits that let one IC own a lot of scope. He actively designs his days and splits them between deep work and what he calls ping-pong, the reactive Slack mode that scrambles the brain. As a morning person, he blocks mornings for deep work; he goes further and does not open Slack before noon, a habit he has kept for eight years.

He keeps a to-do list section for messages to send when he opens Slack, written as if he is about to hit enter. He finds that most 11 a.m. thoughts do not need to be sent at 11 a.m., and in rare cases he asks someone nearby to check a channel for him. People learn his working style, and the key people have his phone number for real urgency. He estimates an urgent interruption happens only twice a year, which shows how rarely the PM role is truly urgent.

Tal also keeps a product scrapbook: a messy Notion database of every opportunity, support ticket, Gong call, Slack brainstorm, screenshot, and data point. He files evidence as it appears and clusters it over time, because roadmaps look linear while customers and insights do not. When an opportunity resurfaces, he can start with real-world clues; when sales or customer success raises a request, he can show that other customers mentioned it too. The effect is that people feel heard.

Tal believes in cultivating self-reliant teams so one IC can manage multiple teams and bigger areas. He cites Ebi Atawodi's idea that product is not a role but a team, and he makes that language explicit. When a new engineer said he found a case Tal had not thought about, Tal reframed it: product is a team, and the engineer had found a way to improve the product. The goal is to avoid a hub-and-spoke model where the PM sits at the center and passes decisions through.

He looks for places where he is the bottleneck: games of telephone, direct messages instead of public channels, working meetings with only one other person, and communication that keeps routing through him. He tries to create a culture where people figure things out with each other and involve him at the end. He asks people to move questions into team channels, both for transparency and so decisions are searchable later. In a large customer-success org, he asked CSMs to post questions in a big channel so others could find the answer; repeated enough, this becomes a snowball.

Tal acknowledges this requires confidence and comfort with chaos. PMs often want to be the hub so they can control the narrative and prevent an engineer from acting on an ad hoc request. His mentor's phrase, culture of a process, captures his view: process can scaffold a team, but the real asset is a culture resilient to those ad hoc requests. That culture is built gradually through small messages, positive feedback, reasons for working differently, and trust; it will not happen in the first quarter.

When someone takes on work that would have been the PM's job, Tal showers them with positivity so they feel bold enough to do it again. He also does next steps live with people, opening Mixpanel together to answer a data question or creating a JIRA ticket on the call, so they see how easy it is and start doing it themselves. Over time, teammates ask for access and begin writing tickets or running analyses. Tal is packaging these practices into a Maven course, Build Your PM Productivity System, launching in mid-October.

Tal observes that at hypergrowth companies, roughly two departments explain why the company won the market. Even if product does a 10x job, it may not create a 10x company outcome; if marketing, support, data accuracy, customer success, brand and trust, payments, or engineering scalability is the real lever, that is where the career-defining work sits. In his experience product is often not one of the two, even at tech product companies, though he has worked at a company where product and design were the lever.

To identify the two departments, Tal says to ask what drives growth, what the growth model and levers are, and to verify that through back channels and reference checks. Also ask what customers are actually paying for beyond the product or service. The department that drives growth is where careers step-function; being a salesperson at a sales-driven company is valued differently from being a PM there. He cites the advice not to be the finance person at a tech company or the tech person at a finance company, and uses an Olympics analogy: a marathon runner and a swimmer both need a lat muscle, but you want to be the lat muscle on the athlete you want to support.

Tal defines book-smart decision making as data, design, technology, strategy, frameworks, and logic, the tools PMs are trained to use. Street-smart decision making adds another person's point of view, especially the customer's perception, and gives it as much weight as logic. He describes a pricing-structure change meant to unblock payments and enable requests; the analyses were correct and the people were empathetic, but customers revolted because the negative was immediate and the positive came 30 days later. The rollout was rolled back.

Another example: features on higher plans were invisible to lower plans, and the company prepared to make them visible so customers could upgrade. Tal and the team realized customers would see a pile of requested features suddenly require more money, even though nothing new had been built, so they rolled it out in smaller pieces. He also warns that a logical UX optimization can ruin a sales demo by making value harder to see at a glance; sales sent him Gong recordings showing the difference. He jokes about logging out of social media for two weeks after a controversial launch, but the real point is to watch whether complaints persist beyond natural resistance to change.

Tal says he did not always understand that there is no one right way to run a product team or business. He moved from Israel to San Francisco because of professional FOMO, believing Silicon Valley knew how to work. After working with people from Apple, YouTube, Salesforce, Facebook, Slack, Amazon, and Stripe, he concluded that everyone in tech is improvising, as they should, because every market, company, and winning situation is different. He has cycled through phases of zealotry: outcomes-driven, ship fast, A/B test everything, quarterly planning must work a certain way, scrum or no scrum.

When he landed in San Francisco he felt like an imposter, assuming everyone else knew how to work. Six months later he was giving talks and writing blog posts about how to work, some used in Reforge courses. That happened because he was on a team solving a difficult, interesting problem in a unique way. His takeaway is that the best learning is doing really good work at a really good company with really good people on problems that have not been solved that way before.

He recalls his manager's advice that the best networking is doing good work at a successful company and letting everything else follow. He applies the same logic to learning: you become the person writing the blog posts rather than only reading them by working where hard, impactful problems are being solved. He notes he did this from Israel, away from Silicon Valley, so great places to learn exist outside the Valley.

Tal asked for meaningful time in Failure Corner because seeing successful people's LinkedIn profiles can make it seem as if everyone else had smooth sailing; sharing low points helps others understand failure is part of the path. Twice he wasted an entire quarter of a growth team's time through poor use of user research. In one case, 12 failed A/B tests finally forced the team to revisit its hypothesis, but earlier qualitative research would have shown that the checkout psychology was not Groupon's, Amazon's, or Booking.com's; customers had different motivation and reminders. In the second, a referral program's research plan was only half executed: they spoke to successful users but skipped people who should have used it and did not, then shipped under time pressure. The lesson was to use first principles rather than take others' word for what would work.

Tal says he has been a hair away from being fired three times. In one, he repeatedly and candidly disagreed with changes the head of product wanted; a colleague told him that leadership needed to know he would stay with them even while disagreeing, and that if he was right they would adapt and if he was wrong he would learn. In another, he and a manager were simply not a fit, and his manager's manager asked him to stay at the company and find another group while finishing current initiatives. When no opportunity emerged and a director warned him he could not float without a role, a mentor, Gai Peleg, advised him to address the elephant in the room with a new director. Tal shared vulnerably what he thought he had messed up and what was outside his control; the vibe changed, and two days later he joined the group.

He once single-handedly tanked new payments for a week by skipping an A/B test on a sensitive flow, despite having written a framework about when to test, and marketing called because campaigns stopped converting. He also disobeyed quarterly planning with a small team for a quarter to pursue a nonlinear opportunity, which he says was the right call and grew into a bigger team. An April Fools prank on the executive team, a fake German tech publication about a feared European launch, worked because it touched leadership's strategic fear, though the CTO was accidentally left out and walked out of the Monday meeting. Separately, thousands of people tagged his CEO on Twitter calling for Tal to be fired after a pricing uproar; someone used a limited screenshot of a year-old interview to claim he hated poor people, and the tweets were embedded by NPR and the Washington Post. He was not fired because he was not connected to the pricing change, and he says executives trust him because however silly he is, they know how seriously he takes the work.

In the lightning round, Tal names How to Talk So Kids Will Listen & Listen So Kids Will Talk as his best product-management book because it illustrates nonviolent communication with concrete examples, and he connects it to Never Split the Difference. He recommends Ted Lasso as a leadership text; watching it that way changed how he handles aggressive situations, including a Chilean surf break where he disarmed a local surfer by telling him he was one of the luckiest people in the world. His favorite product is an O'Neill Hyperfreak wetsuit, which he experiences as well-designed gear made by someone who understands surfers. His life motto, painted on plywood outside a Mexican surf shop, is that you cannot stop the waves but you can learn how to surf. He closes by describing work during war: teammates in Israel and Ukraine go to shelters or deal with missile alerts and power-grid attacks, and the routine of work becomes more important; he notes that 107 hostages had been held by Hamas for 328 days and calls for them to come home.