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.
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.
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.
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 tool for a culture of improvement and fair evaluation that implements these ideas.