Staying a senior IC PM for 12 years: lessons from Tal Raviv

Executive overview

Most PMs assume career progression means moving into management. Tal Raviv has spent over 12 years as an individual contributor PM — at Patreon, Wix, AppsFlyer, and Riverside — and argues the IC path is both viable and deeply rewarding if you understand its mechanics.

The key is building leverage without headcount: design your time ruthlessly, cultivate self-reliant teams, and use AI to do the work that once required a director-level organisation. The super IC wins not by being indispensable, but by making the team function without them.

Why stay an IC

• The test: "If I could push a button and switch roles with that manager, would I?" — if no, stay.
• Autonomy, mastery, and purpose (from Drive) all exist in the IC PM role without management overhead.
• The industry is catching up: post-layoff flattening has increased demand for hands-on senior PMs.
• In compensation negotiations, flip the script: "I have no intention of going into management — so I need the right number now."
• Create the path structurally: titles (PM → Senior PM → Principal PM → Distinguished PM) plus a written career ladder signal it is real.

Using AI to scale yourself

• Dictate project context naturally into ChatGPT (via Whisper) as you would to a new team member, then have it generate Jira user stories in Gherkin format.
• The human judgment still required: deciding how to decompose a large change into logical engineering stories.
• A single PM can now do what once required a director-level org; being a "10x PM" is becoming table stakes.
• Next frontier: feed the actual recorded kickoff transcript in directly — still being refined.

Designing your time

• Split days strictly between deep work and "ping pong" (reactive Slack time) — never mix them.
• Don't open Slack before noon; queue messages in a to-do list and send them all at once.
• Give key collaborators your phone number for genuine emergencies — they almost never use it (roughly twice a year).
• Product scrapbooking: maintain a Notion database of every opportunity, support ticket, Gong call, and data point; cluster them over time so evidence is ready when the roadmap reaches that area.

Building self-reliant teams

• Reframe language: "product" is a team function, not a role — engineers and designers should say "I found something we didn't think about," not "product missed this."
• Seek to not be needed, but be valuable — identify where you are the bottleneck and remove yourself from it.
• Move conversations from DMs into public channels; answer questions there, not in private.
• Celebrate loudly when teammates do "PM thinking" — ideas, data pulls, Jira tickets — so they do it again.
• Teach by doing live, not by delegating: open Mixpanel together on a call rather than saying "I'll get back to you."
• Culture over process: the self-reliant team is the real product a PM is building.

Every tech company has two departments that matter

• In any company, roughly two departments drive 10x outcomes if they perform 10x — identify them before joining.
• Examples seen: product + design, data accuracy + customer success, trust/brand + payments, marketing + engineering scalability.
• Product is sometimes on the list — but often is not, even at tech product companies.
• How to find them: understand the growth model, understand what customers are actually paying for beyond the surface product.
• Being a PM at a sales-driven company means being a feature factory — that is not a failure, just a mismatch.

Book smart vs. street smart decisions

• Book smart: data, frameworks, design, strategy — all necessary, not sufficient.
• Street smart: weighting customer perception as heavily as logic, even when the logic is airtight.
• A pricing restructure that was numerically correct caused a public revolt because customers only saw the negative immediately; the positive arrived 30 days later.
• Features locked behind paywalls suddenly made visible felt like "the company built everything you asked for and now wants more money" — even though nothing changed in pricing.
• Sales demo risk: UX optimisations that reduce clicks can destroy the "aha moment" in demos; get Gong recordings before and after.
• Rule: if a change affects perception-sensitive flows (payments, pricing, trust), run an A/B test even when logic says there's no downside.

Failure corner

• Wasted two full quarters of growth team time by skipping qualitative research and assuming e-commerce conversion tactics (Groupon, Booking, Amazon patterns) would transfer to a different customer psychology.
• Built a referral program based on research with only existing users — skipped the "should use it but don't" cohort due to time pressure; the result did not work.
• Tanked new payments for a week by skipping an A/B test on a "clearly harmless" UX change — violated his own published framework.
• Came close to being fired three times: once for repeatedly voicing disagreement with a head of product without giving them the trust they needed; once for a manager mismatch resolved by openly naming the elephant in the room with a new director.
• Pulled an April Fools prank on the executive team involving a fake German tech publication, fake domain, fake cease-and-desist, and an emergency Saturday leadership call — the CTO found out two days later.
• Went viral on Twitter (wrongly) as hating poor people due to a decontextualised screenshot from an old interview, embedded in NPR and Washington Post during a pricing controversy.

No right way to do product

• Working shoulder to shoulder with people from Apple, YouTube, Stripe, and Facebook revealed: everyone is improvising.
• Every market, company, and moment demands a different approach — outcomes-driven, ship-fast, A/B-everything are all contextually valid.
• The best learning comes from doing hard work at a good company on unsolved problems, not from reading about how others did it.
• The best networking is doing really good work at a successful company; everything else follows.

Lightning round

• Favourite PM book: How to Talk So Kids Will Listen and Listen So Kids Will Talk — the most concrete illustration of nonviolent communication principles.
• TV: Ted Lasso watched as a leadership study, not a comedy.
• Life motto (from a plywood sign outside a Mexican surf shop): "You can't stop the waves, but you can learn how to surf."
• Course: Build Your PM Productivity System on Maven — covers time design, self-management, self-reliant teams, and feedback culture.