Built to Need You
Structures That Can't Function Without You
When the system can't lose you, that's not loyalty. That's a system problem.
Some setups are designed—accidentally—to require a specific person to function. The knowledge lives only in their head. The access credentials only they hold. The authority only they can exercise. The capability only they possess. When that person leaves, the whole thing stalls.
This isn't a compliment. It's a dependency that was created through five specific mechanisms: the knowledge is concentrated in one person, access is controlled by one person, authority is tied to one person, capability exists only in one person, and justification loops make the setup seem necessary. This book explains how dependency gets baked into your job and gives you 12 moves across 3 move families to get the knowledge out of your head, spread access and decision-making across the team, and build capability in others—so the system runs without requiring you to be present.
What's Inside
- The System That Cannot Lose You — Why "you're indispensable" is a system problem, not a compliment
- How Dependency Is Manufactured — The five mechanisms: knowledge, access, authority, capability, justification
- Why Relief Doesn't Work Here — Delegation, hiring, documentation, rest, stepping back—and why all five fail
- Map the Dependency — Produce the Dependency Map diagnostic
- Knowledge Externalization — Extract knowledge dependency
- Access and Authority — Extract access and authority dependency
- Capability and Collapse — Extract capability and test all extractions
Who This Is For
- Anyone the system literally cannot function without—and who knows it
- Founders, leads, or senior staff who can't take leave without everything stalling
- People who've been told they're "irreplaceable" and recognize that as a trap
- Managers trying to build teams that don't collapse when one person is absent
What Shifts After Reading
You stop hearing "we can't do this without you" as praise and start hearing it as a system failure report. The question changes from "How do I keep up?" to "What knowledge, access, authority, and capability currently lives only in me—and where should it live instead?"
You'll have a Dependency Map showing exactly what the system requires from you, and a set of moves that systematically move each dependency out of you and into documentation, shared access, distributed authority, and transferable capability.