Forge insight 001 / Leadership dependency
When one capable leader becomes the operating system.
A sports operation can look efficient precisely because one person is absorbing the complexity. That is performance, but it is not resilience.
Leadership dependency develops when important decisions, relationships, routines and exceptions repeatedly route through the same person. The leader becomes the fastest way to get things done, so the wider operation learns to use them as infrastructure.
The warning sign is not simply that the leader is busy. It is that normal delivery becomes slower, less certain or less consistent when that person is absent.
The test: if the leader disappeared for two weeks, what would stop, stall or require guessing?
Four signals
Routine approvals climb upward
Staff wait for the leader to resolve decisions that should have clear owners or rules.
Knowledge lives in memory
Contacts, exceptions, timelines and decision logic are known rather than captured.
Problems are rescued, not removed
The same operational failures recur because capable people keep absorbing them.
Absence creates uncertainty
People can execute tasks, but hesitate when the situation falls outside the normal script.
One useful move
Run a dependency audit before writing another procedure.
For one working week, record every issue that requires a specific person to remember, approve, explain or rescue it. At the end, classify each dependency: decision right, missing information, unclear ownership, undocumented process or relationship knowledge. Fix the repeated dependency, not the individual incident.
Forge note: this is an operating framework, not a benchmark claim. Forge will publish comparative findings only when sufficient diagnostic evidence exists.
Measure the system