“Faithful are the wounds of a friend.”1
Proverbs 27:6
A thread snaps. The loom stops.
It does not keep moving because the target is due. It does not weave the fault deeper into the cloth and send the damage to an inspector at the end. The machine notices that something is wrong, then refuses to carry the error forward.
This was the genius inside Sakichi Toyoda’s automatic loom. It could make a judgment and stop itself when an abnormality appeared. The principle later entered the Toyota Production System as jidoka: when something goes wrong, stop, make the problem visible and prevent the defect from travelling farther.
On a Toyota production line, a worker who sees an abnormality can call for help. The andon display shows where the problem is. If it cannot be corrected in time, the line can stop. A vast system gives the smallest useful truth a path to authority.2
Most organisations build the opposite machine.
The problem appears. The work continues. The warning enters a meeting, loses its edge in a slide and climbs through people who each make it sound a little safer. By the time someone with power sees the defect, it has been woven into the quarter, the product or the culture.
Thursday’s essay showed why teams learn to hide bad news. This is the practical answer.
What follows is built as a concise, world-class how-to manual: powerful enough to change what happens in your next room, and short enough to use today. You can read it in about ten minutes and install it in seven days. It has one purpose: to help your team tell you the truth while you can still do something with it.
It does not require another survey, an anonymous suggestion box or the surrender of your authority. It requires a clear route for warnings, better questions, a disciplined first response and visible decisions.
First, Measure the Delay
Choose one important warning that reached you late in the last ninety days. Write down two times: when someone first saw the problem, and when the person able to act understood it clearly.
The distance between those moments is your truth latency.
If a customer-service agent saw the same complaint on Tuesday, but the head of the business understood the pattern on Friday, truth latency was three days. Do not write “fairly quickly” or “eventually.” Use hours or days. Then ask what became harder, slower or more expensive during that interval.
You do not need to repair the whole culture this week. Choose one place where truth is losing time. Then shorten the distance.
