You don't need more information. You need a decision.
Most advice on decision making under uncertainty tells founders to gather more data, collect more opinions, and compare more models. That's backward. If the core variables are unstable or missing, more input usually adds noise. It increases decision load. It delays commitment. It keeps you in operator mode.
The harder truth is simpler. You're not stuck because you lack information. You're stuck because you haven't chosen the filter that will eliminate options and force a committed move.
Table of Contents
- Your Real Problem Is Not Lack of Information
- Why Common Frameworks Fail Under Uncertainty
- The Decision Filter A Five-Level Protocol
- A Filter in Practice Two Founder Examples
- What This Framework Is Not
- From Uncertainty to Committed Action
Your Real Problem Is Not Lack of Information
A founder faces a live decision with real cost attached. Enter a new market or stay concentrated. Hire senior help or keep the margin. Rebuild the offer or fix the sales process. The data is incomplete, the advice conflicts, and every extra conversation creates another branch.
That usually gets misdiagnosed as an information problem. It isn't. It's a commitment problem.
When people say they need more clarity, they often mean they want permission to avoid loss. So they keep researching. They call that diligence. Most of the time it's drift.
More input can be avoidance
The pattern is common. You tell yourself that one more spreadsheet, one more advisor call, or one more framework will reveal the obvious answer. It rarely does. It just preserves optionality a little longer.
That's why a lot of founders mistake motion for progress. They stay busy around the decision instead of making it. If that sounds familiar, the problem may be closer to what I described in these shadow patterns in decision making.
Practical rule: If the same decision has survived repeated review, the blocker usually isn't missing data. It's unwillingness to eliminate a path.
The upstream issue
Decision making under uncertainty must be handled upstream. Not with a bigger library of mental models. Not with a productivity tool. Not with a team workshop designed to make everyone feel included.
You need a stricter filter. One that narrows the field fast, surfaces the core trade-off, and leaves you with one move you can defend.
A founder acting as an Operator keeps searching for certainty. A founder acting as an Architect accepts that certainty isn't available and commits anyway. That's the job. Not to predict perfectly. To choose cleanly.
Why Common Frameworks Fail Under Uncertainty
Most frameworks fail because they implicitly assume the world is legible. It often isn't.
In standard decision thinking, risk and uncertainty are different. Under risk, the probability distribution is known. Under uncertainty, it isn't. That distinction matters because one allows calculation and the other doesn't, as outlined in this explanation of certainty, uncertainty, and risk.
If you can model the probabilities, you can compute expected values and compare paths with some confidence. If you can't, the decision changes shape. You're not optimizing a forecast. You're dealing with model fragility.
Why founders get trapped
A lot of business advice still treats uncertainty like an incomplete version of risk. It tells you to gather enough data until the answer becomes obvious. That works only when the missing information is recoverable and the environment is stable enough to support the model.
Founders rarely get that luxury. Markets shift. Buyers hesitate for reasons they won't state. A channel works until it doesn't. A partnership looks promising until one person leaves.
When the probabilities are unreliable, more analysis doesn't produce confidence. It produces prettier confusion.
A useful heuristic here is Jeff Bezos's reported 70% certainty rule. Act when you have about 70% of the information you need rather than waiting for 90%, because delay can destroy opportunity, as discussed in that same decision making under uncertainty reference. That's not a law. It's a reminder that speed and information quality trade against each other.
What common frameworks optimize for
They often optimize for the wrong thing:
- Consensus: Good for committees. Bad for founder speed.
- Completeness: Good for reporting. Bad for live decisions.
- Exploration: Good early. Expensive when the primary need is elimination.
The founder's problem isn't lack of frameworks. It's overexposure to them. You don't need more ways to consider. You need one way to cut.
The Decision Filter A Five-Level Protocol
I use one proprietary term here. The Decision Filter. It means a linear protocol that forces elimination until one committed choice remains.
It isn't a menu of models. It's a sequence. You move through it once, in order, and you don't loop back unless a premise breaks. That matters because looping is where overthinking hides.
The roots of this are old. Formal decision theory developed tools such as Bayes' decision rule, decision trees, and minimax regret to replace guesswork with repeatable logic when exact forecasts aren't available, as noted in this decision theory overview.
Level 1 Recognize the Real Decision
Most founders start too wide. They say things like, "We need a growth strategy," or, "I need to figure out the business model."
That's vague enough to support endless thought.
The core decision is narrower. It usually sounds like this:
- Market choice: Stay in the current segment or move upmarket.
- Resource choice: Put cash into distribution or product.
- Structure choice: Keep the current offer or cut it and simplify.
Write the decision as a binary or forced trade-off. If you can't state it cleanly, you aren't deciding yet.
A decision gets easier the moment you stop describing the whole situation and isolate the fork.
Level 2 Map Plausible Scenarios Not Predictions
Once the core decision is clear, stop trying to predict the single best future. Under uncertainty, that's weak practice.
Instead, map a small set of plausible scenarios. Not because you're trying to be exhaustive. Because you need to see which option survives across different conditions.
A simple founder version looks like this:
| Scenario | What changes | What survives |
|---|---|---|
| Demand holds | Current buyers keep buying | Keep exploiting existing channel |
| Demand softens | Conversion slows or timing stretches | Preserve cash and shorten feedback loops |
| New segment responds | New buyer type shows traction | Shift offer and sales motion deliberately |
Use scenarios to test resilience, not intelligence. If one option only works in one favorable future, it isn't strong.
A related method is scenario analysis for founders, but the point here is narrower. You're not building a planning department. You're trying to remove fragile options.
Before moving on, use this brief walkthrough if you want another lens on how structured decisions work in practice.
Level 3 Diagnose Asymmetry and Leverage
Now ask the question most founders skip. Which option has limited downside and meaningful upside if you're even partly right?
Asymmetry holds importance. Some decisions are reversible. Some aren't. Some create learning fast. Others trap resources in place.
Look for three things:
- Reversibility: Can you undo the move without serious damage?
- Learning rate: Will this option reveal useful truth quickly?
- Impact: If it works, does it change the business direction, not just local output?
An option with moderate downside, fast feedback, and meaningful directional upside usually beats a safer-looking option that preserves comfort and teaches you nothing.
Level 4 Adjust with Probabilistic Thinking
People often get sloppy. They hear "uncertainty" and abandon all structure. That's a mistake.
Even if you can't build a reliable probability distribution, you can still think in ranges, conditions, and regret. You can ask which assumptions are load-bearing. You can ask what would have to be true for an option to fail badly.
Use rough probabilistic thinking without pretending to have precision.
- If one assumption breaks, does the whole option collapse?
- If the upside arrives late, can the business carry the wait?
- If you're wrong, what's the most expensive form of wrong?
This isn't spreadsheet theater. It's disciplined humility.
Level 5 Set Commitment Rules and Execute
A decision without commitment rules becomes a recurring debate.
Define the move. Define the trigger for review. Define what evidence counts. Then execute long enough to let the decision express itself.
A useful commitment rule has three parts:
- The choice: What you're doing now.
- The operating window: How long or under what conditions you'll hold it.
- The reversal trigger: What would invalidate the decision.
For range-based uncertainty, leaders should pre-approve options with triggers. For more radical uncertainty, they should simplify governance and shorten cycles so the business can adapt faster than conditions change, according to this guidance for leaders under uncertainty.
That last point is where most founder decisions fail. Not at analysis. At enforcement.
A Filter in Practice Two Founder Examples
Theory is easy to admire and easy to misuse. The filter matters only if it collapses a live decision into a move.
Capital allocation
A founder has limited cash left. One option is a new product line with unclear demand. The other is doubling down on the current marketing channel, which still works but has gone flat.
The decision isn't "how do we grow?" It's whether to fund known but weakening distribution, or uncertain but potentially stronger demand creation. So the founder maps scenarios. In a flat market, the current channel likely preserves stability but teaches little. In a favorable market, the new product could open a better lane. The asymmetric move is usually the one that buys learning without risking the company.
That doesn't mean "bet the company." It means define a limited commitment to the new line, set a review trigger, and preserve enough room to reverse. The filter turns a vague growth debate into a bounded test with real consequences.
Strategic pivot
Another founder serves a familiar customer base but sees pressure on margins. A more lucrative enterprise segment looks promising, but the sales cycle, expectations, and positioning are unfamiliar.
The trap is trying to run both paths indefinitely. That's what operators do. Architects cut.
A proper pass through the filter usually reveals that the actual choice isn't whether enterprise is attractive. It usually is. The crucial choice is whether the founder is willing to accept the operational changes that enterprise requires. Different sales motion. Different proof points. Different patience.
The useful question isn't "Could this work?" It's "What do I have to stop doing if I commit to it?"
If the answer is still unclear, map scenarios and test the shift with explicit rules. That's where scenario analysis in founder decisions becomes useful. If the answer is clear, cut the split focus and commit.
What This Framework Is Not
This framework isn't a productivity system. It won't help you manage more tasks. It won't organize your notes. It won't improve team morale.
It also isn't a mental-model library. You don't need another set of concepts to admire and never apply. And it isn't an execution playbook. Execution starts after the directional choice is made.
Keep the category clean
This is a tool for one leader making one directional choice under conditions where the probabilities are unreliable or missing. That's the gap a lot of business advice avoids.
Deep-uncertainty methods start from the opposite premise. They stress-test plans across multiple plausible futures instead of trying to predict one best future, which is especially relevant for founders making market-entry or scaling decisions, as described in this deep uncertainty explainer.
If you mistake this for a planning tool, you'll overbuild. If you mistake it for coaching, you'll stay in reflection. If you mistake it for consensus design, you'll slow the decision until it no longer matters.
The filter exists for one reason. To force a committed choice when the map is incomplete.
From Uncertainty to Committed Action
A decision is useful when it creates movement.
Start by diagnosing the kind of uncertainty you're facing. If the range is clear enough, set options and triggers in advance. If the situation is more radical, simplify the way decisions get made and shorten the path from idea to action. That's the practical implication of the leader guidance covered in this HEC note on uncertainty and decision systems.
Then run the filter once. Name the core decision. Map plausible scenarios. Check asymmetry. Use rough probability without pretending to know more than you do. Set commitment rules. Move.
For some founders, that's enough. A single focused session will clear the backlog. For more complex or time-sensitive decisions, the same structure can be applied in a more direct advisory format, including through Lucas Hubert Advisory, where the work centers on strategic direction, scenario mapping, and committed choices under uncertainty. If you're also weighing decisions with other operators in the room, this piece on a founder mastermind group may help you see where outside input clarifies and where it muddies the call.
You don't beat uncertainty by removing it. You beat it by committing before it removes your options.
If this is the kind of writing you want more of, subscribe to Beyond Noise via Lucas Hubert. That's where I publish practical essays for founders who need a real decision, not more input.
