Key takeaway
Treat pivot-or-persevere as a question about evidence and runway, not morale. The post recommends persevering only while you have a specific untested hypothesis and the runway to test it, and pivoting when the evidence has gone quiet and the remaining hypotheses are exhausted or untestable within runway.
"Is it working?" is the wrong question, because it rarely is — cleanly — on the day you feel compelled to ask. Here is the worked version: the same seven-section structure YourBrief generates, applied to the pivot-or-persevere call so you can decide it on signal and runway rather than on the mood of a bad week.
The decision
A pivot is close to a one-way door. You spend down runway, team conviction, and investor patience, and you cannot fully return to the abandoned path once the team has moved on. So the decision is not "is this working?" — it is "do we still have a specific hypothesis we have not tested, and the runway to test it, or are we out of both?"
Key questions to answer before deciding
- What was the last real signal — not a vanity metric — that the current path is working, and how recent is it?
- Do you have a specific, testable hypothesis left, or are you iterating on hope?
- How much runway funds how many more genuine experiments?
- Is the problem the market, the execution, or the sequencing — and how would you tell them apart?
- If you pivot, what evidence, audience, or technology from this attempt actually transfers?
Recommended frameworks
Hypothesis-runway accounting. Count the experiments you can still afford: runway divided by cost-per-test. As a rough heuristic, if you can no longer fund even one decisive test with enough margin to act on the result, the decision is already being made for you.
Signal-versus-noise triage. Separate a real demand signal from founder hope and vanity metrics — retention and repeat use are signal; a spike in signups you cannot explain is usually noise.
Market / execution / sequencing diagnosis. Name which one is failing. Wrong market means pivot; wrong execution means fix and persevere; right idea too early is a sequencing call that changes what you do next.
Decision criteria
Persevere only if you have a specific untested hypothesis and the runway to test it. Pivot when the evidence has gone quiet, the remaining hypotheses are exhausted or untestable within runway, and you can name what transfers. Do not pivot on a bad month, and do not persevere on hope alone.
Sources to consult
Your own cohort and retention data (is anyone actually coming back?); direct conversations with the users who churned and the few who stayed; one honest advisor who will tell you it is not working when it is not.
Next steps
List the hypotheses you have not yet tested; compute experiments-left from runway; run the cheapest decisive test now; if the signal is quiet and the list is empty, inventory what transfers and pivot deliberately rather than drift into it.
When to escalate
Escalate to cofounders and board when runway falls below what it takes to fund even one more decisive experiment with margin to act on it, when the team has quietly stopped believing, or when the honest diagnosis is "right idea, wrong time" — a sequencing call that reshapes the entire plan.
The honest answer is almost never "grind harder" or "start over" — it is "run the one test that would settle it, while you can still afford to." Generate this exact brief against your own runway and signal — $1 to start.