Decision Quality Is Not Outcome Quality

A Little Side Trip

---

I’ve been thinking about one of the most debated decisions in sports.

Twenty-six seconds remained in Super Bowl XLIX.

The Seattle Seahawks trailed the New England Patriots 28–24. They were on the one-yard line, facing second down, with one timeout remaining.

Seattle had Marshawn Lynch in the backfield.

Many people expected a run.

Instead, the Seahawks passed.

Malcolm Butler stepped in front of the receiver and intercepted the ball.

Game over.

The outcome was devastating.

And almost immediately, the outcome became the verdict:

It was a terrible decision.

Maybe it was.

But not simply because the pass was intercepted.

That distinction matters.

I’m not trying to prove that Seattle made the right call. Football experts can continue debating the personnel, the defensive formation, the route, the clock, and whether Marshawn Lynch should have received the ball.

I’m asking a narrower question:

Can the result, by itself, tell us whether the decision was good?

Pete Carroll later explained that the Seahawks were trying to preserve several opportunities to score while managing the remaining time and their final timeout. He believed the defensive formation created an opportunity for the pass.

We can disagree with that reasoning.

We can conclude that another choice would have been better.

But Carroll had to make the decision before he knew that Butler would recognize the play and jump the route.

We judge it afterward, already knowing the answer.

That difference — between deciding before the outcome and judging after it — is easy to overlook.

Consider a very different situation.

Imagine a wildfire moving toward a neighborhood.

The wind is unpredictable. The fire is still some distance away, but conditions could change quickly. Roads may become congested or close. Officials recommend that residents evacuate before the danger becomes immediate.

Two families live next door to each other.

The first family leaves.

They pack what they can, load the car, and drive away while the roads are still open.

The second family stays.

They look at the same sky, hear the same warning, and decide that the fire probably will not reach them.

During the night, the wind changes direction.

The fire turns away from the neighborhood.

By morning, both houses are untouched.

Now look only at the outcomes.

The family that evacuated endured inconvenience, lost sleep, spent money, and left a home that was never damaged.

The family that stayed slept in their own beds and woke to find everything exactly as they had hoped.

So which family made the better decision?

Was evacuating a mistake because the fire never arrived?

Was staying home a good decision because nothing happened?

Not necessarily.

Both families had to decide before they knew which way the wind would turn.

The family that evacuated may have made a careful decision based on the information, uncertainty, and potential consequences available at the time.

The family that stayed may have accepted a much larger risk and simply been fortunate.

The wind changing direction did not retroactively make the warning unreasonable.

And surviving the night did not necessarily prove that staying was wise.

One family’s caution was not disproved by a safe outcome.

The other family’s risk was not validated by luck.

That is the difference between outcome quality and decision quality.

Outcome quality asks:

What happened?

Decision quality asks:

Given what was known at the time, were the reasoning and the choice reasonable?

The two are related.

But they are not the same.

A physician can make a careful, well-supported decision and the patient can still worsen.

An investor can take a poorly understood gamble and make money.

A reckless driver can arrive home safely.

A careful driver can be struck by someone else.

A bad outcome does not prove a bad decision.

A good outcome does not prove a good one.

This does not mean outcomes should be ignored.

Outcomes matter.

They are evidence.

They may reveal a risk we underestimated, an assumption we failed to question, or an option we should consider the next time.

But an outcome should update our judgment of the decision — not replace the judgment entirely.

Otherwise, we make two serious mistakes.

We punish sound reasoning whenever reality produces an unfavorable result.

And we reward poor reasoning whenever luck produces a favorable one.

Misfortune begins to look like incompetence.

Luck begins to look like wisdom.

Perhaps the better way to examine a decision is to ask two sets of questions.

First, before we know how the story ends:

What was known when the decision had to be made?

What alternatives were available?

What were the risks and consequences?

Was the reasoning reasonable under those conditions?

Then, after reality answers:

What did the outcome reveal?

What should we learn?

What should change the next time?

The Seahawks’ decision can still be debated.

Perhaps they should have handed the ball to Marshawn Lynch.

Perhaps the pass was defensible but poorly executed.

Perhaps the reasoning underestimated a particular risk.

Those are legitimate arguments.

But the interception alone cannot settle the question.

Just as a wildfire turning away does not prove that evacuation was unnecessary.

The outcome tells us how the story ended.

Decision quality asks whether the choice made sense while the ending was still unknown.

I’ve been wondering…

How many decisions have we called foolish only because we already know how the story ended — and how many reckless decisions have we praised simply because luck was kind?