Lenny's PodcastChandra Janakiraman: A five-step path to product strategy
Through cross-functional sprints that group problems into pillars; Chandra turns mission-to-roadmap strategy into a repeatable 8-to-12-week run at VRChat.
CHAPTERS
- 0:00 – 10:59
Chandra’s origin story: strategy as the missing “why”
Chandra shares the Headspace moment that sparked his obsession with strategy: a solid roadmap and metrics still left the team unclear on why they were building what they were building. That experience led him to codify a repeatable, teachable approach to product strategy—debunking the idea of a “strategy gene.”
- •At Headspace, leadership feedback revealed weak shared understanding of the roadmap’s rationale
- •A written product strategy helped reimagine Headspace beyond meditation into broader wellness
- •Strategy is often treated as mystical; Chandra set out to make it procedural and accessible
- •The goal: a repeatable playbook that creates alignment and business impact
- 10:59 – 12:36
Who this playbook is for (and what it is not)
Lenny frames the episode as a practical operator’s guide, and Chandra positions his method as a synthesis of proven strategy thinking rather than a new theory. The intended audience is especially product leaders who feel they’re “not strategic” and want a concrete process.
- •An operator’s interpretation of classic strategy sources (Rumelt, Porter, Playing to Win, etc.)
- •Designed to be friendly, repeatable, and alignment-producing
- •Used and iterated multiple times across companies including Meta
- •Targets product practitioners who want a reliable, step-by-step process
- 12:36 – 15:59
Defining product strategy: resonance, choices, and explicit non-goals
Chandra gives a crisp definition: strategy sits between mission/vision and the plan (roadmap) and forces choices about scarce resources. He introduces “resonance” as the metaphor—finding the right frequency where product meets market—plus the importance of stating what you won’t do and why.
- •Strategy bridges mission/vision (purpose) and roadmap (ordered work)
- •Core function: force choices to maximize impact with limited resources
- •Three components: strategic pillars (focus), non-focus areas, and the “why”
- •Resonance metaphor: pick the frequency that creates outsized market impact
- 15:59 – 18:51
The small‑s strategy timeline: an 8–12 week, 5‑phase process
Chandra lays out the end-to-end structure for “small‑s” strategy (typically a 18–24 month horizon). He emphasizes that teams underestimate the time required, and that the ROI is strong because a good strategy can guide years of execution.
- •Small‑s strategy is “present-forward” and problem-focused
- •Five phases: Preparation → Strategy Sprint → Design Sprint → Document Writing → Rollout
- •Time boxes: ~4 weeks prep, ~1 week strategy sprint, ~1 week design sprint, ~1–2 weeks writing, ~2–3 weeks rollout
- •Set expectations early; shortcuts exist but quality typically requires the full cycle
- 18:51 – 21:53
Preparation phase: build the strategy working group and gather inputs
The largest phase is preparation, driven by a cross-functional strategy working group. The team compiles a single “master readout” that synthesizes data, research, leadership context, and market signals—without yet socializing broadly.
- •Form a strategy working group (minimum: Product, Engineering, Design, Data; optionally PMM/UXR)
- •Create meta-analyses of behavioral/data insights and UXR/customer insights
- •Run leadership interviews early to avoid late-stage review surprises
- •Add competitive analysis, adjacent team roadmaps, and user observation to build empathy
- 21:53 – 30:52
Leadership interviews and the ‘fruit’ story: pre-align before reviews
Chandra explains why early leadership interviews prevent painful, unproductive strategy reviews. By learning what success, failure, principles, and “pet ideas” leaders have upfront, teams reduce churn and increase buy-in.
- •The ‘fruit’ parable: don’t bring mangos/apples/bananas without knowing preferences
- •Ask leaders: success/failure definitions, metrics, principles, and favorite ideas
- •Senior leaders usually welcome these conversations; it’s creative and energizing
- •This input becomes a key ingredient in later alignment and rollout
- 30:52 – 40:05
Strategy sprint (days 1–2): from raw problems to top strategic pillars
The strategy sprint is the decision engine. Day 1 is a share-out of prep work; Day 2 turns notes into problem lists, clusters them, reframes them as opportunities, and then ranks to select the top pillars the team will bet on.
- •Day 1: share prep readout; everyone captures problems, blockers, and suboptimal areas
- •Day 2: generate many problems, cluster into ~10–15 themes, then flip to opportunity framing
- •Rank opportunities with criteria: expected impact, certainty/confidence, clarity of levers, differentiation/uniqueness
- •Down-select to ideally three strategic pillars; the rest become explicit non-focus areas
- 40:05 – 48:26
Strategy sprint (day 3): ‘How might we’ + the winning aspiration headline
After selecting pillars, the team translates them into ‘How might we’ questions to seed solution exploration. Then they craft a winning aspiration using a “newspaper headline in two years” exercise that forces plain-speak outcomes and shared ambition.
- •Strategic pillars become 2–3 ‘How might we’ prompts each (fertile problem framing)
- •Winning aspiration exercise: imagine a journalist headline describing success in ~2 years
- •Blend headlines into a single aspiration statement using common themes/word-cloud-like synthesis
- •Outputs: pillars, HMWs, rationale/why, non-focus areas, and winning aspiration
- 48:26 – 51:21
Design sprint: illustrate the strategy with concepts (not a feature list)
A design-led sprint produces illustrative concepts that make the strategy tangible and communicable. The goal isn’t final feature specs, but visuals and prototypes that help stakeholders immediately grasp what the pillars could mean in practice.
- •Led primarily by Design/UX; PM can step back temporarily
- •Input: pillars + HMWs; Output: many illustrative concepts mapped to each pillar
- •Concepts help people ‘see’ the strategy (a picture worth a thousand words)
- •Optionally test rough prototypes with users to sharpen understanding
- 51:21 – 57:58
Writing the strategy doc: a short narrative plus a defensible appendix
The PM writes the document, leveraging the extensive building blocks produced earlier. The main document stays concise (3–4 pages), while the appendix carries the scoring table and supporting evidence to answer ‘why these pillars?’
- •Writing is mostly solo for 1–2 weeks; avoid over-taxing the working group
- •Suggested structure: leadership context → insights (user/data/competitive) → pillars + why → aspiration → alignment questions
- •Include the full prioritization/scoring table in the appendix for defensibility
- •Keep roadmap out of the core strategy doc; at most, add an illustrative version in the appendix
- 57:58 – 1:02:34
Rolling out strategy: gatekeepers, stakeholders, and team roadshows
Rollout is treated as a structured landing process, not an open-ended rewrite cycle. Start with one-on-one alignment with a small set of gatekeepers, then broaden to key stakeholders and finally smaller-group roadshows that invite questions without derailing the core choices.
- •Preflight with 2–3 gatekeepers via 1:1s before broader circulation
- •Engage key stakeholders async or in group reviews
- •Run roadshows (8–10 people) to encourage real Q&A and understanding
- •Balance openness with firmness: clarify and refine language, but don’t easily change pillars
- 1:02:34 – 1:15:55
Why the process works + examples from Zynga and Meta
Chandra explains the benefits: built-in alignment, better thinking via multiple minds, and defensible prioritization criteria. He then shares strategy lessons from Zynga’s encoded pillars and Meta’s contrasting outcomes—highlighting that strategy only has value when tested through execution.
- •Alignment psychology: people accept what they helped create
- •Collaborative work improves problem articulation and pillar quality
- •Defensible criteria make changes and debates grounded and productive
- •Zynga: clear pillars (viral loops, pay-to-complete, cross-promo) reinforced by systems until the market shifted
- •Meta: similar pillars led to different outcomes (Oculus succeeded, Portal didn’t), proving execution is the real test
- 1:15:55 – 1:26:56
Big‑S strategy: future-backward visioning, prototypes, and parallel workstreams
Big‑S strategy complements small‑s by exploring aspirational futures over 5–10 years, often over a longer, more fluid cycle. The work is design/UX-research-led: create multiple distinct futures, build “concept car” prototypes, test for resonance, and feed winning components into real product tests—then merge with small‑s into a single roadmap.
- •Small‑s is present-forward problem solving; Big‑S is aspirational future-backward thinking
- •Groundwork includes cultural/social/competitive/tech trend scanning plus leadership vision interviews
- •Cluster into ~3 distinct future scenarios; prototype them like concept cars
- •Test prototypes with users, synthesize what resonates, then run live product tests
- •At VRChat: PMs lead small‑s while Design leads big‑S in parallel; both merge into one roadmap
- 1:26:56 – 1:47:21
AI’s role in strategy + final recap and lightning round
Chandra outlines where AI already helps (research synthesis and mock strategies) and where it’s headed (multi-agent workflows and generative experimentation). They close with a concise recap of definitions and processes, then a lightning round on books, media, favorite products, and personal mottos.
- •AI can accelerate prep: competitive/review analysis, trend mining, head-to-head comparisons
- •Mock strategies from LLMs are surprisingly good but often too broad—humans must force focus and choice
- •Future: multi-agent systems that iterate strategy/roadmap/engineering constraints; generative variants + advanced experimentation
- •Recap: strategy sits between mission/vision and plan; pillars + non-goals + why; validate through execution
- •Lightning round: favorite books (Disney biography, Creativity Inc., IDEO innovation archetypes), recent watches, products, and craftsmanship mindset
