Resilience documentation that nobody reads (and how to fix it).
The documentation problem is a positioning problem in disguise. Three patterns from working with regulated industries.
Every regulated company has a shelf — literal or digital — of resilience documentation that satisfies an auditor and helps no one. The plans are thorough, current, and unread. When an incident hits, the people responding rarely reach for the binder; they lean on each other.
This gets treated as a discipline problem: if people would just read the plan, we'd be fine. It's actually a positioning problem. The documentation was written for the wrong reader.
Pattern one: it's written for the auditor.
Most resilience documentation is optimized to prove compliance, so it's organized around regulatory categories rather than around what a human needs at 2 a.m. The responder wants the one page that tells them what to do in the next ten minutes. Write for that person first, and the auditor is still satisfied.
Pattern two: it confuses completeness with usefulness.
Thoroughness works against retrieval. A plan that covers every scenario is a plan nobody can navigate under stress. The most useful resilience documentation is aggressively edited — short, scannable, and built around the decisions a responder has to make. Completeness lives in the appendix, while the front page is reserved for action.
Pattern three: it's static in a moving situation.
A document is a snapshot, while an incident keeps moving. The teams that respond well don't depend on the plan to be perfectly current; they've rehearsed the motion enough that the plan works as a reference. Good documentation supports muscle memory, and it works best as a complement to it.
- Lead every plan with a one-page action card; everything else is reference.
- Organize around the decisions a responder actually makes.
- Rehearse the retrieval. If people can't find it under mild pressure, it effectively doesn't exist.
Resilience documentation earns its keep only when a responder can find the one page that matters under pressure.
Documentation nobody reads comes down to a failure to decide who it was for. Decide that, edit ruthlessly, and rehearse the rest.