Succession Planning and Knowledge Transfer
Succession planning and knowledge transfer ensure that critical organisational knowledge, capabilities, and leadership do not disappear when key people leave. In technology teams, knowledge concentration — where one person is the sole expert on a critical system — is a significant operational risk and a common source of "bus factor" anxiety.
The Bus Factor Problem
The "bus factor" (or lottery factor) asks: how many people would need to be hit by a bus (or win the lottery and quit) before a critical system or process breaks? A bus factor of one — where one person is the sole keeper of essential knowledge — is a serious organisational risk. It also makes that person impossible to promote or take on leave.
Reducing Knowledge Concentration
- Documentation: Systems, processes, and architectural decisions should be documented — not just in one person's head
- Pair programming and code review: Working together on code spreads knowledge naturally
- Rotation: Deliberately move engineers across systems and services — spreads knowledge, builds empathy between teams
- Architecture Decision Records (ADRs): Document why decisions were made — allows successors to understand context, not just the current state
Leadership Succession
Identify potential leaders early and deliberately develop them. A leadership vacuum when a senior person leaves unexpectedly creates significant instability. Even if no immediate succession is needed, developing leadership capability in your team is a good investment in retention and capability.