2026-09-24
Managers submit their own daily report first: shaping the team's reporting culture from the top
If managers ask only their staff to write daily reports and do not write their own, reports tend to be received as surveillance. This covers how managers can create a writable atmosphere by showing their own plans and reflections.
A daily report only subordinates write looks unfair
When a manager demands daily reports but does not write one, subordinates easily feel watched. The report looks like a reporting duty rather than a tool for building trust. The starting point for shaping a reporting culture is for the person asking to show the same habit themselves. Simply saying "I will submit the same thing" makes it more likely that the report is seen as something everyone uses, not surveillance from above. Conversely, if the only reason for not writing is "I'm busy," subordinates may feel their own workload is being treated lightly.
What to write in a manager's daily report
Managers also write their plan (P), do (D), check (C), and act (A) briefly. It is enough to show what the team is prioritizing and where you spent your time today. Rather than a list of small tasks, adding the reason for a judgment or what you were unsure about gives subordinates something to learn from. For example, a line such as "Today I prioritized the new hire's questions and pushed the document check to tomorrow, because I judged that keeping them waiting would have a bigger impact" lets subordinates learn concretely how to set priorities.
Show failures and doubts too
Not only what went well: show, to the extent you can, decisions you got wrong and matters you are unsure about. When a manager does not hide failure, subordinates find it easier to write about theirs. Psychological safety grows not by being declared but by senior people actually showing it. The knack is to pair the fact with the next step, such as "I proceeded without confirming the intent of the request and had to redo it; next time I will align once before starting." Avoid venting that names individuals or exposes a subordinate's mistake; keep it a reflection on your own judgment.
Share your own learning when replying to reports
When commenting on a subordinate's report, add your own past experience or something you noticed from this report. It conveys a stance of learning from each other rather than one-way instruction. Talking in connection with your own report turns the daily report into a place of learning for the whole team. A line like "I'd like to borrow this idea" or "I got stuck in the same place once" is easier to receive than an evaluation or an instruction, and it can prompt the subordinate to write their own thinking one step deeper next time.
Keep going in a way that isn't a strain
Managers are busy, and if the report becomes a burden it will not continue. A short format is fine; keep it up daily or at a set frequency. If you decide that on busy days bullet points alone are acceptable, it is less likely to break off. The act of continuing is itself the clearest model of the value of daily reports for the team. Deciding in advance when you will write, or that a missed day gets combined into the next, gives you your own rules and helps the habit settle.
The smallest first step to try
There is no need to aim for a perfect report from the start. Begin by submitting a few lines of plan and a single line of reflection. Then tell the team, "I've decided to write one too; I'd appreciate your reactions," which makes it easier for subordinates to respond. After keeping it up for a few weeks, ask your subordinates what is hard to write and revisit the format or frequency. Showing yourself as a participant in the improvement is the surest shortcut to shaping reports from the top.
Related articles
A tool for a culture of improvement and fair evaluation that implements these ideas.