Leadership readiness before growth asks whether the leadership system can carry the next version of the business. Current performance matters, but it does not settle the question. A team can be highly capable in one environment and still be unprepared for the decisions, pace and complexity that the next stage will create.
I see this most often when a company is about to cross a meaningful threshold. Revenue is moving. Hiring is accelerating. A new market is opening. The board is asking for a more ambitious plan. Everyone is busy, which makes the readiness question easy to postpone. Then the new stage arrives and the organisation discovers that the leadership team was built for the previous set of problems.
Readiness is not the same as performance | leadership readiness
Past performance gives you useful evidence. It does not give you a complete answer. A leader may have delivered strongly in a familiar environment where the team was small, the founder was close and the consequences of delay were limited. The next stage may require them to lead through ambiguity, build leaders beneath them, make decisions across functions and hold a wider set of stakeholders.
That is a different test. Promoting someone because they succeeded in the last operating model is reasonable. Assuming they will succeed in a larger one without checking the new demands is where the trouble begins. Readiness is a relationship between a person, the work and the system around them.
| What you are testing | The weak question | The useful question |
|---|---|---|
| Decision range | Has this leader made good decisions? | Can this leader own the new categories of decisions the next stage creates? |
| Span of influence | Does the team respect this leader? | Can this leader improve the capability of people who do not report directly to them? |
| System reliance | Can this leader deliver under pressure? | Can the organisation keep delivering without this leader personally carrying every detail? |
| Future capacity | Has this role worked so far? | Will this role still make sense when the company is twice as complex? |
| Team architecture | Do the executives get along? | Can the team disagree, decide and hold one another to the decision? |
The five dimensions of leadership readiness before growth
Readiness is assessed across five dimensions. They are connected, but they are not interchangeable. A leader may have strong judgement and weak delegation. An executive team may be aligned on strategy and weak at cross-functional execution. The purpose of the assessment is to see the pattern, not award a single flattering score.
The readiness architecture
- Judgement: Can the leader make sound calls with incomplete information, explain the reasoning and change course without protecting their ego?
- Scale of influence: Can the leader improve outcomes through people, teams and functions beyond their direct control?
- System-building: Can the leader create routines, decision rules and successors so performance does not depend on personal rescue?
- Pressure identity: What happens to the leader's behaviour when speed, scrutiny or uncertainty rises?
- Collective contribution: Does the executive team act as a system, or do strong individuals still protect their own functions?
Judgement
Readiness starts with judgement because the next stage will present decisions that cannot be solved by experience alone. Ask leaders to describe a decision where the information was incomplete, the trade-off was real and the outcome was not guaranteed. Listen for how they framed the choice, what they knew, what they assumed and what they did after the decision.
I care less about whether the outcome was positive than about whether the reasoning held up at the time. Good results can come from poor decisions. Bad results can follow a well-made call in a difficult market. A readiness review should not reward luck or punish honesty about uncertainty.
Scale of influence
A leader who produces excellent work through a small team is not automatically ready to influence a larger organisation. The next question is whether their judgement travels. Can they set a standard that other leaders use? Can they resolve a disagreement between functions without taking over? Can they make a colleague stronger without needing formal authority over that person?
This is where many readiness reviews stay too close to the org chart. Growth makes the seams between functions more important. A leader may be ready for a larger role only when they can carry responsibility across those seams, not when they have mastered their own department.
System-building
System-building is the difference between being the person who saves the week and being the person who makes saving the week less necessary. Ask what the leader has made repeatable. Which decisions can the team now make without escalation? Which routines create useful feedback? Who can step into the work when the leader is away?
A leader who stays indispensable may be working hard and still creating a growth constraint. The test is not whether they care. The test is whether their way of caring has become a structure other people can use.
Pressure identity
Growth increases the distance between an action and its consequences. A decision may affect several teams, a major customer or a public commitment. Under pressure, some leaders become controlling. Others become vague and call it giving people room to decide. Some move too quickly because delay feels dangerous. Others gather more information long after the decision is clear.
The useful question is not whether a leader feels pressure. Everyone does. It is what their pressure does to the people and decisions around them. The 5D Model gives this dimension a place beside alignment, execution cadence, capability pathways and cultural reinforcement. Identity under pressure changes the system, whether the leader intends it or not.
Collective contribution
An executive team can look united because nobody challenges the plan in the room. That is agreement, not necessarily alignment. Readiness requires a team that can surface disagreement, decide at the right level and support the decision once it is made.
I look for the subjects that never appear on the agenda. Which function is carrying a risk alone? Which leader is waiting for the CEO to settle a disagreement? Which issue gets discussed privately but not named collectively? Silence is data. It tells you where the current team may be avoiding the work the next stage will require.
How to run a readiness review
A useful readiness review does not begin with a rating form. It begins with the next stage of the business. Define the work first, then test whether the leadership system can do it.
- Describe the next stage in decisions: Write down the decisions the business will need to make more often, at greater speed or with wider consequences. Avoid vague phrases such as scale and growth.
- Map current ownership: For each decision, identify who owns it now, who contributes and where the decision returns to the CEO or executive team.
- Gather three kinds of evidence: Use the leader's account, the team's observed experience and the actual operating record. No single source shows the whole picture.
- Separate a person gap from a system gap: Ask whether the issue would remain if the current leader changed. If it would, the organisation needs a design response rather than a coaching response alone.
- Set a readiness commitment: Name the one capability or structural change that must be visible before the next stage begins, then review it on a fixed cadence.
How to run the review without turning it into theatre
Keep the review close to a real decision. Choose one change the next stage will require, such as entering a new market, combining two functions or replacing a founder-led approval habit. Ask the leadership team to describe the decisions, capabilities and relationships that change will demand. Then collect examples from the last ninety days that show how each person handled a comparable demand. The point is not to create a new form. The point is to see whether the current system already behaves like the next version of the organisation.
Use more than one vantage point. A self-rating can show what a leader notices. A direct-report interview can show what the leader makes possible. A peer review can reveal where hand-offs break. Operating evidence can show whether decisions travel at the right speed. These views will not match perfectly, and that is useful. The gaps between them often identify the work that a polished executive discussion hides.
Make the evidence reviewable. For each dimension, record the observation, the business consequence and the next test. If the issue is judgement, define the next decision and the information that must be weighed. If the issue is system-building, identify the routine that should work without personal rescue. If the issue is collective contribution, name the disagreement that must be handled in the open. A clear test turns a broad concern into a manageable commitment.
What to do with a mixed result
Mixed results are normal. A leader may show strong judgement and weak delegation. Another may build excellent systems but avoid the conflict needed to align peers. Do not average these findings into a single score and call it an answer. The next stage may make one weakness much more consequential than another. Rank the gaps by the decisions they could block, the people they could overload and the time available to close them.
Then choose an intervention that matches the gap. A decision-rights problem needs clearer authority. A capability problem needs practice, feedback and a defined application. A relationship problem needs a conversation that changes the working agreement. A role-design problem may need a different span, a stronger partner or a revised remit. Coaching can support several of these moves, but it cannot replace a missing operating decision.
The best readiness review gives the organisation a more honest starting point for growth. It shows where a leader can carry more, where a system is still carrying too little and where the next stage will expose an assumption that has gone untested. If you want to map those gaps, begin with the Leadership Capability Diagnostic, review the Leadership Capability Architecture, or explore Leadership Assessments.
If you are testing readiness before growth, compare the team’s evidence with the executive-team coaching perspective and use the Leadership Capability Diagnostic to locate the next constraint.
A readiness review is strongest when it uses work the business is genuinely about to face. Select a small set of future decisions, ask leaders to explain the judgement they would apply and examine the support the system gives them. Include the voices of peers and the people who depend on the decisions. The result should be a practical sequence of development, role design and operating changes, not a ranking that pretends context can be removed from leadership.
The review also needs a boundary around what it is not trying to prove. It is not a prediction of who will be promoted, and it is not a verdict on a leader's worth. It is a disciplined look at the match between future work and current conditions. When the evidence is mixed, the response can be staged: give the leader a defined stretch, change the support around the role and review the result before making a larger appointment decision.
The final output should be a set of decisions the business can act on. Which leader needs a stretch assignment? Which role needs redesign? Which capability should be built collectively? Which risk needs an operating control rather than a course? Keeping those decisions together prevents the review from becoming a label that follows people around. It also respects the fact that readiness is shaped by the work, the system and the support available at the time.
A readiness decision should be revisited after the business has tested the next-stage work. Evidence changes when roles, customers and pressure change. The review can therefore combine a current view with a small set of observable experiments: a leader carries a larger decision, a team takes on a new coordination demand, or a successor leads through a difficult trade-off. Review what happened, what support was needed and what the organisation learned. This keeps the process developmental without losing the seriousness of the appointment decision.
The review should leave leaders clearer about the next experiment, the next support decision and the evidence that will change their mind.
A readiness review also protects leaders from being judged against an invisible standard. The business can name the new decisions, the support available and the signals that matter before asking someone to carry the work. That makes development more honest and appointments more defensible. It acknowledges that leadership is shaped by context, while still insisting that the organisation learn whether its current design can meet the next demand.
Review readiness against the next stage
The review should use decisions the business is genuinely about to face. Connect it with building a scaleup leadership team, why capability stops scaling with growth and measuring leadership capability across an organisation to separate current performance from future capacity.
A practical reading path
This topic sits beside three decisions that often get separated in practice. Read building a leadership pipeline in a growth-stage company; what causes leadership development programmes to fail; the team collaboration and effectiveness framework. The comparison is useful because it keeps the argument in this article specific: which decision is changing, who owns it and what evidence would show that the change has travelled into everyday work? Use the linked pieces as contrasts, not as a substitute for the judgement required here.