D01 - Process Documentation Coverage
< All Dimensions | Dimension D02 >
Definition
Whether the knowledge required to run your operation lives in documents people can find and use or in the heads of people who might leave.
Why It Matters
Undocumented processes are not free. They are a standing tax paid in repeated questions, inconsistent execution, and slow onboarding that compounds over time. The cost is invisible until the person holding the knowledge is unavailable.
The Diagnostic Question
Hand one of your five most-used SOPs to someone who has never executed the process. Watch them attempt it without help. Note every step where they pause, re-read, or ask a question. Each one is a required document revision.
If three or more of your five most-used processes fail this test, the problem is structural — not a content quality issue and not a training gap.
What This Dimension Looks Like When It's Working
- Every high-frequency process has a numbered, verb-first checklist with a named owner, a documented review date, and a completion definition — not a prose narrative that requires interpretation.
- New hires execute their five most common tasks independently within their first two weeks using documentation alone, not by asking the person next to them.
- When a team member changes roles or leaves, their process knowledge transfers through the document rather than through their successor watching them work.
- Documentation lives inside the tools where work happens, not in a separate wiki that requires three application switches to access.
The Most Common False Positive
Having 83 documents in a wiki is not process documentation coverage.
Documentation that cannot be found in under 90 seconds, is materially out of date, or requires reading more than 400 words to find a 20-word answer fails the coverage standard regardless of its existence.
The gap is not between having documentation and not having it. It is between documentation that gets used and documentation that gets ignored.
The Failure It Prevents
Target Canada's $4.1 billion net loss is partly traceable to an operations team learning its processes from an ERP system simultaneously operating on corrupted data — because no process documentation existed before go-live to verify the system's configuration against operational requirements.
Knight Capital Group's $440 million loss in 45 minutes is partly traceable to deprecated trading code left in a production system because no documentation standard required a registry of code pathways with their status and scheduled removal date.
What This Dimension Requires And Enables
D01 is a foundational dimension.
It is a prerequisite for D02 — Backup coverage only works if the process can be documented well enough for a backup executor to follow independently.
It is a prerequisite for D09 — Onboarding effectiveness requires documented processes for new hires to execute from Day 1.
It is a prerequisite for D06 — Major system implementations require process documentation to precede configuration, not follow it.
Register for HQ Score - Early Access
What early access includes:
Immediate: OFA-02 (Southwest Airlines), OFA-03 (Knight Capital Group), and The Operations Leader's AI Evaluation Framework — subscriber-exclusive content available from the moment you subscribe.
At HQ Score launch: You are notified the day the HQ Score goes live, before the general announcement.
Note: You can access subscriber-exclusive content on Headroom HQ for free by registering for early access. You can login to Headroom HQ website with the same email you have used for early access registration to access the free subscriber-only content.
Terms
Issues
Operational Failure Archive
Industry Articles
Verdicts
Apply
- The Documentation and Process Bundle
- The SOP Library Audit and Rebuild Kit
- SOP Library Audit Working Example
Register for HQ Score early access to find out how many of your most-used processes are genuinely executable by a new hire with no prior knowledge →