When a colleague is off sick, the business discovers what it actually knows. Some tasks carry on, because the steps are written down or obvious. Others stop, because the only way to do them is to ask the person who is not there. For the people who step in, this moment is often a sharp lesson: either a role that can be learned from the page, or one that can only be learned by being in the room for years.
This piece is about the first kind. It argues, as a hypothesis, that documented processes help people grow into roles, because they give a learner something to practise against, give a stand-in permission to try, and give the business more than one person who can do the work. It also covers where documentation fails and what a realistic version looks like in a small South African business.
What absence reveals
Staff absence is an unusually honest test of how a role is held. Planned leave can be prepared for. A sudden illness, a family emergency or a resignation with a short notice period cannot. In each case the question is the same: can someone else do this work, tomorrow, without phoning the person at home?
In many small businesses the answer is partly yes, because colleagues have picked things up informally. But informal learning has limits. It depends on who happened to be nearby, on whether the expert had time to explain, and on whether the learner felt able to ask. Wikipedia's overview of tacit knowledge describes knowledge that is difficult to put into words or writing, such as judgement and experience, as harder to pass on than explicit knowledge that is written down. Not everything in a role can be documented, but a surprising amount of what feels tacit is simply undocumented.
From a rescue to a path
There is a difference between a document that rescues the business during an absence and one that helps a person develop. The same page can do both, but the framing matters.
A rescue document says: here are the steps, follow them. A growth document says: here is how this work is done, here is why each step exists, and here is what good looks like. The second kind is what lets a learner move from following instructions to making sensible decisions.
Consider what a written process offers someone who is growing into a role:
- A starting point that does not depend on another person's time. A newer colleague can read before asking, and ask better questions as a result.
- A way to see the whole job. People often learn their own corner of a process well and never see what comes before and after.
- A safe first attempt. Doing a task from a checklist, with a colleague available to review, is less frightening than doing it from memory.
- A record of the reasons. When a step looks pointless, a note explaining that it exists to satisfy an auditor, a supplier or SARS stops it being quietly dropped.
- Evidence of progress. A person who has covered three tasks from the written steps can point to what they now do, which matters at review time.
The business gains the same thing from the other direction: optionality. If more than one person can do the work, the business can choose whom to ask, whom to train and when to let someone take leave without apology.
What the available guidance says
Atlassian's guidance on internal documentation makes the practical case that written knowledge helps teams work without constant interruptions to the people who know the answers. It is vendor guidance, written by a company that sells collaboration software, so it is best read as a sound description of the idea rather than as proof of results in any particular business.
Wikipedia's entry on the standard operating procedure describes it as a set of step-by-step instructions that helps workers carry out routine operations and aims to achieve efficiency, quality output and uniformity of performance. That is a useful reminder that the idea is old and widely used in fields such as manufacturing, healthcare and aviation, where getting the steps right matters.
Neither source establishes that documentation causes growth. The link is a reasoned one: if learning depends on access to knowledge and practice, then making the knowledge accessible should help. Whether it does in a given team is something that team can observe.
An illustrative scenario
Consider a hypothetical example, not a real business: a Pietermaritzburg packaging distributor with fourteen staff. The only person who knows how to prepare the weekly customer statements and chase the oldest invoices is the bookkeeper. Everyone, including the bookkeeper, regards the job as slightly mysterious: there is a particular order for running the reports, a customer who must always be handled first, and a few manual corrections made from memory.
When the bookkeeper is hospitalised for a week, the owner and an admin clerk work through the process by trial and error. Statements go out late, one is wrong, and a large customer queries it. The clerk, who is eager to progress, finds the experience stressful but also illuminating: for the first time she sees how the pieces fit.
When the bookkeeper returns, they write the process down together over two afternoons, with the clerk asking questions and the bookkeeper explaining why each step exists. The following month the clerk prepares the statements herself, with the bookkeeper reviewing. The bookkeeper later takes a week of leave without being contacted. Nobody planned this as a development programme, but that is what it became.
What realistic documentation looks like
Documentation has a poor reputation because it is often done badly: long manuals written once, never updated, and read by nobody. A more modest approach tends to work better.
- Start with the tasks that stop when someone is away. Absence shows you which processes matter most. Begin there, not with a company-wide manual.
- Write it with the learner, not for them. Having the less experienced person ask questions as the expert talks produces clearer steps than the expert writing alone.
- Keep each document short and specific. A page that says what triggers the task, the steps, where the files are and who to ask when something looks wrong is enough.
- Include the judgement calls. Note the common exceptions and what to do about them. This is where growth actually happens.
- Put it in one findable place. Documents scattered across inboxes defeat the purpose. Mellorca's article on the cost of the same internal questions and undocumented knowledge shows what it costs when answers can only be obtained from a person.
- Test it by having someone else follow it. A process is documented only when a person who has never done it can complete it without phoning the expert.
- Review it when the work changes. An out-of-date process is worse than none, because it is trusted.
Mellorca's analysis of catching up after absence and poor handover covers the return-to-work side, and the piece on handing over an undocumented job during parental leave shows how the same problem appears in planned absence. On the learning side, see the employee who never has time to learn.
The human dividend
The dividend is optionality, with predictability alongside it. For the learner, it is the option to take on more of the work, supported by something to practise against. For the established expert, it is the option to be away, or to move on to a different role, without the business depending on a phone call. For the owner, it is a team that can absorb an absence without a scramble.
The trade-offs
- Documentation takes time that busy people feel they do not have. The cost is real and arrives before the benefit.
- Experts may feel exposed. Writing down what you know can feel like making yourself replaceable. Done well, it should make you able to move up or take leave, but that needs to be said and meant.
- Documents go stale. Without an owner and a review habit, they quietly mislead.
- Not everything can be written. Judgement and relationships still need mentoring, observation and time.
- Rigid steps can discourage thinking. A process that is followed blindly can stop people from noticing when it no longer fits.
Why it matters
Absence is the moment a business finds out whether its roles can be learned. Documented processes will not replace mentoring or experience, but they give people a place to begin, a way to practise and a reason to believe the role is within reach. They also give the business more than one person who can do the work. That combination is what turns a sick day from a crisis into a quiet test that the team passes.
Sources and further reading
- How to Ace Internal documentation - The Workstream (last verified 10 October 2026)
- Standard operating procedure - Wikipedia (last verified 10 October 2026)
- Tacit knowledge - Wikipedia (last verified 10 October 2026)
- 3 Ways to Use Knowledge Sharing - The Workstream (last verified 10 October 2026)
Related Mellorca reading
- The Owner Who Can't Decide Without the Spreadsheet Wizard
- When the Out-of-Office Reply Doesn't Stop the Work
- Why Nobody Trains for the Job of Being Human Middleware