How to Run Go, Hold, Stop Decisions Without False Certainty
Phase One decisions carry real consequences. Many organizations either delay decisions until certainty appears, or push initiatives forward based on optimism and momentum. This guide explains how TURN8 runs go/hold/stop decisions in Phase One without pretending certainty exists. The objective is to make timely, defensible calls based on evidence thresholds, learning progress, and controlled downside – not narratives or confidence.
The Core Problem
In early venture work, decision-making usually fails in one of two ways. Decision paralysis: leaders wait for “one more data point,” validation cycles extend repeatedly, and weak initiatives survive by default. Decision by momentum: activity gets mistaken for progress and confidence replaces evidence, because stopping feels politically costly. In GCC organizations this is reinforced by a cultural preference for certainty, hierarchical escalation dynamics, and fear of visible failure. Phase One decisions must be made before certainty exists – delaying decisions does not reduce risk, it increases cost.
What Must Be in Place First
This requires defined venture challenge statements and opportunity areas, Phase One governance with a fixed decision cadence, and predefined evidence requirements. Red flags that mean decisions will drift include decisions being routinely deferred, evidence thresholds shifting over time, and outcomes not being documented.
Separate Confidence From Evidence
Explicitly distinguish what the team believes from what the evidence actually shows. Confidence is allowed in the room, but decisions are not based on it – strong narratives often mask weak evidence.
Anchor Decisions to Predefined Criteria
Use the evidence thresholds defined earlier to frame every decision, asking only: did we meet the criteria, and if not, why? Changing criteria retroactively protects weak initiatives.
Treat "Hold" as a Real Outcome
Use hold only when evidence is genuinely inconclusive, specific conditions can resolve the uncertainty, and a clear time-box is set. “Hold” is not “continue exploring” – misused holds create zombie initiatives with no quiet carryover allowed.
Make Stop Decisions Explicit and Final
When evidence fails, stop decisively – document what was tested, what failed, and why stopping is correct. Ambiguous stops erode governance credibility.
Decide on Go With Conditions, Not Optimism
When deciding “go,” explicitly state what is now believed to be true, what remains uncertain, and what must be proven next. A go without conditions is premature commitment.
Common Failure Modes
Rebranding stops as “pauses,” which leaves initiatives unofficially alive instead of formally closed. Using hold to avoid making an actual stop decision, with vague, open-ended conditions attached. Treating a go decision as full validation and escalating without any guardrails or named next-phase risks.
What Success Looks Like
A well-run decision process produces faster Phase One cycles, fewer initiatives entering build prematurely, and higher confidence at escalation points – because every decision was anchored to evidence that existed before the call was made, not narrative built after it.
Frequently Asked Questions
What does it mean to run a go/hold/stop decision without false certainty?
Making a timely, defensible call based on predefined evidence thresholds rather than waiting for certainty that will never arrive, or pushing an initiative forward on optimism and momentum instead of evidence.
Why do venture decisions often get delayed indefinitely?
A cultural preference for certainty, hierarchical escalation dynamics, and fear of visible failure push leaders to wait for “one more data point” rather than decide – but delaying a decision doesn’t reduce risk, it just increases cost.
What are the five steps to running go/hold/stop decisions well?
Separate confidence from evidence, anchor decisions to predefined criteria, treat hold as a real outcome with explicit time-bound conditions, make stop decisions explicit and final, and decide on go with named conditions rather than optimism.
What's the difference between a real 'hold' and a disguised delay?
A real hold only applies when evidence is genuinely inconclusive, specific conditions could resolve the uncertainty, and a clear time-box is set. If it’s open-ended or used to avoid a stop decision, it’s a disguised delay, not a real hold.
What's the most common failure mode in venture decision-making?
Rebranding a stop as a “pause” – this leaves the initiative unofficially alive instead of formally closed, and quietly erodes the credibility of the entire governance process.
