Human Skills: Trust · Step 4: Sustain · Let's Practice!
Your 5 Whys
Dig past the person to the system underneath
When something goes wrong, the fastest "answer" is usually a person to blame. The 5 Whys is a simple tool that keeps you digging past that first answer to the real, systemic root — and getting to the root, instead of a scapegoat, is exactly what protects trust.
The method: name a problem, ask why, and for each answer, ask why again — five times.
The widget factory, one why at a time
ProblemThe factory made fewer widgets this month than last.
Why? → One of the widget machines was broken.
Why? → Its left doohickey broke off.
Why? → It hadn't been oiled.
Why? → The oiling specialist didn't come in last week and no one covered.
Why? → The specialist was out sick — and the back-up specialists had all been let go in a staffing cut.
Root fixCross-train employees across departments so oiling is always covered.
Here's the trapStop after two whys and you'd "fix" a broken machine. Stop after four and you'd blame the absent specialist. Only the fifth why reveals the real cause — a staffing decision — and if leadership had fired the foreman at why two, the true problem would still be there, and trust would quietly erode.
Your problem · start
Name a problem on your team worth getting to the bottom of. Pick one or write your own:
You reached the rootLook at your last answer versus your first. The first was probably close to a person or a surface symptom; the last is closer to a system, a process, or a decision. That gap is the whole point.
Two roads from the same problem
The road that stops earlyBlame the nearest person → they carry it alone → the real cause stays in place → it happens again → the team learns that being closest to a failure is dangerous, and stops surfacing problems.
The road you just tookFix the system → the cause is actually gone → the team sees that leadership hunts for causes, not culprits → people keep bringing problems forward early.
One more thingBefore you commit to your fix, gather perspectives from everyone the problem touched. You may have the chain slightly wrong, and the people closest to it will tell you.
Choosing to dig for the cause instead of the culprit is a response — and your team feels which one you reach for.
Trust = consistent Responses to Challenges over Time
Every time you get to the real root instead of the easy scapegoat, the team learns that a mistake here leads to a fix, not a hunt. That's what makes it safe to tell you the truth.
Now head back to the book and run one of your own problems through all five whys.