The output should make the tradeoff visible enough for someone else to inspect, challenge, and act on.
loading…
business model & innovation framework
Decide whether evidence supports continuing or pivoting.
quick answer
Pivot or Persevere Decision is a flowchart for Venture validation. It turns the decision into named fields, evidence, and a visible pivot or persevere decision worksheet / visual.
The output should make the tradeoff visible enough for someone else to inspect, challenge, and act on.
Decide whether evidence supports continuing or pivoting.
Use Customer Development Model when its output is closer to the conversation you need: Move through customer discovery, validation, creation and company building.
worked example
A filled example is easier to understand than a blank template. Use it to see the shape before applying the framework to your own case.
A filled example so you can see the shape before applying Pivot or Persevere Decision to your own context.
A filled example so you can see the shape before applying Pivot or Persevere Decision to your own context.
generate yours
Start Ask PL with the framework, required inputs, and your context. It will ask for missing details, render the flowchart, and explain what decision the output should change.
Apply Pivot or Persevere Decision to my situation. Context: [Decision, audience, options, evidence, and constraints.] Use the Pivot or Persevere Decision structure: - Start/end: - steps: - decisions: - flows: Ask only for missing inputs that would change the output. Then render the flowchart and name the decision it should change.
how to use it
Use the framework to change a decision, not to fill a worksheet. Start narrow, add evidence, then inspect what the pivot or persevere decision worksheet / visual makes clearer.
Write the concrete venture validation choice, tradeoff, or conversation the framework should change.
Fill the important slots: Start/end, steps, decisions, flows.
Mark what is measured, what comes from customers, and what is still judgment.
End with the next move, the riskiest assumption, or the evidence that would change the pivot or persevere decision worksheet / visual.
quality check
Use this check after the artifact is filled. Blank fields are not failure; they are the next research question. Look for concrete evidence, missing constraints, and assumptions that would change the next move.
The framework needs a concrete decision. Broad intent turns it into a worksheet, not a decision aid.
Good framework output makes assumptions visible enough for someone else to challenge.
The diagram is useful only if it changes the next product conversation.
common mistakes
Do not use Pivot or Persevere Decision as a worksheet. Name the choice, conversation, or tradeoff the output should change.
Separate measured facts, customer evidence, and leadership judgment so weak assumptions stay visible.
If the diagram does not match the decision, switch frameworks instead of stretching the boxes.
The framework should clarify the next move. It should not replace strategy, sequencing, or judgment.
use something else when
Move through customer discovery, validation, creation and company building.
Run empathize, define, ideate, prototype and test cycles.
Describe how an organization creates, delivers and captures value.
faq
Decide whether evidence supports continuing or pivoting.
Business context; objectives; available evidence; stakeholder judgment
Pivot or Persevere Decision worksheet / visual
Use Pivot or Persevere Decision when the decision matches this job: Decide whether evidence supports continuing or pivoting.
Avoid it when you need Customer Development Model's output instead: Move through customer discovery, validation, creation and company building.
It is both: a structure for thinking and a visible flowchart that makes the decision easier to inspect.
A good input names the real decision, uses concrete evidence, and separates facts from assumptions.
Use the pivot or persevere decision worksheet / visual to choose the next move, name the riskiest assumption, or decide what evidence would change the call.
Use Customer Development Model when the real output you need is closer to: Move through customer discovery, validation, creation and company building.
Yes. Describe your context and Ask PL can ask for missing inputs, render the flowchart, and explain what decision it should change.