🧭Write a Product Strategy in 1 Day / 1 Week / 1 Month
Three depths of strategy. Pick the right one for the decision you're trying to make.
Most PMs either over-engineer their strategy docs (3-month exercises that nobody reads) or skip strategy entirely (and ship reactive features). The right move is to match the depth of the strategy to the decision at hand.
A 1-day strategy is a one-pager that aligns a team for a quarter. A 1-week strategy is a 5-pager that aligns a department for 6 months. A 1-month strategy is the annual vision that aligns the company. Use the lightest level that resolves the question; expand only when stakes demand it.
The three depths
1-Day Strategy (one-pager)
For: aligning a team for a quarter, evaluating a single bet, reframing a roadmap conversation.
Sections (in order):
- Where we are. One paragraph on the current state — metrics, customer feedback, what's working/not.
- Where we're going. One paragraph: the outcome you want in 90 days.
- The bet. What you're going to do, in 3 bullets.
- What we're explicitly NOT doing. Equal length. Forces the trade-off.
- Success metric. One number.
- First two weeks. What ships first.
That's it. You can draft in 4 hours, polish in 2 more, ship same day.
1-Week Strategy (5-pager)
For: setting direction for a department for 6 months, justifying a major investment.
Adds to the 1-day:
- Market analysis. What's happening in your competitive landscape, customer trends.
- Strategic options considered. What we evaluated and why we picked this one.
- Operating model implications. Team structure, hiring, dependencies.
- Risk and mitigation. What could go wrong.
- Quarter-by-quarter milestones.
1-Month Strategy (20-pager, annual vision)
For: annual planning, board reviews, multi-year strategic shifts, CEO-level conversations.
Adds further:
- Long-term vision narrative. Where the product is in 3-5 years.
- Detailed customer/market segmentation.
- Build/buy/partner analysis.
- Financial projections and unit economics.
- Org design implications.
The cardinal rule: write the shortest version that resolves the question
Most PMs write 1-month docs for 1-day decisions. The doc is impressive; the team doesn't read it; the decision gets made on the fly anyway. Wasted week.
The senior move: ask "what decision needs to be made and who needs to be aligned?" If it's the team for a quarter, write the 1-day. If it's the CEO for a year, write the 1-month. Match depth to stakes.
What every strategy doc needs
Regardless of depth:
- A point of view. Strategy is a choice. If your doc could describe any company in your space, it's not a strategy.
- An explicit trade-off. What you're NOT doing is half the value.
- A measurable outcome. Otherwise you can't tell if the strategy worked.
- A theory of why. Why this bet will work; what has to be true.
The writing pattern
Strategy docs are written in 3 passes:
- Brain dump. Get all your thinking on the page, ugly.
- Structure. Move things into sections, cut anything not in service of the argument.
- Sharpen. Every sentence earns its place. Cut 30% of the words.
The last pass is where great strategy docs are made.
Key frameworks
Vision → Strategy → Roadmap → Execution. Each layer informs the next; the strategy doc lives in the middle.
Roger Martin's classic. Forces explicit choices about market and competitive advantage.
Real-world examples
Stripe is famously memo-driven. Strategy docs circulate widely, get debated in writing, and shape product decisions for years. The discipline of writing forces clarity that PowerPoint hides.
Go deeper — recommended reading
Interview questions (1)
Q1Walk me through how you'd write a product strategy for a team you've just inherited.strategysenior▼
Five-step plan over ~3 weeks:
- Listening tour (week 1). 20 customer interviews, 10 internal stakeholder interviews (sales, support, engineering, design, leadership), data deep-dive.
- Synthesize patterns (week 2 first half). What's broken? Where's the leverage? What does leadership want? What do customers actually need? Triangulate.
- Draft the 1-day strategy (week 2 second half). Where we are, where we're going, the bet, what we're NOT doing, success metric. One page.
- Pressure-test with team and stakeholders. Iterate based on what breaks.
- Commit and execute. Reference weekly. Update quarterly.
The output should be sharp enough that an engineer can build from it, a CEO can quote from it, and a salesperson can pitch it. If it can't do all three, it's not done.