Present-Forward Product Strategy Playbook (Small-s)
A repeatable five-phase, 8–12 week process to turn scattered inputs into three focused strategic pillars.
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 95%
Chandra Janakiraman's operator playbook for building a problem-focused product strategy that sits between mission/vision and the roadmap and typically covers a two-year horizon. It runs as five sequential phases — preparation, strategy sprint, design sprint, document writing, rollout — executed by a small cross-functional working group so alignment is built in rather than bolted on. The goal is a defensible strategy of a handful of focus areas, an explicit list of what you are NOT doing, and the reasoning why.
Origin
Janakiraman's own synthesis, packaged as an 'operator's interpretation' of established strategy canon: Rumelt's Good Strategy Bad Strategy, Lafley & Roger Martin's Playing to Win, Michael Porter, and Sun Tzu's Art of War. Sparked by a founder-CEO at Headspace telling him 'a lot of people don't really understand why we are working on what we are working on.' Refined across five to six runs, including several at Meta.
Core principles
- 01Strategy sits between mission/vision and the plan; it forces choice to deploy scarce resources for maximum impact.
- 02A strategy has exactly three components: a handful of focus areas (strategic pillars), the areas explicitly NOT in focus, and the why.
- 03Output quality is determined by input quality — front-load the work into preparation.
- 04The strategy is authored by the working group, not the PM; work that 'comes from you' is far easier to accept.
- 05A strategy has no value sitting in a doc — it only accrues value when tested through execution.
How to run it
- 1
Preparation (≈4 weeks)
Form a strategy working group — at minimum engineering, product, design and data — and run a kickoff. Assign six parallel deliverables: a meta-analysis of behavioral/data insights, a meta-analysis of UXR insights, leadership interviews, competitive analysis, adjacent team roadmaps, and firsthand user observation. Compile everything into one master 'preparation readout' deck.
Pro tip This is not full-time work — it runs alongside day jobs over ~4 weeks. As a leader, start gathering inputs before a strategy is even asked for.
Watch out Don't share the preparation deck outside the working group yet; it is an input to the next phase, not the strategy.
- 2
Strategy Sprint (≈1 week / 3–5 days)
Day 1 is a share-out so everyone reaches shared understanding while noting problems. Day 2 (the single most important day) generates every problem, clusters them into 10–15 related groups, flips each cluster from a problem into an opportunity framing, then down-selects to three pillars using a four-criteria ranking. After a rest, Day 3 creates the winning aspiration. Finish by translating pillars into a few 'how might we' questions.
Pro tip Day 2 is mentally brutal — deliberately give the team a break before the Day 3 creative work.
Watch out Don't reopen the three pillars later on a hunch; only revisit them if someone challenges the ranking criteria themselves.
- 3
Design Sprint (≈1 week)
Hand the three pillars and their 'how might we' questions to the design lead (PM takes a backseat). Generate illustrative concepts that bring each pillar to life visually — a picture is worth a thousand words. Optionally test with users.
Pro tip Emphasize input and output: input is the strategic pillars, output is illustrative concepts per pillar — nothing else.
Watch out The goal is NOT feature-ready designs or a feature list — it is generative concepts that make the strategy tangible.
- 4
Document Writing (≈1–2 weeks)
The PM solo-writes a tight 3–4 page strategy doc: context/leadership goals, key insights and analysis, the three strategic pillars with the why, the winning aspiration, and embedded illustrative concepts. Put the full Day-2 scoring table (with criteria) in the appendix, and end with alignment questions.
Pro tip You are not starting from scratch — you have insights, pillars, how-might-we's, aspiration and concepts already. The job is connecting, editing and weaving one cohesive story.
Watch out Do NOT include a roadmap in the strategy doc — the strategy is a companion to the roadmap, kept separate. An illustrative roadmap can go in the appendix at most.
- 5
Rollout (≈2–3 weeks)
Pre-flight one-on-one with two or three 'gatekeepers' whose blessing is mandatory. Then brief the wider key stakeholders async or in a group. Finally run team road shows of ~8–10 people so questions feel comfortable.
Pro tip Keep your own manager lightly in sync throughout (interview them in prep, pre-flight the pillars on Day 2) so they can champion you in the big meetings.
Watch out The purpose of rollout is to LAND the strategy, not to reopen it for feedback — clarify freely, but defend the three pillars using the criteria.
In the wild
As a new VP of Product, Janakiraman had metrics and a buttoned-up roadmap, but the founder-CEO told him people didn't understand why they were building what they were building. Working with a product-savvy board member, he built Headspace's first written product strategy.
→ A complete reimagination into 'Next Generation Headspace' — a personalized health-and-wellness service beyond meditation — that put the company on a new trajectory and led to his promotion to Headspace's first CPO.
He stood up product-growth strategies for two Reality Labs teams (Oculus Quest 2 and Portal) using this exact process, landing nearly identical strategic pillars for both.
→ About 18 months in, outcomes diverged completely: Oculus succeeded and graduated into the VR division, while Portal didn't move the needle and was sunset — proof that identical strategy only earns value through execution.
Common mistakes
Underestimating how long it takes
People assume they can stand up a strategy in a couple of weeks; through iteration it almost always takes 8–12 weeks. Set that expectation up front and justify the ROI against the ~2-year payback.
The PM writing the strategy alone
A doc that 'this PM went off and wrote' invites disagreement. Because the working-group leads and leadership inputs are baked in, the strategy is team-representative and survives rollout.
Skipping leadership pre-alignment
Building a strategy without first asking leaders what success looks like leads to the 'fruit story' — repeatedly presenting mangoes, apples and bananas to a reviewer who rejects each in turn.
Is it for you?
Best for
A product manager at a growth-stage company (or leading a vertical inside a larger company) who has been told they are weak at strategy and needs a reliable, alignment-heavy process.
Not ideal for
Massive multi-product company-wide strategy, pure blue-sky/aspirational bets (use the Big-s future-backward process), or situations demanding a strategy in days.
From the transcript
“it forces choice to deploy scarce resources to generate Maximum Impact”
“the first is a handful of areas to focus on and I call these strategic pillars and then a whole bunch of areas that are…”
“there's the preparation phase there's a strategy Sprint the design Sprint the document writing and the rollup”
“it typically consists of engineering product design and data at a minimum”
“the goal of the design Sprint is not to sort of come up with oh these are the features we should build that's not the…”
“it's important not to include like a road map as part of a strategy doc because a strategy Doc is meant to be separate from…”
“I would start with you know what I call Gatekeepers and these are people who are like absolutely like you have to get their one-on-one…”
“any strategy is only as good as the results it can produce and so one has to have the intellectual honesty and the humility and…”
From the episode
An operator’s guide to product strategy
Chandra Janakiraman (CPO at VRChat, ex-Meta, Headspace, Zyng