Related: the practical companion to this is The Scaffolding Prescription — what actually gets distributed when you stop hoarding is scaffolding, not just information.
For a long time I believed knowing something other people didn't was a form of security. Keep the one thing nobody else understands close to your chest, and the organization can't run without you. It took me an embarrassingly long time to see the actual shape of that trade: it doesn't make you secure. It makes you capped. You cannot be promoted past the thing only you can do. You become the thing the org has to route around instead of the thing it builds on top of.
The Security Illusion
Software engineering has a blunt name for this: the bus factor — the number of people who'd have to get hit by a bus before a project stalls completely. A bus factor of one means one person holds the whole thing together, undocumented, in their head, and everyone treats that as impressive right up until that person takes a vacation. A high bus factor — the knowledge spread wide, documented, boring, redundant — is what a healthy system actually looks like, and it correlates with almost nothing about how replaceable any individual on that team feels. Replaceable and expendable are different words. A team with a bus factor of five isn't a team of five interchangeable nobodies. It's a team where the work survives the person, which is the only kind of work that ever gets bigger than one person's hours in a day.
Holding the keeper-of-knowledge position feels like leverage. It's the opposite. Leverage is what you get when something you built keeps working without you standing next to it.
The Trail You Leave
Here's the tell that actually separates the two kinds of people in any organization: what they leave behind when they move on. Leaders are recognizable by what remains after they've left the room — people who got better under them, documentation that survived them, systems that don't wobble the week they're out sick. Followers — and I don't mean that as an insult, I mean it structurally — are recognizable by what they take with them instead: the one undocumented process, the login only they remember, the client relationship nobody else was ever looped into. One of those trails compounds. The other one evaporates the day the person walks out the door, taking the only copy of the knowledge with them.
This isn't really about generosity. It's about which kind of asset you're actually building. A hoarded fact is worth exactly what it's worth to you, once, as long as you're in the room. A distributed fact is worth what it's worth to everyone who now has it, forever, whether you're in the room or not. Only one of those scales.
Give It Away to Get It
There's an old principle, worn smooth from use in every field that's ever depended on people carrying knowledge forward instead of just accumulating it for themselves: you keep what you actually have only by handing it to someone else. Not a paradox — a mechanism. The teaching forces you to actually understand the thing well enough to make it make sense to someone who doesn't have your context. Half of what people think they know falls apart the moment they try to explain it clearly, and that fallout is information — it tells you exactly where your own understanding was thinner than you thought. Teaching isn't a tax on your expertise. It's a stress test for it, and you come out the other side knowing the material better than you did going in.
John Maxwell has a version of this in his leadership work that lands the mechanism precisely: to add growth, lead followers. To multiply, lead leaders. Leading followers gets you addition — you, plus whatever your own two hands can do. Leading leaders gets you multiplication — every person you actually develop becomes another source of the thing you were trying to produce in the first place, running in parallel, without you in the room. Addition is what hoarding caps you at. Multiplication is the only thing on the other side of giving it away.
The Redundancy Requirement
Here's the part that actually explains why hoarding caps a career instead of just feeling unfair: every real level of advancement requires making your previous level's skills redundant in your own hands. An individual contributor who becomes a manager has to stop being the best coder in the room and start making everyone else better at coding — if they don't, they're just an expensive IC with a new title, doing the old job worse because now they're also in meetings. A manager who becomes a director has to do the same thing again, one level up. The pattern doesn't stop. At every level, the actual job is working yourself out of the job below it, on purpose, so there's room to do the job above it.
Hoarding is the opposite move at every one of those thresholds. It's staying essential to the old job specifically so nobody can promote you past it — and it works, in the narrowest, worst sense. You get to stay needed. You also get to stay exactly where you are, because the organization structurally cannot move you off the one thing only you can do.
What to Do Right Now
Pick one thing this week that only you know how to do — a process, a system, a piece of context nobody else has. Don't protect it. Document it, teach it, or better, build the thing that does it without you (a script if it has to be, an API if it's going to matter — same principle as everything else in this scaffolding series). Then notice what happens to your own bandwidth once it's off your desk permanently. That's the whole test. Addition feels like control. Multiplication feels like loss, right up until you notice what you're now free to build instead.
— J.P. Howlett
Related:
- The Scaffolding Prescription — what you're actually distributing when you stop hoarding: not facts, structure.
- Kingdom: AI — the same "build the thing that outlives the moment" principle, applied to system architecture instead of people.
Sources
- Bus factor — the software-engineering metric this piece's "security illusion" section is built on.
- The Law of Explosive Growth — John C. Maxwell, "The 21 Irrefutable Laws of Leadership" — "to add growth, lead followers; to multiply, lead leaders."