Why this matters
Validation without a decision is procrastination with extra steps. This is where you sit down with the evidence, interviews, smoke test, solution feedback, commitments, and choose: build, pivot, or kill. Deciding explicitly, against pre-set criteria, is what protects you from the two classic deaths: building on hope, and researching forever.
What "done" looks like
- The evidence summarized on one page: pain pattern, conversion vs. threshold, solution-fit notes, commitments collected
- A decision made, GO / PIVOT / KILL, against the thresholds you set earlier
- The reasoning written down (your future self will re-litigate this)
- If GO: the MVP scope and first 10 customers named. If PIVOT: which assumption changes. If KILL: what you learned, archived
How to do it
- Assemble the scorecard: problem validation (how many described the pain unprompted?), demand (conversion vs. pre-set line), solution fit (behaviors, not compliments), commitment (pre-orders/LOIs vs. asks).
- Apply the honest pattern: strong on all four → GO. Strong pain, weak solution fit → pivot the solution. Weak pain everywhere → pivot segment or kill. Mixed → name the ONE uncertainty and run one more focused test, with a deadline.
- Have the meeting (with cofounders, or a trusted skeptic if solo) and decide out loud.
- Write the memo, one page: evidence, decision, reasoning, next milestone.
- Act within a week. A GO that doesn't start building, or a KILL that keeps lingering, is not a decision.
Common mistakes
- Letting sunk cost vote ("we've come this far")
- The eternal "one more test" loop with no deadline
- Killing quietly without extracting the lessons that made the next idea better
Real-world examples
- Slack grew out of Tiny Speck's failed online game Glitch, when the game didn't work, the team recognized the internal chat tool they'd built was more valuable than the product they set out to make, and pivoted rather than persevering.
- Instagram started as Burbn, a cluttered check-in app; the founders cut nearly every feature except photo sharing once they saw that was where users actually engaged. Killing the original scope was the decision that made the company.
- The persevere / pivot / kill framework is central to Lean Startup thinking: the discipline is letting pre-agreed evidence drive the call, not sunk cost, which is exactly why it helps to validate the problem and measure conversion before you're emotionally committed to an answer.
From a founder's point of view
This is the decision founders most want to skip, because all three options feel like admitting something. But refusing to decide is itself a decision, usually the expensive one where you drift for another six months. The healthiest version treats "kill it" and "pivot" as normal, respectable outcomes, not failures, and judges the idea against the threshold you set earlier rather than the effort you've already spent.
Rule of thumb
If you would not start this project today, knowing what you now know, that is your answer. The memo just makes you say it out loud.