strategy-sprint

Strategy Sprint: Write Strategy in 1 Day / 1 Week / 1 Month

When to use: When you need to create or update product strategy quickly, align stakeholders, or prepare for planning cycles

Framework source: Aakash Gupta's "How to Write a Product Strategy in 1 Day/Week/Month"

Quick Start

1. Tell me: "I need a [1-day / 1-week / 1-month] strategy for [topic]"
2. I will check thoughts/shared/pm/frameworks/ and thoughts/shared/pm/context/business-info-template.md for existing context
3. I will ask 3-5 clarifying questions about scope, stakeholders, and constraints
4. We build progressively -- even a 1-month sprint starts with the 1-day foundation first
5. Output goes to thoughts/shared/product/strategy/strategy-[topic]-[date].md

Which tier should you pick?

• 1-Day: You need a quick strategic POV for a specific question. An exec asked for direction, a new opportunity appeared, or you need to align the team before deeper work. Output: 1-page doc.
• 1-Week: You are building a full strategic plan for a new initiative, quarterly planning, or cross-functional buy-in. Includes research, validation, and rollout planning. Output: 3-5 page doc with research backing.
• 1-Month: You are defining annual/quarterly strategy for the entire product, planning a major pivot, launching a new business line, or preparing for board-level decisions. Includes financial modeling, competitive analysis, and full stakeholder socialization. Output: 10-15 page comprehensive strategy doc.

Tier Escalation Triggers

Sometimes you start at one tier and realize you need a bigger sprint. Here's when to escalate:

1-Day → 1-Week Escalation: Escalate when any of these appear during your 1-day sprint:

• You discover the problem is not well-defined (you're debating WHAT to solve, not HOW)
• Competitive landscape has shifted significantly and you need fresh research
• Key stakeholders disagree on the strategic direction (not just the tactic)
• The "snap strategy" keeps changing scope as you work -- sign of insufficient framing

1-Week → 1-Month Escalation: Escalate when any of these appear during your 1-week sprint:

• The strategy requires cross-functional alignment that can't happen in a week (e.g., pricing changes, platform shifts)
• You need primary research (user interviews, market data) that takes time to collect
• The strategy touches 3+ product areas and each needs its own analysis
• Leadership wants a Board-level strategy document, not an internal working doc

How to escalate gracefully:

1. Don't restart -- use what you've already produced as input to the higher tier
2. Frame it: "The 1-day sprint surfaced that this is bigger than a tactical fix. Here's what I found so far. I recommend a 1-week sprint starting with [specific question we need to answer]."
3. The 1-day output becomes Day 1 of the 1-week sprint

Overview

Strategy doesn't always need to be a month-long exercise. Depending on your timeline and context, you can create effective strategy in three different timeframes:

• 1 Day: Snap strategy for quick alignment
• 1 Week: Iteration with design sprints and validation
• 1 Month: Full socialization with all stakeholders

The Framework

1-Day Strategy (Snap Strategy)

Use when:

• New opportunity emerges suddenly
• Executive asks for quick direction
• Need to align team before deeper work

What to include:

1. Problem/Opportunity (2-3 sentences)
2. What's the core issue or opportunity?
3. Why does it matter now?

1. Target Customer (1 paragraph)
2. Who are we solving this for?
3. What's their current pain?

1. Hypothesis (1 sentence)
2. If we build X, then Y will happen because Z

1. Success Metric (1 metric + target)
2. What number moves if this works?
3. Example: "Increase activation from 45% to 60%"

1. Key Risks (3 bullets)
2. What could prevent success?
3. What assumptions are we making?

1. Next Steps (3 action items with owners)

Time investment: 4-6 hours Output: 1-page doc that gets everyone pointed in the same direction

1-Week Strategy (Iteration Strategy)

Use when:

• Quarterly planning cycle
• New product area exploration
• Need cross-functional buy-in

Build on 1-day foundation with:

1. Jobs-to-Be-Done Analysis
2. What job is the customer hiring our product to do?
3. What progress are they trying to make?
4. Reference: [[jtbd-canvas]]

1. Competitive Positioning
2. How do we differentiate?
3. What's our unfair advantage?
4. Reference: [[7-powers-framework]]

1. User Research Validation
2. 5-10 customer interviews
3. Survey existing users
4. Review support tickets and feedback

1. Technical Feasibility Check
2. Sync with engineering leads
3. Identify major technical risks
4. Get rough effort estimates

1. Success Criteria (expanded)
2. Primary metric + 3-5 guardrail metrics
3. Leading indicators to track early
4. Definition of "good enough" to ship

1. Rollout Plan
2. Phased approach or big bang?
3. Beta testing strategy
4. Kill criteria (when to stop)

Daily Breakdown (1-Week Sprint):

| Day | Focus | Deliverable | Hours | | ------------- | --------------------------- | --------------------------------------------------------------------------------------------------------- | ------- | | Monday | Foundation + Research Setup | 1-day snap strategy draft; schedule 5-8 interviews; pull support tickets and NPS data | 5-6 hrs | | Tuesday | Customer Research | Conduct 3-5 interviews; review survey data and support themes; draft JTBD canvas | 5-6 hrs | | Wednesday | Competitive + Technical | Competitive positioning analysis; engineering feasibility sync; identify top 3 technical risks | 4-5 hrs | | Thursday | Synthesis + Strategy Draft | Combine research into strategy doc; define success criteria and guardrails; draft rollout plan | 5-6 hrs | | Friday | Review + Finalize | Get feedback from 2-3 key stakeholders; incorporate feedback; finalize 3-5 page doc with clear next steps | 3-4 hrs |

End-of-week deliverable: 3-5 page strategy doc with JTBD analysis, competitive positioning, success metrics, and rollout plan.

Time investment: 20-30 hours across 5 days Output: 3-5 page doc with research backing

1-Month Strategy (Full Socialization)

Use when:

• Annual planning
• Major product pivot
• New business line
• Board-level strategic decisions

Build on 1-week foundation with:

1. Market Analysis
2. TAM/SAM/SOM sizing
3. Market trends and forces
4. Competitor deep dives (3-5 players)
5. Reference: /competitor-analysis

1. Strategic Fit
2. How does this ladder up to company vision?
3. Resource allocation tradeoffs
4. What are we NOT doing as a result?

1. 7 Powers Analysis
2. Which power(s) does this unlock?
3. Network effects, brand, scale, switching costs?
4. Reference: [[7-powers-framework]]

1. Financial Model
2. Revenue projections
3. Cost to build and maintain
4. Payback period and ROI

1. Org & Resourcing Plan
2. Team structure needed
3. Hiring requirements
4. Dependencies on other teams

1. Risk Mitigation
2. For each major risk, what's the mitigation plan?
3. What experiments can de-risk early?

1. Roadmap (6-12 months)
2. Phased milestones
3. Key decision points
4. Go/no-go criteria at each phase

1. Stakeholder Alignment Sessions
2. Engineering review
3. Design review
4. Executive review
5. Sales/CS input (if relevant)
6. Legal/compliance check

Weekly Breakdown (1-Month Sprint):

| Week | Theme | Key Activities