2026-06-29
Prevent key-person dependency: use the daily report to reduce 'only they know'
The 'nothing works when they're off' kind of key-person dependency arises when know-how isn't recorded. How to leave daily judgments and ingenuity in the report and turn them into shared team knowledge.
Dependency arises from the absence of records
The state where 'work stops when they take a day off' arises when judgments and ingenuity live only in one person's head. If the method isn't recorded, no one can reproduce it when they're away. Dependency is a problem of missing records more than uneven ability. The person themselves often feels that routine steps and judgment habits are 'not worth writing down,' and left alone, records don't grow.
Leave daily ingenuity in the report
Leave 'how I judged' and 'why I did so' in the report's C (reflection) and A (improvement) and the tacit knowledge in your head gradually becomes words. The accumulation of small daily records becomes a body of know-how others can read later. As an example, add three things in one or two sentences: situation, judgment and reason, such as 'this request looked urgent, but I checked X and put it off, because...' You don't need to write a full manual; fragments that accumulate are useful enough.
Make it readable by the team
Don't keep the recorded know-how to one person; make it referenceable by the team. Share someone's stumble and its resolution and another person avoids repeating the same mistake or the same question. Records dissolve dependency only when shared. Even a short slot in a weekly meeting to introduce one idea from the week makes a habit of reading easier to form.
The contribution of dissolving dependency can be evaluated too
Recording your methods and leaving them in a readable form is a real contribution to the team. Grounded in the facts left in reports, this 'work of creating shared knowledge' can be evaluated fairly alongside flashier results.
Common stumbles and how to avoid them
If the recording burden is heavy it won't last, so at first don't demand perfection; start by leaving notes only for moments when you hesitated over a judgment. It's also worth checking whether the know-how is written in a way only certain people can read. When someone has a planned absence, testing how far another person can take over their work relying only on the reports makes the gaps in the records concrete. It also helps to periodically view the team's records from the angle of 'could someone new to this task take a first step from the reports alone?' If you find where they'd get stuck, simply adding notes there fills the gaps in shared knowledge bit by bit. Furthermore, when someone new joins, have them read the reports and ask what was hard to follow; this reveals gaps in assumptions the writer doesn't notice.
Related articles
- Managing and Growing a Caregiving Team Through Daily Reports ― Leading a Team That Can't Gather
- Closing the Head-Office-to-Store Information Gap with Daily Reports — Catching Both Trouble and Wins Without Visiting
- Turning Construction Daily Reports from Paperwork into Tomorrow's Plan: Designing Field PDCA
A tool for a culture of improvement and fair evaluation that implements these ideas.