Five questions every leadership team should ask

At an executive away-day, the senior team agrees an ambitious strategy. The organisation will accelerate digital transformation, expand into new markets, improve customer experience and strengthen execution. It may need to innovate more rapidly, develop a deeper leadership pipeline or work more effectively across functions.

Considerable thought has gone into what the institution wants to achieve. Less attention, however, may have been given to a different question: what must this organisation become especially good at for the strategy to work?

Strategies are usually expressed through priorities, targets, programmes and financial commitments. Capability is often discussed later, perhaps when HR presents the talent plan or the learning budget comes forward for approval. That sequence is risky.

Strategy is not delivered by intention alone. It depends on whether the institution possesses, or can build, the collective ability to do what the strategy requires.

A serious capability conversation begins with five questions.

1. What does our strategy require us to be able to do?

Leadership teams sometimes move directly from strategic ambition to projects, structures and budgets.

The institution wants to expand, so it establishes a market-entry programme. It wants to transform digitally, so it invests in technology. It wants to innovate, so it creates an innovation function.

Each may be sensible. None answers the capability question.

Expansion may require the organisation to enter unfamiliar markets, transfer knowledge across locations, operate in different regulatory environments and develop leaders who can work beyond the centre.

Digital transformation may require strong product ownership, data-informed judgement, cross-functional execution and the ability to govern technology responsibly.

Innovation may depend less on generating ideas than on running intelligent experiments, allocating resources, learning quickly and stopping initiatives that show little promise.

The organisation should identify a small number of capabilities that are genuinely consequential to the strategy.

This is not an invitation to create an exhaustive catalogue of desirable behaviours. Long capability lists frequently become detached from the choices the organisation is actually making.

The useful test is simpler: if we remain weak in this capability, does the strategy become materially less likely to succeed? If the answer is no, the capability may still be desirable, but it is probably not strategic.

Choosing matters. If every capability is a priority, none will receive the sustained attention required to become a source of institutional strength.

2. Where does the capability need to exist?

Capability does not need to be distributed equally across an organisation.

Some roles require deep technical expertise. Others require enough understanding to make sound decisions, commission work or recognise risk. Some capabilities sit principally within individuals. Others exist only when several functions work effectively together.

This question often reveals hidden dependencies – and concomitant risks.

An organisation may appear highly capable because one or two exceptional people repeatedly compensate for weaknesses around them. They hold key relationships, remember why historical decisions were made and know how to navigate informal systems. When something becomes difficult, the issue finds its way to them. Their contribution is valuable, but the institution may be mistaking personal reliability for organisational capability.

The risk becomes visible when those individuals are overloaded, unavailable or decide to leave.

A leadership team should know:

• where critical expertise is concentrated;
• which roles carry disproportionate institutional knowledge;
• where judgement needs to be distributed more widely;
• which teams must become capable together;
• where succession is fragile;
• which future roles will require capabilities that are currently scarce.

This is not simply a workforce-planning exercise.

It concerns the architecture of performance. The organisation needs to understand how capability is distributed, where it resides and how reliably it can be mobilised when needed.

3. How will the capability grow?

Once a capability gap has been identified, many organisations reach immediately for training. Sometimes that is appropriate. Often it is only part of the answer.

Capability may grow through recruitment, particularly where specialist expertise does not exist internally. It may develop through stretch assignments, coaching, mentoring, role rotation or exposure to more complex decisions. An organisation may need to build a cohort around an important strategic challenge, strengthen line managers as developers of others or create a community through which professional practice can be shared.

It may need to capture knowledge held by a small number of experts. It may need to redesign work so that emerging leaders can take greater responsibility. It may need to give people better information, clearer authority or more useful feedback.

Formal programmes have an important role, particularly where people need new knowledge, structured practice, shared language or access to perspectives beyond their daily work.

The leadership task is to choose a coherent combination.

For one capability, the principal need may be recruitment. For another, the institution may already have talented people but provide too little opportunity for them to practise. Elsewhere, the problem may lie less with people than with an organisational environment that prevents them from using what they know.

A capability plan is therefore not the same as a curriculum. It describes how an institutional ability will be identified, acquired, developed, practised, shared and sustained.

4. What would convince us that capability is strengthening?

Participation is relatively easy to measure. Capability is more demanding.

If an organisation says it is strengthening decision-making, what would better decisions look like? Would they be faster, more consistent or more clearly owned? Would the quality of challenge improve? Would fewer decisions be escalated unnecessarily?

If it is building management capability, would employees receive more useful feedback? Would delegation improve? Would the organisation become less dependent on a handful of senior leaders?

If it is strengthening strategic execution, would priorities remain clearer? Would cross-functional blockages be resolved earlier? Would review meetings become more focussed on decisions and less on the presentation of activity?

Useful evidence might include:

• stronger performance in a strategically important process;
• more consistent decisions;
• visible changes in management practice;
• a healthier succession pipeline;
• reduced dependency on particular individuals;
• better handling of risk;
• improved work across organisational boundaries;
• greater confidence that leaders can assume broader responsibility.

Some evidence will be quantitative. Other evidence will require professional judgement.

That should not make the organisation uncomfortable. Leaders already exercise judgement in assessing risk, strategic progress and organisational health. What matters is that the basis for judgement is explicit rather than convenient.

The institution should agree in advance what movement might look like. Otherwise, almost any positive anecdote can be claimed as success and any disappointing result explained away.

Completion data tells the leadership team whether an intervention happened. Capability evidence helps it judge whether anything important changed.

5. What in our organisation will help or hinder this capability?

This may be the most important question.

Capability does not sit inside people independently of the organisation around them. It is shaped by decision rights, incentives, management behaviour, information flows, workload, technology, governance and culture.

A business cannot credibly say it wants distributed leadership while escalating every significant decision. It cannot build experimentation while making failure professionally dangerous. It cannot strengthen collaboration while rewarding only functional results. It cannot expect strategic thought if every senior meeting is consumed by operational reporting. It cannot improve accountability if priorities change without explanation and authority remains unclear.

In each of these cases, the organisation sends contradictory messages. It asks people to develop one capability while rewarding the behaviour that prevents it.

This is why attempts to build capability so often disappoint. The focus remains on improving the individual while the surrounding system remains largely unexamined.

A leadership team should ask:

• Do people have the authority to use the capability?
• Does the governance system create space for it?
• What behaviours do our incentives actually reward?
• What do managers notice and discuss?
• Is the necessary information available?
• Does the design of work allow practice?
• What happens when somebody tries a different approach?
• Do senior leaders model what the organisation says it values?

These questions are not peripheral to development. They are part of the development architecture.

Joining the pieces

A coherent capability system connects several things that organisations often manage separately.

It begins with strategy and the capabilities that strategy requires. It identifies where those capabilities need to reside, whether in particular roles, teams or relationships across the institution.

It creates deliberate routes through which capability can grow. These may include recruitment, learning, practice, coaching, experience, management support and workplace redesign.

It examines whether the operating environment enables people to use what they know.

It gathers evidence of whether capability is strengthening and whether that change is contributing to performance.

When these elements are disconnected, investment leaks value. Capability frameworks sit apart from strategy. Leadership programmes sit apart from performance management. Talent reviews sit apart from succession decisions. Learning platforms sit apart from the daily work. Organisational data exists, but leaders struggle to see what it means.

The problem is not necessarily a lack of activity. It is a lack of architecture.

Capability belongs at the executive table

Capability is often treated as an HR concern because HR owns many of the relevant processes. HR has an important role, but it does not control the whole environment through which capability develops.

The executive team sets strategy and allocates resources. Senior leaders establish priorities and shape governance. Line managers determine whether people have opportunities to practise and whether application receives attention. Functions maintain specialist standards and professional knowledge.

Boards also have an interest where capability weakness creates a material strategic, succession or execution risk.

Ownership is therefore distributed.

This does not mean creating another cumbersome central process. It means recognising that capability is too important to be left as a series of disconnected activities.

Leadership teams should review capability with the same seriousness they bring to financial resources, technology, risk and operating performance. They should know which capabilities matter, where the most significant gaps lie, what is being done about them and whether those actions are producing credible movement.

From human potential to institutional performance

Most organisations contain capable people. The more difficult question is whether the institution can reliably convert that human potential into coordinated performance.

Individual excellence matters, but it is not enough. Talented people can become isolated, overloaded or frustrated. Knowledge can remain trapped within functions. Leadership development can improve insight without changing behaviour. Strategic intent can remain disconnected from daily execution. A capability system closes those gaps.

It does not attempt to engineer every aspect of human performance. Organisations are too complex and people too varied for that. It does, however, create greater coherence between what the institution is trying to achieve, what its people need to be able to do and the conditions under which they are expected to perform.

Strategy is an expression of intent. Capability determines whether that intent is plausible.

Between them lies the real work of institution building: developing people, distributing judgement, strengthening management, changing routines and creating the conditions in which good performance can be repeated.Perhaps the most important question is not how much the organisation is investing in its people, but whether that investment is making the institution more able to deliver what it has promised.