What your organization is quietly forgetting how to explain
Why understanding used to arrive free, why better documentation does not replace it, and how to measure what you have left in an hour.
Four questions this volume answers
Your organization understood its systems because people built them: you can't build something without learning how it fails. Automate the building and that stops, and because nobody was assigned the understanding, nobody reports it going. Normal operation hides the gap; an incident reveals it, at the worst possible time to measure.
For each system you wouldn't want to lose: who could explain it in a meeting right now, without reading anything first? Not the repository owner or whoever is on the rota. Keep the blank rows; a blank row is a fact with a date. And ask who owns the prompts and context files that took over from people.
Incidents where most of the time goes before anyone can say what they think is wrong; failures nobody can trace to a decision; documentation that is current and correct and still doesn't help, because it keeps conclusions and loses reasoning. Test on a quiet day: pose a plausible failure and time how long until someone offers a hypothesis.
Fund practices that make someone work out what they could have looked up: teardowns (an afternoon per system, the cheapest start), rotation, reviews that reconstruct the reasoning, and the posed-failure test. Not a better wiki. Name it as work, defend the output cost upward, and ask for the test result more than once, or decide openly that the incidents are survivable.
Your organization understood its systems because people built them. That has stopped.
Nobody was ever assigned to understand your systems. It came attached to the work: you cannot build a thing without learning how it fails. Automate the building and the side effect stops arriving, and because nobody was assigned it, nobody is positioned to report that it has.
This volume is twelve short steps on what that costs, why every instrument you have says you are fine, and what it takes to produce understanding on purpose. It assumes you have read nothing else in this series.
The one page to read if you read one
The deficit is invisible for as long as normal operation lasts, because knowing where to look is genuinely sufficient for normal operation. It becomes visible during an incident, when the only thing that helps is somebody who can explain the system.
Which means the only instrument that measures this is an incident — unscheduled, under load, in front of people. The most useful page here is the one that shows you how to take the measurement at a better time, on purpose, in an hour.
What you can do afterward
Write down what your organization knows as a list of names, and find the blank rows. Tell a documentation problem from a comprehension problem. Run a test that produces a number about your own team. And explain to your own leadership why this particular cost cannot be delegated downward.
The questions and the four practices that work are collected on one page you can print.