Lenny's PodcastThe art of product management | Shreyas Doshi (Stripe, Twitter, Google, Yahoo)
CHAPTERS
- 0:00 – 0:16
Cold open: why internal optics matter (and what it unlocks)
Shreyas opens with a counterintuitive reminder: internal optics isn’t fluff—it can create energy, awareness, excitement, and better feedback loops. This sets up a recurring theme of using communication intentionally to amplify impact and execution.
- •Internal optics can generate momentum and buy-in
- •Awareness and excitement lead to more feedback and opportunities
- •Optics can be a force-multiplier for execution and outcomes
- 0:16 – 4:44
Lenny’s setup: Shreyas’ credibility, the episode structure, and focus areas
Lenny introduces Shreyas’ background (Yahoo, Google, Twitter, Stripe) and explains the “five big ideas” format. He previews the core topics: pre-mortems, time allocation, product work levels, execution vs. strategy, and prioritization pitfalls.
- •Why Shreyas’ frameworks resonate (memorable, contrarian, experience-backed)
- •The episode will go deep on five ideas (plus a bonus)
- •Preview of topics: pre-mortems, time leverage, work levels, execution diagnosis, prioritization
- 4:44 – 12:16
From Mumbai to the U.S.: early influences and finding product management
Shreyas shares his upbringing in Mumbai, his parents’ influence, and early career aspirations (including a French detour). He traces the transition from computer engineering and a brief PhD attempt to engineering roles that gradually pulled him into PM work.
- •Family business exposure shaped practical thinking about packaging/marketing/pricing
- •Dropped out of a CS PhD quickly; entered startups during a tough job market
- •Got “accidental PM” exposure via customer meetings and problem-solving
- •Realized he’d be a strong but not elite engineer; chose PM as a better fit
- 12:16 – 14:22
Early career crucible: Loudcloud/Opsware and learning what great teams feel like
Shreyas recounts joining the Loudcloud side post-split and unexpectedly managing a vendor relationship with Opsware. The standout lesson was experiencing a high-caliber, high-energy team early in his career—and how that standard stays with you.
- •Worked in a startup team inside a larger org (post-acquisition dynamics)
- •Learned by doing: managing vendor relationships in his early 20s
- •Observed leadership and strong talent density up close
- •“Team magic” comes from energy + collaboration + capability
- 14:22 – 27:17
Rapid-fire lessons from Yahoo, Google, Twitter, and Stripe (plus founder takeaways)
Shreyas distills what each company taught him: identity bundling at Yahoo, thinking big at Google, network effects + differentiation at Twitter, and “small teams + low ego + sound judgment” at Stripe. He also highlights founder/CEO traits—from Larry Page’s strategic foresight to Jack Dorsey’s question-asking and Stripe’s marketing and clarity strengths.
- •Yahoo: power (and pain) of unifying services under one account
- •Google: default to huge opportunities; benefits and blind spots of high bars
- •Twitter: stickiness when network effects combine with unique differentiation
- •Stripe: small teams + high energy + low ego can create “magic”
- •Founder lessons: Larry’s future-simulation, Jack’s user-love question, John’s marketing instincts, Patrick’s clarity
- 27:17 – 33:43
Pre-mortems: preventing ugly postmortems by imagining failure early
Shreyas explains the pre-mortem ritual: assume the project failed and work backward to uncover what caused it. He emphasizes why it works—especially psychological safety—and introduces a shared vocabulary that makes risk discussion normal rather than “negative.”
- •Pre-mortem prompt: “Imagine this failed—what went wrong?”
- •Goal: surface risks before they become costly failures
- •Psychological safety increases because pessimism is explicitly invited
- •Framework vocabulary: tiger (real threat), paper tiger (false alarm), elephant (unspoken concern)
- 33:43 – 39:20
How to run a pre-mortem: attendees, structure, voting, and action plans
Shreyas gets tactical on execution: include every relevant function and split sessions for big launches (engineering vs. go-to-market). He advocates alternating quiet writing with discussion, then “voting” on the scariest risks and producing a prioritized mitigation plan the leader owns.
- •Invite cross-functional stakeholders; sometimes run two pre-mortems (eng + GTM)
- •Use quiet time to collect risks privately before group sharing
- •Add a voting step: each person flags the scariest tiger someone else raised
- •Leader synthesizes outputs into a prioritized action plan and follows through
- •Pre-mortems are low-cost, high-upside compared with reactive damage control
- 39:20 – 47:49
LNO framework: classifying PM work into leveraged, neutral, and overhead
Shreyas shares how early PM years at Google were overwhelmed until he adopted LNO: Leveraged tasks (10–100x impact), Neutral tasks (~1x), and Overhead tasks (<1x). The core shift is to stop treating all tasks equally and deliberately reserve prime energy for leveraged work.
- •Leveraged tasks produce outsized impact; they’re rare and deserve your best time
- •Neutral tasks return roughly what you put in
- •Overhead tasks should be minimized and de-perfectionized
- •Same activity can be L/N/O depending on context (bug reports, note-taking, etc.)
- 47:49 – 53:20
Beating procrastination on high-leverage work: placebo productivity + change of location
They explore why leveraged tasks are often the ones we avoid—fear, ambiguity, and the need for deep focus. Shreyas offers two practical tactics: use “placebo productivity” as a ramp and physically change where you work to trigger focus and momentum.
- •You often already know your L-tasks—the ones you feel guilty not doing
- •Procrastination is frequently fear of not having something smart to say
- •Tactic 1: intentionally do N/O “placebo” tasks, then pivot to the L-task
- •Tactic 2: change location to break patterns and force focused execution
- 53:20 – 1:03:43
Three levels of product work: impact, execution, and optics (and why teams conflict)
Shreyas introduces a simple model that explains many stakeholder clashes: people default to different levels (impact vs. execution vs. optics). A CEO may evaluate a plan through brand/customer impact while a PM defends execution constraints—creating tension unless the level mismatch is named and addressed.
- •Impact: customer and business outcomes (often leaders/founders default here)
- •Execution: milestones, tradeoffs, getting things shipped (PMs often default here)
- •Optics: creating awareness of work/results; useful but risky if it becomes the goal
- •Conflicts often come from level mismatch, not bad intent or poor logic
- 1:03:43 – 1:13:13
Diagnosing “execution problems” that are really strategy, culture, or interpersonal issues
Shreyas argues that in high-performing orgs, recurring execution pain is often a symptom of deeper causes. He uses team misalignment to show how leaders can mistakenly “solve” with more process, when the real fix is clarifying strategy, addressing cultural incentives, or coaching interpersonal friction.
- •True execution issues exist (infra limits, skill gaps), but many are misdiagnosed
- •Band-aid fixes (new meetings/process) often mask missing strategy and priorities
- •Culture traps: teams optimize for local OKRs and won’t help others without penalty
- •Interpersonal friction between managers can be the real root cause
- •Heuristic: if the band-aid keeps falling off, it’s probably not execution
- 1:13:13 – 1:21:24
Prioritization pitfall: why ROI thinking leads to quick wins (and missed futures)
Shreyas critiques ROI-first prioritization for high-leverage roles: it incentivizes shrinking the denominator (time) and over-selecting “quick wins.” He reframes prioritization as minimizing opportunity cost—choosing the best use of time, not merely a good use.
- •High-leverage roles have endless positive-ROI options—most still shouldn’t be done
- •ROI framing nudges teams toward low-hanging fruit and short tasks
- •Opportunity cost mindset asks: “Is this the best use of time?”
- •Common planning failure: pick 5 sure small wins, ignore 2 ambiguous potential game-changers
- 1:21:24 – 1:31:21
Applying opportunity-cost thinking: percent allocations + the bonus lesson on high agency
Shreyas recommends avoiding fake precision in opportunity-cost calculations; instead, create planning constraints that force exploration of big bets (e.g., 60/30/10 allocations). He closes with “high agency” as the bonus idea—ownership, creative execution, and resilience as key differentiators for standout PMs.
- •Don’t quantify opportunity cost; give teams permission and space to pursue it
- •Use allocation guidance (inspired by Google 70/20/10) to ensure room for big bets
- •Example allocation: incrementals vs. new initiatives vs. stability/infrastructure
- •High agency = ownership mindset + creative execution + resilience under constraints
- •Wrap-up: where to follow Shreyas and what he’s working on
