THE IDEA
The small thing everything depends on
In ecology, a keystone species is one whose impact on the system is disproportionate to its abundance. Remove it and the ecosystem transforms. Sea otters keep sea urchin populations in check; remove the otters and urchins devour the kelp forests, which sheltered fish, which fed birds. One species, when removed, triggers a cascade that reshapes the entire system.
The concept transfers directly to human systems. A keystone role in an organisation - the person who connects departments, who holds institutional knowledge, who mediates conflicts - can be invisible in the org chart and essential in practice. Remove them and functions that seemed unrelated start failing, because they were all, invisibly, passing through that one node.
What makes keystones dangerous isn’t their importance - it’s the gap between their importance and their visibility. A keystone species doesn’t look important. It’s not the biggest animal or the most numerous. A keystone person doesn’t look important. They’re often not the most senior or the most celebrated. But the system is structured so that an extraordinary amount passes through them. Their removal doesn’t just create a gap. It triggers a reorganisation that affects parts of the system nobody connected to them.
IN PRACTICE
The node nobody noticed until it was gone
An office administrator retires. She was never in the leadership meetings. Her title was modest. Her salary was average. Within weeks, the office starts to dysfunction. She was the person who knew how to navigate the procurement system, who remembered the deadlines nobody had in their calendar, who mediated small conflicts before they became big ones, who connected the new hires to the people they needed to know. She was a keystone. Her role wasn’t described in any document. It was woven into the fabric of how the organisation worked.
A coral reef supports hundreds of species. The coral itself is the keystone - it provides the physical structure that everything else depends on. When coral bleaches and dies, the fish lose habitat, the algae take over, the food chain collapses. The reef doesn’t gradually decline. It regime-shifts to a completely different state. The keystone wasn’t just important. It was the infrastructure the rest of the system was built on.
A community loses its gathering place - the pub, the community centre, the local shop where people met. The building’s function (selling drinks, hosting events, selling groceries) was unremarkable. Its system function (connecting people, enabling informal coordination, maintaining social bonds) was keystone. Its closure doesn’t just remove a service. It fragments the community’s social infrastructure.
WORKING WITH THIS
Identifying and protecting your keystones
Ask: if this person, role, or element disappeared tomorrow, what else would break? If the answer is “many things that don’t seem obviously connected to it,” you’ve found a keystone. Protect it. Build redundancy around it. Don’t let its low visibility translate into low investment.
Map dependencies, not just functions. The org chart shows reporting lines. The actual system runs on connections that no chart captures. The person who connects departments. The process that enables three other processes. The tool that everyone depends on but nobody owns. These are potential keystones.
The most important intervention is reducing keystone dependence. Not by removing the keystone, but by building backup - cross-training, documentation, shared relationships, redundant systems. A system that depends on a single keystone is structurally fragile, no matter how reliable that keystone is. Building resilience means ensuring that no single removal can cascade.
THE INSIGHT
The line to remember
The most important element in a system is often the least visible one. You discover keystones by their absence, and by then it’s too late to protect them.
RECOGNITION
When this is in play
You’re seeing a keystone when one person’s absence causes disproportionate disruption. When a single point of failure turns out to be connected to far more of the system than anyone realised. When a “minor” change triggers a cascade of unexpected consequences. When the question “what would happen if we lost X?” produces a much longer answer than expected.