Why Your 5 Whys Keep Ignoring Decisions: The Simple ‘Choice Why’ That Reveals the Real Commitment Behind Any Problem

You have probably lived this already. A problem blows up. The team runs a 5 Whys. Everyone nods. A process gets updated, a checklist gets longer, somebody gets retrained, maybe a tool gets swapped. Then, a few weeks later, the same mess shows up wearing a slightly different hat. That is exhausting. It also makes people quietly cynical about root cause analysis. The reason is often simple. Your 5 Whys stopped at a broken step, but missed the decision hiding underneath it. Someone chose speed over review. Someone chose silence over conflict. Someone chose to keep a bad workaround because it made today easier. If you never name that choice, you do not reach the real commitment behind the recurring problem. You just clean up the evidence. A simple extra question, what I call the “Choice Why,” can change that fast.

Why normal 5 Whys often stop too soon

The classic 5 Whys is useful. It helps teams move past the first obvious answer. But in practice, many groups stop at things that feel safe to say out loud.

Examples sound like this:

“The handoff failed.”

“The SOP was outdated.”

“The alert was missed.”

“The engineer was not trained.”

Those can all be true. They are just not always the whole truth.

What often gets skipped is the human part of root cause. Not the messy emotional theater people fear, but the plain old decision-making reality. People do things for reasons that make sense to them at the time. Even bad calls usually solve a short-term problem.

If your RCA never asks what choice was made, you can end up fixing the scenery while the same play keeps running.

The hidden layer: every recurring problem usually contains a choice

Here is the uncomfortable bit. Repeated problems are rarely just accidents floating in space. They often sit on top of a decision pattern.

What that looks like in real life

A manager keeps skipping planning because urgent work earns praise faster than careful prep.

A developer keeps pushing without asking for review because asking feels slow and slightly embarrassing.

A team keeps tolerating a flaky tool because replacing it would force a political fight no one wants this quarter.

An employee keeps saying “yes” to impossible deadlines because disappointing others feels more dangerous than burning out later.

Notice what these examples have in common. The bad outcome is not random. It is connected to a choice that secretly works in some way.

That is where psychological decision making enters the picture. Not as therapy-speak. As plain reality. Humans make tradeoffs. We pick the option that seems safest, fastest, least awkward, most rewarded, or easiest to defend in the moment.

The simple fix: add a “Choice Why” to your 5 Whys

After you ask the usual whys, add one more:

What decision was made here, and why did that choice look like the best option at the time?

That is the Choice Why.

It sounds small. It is not.

This question changes the mood of the conversation. Instead of pretending the problem was caused by a floating process failure, it asks what someone was trying to protect, avoid, gain, or survive.

Why this works better than “Who messed up?”

Because “Who messed up?” creates defense.

“What choice made sense at the time?” creates honesty.

It lets people admit things like:

• “We skipped the review because leadership cared more about launch date than quality signals.”
• “I did not escalate because every previous escalation got me labeled difficult.”
• “We kept the manual workaround because it was ugly but reliable, and nobody trusted the replacement.”

Now you are getting somewhere.

A quick before-and-after example

Standard 5 Whys

Problem: A customer received the wrong invoice.

Why? The billing data was outdated.

Why? The CRM was not updated after the sales change.

Why? Sales forgot to log the change.

Why? The handoff process is inconsistent.

Why? There is no enforced workflow.

That leads to a pretty normal fix. Update workflow. Retrain sales. Add a required field.

Now add the Choice Why

What decision was made here? Sales reps chose to delay CRM updates until end of day.

Why did that look like the best option? Because entering changes in real time slowed them down, hurt response speed, and the team rewarded fast closing behavior more than clean records.

That is a different root cause.

The real issue is not just “missing workflow.” It is that the system rewarded one choice and quietly punished the better one.

Without naming that, the same problem comes back.

How to use the Choice Why without turning your retro into a blame fest

This matters. The moment people hear “decision,” they may think “accusation.” So the wording is everything.

Use these questions

• What choice did we make, even if we did not say it out loud?
• What did that choice help us avoid?
• What did it help us get sooner, faster, or with less friction?
• What would have made the better choice feel realistic in that moment?

Avoid these traps

• Do not ask, “Why did you do that?” in a sharp tone.
• Do not assume the first decision named is the deepest one.
• Do not stop at personal weakness if the environment kept rewarding the same move.

Good RCAs look at both the person and the system around them. A bad system can train smart people into bad habits very quickly.

If your team tends to get guarded during these talks, this piece on Why Your Nervous System Sabotages Every Root Cause Analysis (And How To Ask Whys It Actually Trusts) is worth reading. It explains why people shut down the moment an RCA feels like a courtroom.

What the Choice Why usually reveals

Once you start using it, the same themes show up again and again.

1. The choice protected status

People avoided looking slow, needy, junior, or difficult.

2. The choice bought speed

Shortcuts won because the culture rewarded immediate output more than long-term stability.

3. The choice avoided conflict

No one wanted to challenge a leader, push back on a deadline, or expose a weak process owned by another team.

4. The choice reduced uncertainty

People stuck with familiar bad methods because the better alternative felt risky or unclear.

5. The choice preserved energy

Sometimes the “wrong” move was simply the only one that felt survivable in an overloaded environment.

This is why 5 whys root cause analysis psychological decision making belongs together. Problems repeat because choices repeat. Choices repeat because they still make sense inside the current incentives, fears, and habits.

Use it in a team retro, a 1:1, or on yourself

The Choice Why is not just for incident reviews.

In a team retro

Ask, “What did we keep choosing as a team, and what did that buy us?”

This helps groups admit things like, “We chose to stay vague because alignment meetings never end well,” or “We chose speed because leadership only noticed visible shipping.”

In a manager 1:1

Ask, “What felt like the safest option when this happened?”

That gets better answers than, “Why didn’t you follow the process?”

In self-reflection

Ask yourself, “What am I choosing again and again because it works for me in the short term?”

That one can sting. It is also where real change starts.

What to do after you find the hidden decision

Naming the choice is step one. Then you need to make the better choice easier, safer, or more rewarding.

Try this simple sequence

1. Name the recurring problem clearly.
2. Run the usual 5 Whys.
3. Add the Choice Why.
4. Identify what the choice was protecting or rewarding.
5. Change the condition around it. Incentives, timing, approval rules, communication norms, ownership, or safety.

For example, if people keep bypassing review because review slows shipping, the answer is not another lecture about quality. It may be lighter review rules, faster reviewer rotation, clearer exception paths, or leadership signaling that rework costs more than a slightly slower launch.

In other words, do not just tell people to choose better. Change what the environment makes attractive.

At a Glance: Comparison

Feature/Aspect	Details	Verdict
Standard 5 Whys	Good at tracing process breakdowns, missing steps, and obvious operational causes.	Useful, but often incomplete for recurring human-pattern problems.
5 Whys plus Choice Why	Adds the hidden decision, short-term reward, fear, or tradeoff that made the bad outcome likely.	Best option when the same issue keeps returning despite process fixes.
Blame-based postmortem	Focuses on who failed, which makes people defensive and less honest.	Usually the worst choice if you want real accountability and better future decisions.

Conclusion

A lot of current talk about root cause analysis stays parked at tools, workflows, SOPs, dashboards, and telemetry. Those things matter. But they are only part of the story. Real teams get stuck because recurring problems often hide a decision someone keeps making because, in some quiet way, it still works for them. That is the piece many 5 Whys sessions miss. Add the Choice Why to your next retro, 1:1, or personal review. Ask not only, “What failed?” but “What decision was made here, and why did that choice look like the best option at the time?” That one question moves the conversation from abstract framework talk to concrete accountability and self-honesty. And that is usually where the real fix finally starts.