What Cannot Be Delegated
Not all valuable knowledge becomes more abstract as tools improve. Some of it becomes more specific, tied to one system's history and to people who have watched it fail. Under time pressure the machine has the events, the retries, the identifiers and the timestamps. It does not know which piece of state will matter ten minutes from now.
Framework 4 of 10 · Chapter 4: What Cannot Be Delegated
The comfortable assumption is that as tools get stronger, the remaining human work climbs toward the abstract: architecture, strategy, taste. Some of it does. A significant part of it goes the other way.
It becomes more specific. Tied to this system, this failure two years ago, this one rule that is deliberately lopsided and was never commented. That knowledge acts before it can be explained, which is the whole problem with it.
In an incident, the difference between having the data and having the judgment is narrow and total. Everything is logged. What is not logged is which piece of state is about to age out and matter.
When it applies
Under time pressure, where the cost of being wrong lands before anyone could have written the reasoning down. Incidents. Migrations with a cutover. Anything where the clean-looking answer is available immediately and could still be wrong.
How to run it
- After an incident, before the writeup, answer one question: what did I know that was in no system anywhere?
- Decide whether it can be written down, and where it would have to live to be found under pressure.
- If it genuinely cannot be written, if it is contact knowledge rather than stated knowledge, name who else is getting that contact. If the answer is nobody, that is a staffing risk with a date on it.
Most of what feels undelegatable is undelegatable only because nobody wrote it down. Some of it is real. Sorting the two is the work.
Where it fails
It is invisible in output metrics. None of this shows up in throughput, and the person holding it often looks slower than the people who do not.
It cannot be hired quickly. It is accumulated by contact with one system over time, which means the market cannot supply it on demand at any price.
It gets treated as permanent. Concluding that judgment is unwritable is the comfortable version. Most of it can be written down, and refusing to try is the same mistake in the other direction.
Practice
Take your last incident. Write down the one thing you knew that was in no system. Then decide where it would have had to live for someone else to find it that day, and put it there.