How to Build Capability
in a Scaling Business
Moving from programmes to systems that actually change performance
#Strategy
How to Build Capability in a Scaling Business
Moving from programmes to systems that actually change performance
#Strategy
Building capability in a scaling business
In a scaling organisation, capability rarely begins as a clearly defined priority. It tends to emerge as a constraint. As the business grows, individuals take on roles they have not previously held, teams inherit greater complexity, and decisions begin to carry more weight and consequence. Over time, performance becomes less constrained by strategy and more by the organisation’s ability to execute against it.
At that point, most organisations do what feels logical. They invest in development. They introduce programmes. They bring in external support. The intent is right. The results are often uneven.
The issue is not effort. It is that capability is being treated as a set of interventions, rather than as a property of how the organisation operates.
Building capability in a scaling business requires a shift in approach. Not more programmes, but greater clarity, sharper focus, deeper integration into the work, and alignment across the system.
1. Start with what “good” actually looks like
Most organisations can describe where things are not working. Decisions feel slow or unclear. Priorities shift. Managers apply inconsistent standards. Teams struggle to align around what matters most.
What is much less common is a clear, shared understanding of what good looks like instead.
In the absence of that clarity, organisations tend to rely on generic competency frameworks or imported models. These often sound credible, but they rarely translate into day-to-day behaviour. They describe leadership or management in theory, rather than performance in context.
Research from McKinsey & Company has consistently shown that organisations with clear role expectations and well-defined performance standards are significantly more effective in translating strategy into execution. Yet in many scaling environments, expectations remain implicit.
Defining “good” in a useful way means grounding it in the realities of the business. It requires moving beyond abstract traits and focusing on how work actually gets done.
In practice, that means asking:
- What does effective decision-making look like here?
- How are priorities set and communicated when everything feels urgent?
- What distinguishes strong execution from acceptable execution?
- Where do capable people consistently get stuck as the organisation grows?
The answers to these questions should be specific enough that someone can recognise them in their own work. A useful test is whether a manager could read the definition and think, “I know what I would do differently next week.”
If not, it is probably too abstract.
What this looks like in practice
In most scaling businesses, this does not start with designing a framework. It starts with observation.
- Sit down with leaders and teams and ask where work slows down or breaks
- Look at real decisions, not hypothetical scenarios
- Identify patterns in how strong performers operate differently
From there, capability can be defined in terms of observable behaviour in real situations, rather than generalised attributes.
2. Focus on the capabilities that matter most
Once there is clarity on what good looks like, the next challenge is deciding where to invest.
Scaling organisations rarely lack development activity. More often, they have too much of it, spread across too many priorities. Manager programmes, leadership workshops, coaching, tools, frameworks. Each addressing a different issue, often triggered by a specific request.
Over time, this creates a fragmented landscape. Activity increases, but impact remains uneven.
A common pattern is the “squeaky wheel” effect. The most visible or frustrating issue gets attention, regardless of whether it represents the most meaningful constraint on performance. At the same time, external influence plays a role. Leaders import approaches that have worked elsewhere, assuming they will translate into a new context.
Research from Gartner suggests that organisations that concentrate development on a small number of critical capability gaps see significantly stronger outcomes than those that attempt to address capability broadly.
The implication is simple, but not easy. Capability building requires deliberate focus.
Not “what could we improve?”, but:
- Which capabilities will most directly impact our ability to execute?
- Where are the most significant performance constraints today?
- If we improved one or two things meaningfully, what would change?
Answering these questions often requires trade-offs. It means saying no to good ideas in order to prioritise what matters most.
What this looks like in practice
- A useful exercise is to force prioritisation:
- Identify 6–8 capability areas that feel important
- Ask leaders to rank them based on impact on business performance
- Cut the list down to 2–3 that will genuinely move the needle
This creates alignment and prevents capability building from becoming diluted across too many initiatives.
3. Build capability in the work, not outside it
One of the most persistent assumptions in capability building is that development happens primarily through programmes.
Workshops, courses, structured learning experiences. These can be useful, but they are rarely where capability is actually formed.
In scaling environments, capability is built in the flow of work. In how decisions are made, how priorities are set, and how teams execute under pressure.
Formal development can support this, but it cannot replace it.
Data from CIPD shows that while structured learning can improve knowledge and confidence, sustained behaviour change depends heavily on reinforcement in the workplace. Without that reinforcement, the impact fades quickly.
This is often where organisations become frustrated. They invest in a programme, see strong engagement, but observe little change in day-to-day behaviour.
Shifting this requires a different starting point. Instead of asking “what programme should we run?”, the question becomes:
- Where does this capability show up in day-to-day work?
- What are the critical moments where it matters?
- How can we support people in those moments?
What this looks like in practice
This often involves relatively simple but high-leverage changes:
- Embedding decision-making frameworks into team meetings
- Using real business challenges as development material
- Structuring conversations around priorities and trade-offs
- Supporting managers to run more effective performance discussions
Programmes then play a supporting role. They provide language, tools, and reflection, but the real development happens in how work is carried out.
4. Design the system, not the intervention
Even when organisations get clarity, focus, and integration right, capability building can still fail to stick.
People understand what good looks like. They begin to behave differently. But over time, the organisation pulls them back to previous patterns.
This is not a failure of individuals. It is a reflection of the system.
Capability is reinforced, or undermined, by how the organisation operates. What gets measured, how performance is assessed, what leaders prioritise, how decisions are made, and which behaviours are tolerated all send signals about what really matters.
If these signals are not aligned with the capabilities the organisation is trying to build, progress will be limited.
For example, an organisation may want faster, clearer decision-making. But if decision rights are ambiguous or decisions are routinely revisited, the system reinforces hesitation. Or a company may expect managers to develop their teams, but if performance is judged primarily on short-term output, development becomes secondary.
Designing for capability means paying attention to these dynamics.
- Are expectations clear and consistently applied?
- Do performance systems reinforce the behaviours we want to see?
- Are leaders modelling those behaviours in practice?
What this looks like in practice
This does not require a full system redesign. Often, small adjustments have outsized impact:
Clarifying decision ownership for key areas
- Aligning performance conversations with capability expectations
- Making expectations visible and consistently referenced
- Holding leaders accountable for how results are achieved, not just what is delivered
These changes signal what matters and create the conditions for capability to stick.
Bringing it together
Capability in a scaling business is not built through isolated initiatives. It is shaped by how the organisation defines performance, where it focuses its effort, how work is structured, and what it consistently reinforces.
Organisations that do this well are not necessarily doing more. They are doing fewer things, more deliberately, and in a way that is connected to how the business actually operates.
The shift is subtle but significant. From programmes to systems. From content to context. From activity to performance.
