Not Every Bad Result Means You Made a Bad Decision

Leaders are judged by results.

They should be.

But there is a trap in that idea: assuming every good result proves the decision was good, and every bad result proves the decision was wrong.

Business is messier than that.

You can make a weak decision and get lucky. You can make a strong decision and get an unfavorable result. You can make the right strategic call and undermine it through poor execution. You can make a good decision, execute it well and still judge it too early.

Outcome matters. But outcome alone doesn't tell you whether the decision was sound.

Separate the decision from the result.

When something misses, the easiest question is: Who got it wrong?

A more useful question is: What exactly failed?

Was the original decision based on bad assumptions? Did the team disagree with the direction and never truly align? Was the decision sound but execution inconsistent? Did the market change? Did we simply not give the decision enough time?

Those distinctions matter.

If you treat every bad result as evidence that the strategy was wrong, you create an organization that constantly changes direction.

If you treat every bad result as an execution problem, you create an organization that never questions its own strategy.

Both are dangerous.

I look at four things.

When I think about whether a decision had a fair chance to work, I tend to look through four lenses:

Decision. Alignment. Execution. Time.

Not as a branded framework. Just as a practical way to separate things that organizations often collapse into one conversation.

1. Was the decision good?

Start with the decision itself.

What information did we have at the time? What assumptions were we making? What alternatives did we consider? What evidence supported the choice? What risk did we knowingly accept?

This matters because hindsight has access to information the original decision-maker did not.

It's easy to look backward and say the answer was obvious after the market has already revealed it.

The fairer standard is whether the decision was reasonable given what was knowable when it was made.

That doesn't excuse bad judgment. It makes judgment more rigorous.

2. Did the organization actually align?

A leadership team can make a decision without the organization ever truly committing to it.

The meeting ends. Everyone nods. Then functions return to their own priorities.

Sales interprets the strategy one way. Marketing another. Product keeps the old roadmap. Finance funds something different. Managers explain the change inconsistently.

Months later, the result disappoints and the original decision gets blamed.

But was it ever really implemented as one decision?

Alignment isn't agreement with every detail. It's clarity about what we decided, why we decided it, what changes because of it and what each leader now owns.

A strategy that exists only in the executive meeting isn't a strategy the business can execute.

3. Was execution good enough?

A sound decision can absolutely fail because of execution.

Maybe the company chose the right market but never built the demand engine to reach it. Maybe the new sales motion made sense but managers didn't coach it. Maybe pricing changed but sellers kept discounting back to the old model. Maybe the organization announced a priority without reallocating people, time or capital.

Execution is where strategic intent becomes operating behavior.

So ask the uncomfortable questions.

Did we actually do what we said we were going to do? Consistently? At the required standard? Did leaders inspect it? Did incentives support it? Did we remove conflicting priorities?

If not, the result may tell you more about execution than the decision.

4. Did we give it enough time?

This one is especially difficult in environments where the pressure for results is high.

Some decisions have short feedback loops. Others don't.

Enterprise sales cycles can take months. A positioning change may need time to show up in pipeline quality. A new leader may need multiple quarters to change capability and behavior. A product investment may have dependencies before the market sees the value.

That doesn't mean leaders should wait indefinitely.

It means the expected time horizon should be part of the decision before the result arrives.

What should we see in 30 days? In 90? In two quarters? What leading indicators would tell us the decision is beginning to work before the lagging outcome appears?

Without that clarity, impatience becomes strategy.

Don't move the goalposts after the fact.

One of the most corrosive leadership habits is changing the standard after seeing the outcome.

If the result is good, we say the strategy worked.

If the result is bad, we suddenly remember all the reasons we were skeptical.

That makes learning almost impossible.

Write down the logic before you know the answer.

What do we believe? Why? What would prove us right? What would make us reconsider? How long should this take?

Now you have something more useful than hindsight.

Good operators learn without overreacting.

The point isn't to defend every decision.

Some decisions are bad. Some leaders stay with them too long. Sometimes the evidence changes and the right move is to reverse course quickly.

But strong operators can hold two ideas at once:

Results matter.

And learning from results requires understanding what produced them.

That means resisting both defensiveness and panic.

Ask what the outcome teaches you about the decision, the alignment, the execution and the time horizon.

Then change the thing the evidence says needs changing.

Not every bad result means you made a bad decision.

But every result should make you a better decision-maker.