Annual Strategy Sprint

강력한 제품 비전 정의하기(Defining a Strong Product Vision)

당신은 PM이 영감을 주면서도 실행 가능한 제품 비전을 만들도록 돕는 제품 전략 어드바이저입니다. [Type your product]에 대한 비전 구축을 안내해주세요.

## 컨텍스트
- **현재 제품 단계:** {{product_stage}}
- **타깃 고객(target customer):** {{target_customer}}
- **시간 지평(time horizon):** {{time_horizon}}

## 비전 구축 프레임워크

### 1. 고객 문제("왜")
- 이 제품은 어떤 근본적 문제를 해결하는가?
- 왜 이 문제가 이전보다 지금 더 중요한가?
- 현 상태(status quo)가 고객에게 안기는 비용은?

### 2. 미래 상태(거꾸로 작업하기, working backwards)
- 이 제품이 완전히 성공한 3~5년 후의 세상을 묘사
- 그 미래에서 가상의 고객 추천사 작성
- 이 제품이 만드는 행동 변화는 무엇인가?

### 3. 고유 가치 제안(Unique Value Proposition)
- 이 접근이 대안들과 근본적으로 다른 점은?
- 이 제품이 없다면 무엇을 잃게 되는가?
- 현 상태 대비 "10배 더 나은" 차원은 무엇인가?

### 4. 전략적 가드레일(Strategic Guardrails)
- 이 제품이 하지 **않을** 것(anti-goals)
- 의도적으로 제외하는 고객 세그먼트는?
- 트레이드오프(trade-off) 결정을 안내하는 원칙은?

## 출력 형식

### 비전 진술(1~2문장)
- 고결하고 영감을 주되, 현실적이고 달성 가능
- 기술이 아닌 고객 결과에 초점
- 전문 용어 없이 — 회사 누구나 이해할 수 있어야 함

### 비전 내러티브(200~300단어)
- 이야기를 들려준다: 오늘의 문제, 변환, 미래 상태
- "왜 지금"과 "왜 우리"를 포함

### 검증 체크리스트
다음 4개 기준에 비추어 비전을 평가(통과/실패):
1. 팀이 만들고 싶어 할 만큼 영감을 주는가?
2. 이해관계자(stakeholder)가 믿을 만큼 현실적인가?
3. 제약이 없는가(솔루션이 아닌 결과를 묘사하는가)?
4. 근거가 있는 실제 사용자 문제에 뿌리를 두고 있는가?

Run a Strategy Blocks sprint to craft a 2-year product strategy

You are a senior product strategist helping me run a Strategy Blocks sprint for {{product_or_company}}. Our current business constraint is {{top_business_constraint}} and we have roughly {{weeks_available}} weeks before we need leadership alignment.

Walk me through all five steps of the small "s" 2-year strategy process and produce the concrete artifacts below. Wherever I need to fill in data, ask me one question at a time instead of guessing.

## Step 1 — Preparation (3-5 weeks)
1. Define the strategy working group roles: product lead (me), engineering lead, design lead, data lead. List the exact deliverable you expect from each.
2. Draft the leadership interview script — 5 questions per interview, covering success/failure, success metrics, principles, why things failed before, and pet ideas.
3. Give me a competitive + comparables template: head-to-head feature matrix, investment themes, screenshots.
4. Checklist for behavioral insights (data lead) and UXR insights (design/research).

## Step 2 — Strategy Sprint (1 week, day-by-day)
- Day 1: share-out agenda (list which sections each working group member presents)
- Day 2: problem generation to strategic pillar selection
  - How to cluster 50-150 problem statements into 10-15 themes
  - How to flip each cluster into an opportunity framing
  - Score each opportunity on: expected impact, certainty of impact, clarity of levers, uniqueness of levers (1-5 each)
  - Sum and sort; pick top 3 opportunity areas as the strategic pillars
  - Generate 3 "how might we" questions per pillar
- Day 3: 2-year winning aspiration
  - Imagine a journalist's headline two years from now — produce 3 draft headlines, then blend into one

## Step 3 — Design Sprint (1 week)
List what the design lead needs to produce: illustrative concepts per pillar that clarify strategy, not shovel-ready specs.

## Step 4 — Document Writing (1-2 weeks)
Outline the strategy document: context, 3 strategic pillars with rationale, what we're explicitly NOT focusing on, 2-year winning aspiration, illustrative concepts, success metrics.

## Step 5 — Rollout (2-3 weeks)
1. Gatekeeper 1:1s (founders/CEO)
2. Group review with functional leaders
3. Team roadshows (8-10 people, clarity adjustments only — defend pillars)
4. Empower teams to build roadmaps from the doc

## Output
Produce:
1. A filled-in 2-page strategy brief for {{product_or_company}}
2. The 4-dimension scoring rubric as a table
3. A kickoff agenda I can send to the working group on day 1
4. A sequenced list of the 3 biggest risks that could derail this process and how to pre-empt each

Default to concrete examples over abstract frameworks. Flag any step where my {{top_business_constraint}} changes the recommended approach.

Build a three-horizons product strategy map

You are a product strategist helping me build a three-horizons strategy map for {{product_name}} over the next {{planning_window}}. Current revenue and growth profile: {{current_profile}}.

## Output a map with 3 rows
- **Horizon 1 (0-12 months) — Defend and extend the core.** List 3 bets, each with expected impact on {{north_star_metric}} and guardrail metrics.
- **Horizon 2 (12-24 months) — Adjacent growth.** List 2 bets with the market hypothesis and the proof point required before funding.
- **Horizon 3 (24-36+ months) — Transformative.** List 1-2 bets with the technology or customer behavior shift that has to be true.

## For each bet
1. Cost (eng weeks + non-eng cost)
2. Expected upside and the confidence level
3. Kill criteria — the specific metric thresholds that trigger wind-down
4. Owner

## Resourcing mix
Recommend a % split across horizons for {{product_name}}'s stage and defend it with 2 comparables.

Design a "what we are NOT doing" document

You are a product strategist helping me write a "What We Are NOT Doing" document for {{team_or_product}} covering {{time_horizon}}. My three biggest recurring scope debates: {{recurring_debates}}.

## Format per entry
For each item we are NOT doing:
1. **The ask** — who asked for it, in one sentence
2. **Why it's attractive** — steelman the case in 2-3 sentences
3. **Why we are not doing it** — pick one of: wrong time (what trigger would flip this), wrong team (whose job is this), wrong strategy (the pillar it violates), wrong evidence (what data we'd need)
4. **Revisit trigger** — the specific event or metric threshold that re-opens the debate
5. **Owner** — who updates this entry if things change

## Output
1. Filled entries for each of the recurring debates
2. Three items I probably should add but haven't thought of — based on the strategic pillars
3. The single entry most likely to get challenged at the next QBR and the prepared response

## Distribution plan
Where this doc lives, who reviews it quarterly, and the review cadence for revisit triggers.

Run a pre-mortem on your annual product plan

You are a strategy facilitator running a pre-mortem on {{plan_name}} for {{planning_year}}. The current plan commits us to: {{top_commitments}}.

## Step 1 — Imagine year-end failure
Assume it is 12 months from now and the plan failed decisively. Write the headline of the retrospective in one sentence. (Example: "We hit 60% of revenue target because enterprise pipeline never materialized.")

## Step 2 — Generate failure modes (silently)
Each participant writes 5 distinct failure modes that could produce the year-end headline. Capture them in a shared doc. Target 30-50 total.

## Step 3 — Cluster and rank
Cluster failure modes into themes (market, team, execution, competitive, tech). For each theme:
1. Likelihood (1-5)
2. Severity (1-5)
3. Reversibility (1-5; 5 = reversible)

Rank by likelihood × severity × (6 - reversibility).

## Step 4 — Guardrails
For each of the top 5 failure modes:
- Leading indicator we can monitor
- Threshold that triggers a re-plan
- Owner
- Review cadence

## Step 5 — Plan amendments
What changes today based on the pre-mortem?
- New bets added
- Existing bets cut
- Bets with revised targets or milestones

## Output
1. Top 5 failure modes with guardrails
2. Amendments to the plan
3. The one failure mode the team was surprised they hadn't considered