name: pivot-decision
description: Documents a strategic pivot or persevere decision with the evidence, analysis, and rationale. Use when evaluating whether to change direction on a product, feature, or strategy based on market feedback.
license: Apache-2.0
metadata:
category: reflection
frameworks: [triple-diamond, lean-startup, design-thinking]
author: product-on-purpose
version: "1.0.0"
Pivot Decision
A pivot decision document captures the analysis and rationale behind a strategic direction change—or the decision to stay the course. Based on the Lean Startup concept of "pivot or persevere," this artifact ensures major strategic decisions are made with evidence, communicated clearly, and preserved for organizational learning.
When to Use
- After significant validated learning suggests the current direction may not work
- At planned pivot-or-persevere checkpoints (e.g., after MVP launch)
- When key hypotheses have been invalidated by market feedback
- During strategy reviews when considering major direction changes
- When stakeholders are debating whether to change course
Instructions
When asked to document a pivot decision, follow these steps:
Summarize Current State
Document what you're currently doing, how long you've been doing it, what you've invested, and what results you've achieved. This grounds the decision in reality.
Present the Evidence
Compile all relevant data: metrics, user feedback, experiment results, market signals. Be comprehensive—include evidence that supports both staying and changing course.
Review Hypotheses
Revisit the original hypotheses that justified the current direction. Which have been validated? Which have been invalidated? Which remain untested?
Define Options
Articulate at least three options: persevere (continue current direction), and two or more distinct pivot options. Describe each option concretely—what would change?
Analyze Each Option
Evaluate options against key criteria: market opportunity, competitive advantage, team capability, resource requirements, and risk. Use evidence, not opinions.
Make the Decision
State the chosen direction clearly. Explain the rationale, acknowledging trade-offs. If the team disagrees, capture dissenting views.
Plan Implementation
Outline what happens next: immediate actions, resource needs, success criteria for the new direction, and communication plan.
Output Format
Use the template in references/TEMPLATE.md to structure the output.
Quality Checklist
Before finalizing, verify:
Examples
See references/EXAMPLE.md for a completed example.
1---2name: pivot-decision3description: <!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->4---5
6<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
7---
8name: pivot-decision
9description: Documents a strategic pivot or persevere decision with the evidence, analysis, and rationale. Use when evaluating whether to change direction on a product, feature, or strategy based on market feedback.
10license: Apache-2.0
11metadata:
12 category: reflection
13 frameworks: [triple-diamond, lean-startup, design-thinking]
14 author: product-on-purpose
15 version: "1.0.0"
16---
17
18# Pivot Decision
19
20A pivot decision document captures the analysis and rationale behind a strategic direction change—or the decision to stay the course. Based on the Lean Startup concept of "pivot or persevere," this artifact ensures major strategic decisions are made with evidence, communicated clearly, and preserved for organizational learning.
21
22## When to Use
23
24- After significant validated learning suggests the current direction may not work
25- At planned pivot-or-persevere checkpoints (e.g., after MVP launch)
26- When key hypotheses have been invalidated by market feedback
27- During strategy reviews when considering major direction changes
28- When stakeholders are debating whether to change course
29
30## Instructions
31
32When asked to document a pivot decision, follow these steps:
33
341. **Summarize Current State**
35 Document what you're currently doing, how long you've been doing it, what you've invested, and what results you've achieved. This grounds the decision in reality.
36
372. **Present the Evidence**
38 Compile all relevant data: metrics, user feedback, experiment results, market signals. Be comprehensive—include evidence that supports both staying and changing course.
39
403. **Review Hypotheses**
41 Revisit the original hypotheses that justified the current direction. Which have been validated? Which have been invalidated? Which remain untested?
42
434. **Define Options**
44 Articulate at least three options: persevere (continue current direction), and two or more distinct pivot options. Describe each option concretely—what would change?
45
465. **Analyze Each Option**
47 Evaluate options against key criteria: market opportunity, competitive advantage, team capability, resource requirements, and risk. Use evidence, not opinions.
48
496. **Make the Decision**
50 State the chosen direction clearly. Explain the rationale, acknowledging trade-offs. If the team disagrees, capture dissenting views.
51
527. **Plan Implementation**
53 Outline what happens next: immediate actions, resource needs, success criteria for the new direction, and communication plan.
54
55## Output Format
56
57Use the template in `references/TEMPLATE.md` to structure the output.
58
59## Quality Checklist
60
61Before finalizing, verify:
62
63- [ ] Current state includes honest assessment of results
64- [ ] Evidence is comprehensive, not cherry-picked
65- [ ] Multiple options are analyzed fairly
66- [ ] Decision rationale is clear and evidence-based
67- [ ] Implementation plan is actionable
68- [ ] Dissenting views are captured
69
70## Examples
71
72See `references/EXAMPLE.md` for a completed example.
majiayu000