2026-06-29
Make a report where failure can be written: psychological safety produces improvement
If only convenient things get written in the report, no improvement arises. How to grow the psychological safety to write failures and stumbles with ease, through how you run the daily report.
A report without failures produces no improvement
When only good things line up in a report, readers feel reassured, but issues hide below the surface and improvement stops. Failures and stumbles are the very entrance to improvement. A report where they aren't written, however calm as a report, drops the material for growth. Behind failures going unwritten there is often worry that writing them will lower one's evaluation or invite blame. Before blaming the writer, first review whether an atmosphere that makes it hard to write exists on our side.
Answering without blame builds safety
Whether the manager first blames or thinks together about a failure written in C (reflection) decides what gets written next. Keep up an attitude of thinking together about 'how to prevent it next time' without blame, and writers can write the truth with ease. For example, respond first with a line such as 'thank you for reporting' or 'let's think together about how to recover first.' When probing causes, focus not on 'who' but on 'which step' and 'what information was missing.' When attention turns to the mechanism rather than the person, writers feel protected.
Treat sharing failure as valuable
The earlier a failure is shared, the smaller it still is when you act. So don't negate the act of surfacing a failure; rather, treat surfacing it early as valuable. Once people see that surfacing beats hiding, bad news rises naturally too. It is also effective for a manager to show their own failures and hesitations first, in reports or meetings. When someone in a senior position shares candidly, subordinates find it easier to follow. What is learned from shared failures is put into words and kept as a lesson for the whole team.
Safety is the foundation of an improvement culture
Only with a state where failure can be written does PDCA turn from reflection (C) to improvement (A). Psychological safety is a practical premise for building an organization where improvement continues, not just a matter of kindness. A safe place produces grounded improvement. Note, though, that being safe is not the same as dropping standards. If the same failure keeps repeating, address its cause as a mechanism. Not blaming and asking for improvement can coexist.
Common stumbles and how to avoid them
A common stumble is saying 'it's fine to fail' in words while the actual reaction is harsh. When words and reaction disagree, writers believe the reaction. Also, raising a failure in a public setting can make the person shrink back. Receive it first in an individual reply, and if you share it, get the person's consent and stick to the facts and the lesson.
The smallest first step to try
The next time you find a report where a failure is written, start the first line with 'thank you for writing this.' Then add one question that thinks about what to do next together. Keep responding this way a few times and watch whether what gets written becomes a little more candid.
Related articles
A tool for a culture of improvement and fair evaluation that implements these ideas.