A startup can make a good decision and still get a bad outcome.
It can also make a poor decision and get lucky.
That creates a problem for founders who judge every decision by what happened afterward.
If the result was good, the decision looks smart.
If the result was bad, the decision looks wrong.
But startups rarely operate with complete information.
Good leadership requires looking at something deeper:
Was the decision reasonable when it was made?
Outcomes Can Hide the Quality of a Decision
Imagine a founder launches a new pricing plan.
At the time, the team has customer interviews, sales data, competitor research, and several weeks of testing.
The team makes a reasonable decision.
Three months later, revenue drops.
Was the decision necessarily poor?
Not automatically.
A market shift, competitor move, unexpected customer behavior, or external event may have changed the situation.
Now consider the opposite.
A founder makes a decision with almost no evidence.
By chance, the decision produces strong revenue.
That does not necessarily make the decision process strong.
If the company only studies outcomes, it can learn the wrong lesson.
Ask What Was Known at the Time
After an important decision, founders should separate two things:
What we know now
from
What we knew then
This distinction is surprisingly powerful.
When reviewing a decision, ask:
- What information did we have?
- What assumptions were we making?
- What alternatives did we consider?
- What risks did we accept?
- What would have changed our decision?
- Which signals did we ignore?
These questions reveal the quality of the thinking behind the decision.
They also reduce hindsight bias.
Create a Decision Record
You do not need a complicated system.
For important decisions, write down five things:
Decision: What are we choosing?
Reason: Why are we choosing it?
Assumptions: What needs to be true for this to work?
Evidence: What information supports the decision?
Review date: When will we examine what happened?
The value is not the document itself.
The value comes from comparing the original reasoning with reality later.
That comparison creates organizational learning.
Review Decisions Before the Next Big Decision
Suppose a startup launches three experiments in a quarter.
The first fails.
The second produces modest results.
The third performs extremely well.
A weak review says:
“The third experiment worked. Do more of that.”
A stronger review asks:
“What did we learn about how we chose these experiments?”
Maybe the successful experiment had a clearer customer problem.
Maybe the failed experiment relied on an assumption nobody tested.
Maybe the team spent too much time optimizing execution before confirming demand.
The real lesson may have nothing to do with the individual experiment.
It may be about the decision process.
This Also Changes How Teams Handle Failure
If employees believe every failed outcome will be treated as evidence that they made a bad decision, they will become more cautious.
They may choose familiar options.
They may wait for founder approval.
They may avoid experiments with uncertain outcomes.
That can make a startup look stable while quietly reducing its ability to learn.
Instead, separate bad decisions from good decisions with bad outcomes.
The distinction does not excuse poor judgment.
It makes the evaluation more accurate.
If someone ignored strong evidence, that matters.
If someone made a reasonable decision with limited information and the situation changed, that matters too.
Those are different lessons.
Founders Should Also Review Their Own Decisions
This is where the practice becomes uncomfortable.
Founders often review employee decisions more carefully than their own.
Ask yourself:
“Which decision did I make recently because I had evidence?”
Then ask:
“Which decision did I make because I simply felt certain?”
The second question can reveal more than the first.
Experience is valuable, but experience can also create assumptions that go untested.
The more senior the decision-maker, the easier it can become for intuition to sound like evidence.
A decision review creates a useful pause.
Build a Culture of Better Thinking
A company does not become better at decision-making because everyone makes perfect choices.
It improves when people can examine their reasoning honestly.
That means discussing decisions without turning every review into blame.
It means documenting important assumptions.
It means revisiting decisions after new information arrives.
And it means rewarding thoughtful judgment, not just lucky outcomes.
The objective is simple:
Make better decisions with the information available at the time.
Results will always contain some uncertainty.
Your decision process is something you can continuously improve.
