2026-06-29
Make reporting a system: use the daily report to reduce 'hard to say'
Reporting doesn't increase just because you say 'do it properly.' Provide the fixed vessel of a daily report and design it so bad news rises fastest — a reporting design that reduces the hard-to-say.
Why reporting doesn't grow by decree
Just saying 'report properly' doesn't increase reports. Bad news especially gets held in, because 'I might get scolded' comes first. Reporting isn't a matter of spirit; it's decided by whether there's a system that makes it easy to raise. Much of what makes it hard to say can be reduced by a system: not being able to read the other person's reaction, not knowing the timing, not knowing how much to convey.
Provide the fixed vessel of a daily report
With a fixed daily slot, reports flow there naturally, because you don't agonize each time over when, to whom and how to convey it. The report's P/D/C/A works as a fixed vessel for reporting and lowers the bar to report. If C is settled as the place to write 'what I'm struggling with,' the psychological burden of going out of your way to ask for someone's time gets smaller. Also share the line that anything urgent is told directly without waiting for the report.
Catch bad news fastest
The manager answering — without blame — the 'got stuck' and 'didn't go well' written in C (reflection): keep this up and it becomes a culture where bad news rises fastest. A problem raised early can be handled while still small. As a guide, first take in the report itself, then think together: 'thanks for telling me; where shall we start?' Tracing the cause can wait until after you have calmly confirmed the facts.
Reaction calls the next report
The experience of submitting and being properly answered creates the action to 'submit next time too.' Reporting becomes a habit not from a single decree but from the back-and-forth of submit, answer, submit again. System and reaction grow the culture. A reaction needn't be a long reply; a single line on the outlook for handling it is enough. Just knowing it was read lets the writer submit the next report with peace of mind.
Common stumbles and how to avoid them
A common one is reacting emotionally to bad news, after which reports decrease. When startled, you can also leave a gap rather than decide on the spot: 'let me think and get back to you.' Also, if replies to reports are late, the vessel loses effect even though it exists. On busy days, sending at least a mark that you've read it promptly is a good guide. Beyond that, you need to show repeatedly, in words and actions, that people are not disadvantaged for what they report.
The smallest first step to try
This week, tell the team they may write just one line in C about 'what I'm struggling with.' When the manager finds one, they send back a word the same day. Just a few days of this and the sense that it's fine to write and that a reply will come grows little by little.
Related articles
A tool for a culture of improvement and fair evaluation that implements these ideas.