Read a sample: 1. Succession Planning as a Management Practice
On Monday morning, a department head learns that the operations supervisor will be away unexpectedly. The supervisor coordinates a demanding workflow, handles exceptions, and knows which customer concerns require immediate attention. Several employees can perform pieces of the work, but no one is sure who can approve a schedule change, where the latest escalation list is stored, or which commitments are most urgent.
The department does not lack capable people. It lacks an agreed way to use their capabilities when a key role is unavailable.
This is the problem succession planning is meant to address. It is not limited to selecting the next chief executive or producing a confidential list of likely promotions. At the managerial level, succession planning is the continuing work of understanding which roles matter most, preparing for interruptions, and helping people build the capabilities the organization may need.
Done well, the process improves decisions before a vacancy occurs. It makes knowledge less dependent on one person, exposes development needs that daily work can hide, and gives employees a clearer path to meaningful experience. It also forces managers to confront uncomfortable questions: What would stop if this person left? What are we assuming someone else could do? Whose potential have we overlooked?
You do not need an elaborate talent-management system to begin answering those questions. You do need a disciplined way to gather evidence, make judgments, and revisit them as circumstances change.
In this book, leadership intelligence means the disciplined use of role, people, and risk information to make better development decisions.
Each part matters.
Role information describes the work that must be done: the outcomes a role produces, the decisions it makes, the relationships it relies on, and the knowledge required to perform it. A job description can be a useful starting point, but it may not reveal the decisions a capable incumbent makes quietly or the problems that arise when those decisions are delayed.
People information describes relevant capabilities, experience, interests, and development needs. It includes what employees have demonstrated in their work, not just what a manager believes they might be able to do. It also includes what remains unknown. An employee who has never had a chance to lead a project may have leadership potential, but the absence of evidence is not proof either way.
Risk information connects roles and people to the consequences of disruption. A role may be vulnerable because its work is time-sensitive, its knowledge is concentrated, its decisions require unusual expertise, or a departure would be difficult to cover. Risk also includes uncertainty: a manager may discover that an apparently secure role has no workable interim arrangement.
Leadership intelligence brings these strands together. Suppose a manager knows that a purchasing lead negotiates with suppliers, resolves shortages, and approves certain orders. The manager also knows that a senior buyer understands the products and has handled supplier problems, but has not yet managed a difficult negotiation. The risk is not simply that the purchasing lead might leave. It is that the team depends on negotiation and approval capabilities that have not been sufficiently shared.
A useful response might include documenting immediate approval arrangements, giving the senior buyer supported negotiation experience, and checking whether other employees are interested in related development. That response is more informative than writing “senior buyer is the successor” on a spreadsheet.
Leadership intelligence is not a claim that managers can predict who will succeed in every future role. It is a way to make current judgments more grounded, make uncertainty visible, and choose useful next steps.
A list of names can create the appearance of readiness. It can also conceal how little the organization knows.
Imagine that a department head names an experienced analyst as the likely replacement for the reporting manager. The analyst produces accurate work and is trusted by colleagues. Those are valuable observations. They do not, by themselves, establish whether the analyst wants a management role, can set priorities across competing requests, or has had experience addressing performance problems.
The list may be reasonable as a starting hypothesis. It becomes risky when the hypothesis is treated as a conclusion.
A working succession process asks the manager to explain the connection between the person and the role. What evidence supports the assessment? Which requirements have not been observed? What opportunity would help the person learn while also giving the organization better evidence? Who else should be considered?
The answers may change. An employee may develop quickly, decide that a different career path is more appealing, or demonstrate strengths that point toward another role. The work itself may change, making yesterday’s requirements less relevant. An external candidate may ultimately be the best choice for a vacancy. A sound plan accommodates those possibilities rather than defending an old prediction.
This distinction is especially important in smaller organizations. When there are few management layers, a potential successor may have limited opportunities to practice a target role. The answer is not to pretend that the experience exists. It is to create appropriately supported opportunities to gain it, while also preparing for the possibility that no internal candidate will be ready when needed.
Emergency coverage and long-term succession are related, but they answer different questions.
Emergency coverage asks: If this role became unavailable now, how would essential work continue?
Long-term succession asks: Who could potentially perform this role in the future, and what development would help them become a credible…