2026-06-27
Turning daily reports into PDCA: team management that doesn't go stale
How to turn a report that ends at 'submitted' into real growth and problem-solving. A concrete pattern for building PDCA into the daily report.
Why daily reports go stale
Most reports stop at 'what I did (D)' and never connect to reflection (C), improvement (A) and the next-day plan (P). Writers turn it into an activity log, readers can't give feedback, and only the burden remains.
Make PDCA the structure of the report
Split the report's own input fields into P (today's goal), D (what you did), C (reflection), A (improvement) and next-day P. With a fixed shape, writers don't hesitate and readers can give specific feedback like 'the C-to-A link is weak.'
Let the person write the improvement (A)
If AI or the manager fills in the improvement and next-day plan, the member's problem-solving never grows. Default to a 'growth mode' where they write it themselves, and only support with a draft or hint on stuck days.
Review weekly
Looking at daily reports a week at a time reveals consistency between plan and execution, and whether reflections feed into the next day's actions. Start 1-on-1s from this weekly flow and they won't devolve into trading impressions.
A tool for a culture of improvement and fair evaluation that implements these ideas.