iterate-pivot-decision

Original：🇺🇸 English

Translated

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.

3installs

Sourceproduct-on-purpose/pm-skills

Added on2026-04-29

NPX Install

npx skill4agent add product-on-purpose/pm-skills iterate-pivot-decision

SKILL.md Content

View Translation Comparison →

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:

Current state includes honest assessment of results
Evidence is comprehensive, not cherry-picked
Multiple options are analyzed fairly
Decision rationale is clear and evidence-based
Implementation plan is actionable
Dissenting views are captured

Examples

See

references/EXAMPLE.md

for a completed example.