In nearly every organization where I've sat down with a management team to raise the subject of documenting procedures, the same scene plays out. The answer comes quickly, confidently: "We don't need that here, everyone knows their job." And every single time, there's one test that reveals the truth behind that sentence: what happens on the day the person who "knows their job" doesn't show up?
In nearly every organization where I've sat down with a management team to raise the subject of documenting procedures, the same scene plays out. The answer comes quickly, confidently: "We don't need that here, everyone knows their job." And every single time, there's one test that reveals the truth behind that sentence: what happens on the day the person who "knows their job" doesn't show up?
The answer is usually uncomfortable. It exposes a paradox many managers overlook: people imagine documentation is an extra layer of complexity, when in fact the absence of documentation is the real complexity — it's chaos deferred, waiting for the moment someone walks out the door to reveal its full cost.
The Real Price of Undocumented Procedures
The problem with undocumented procedures isn't that you don't know what to do at a given moment. The problem runs deeper: you don't even know that there's something you don't know. As long as things run smoothly, skipping documentation looks like a smart call — it saves time, avoids bureaucracy, and leans on individual competence. But this smoothness rests on a fragile assumption: that the people carrying the knowledge will stay, will keep remembering, and will keep agreeing with each other on how things get done.
This triple assumption collapses exactly when you least expect it, through three recurring paths:
1. The Sudden Departure
A resignation, an illness, an unexpected transfer — and the organization discovers that what it thought was "institutional knowledge" was really just fleeting personal knowledge. There's no documentation, no orderly handover, and everyone starts from zero in the middle of ongoing work.
2. The Silent Conflict
When there are no documented procedures, every employee develops their own way of doing things. Over time, you end up with a team executing the same task through multiple different methods, each person fully convinced they're doing it "the right way." This conflict doesn't show up on ordinary days — it surfaces suddenly, when two people have to collaborate on one task, or when someone reviews another's work.
3. The Impossibility of Improvement
You can't improve what you can't measure, and you can't measure what you haven't documented. Organizations lacking written procedures reinvent the wheel every single time — because they simply don't have a reference wheel to build on.
Why Do We Resist Documentation Even Though We Know the Risk?
Before discussing the solution, it's worth understanding why this problem keeps recurring even though everyone recognizes it as a problem.
The Living Illusion
When the person responsible is standing right there among us, we feel no gap at all. But "here today" doesn't mean "will never be gone." We tend to judge risks by how likely they seem right now, not by their true cost when they actually materialize.
Documentation Feels Like an Accusation of Incompetence
In some workplace cultures, asking someone to document a process gets read as an implicit message: "We don't trust you." This misreading turns a documentation proposal into social resistance, not just organizational resistance.
"Not the Right Time"
Documentation doesn't produce an immediate, tangible result. In environments that measure performance purely by daily output, every hour spent documenting feels like an hour stolen from "real work." The price gets paid later, and when it is paid, hardly anyone traces it back to that original, postponed decision.
The Fear of Perfection
Many organizations never even start documenting because they want it "comprehensive and perfect" from day one — all or nothing. Perfection never arrives, so the actual, default choice becomes: nothing.
Where Do You Start?
The common mistake is trying to document everything at once, which produces a massive project that never finishes and a team that loses its enthusiasm by week two. The right question isn't "What do we need to document?" It's: "Which process, if it stopped today, would bring the most things down with it?"
The priority test — just three questions:
- Frequency: How often is this process run each week or month? The most frequent processes are the priority, since documenting them saves the most cumulative effort.
- Concentration: Does only one person run it, or could others do it too? The more knowledge is locked in one person, the more urgent the documentation.
- Impact: What happens if it's done wrong? Processes whose mistakes are costly or hard to reverse deserve documentation immediately.
Start with whichever process scores highest across these three criteria — not necessarily the one that's most complex or most visible.
A Practical Framework: From Idea to Written Procedure
Documentation doesn't need a complex system at the start. It needs a clear structure and a single owner.
1. Capture, Don't Write
Ask the person who performs the process to explain it out loud, or record themselves doing it. Don't ask them to "write a procedure" — ask them to explain what they do as if teaching a brand-new colleague who just joined.
2. The First Draft
Turn the recording or explanation into numbered steps. There's no need for elaborate formal language; what's actually needed is clarity. Every step should answer three questions: What do I do? How do I do it? And how do I know I did it correctly?
3. Testing with Fresh Eyes
Ask someone who has never performed this process before to follow exactly what's written, with no extra explanation from you. Where did they get stuck? Where did they need clarification? Those stumbling points are exactly the gaps in the document.
4. Revise and Approve
Revise the procedure based on the test results, then formally approve it with a date and a clear owner. Not because the signature itself matters, but because the date reminds you when it's time to review it again.
5. Scheduled Updates
Every procedure needs periodic review — not necessarily because it's wrong, but because the processes themselves evolve over time. Set the review date at the moment of approval: every six months for frequent processes, every year for exceptional ones.
How Do You Know Written Procedures Are Actually Working?
Documentation isn't an end in itself — it's a tool. The ultimate goal is for the organization to operate with greater independence and a stronger ability to learn from itself.
Positive signs:
- A noticeable drop in repeated questions
- Shorter onboarding time for new hires
- The team consults the written procedure without being told to
- The procedure gets revised based on real hands-on experience
Warning signs:
- The documents exist, but no one actually refers to them
- What's written differs from what actually happens on the ground
- No one even knows where these documents are stored
- The last update was more than two years ago
If you see these warning signs, know that the problem isn't documentation itself — it's the culture surrounding it.
When Do You Rebuild a Procedure, and When Do You Lock It In?
Not every procedure deserves to be preserved exactly as-is forever. And getting this wrong in either direction is costly: constant change erodes the team's trust in the whole system, while absolute rigidity turns a procedure from an enabling tool into a dead weight.
Rebuild the procedure when:
- The context it was designed for changes (new tools, a new team, new requirements)
- The procedure is followed but consistently fails to produce the intended result
- More than one person is informally tweaking it — a sign it's no longer working as it should
Lock the procedure in when:
- Results are stable and reliably repeatable
- The team consults it on its own, without being asked to
- Requirements haven't changed, and there's no real external pressure demanding revision
The simple rule here: a good procedure gets updated on a scheduled, deliberate basis — not on a whim.
The Bigger Idea
Organizations that make a point of documenting their procedures don't do it because they love paperwork and files. They do it because they've made a conscious decision to be smarter than the sum of their individual people — not merely equal to them.
When knowledge lives only inside employees' heads, the organization stays exactly the size of whoever happens to be there today, no more. When knowledge lives inside clear systems and documents, the organization accumulates and learns from itself, regardless of who arrives and who leaves.
A procedure isn't a constraint on competence — it's the memory that lets an organization grow without starting from zero every single time. Chaos — not documentation — is the real complexity we should fear.
If this article raised a question about your own organization, we would be glad to talk it through.
Talk to MIRAS →