FM-13: Capability Atrophy
A pattern. The structure holds. The skill inside it quietly drains.
Justin R. Greenbaum · The Lexicon · July 2026
A senior engineer is the only person who understands the pipeline that runs the business, and she wants it documented before she leaves, but every sprint is full of shipping, so the knowledge walks out with her, because the system was built to extract her output and never to transfer what she knew. A new analyst wants to understand why the model works the way it does, but the runbook only tells him which buttons to press, so he follows the steps without grasping them. A team lead’s group runs the standard case flawlessly but freezes on anything novel, and because novel cases are rare, the gap never shows on a dashboard. A department head wants to keep the hard, judgment-heavy work in house, but a vendor will do it cheaper this year, so the competence gets outsourced, because the saving lands on this year’s budget and the loss on no one’s.
None of these people are failing. Each one is watching a capability leave the building faster than anyone is rebuilding it.
This has a name. It is Capability Atrophy.
Here’s the pattern. An organization that spends every quarter and invests in no year stops exercising the capabilities the future depends on, and the muscles it never uses quietly waste. The structure stays intact, so nothing looks lost. But the capability inside drains: skills decay, judgment weakens, and work becomes procedural rather than adaptive. The system still functions, now only within a shrinking range of conditions, fine on the cases it has seen and brittle on the ones it has not. Efficiency pressure rewards repeatability over mastery, so as experienced people leave, process is layered in to compensate, and over time process replaces understanding instead of supporting it. The loss never announces itself. It gets read as the system finally running smoothly.
Codifying masquerades as maturity. The team that turns every judgment call into a checklist is called disciplined. The function that swaps experienced people for documented procedure is called scalable. The manager who removes the dependency on one expert is praised for reducing risk. The signal the system reads is maturity. The condition underneath is a slow hollowing-out, an organization that still delivers but no longer learns.
What Capability Atrophy gets mistaken for is what keeps it alive. Operational excellence. Scalability. Professionalization. Risk reduction. Each reading treats the loss as a sign of a system growing up, so the repair is to codify more: another runbook, another control, another judgment standardized away. None of it rebuilds the skill that is draining, so the drain continues under cover of looking mature. These readings are how Capability Atrophy survives contact with the post-incident review, the one moment built to ask why a function broke, most easily spent adding a checklist instead of restoring what the checklist replaced.
The pattern recurs and changes costumes. In one company it is a manufacturer that offshores the engineering it once did in house until no one left can judge whether the vendor’s work is any good. In another, a bank so dependent on documented procedure that a single retirement takes a capability no one can reconstruct. In a third, an agency that has standardized its casework so thoroughly that a case outside the template stalls, because no one still holds the judgment the template was built from.
The conditions are structural, not behavioral. More training hours do not interrupt it; hours spent memorizing the procedure deepen the dependency on it. Hiring stronger talent does not interrupt it; strong people poured into a structure built to extract output and skip transfer atrophy at the same rate as everyone else. Replacing the person who left does not interrupt it; the replacement inherits a runbook and none of the tacit knowledge the runbook was written to stand in for.
What interrupts it is structural. Run apprenticeship models, so tacit knowledge transfers person to person before it walks out the door. Protect time for skill development that shipping is not allowed to raid. Remove abstractions between decision and consequence, so the people deciding still feel what their judgment costs and stay sharp on it. Treat tacit knowledge as a first-class asset, tracked and maintained like any other piece of infrastructure. Where core competence has already been handed out to keep a function cheap, the fail-safe is to stop outsourcing core competence and pull the capability back inside.
When Capability Atrophy has a name, the options change.
The analyst pressing buttons he does not understand stops calling it onboarding and sees a role built to run a process, not to learn a craft. The manager above stops praising the clean runbook and asks what the team can no longer do without it. The executive stops reading stable output as a healthy function and asks what the function can no longer handle. The board stops accepting “we have professionalized” and asks what capability that professionalization quietly spent.
Naming does not fix. Naming changes what can be seen. What can be seen is what can be acted on.
If any of this feels familiar, it has a name and a taxonomy.
The canonical definition of FM-13, including its early warning signals, common misdiagnoses, and recovery conditions, is at dripractice.com/fm/fm-13.
A role-specific view of how the same pattern looks from the HR seat is at dripractice.com/lens/hr.
A five-minute diagnostic that runs entirely on your device and never leaves it is at dripractice.com/diagnose.
Next in The Lexicon: FM-14, Narrative Collapse. When the work goes procedural and the skill drains out of it, the story a company tells about why any of it matters starts to thin. FM-14 is what happens when execution continues and the meaning behind it quietly goes.
Subscribe to The Lexicon.