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.
At a glance
WHAT IT’S REALLY ABOUT
Operator’s five-step playbook demystifies product strategy and execution
- Chandra Janakiraman lays out an “operator’s guide” to product strategy, turning classic strategy theory into a concrete, repeatable five-step process any product team can run in 8–12 weeks.
- He distinguishes between “small‑S” present‑forward strategy (2‑year horizon, problem-focused) and “Big‑S” future‑back strategy (5–10 year horizon, aspirational), and shows how both should feed a single roadmap.
- The small‑S process centers on a cross‑functional strategy working group that gathers inputs, clusters problems into opportunities, selects three strategic pillars, visualizes them through a design sprint, and encodes everything into a concise strategy document and rollout.
- Chandra illustrates the approach with examples from Zynga, Meta, Headspace, and VRChat, emphasizes that strategy is only valuable when tested via execution, and explores how AI can support research, mock strategies, and eventually multi‑agent strategic systems.
IDEAS WORTH REMEMBERING
5 ideasTreat strategy as the bridge between vision and roadmap, not as a roadmap itself.
Product strategy should sit between mission/vision and the plan, forcing explicit choices about where to focus scarce resources, rather than becoming a feature list or release schedule.
Use a structured, five-phase process to build strategy in 8–12 weeks.
Chandra’s small‑S process—Preparation, Strategy Sprint, Design Sprint, Document Writing, Rollout—gives teams a realistic quarter-long cadence to gather inputs, make hard choices, and codify strategy that can guide 1–2 years of work.
Anchor strategy in a cross‑functional working group to build true alignment.
By involving engineering, product, design, and data (plus PMM/UXR where possible) in research, problem clustering, and pillar selection, the strategy feels owned by the team and leadership rather than handed down by one PM.
Select a few strategic pillars by systematically scoring problem clusters.
After clustering problems into 10–15 themes and reframing them as opportunities, the team ranks them on expected impact, certainty of impact, clarity of levers, and uniqueness, then down‑selects to roughly three pillars—and explicitly notes what they will *not* do.
Complement problem-focused “small‑S” with aspirational “Big‑S” futures.
Big‑S work starts from mission, long‑term trends, and leadership interviews to create distinct 5–10 year futures, prototype them like concept cars, test them with users, and feed the winning components back into the live product and roadmap.
WORDS WORTH SAVING
5 quotesIt was almost as if there was a strategy gene that you needed to be born with to be good at it—and that bothered me a lot.
— Chandra Janakiraman
Strategy sits between the mission and vision and the plan. It forces choice to deploy scarce resources to generate maximum impact.
— Chandra Janakiraman
The core of strategy is really picking those areas you will focus on and the areas you are not going to invest in.
— Chandra Janakiraman
Intrinsically, strategy has no business value. It starts accumulating value as you generate business impact and results.
— Chandra Janakiraman
We may be wrong, but we’re not confused.
— Tomer Cohen (quoted by Lenny Rachitsky)
High quality AI-generated summary created from speaker-labeled transcript.
Get more out of YouTube videos.
High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.
Add to Chrome