Is your leadership team ready for the next growth stage? In my view, a leadership team ready to scale is one that can carry more decisions without making the organisation dependent on one person, one meeting or one heroic recovery. You can test that in an afternoon with the five-load scorecard below, which scores decision bandwidth, coordination, depth, adaptability and recovery from 0 to 2 each.
Readiness shows in how the team handles competing priorities, incomplete information, cross-functional trade-offs and the loss of a familiar leader, not in the confidence of a strategy deck. Scale adds load before it adds clarity. More customers create more exceptions. More managers create more interpretation. More locations create more distance between a decision and the people who experience its consequences. A team that worked well in a smaller environment may need a different operating rhythm before it can carry the next stage safely.
Is Your Leadership Team Ready to Scale? Readiness Is a System Property
It is tempting to assess each executive and add the scores together. That misses the work that happens between people. A team can contain excellent leaders and still be poor at integration. It can have a strong CEO and still lack a second layer of judgement. Readiness belongs to the pattern of decisions, relationships and routines the team creates together.
McKinsey's research on the scale-up conundrum points the same way. It describes the transition from founder-led, charismatic growth to a more industrialised approach, names the top team as the final and arguably most important factor, and warns that a company can hit its targets and make all the right moves until stagnation has already set in. That last point is why a readiness test has to look at how the system behaves under load, not at results to date.
The test is also contextual. A team may be ready for geographic expansion but not for a product portfolio. It may be ready to hire managers but not to change a founder-led approval habit. Define the next load before deciding whether the team is ready to carry it.
| Load to test | What readiness looks like | Warning sign |
|---|---|---|
| Decision load | Decisions move to the right level with context intact | Routine choices return to the CEO |
| Coordination load | Functions resolve trade-offs around a shared outcome | Teams push their own measures |
| Leadership depth | More than one person can carry a critical decision | A single executive is the permanent translator |
| Change load | The team can alter the operating model while work continues | Every change becomes a special project |
| Recovery load | The team learns from disruption and changes the system | The same crisis is solved repeatedly |
The Five-Load Scorecard: Score Your Leadership Team Ready to Scale from 0 to 10
Score each load 0, 1 or 2, using evidence from the last quarter and not impressions. Do it with two or three people who see the team from different seats, such as the CEO, a function head and a senior manager, and compare scores. The scale is my own working tool, built from the five loads in this article. It is illustrative and has not been validated as a measurement instrument.
| Load | 0: not yet | 1: partly | 2: ready | Your score |
|---|---|---|---|---|
| Decision bandwidth | Routine decisions queue at the CEO or one meeting | Some decisions have moved down, but exceptions still queue | Most decisions are made at the right level and the CEO sees exceptions only | |
| Coordination quality | Cross-functional conflicts go to the CEO to settle | Leaders settle some conflicts but defend the function first | Leaders name the trade-off and leave with one owner | |
| Leadership depth | Removing one senior person stops a live decision | The next layer can describe the context but not decide | The next layer can describe, decide and learn from the result | |
| Operating adaptability | Every change becomes a special project | Change happens, but accountability slips while it does | Routines and roles change while accountability holds | |
| Recovery learning | The same crisis returns | Lessons are named but the system does not change | Each miss changes a rule, a role or a routine | |
| Total (0 to 10) |
| Total | What I would conclude | What to do next |
|---|---|---|
| 0 to 3 | Not ready for added load | Pick the lowest-scoring load, repair it, and hold new commitments until it moves |
| 4 to 6 | Ready for a bounded step with named repairs | Choose the two lowest loads, name an owner for each and re-score in a quarter |
| 7 to 8 | Ready for most loads | Run the pressure scenario below on the weakest load before committing |
| 9 to 10 | Ready, provided the scores are evidence | Check depth first: a high score with a single translator is not a high score |
Repeat the scorecard each quarter and keep the scores. In 2023 Cornell's CAHRS benchmarked how companies measure leadership capability. All 14 companies in the benchmark used a leadership measurement tool, and most found the change steep and took at least a year to scale it. The lesson for a scorecard like this is to expect it to take a few cycles before the numbers are trusted. The leadership worksheets include templates for the replay and the quarterly review, and the Leadership Capability Diagnostic gives an outside read on the same question.
The Five-Part Scale Load Test, Load by Load
Five loads, five questions
- Decision bandwidth: Can the team make more consequential decisions without creating a queue at the centre?
- Coordination quality: Can leaders integrate work across functions when local goals conflict?
- Leadership depth: Can managers and emerging leaders carry scope without waiting for executive rescue?
- Operating adaptability: Can the team change routines, roles and tools while preserving accountability?
- Recovery learning: Can the team convert pressure and failure into a better system rather than a better story?
Decision Bandwidth
Count the decisions that currently wait for the executive team. Do not count only formal approvals. Include questions that managers could answer but do not because the boundary is unclear, the evidence is missing or a previous decision was punished. The queue tells you how much of the organisation's judgement is still concentrated at the top. McKinsey's 2019 global survey on decision making in the age of urgency found that only 20 percent of respondents said their organisations excel at decision making, and that a majority said much of the time spent on it is used ineffectively.
Run a decision replay. Choose a recent week and trace five decisions from trigger to outcome. Who noticed the issue? Who framed the options? Who had authority? Who was consulted? Where did the decision slow down? A replay shows the real system more accurately than a new delegation chart.
Moving a queue looks like this. In one founder-led business nearly every significant decision still ran through the CEO. We settled which kinds of decision the CEO would pass on, and I coached the next layer to pick them up. Within 12 months escalations to the CEO had fallen by 75%, and the team no longer waited to make operational decisions. In scorecard terms that is decision bandwidth moving from 0 towards 2, and the evidence is a count, which is what you want.
Coordination Quality
Coordination is not the same as more communication. It is the ability to make a trade-off that protects the shared outcome. Ask the team to resolve a live conflict between speed, quality, cost and customer trust. Watch whether the group names the trade-off, or moves straight to defending the function each leader speaks for.
The best teams make disagreement usable. They ask which assumption is carrying the most risk, invite the person closest to the consequence and leave the room with one owner. They do not need perfect agreement. They need a decision that people can explain and carry. Where several parties disagreed on priorities, I made the trade-offs visible, set a clear decision process and secured agreement on how we would decide before deciding what. The final decision was accepted, and none of the parties reopened it. A forum with that shape is what a score of 2 on coordination looks like in practice.
Leadership Depth
A team is not ready to scale if every important issue still requires an executive to translate it for managers. Test depth by removing one senior person from a live decision. Can the next layer describe the context, make a call and learn from the result? If not, identify whether the gap is skill, authority, confidence or system design.
Depth does not mean naming a replacement for every role. It means building enough capability that the organisation has options. Give emerging leaders real scope, clear guardrails and feedback from the people affected by their choices. Observation without responsibility creates confidence theatre. For the structure behind this, see how to build a leadership pipeline in a growth-stage company.
Operating Adaptability
Scaling often exposes an operating model that depended on informal knowledge. The answer is not to document everything. It is to make the critical routines visible: how priorities are set, how risk is escalated, how customer commitments are changed and how leaders know a new process is working.
McKinsey's 2025 operating-model research, based on a survey of 2,000 executives, is useful here because it treats redesign as the integration of people, structures and processes, and puts alignment among leaders and decision-makers among its underlying themes. A leadership team is ready when it can change those elements together, instead of moving a box on the organisation chart and expecting the work to follow.
Recovery Learning
Pressure reveals whether the team has a learning system. After a missed commitment or service failure, ask what the system made easy, what it made invisible and what rule should change. Do not stop at the individual who made the last decision. Trace the conditions that shaped it.
How to Run the Test: Five Steps and a Pressure Scenario
- Choose a real load: Name the next change that will add decisions, coordination or consequence.
- Trace the current system: Replay how comparable work currently moves through the leadership team.
- Run a pressure scenario: Give the team incomplete information and a trade-off with a visible downside.
- Remove a familiar crutch: Test the decision without the CEO, the usual translator or the meeting that normally absorbs ambiguity.
- Set one repair: Choose the smallest change that will make the next load safer to carry, then review it in live work.
A useful scenario is close enough to the business that people recognise the trade-offs, but unfamiliar enough that old scripts do not solve it. Give the team a customer consequence, a resource limit and an incomplete signal. Ask for a decision, not a discussion. Then observe the path the group takes.
- Who frames the problem before proposing a solution
- Which assumption the team tests first
- Who is invited into the decision and who is absent
- Whether the group distinguishes reversible from irreversible choices
- How the decision is explained to people outside the room
The debrief matters more than the performance. Ask each leader what they noticed about the system, as well as what they thought about the answer. Then repeat the scenario with one constraint changed: remove a key data source, shorten the decision window or add a customer commitment that cannot be reversed easily. The aim is to show which parts of the decision method hold up and which depend on ideal conditions. Include the next layer of leaders in the observation. They can see whether the executive team creates clarity or sends mixed signals, and they can practise the translation work that scale requires.
Signals That a Leadership Team Is Not Ready Yet
The clearest signals are usually ordinary. The CEO is the only person who can join two functions around a shared outcome. Managers wait for the executive meeting to interpret a change. Leaders use the same crisis language every quarter. A decision is considered complete when it leaves the room, even though nobody has checked whether the work changed.
Treat these as design information. A weak signal does not mean a person has failed. It may mean the team has never been given a safe way to practise the next level of work. The response could be clearer authority, a new routine, a different role boundary or a development assignment with real consequence. If several signals show up together, the seven signs of an executive team that is not aligned is the next read.
Look for the opposite signals as well. A ready team can say which decisions have moved down, what evidence it expects before changing course and who is developing the capacity to carry a wider remit. It can name a recent disagreement that improved the decision. It can also say where it is not ready yet without turning that admission into a political event.
Build Readiness Into the Operating Rhythm
Do not run the load test once and file it as an assessment. Add a short readiness review to the quarterly operating rhythm. Revisit the decision queue, the cross-functional trade-offs, the depth of leadership coverage and the lessons from pressure. The review should change one operating choice each cycle, and it should finish with a choice, not a label: if decision bandwidth is the constraint, change ownership or escalation; if coordination is, redesign the hand-off; if depth is weak, create a real stretch decision with support; if recovery is poor, examine what the team learns after a miss.
Make the review visible to the people who depend on the team. Managers should know which decisions are now delegated and what escalation means. Keep a short record of the load tested, the observed failure, the repair made and the evidence that will show whether it worked. Without a record, each new stage starts by rediscovering the same constraint.
The aim is not to eliminate stretch. Every meaningful stage asks leaders to learn while they deliver. The aim is to know which stretch is deliberate, which support makes it safe and which unresolved gap would turn ordinary growth into avoidable strain. The people closest to the work can tell you where decisions wait and what happens when a leader is unavailable, often before a formal review does.
To go further, how to build a scaleup leadership team from scratch covers the team, what leadership systems fast-scaling companies need covers the systems underneath it, why leadership capability does not scale with company growth covers the pattern, and how to measure leadership capability across an organisation covers tracking the repair. Why leadership teams lose alignment as companies scale and building executive teams that perform cover the team dynamics, and the team coaching page covers support.
To map your current capability and load, begin with the Leadership Capability Diagnostic, review the Leadership Capability Architecture, or explore the leadership assessments. CapabilityAI, my AI leadership coach, is built around this capability model.
A ready team is not one without gaps. It is one that can see its gaps early and repair them before the next increase in load arrives.