Strategy Says Where You’re Going. Capability Determines Whether You Get There.

Most organizations spend a lot of time developing strategy.

They define priorities.

Set targets.

Identify where they want to grow.

Decide where to invest.

And determine what needs to change.

But there’s another conversation that often receives far less attention:

What must our organization become capable of doing to actually deliver this strategy?

That question matters because strategy doesn’t execute itself.

Imagine an organization that identifies innovation as a strategic priority but takes months to approve a new idea.

Or a company that wants to differentiate through customer experience while its teams continue operating in functional silos.

Or an organization investing heavily in AI without helping employees understand how to redesign their work around it.

In each case, the strategy may be perfectly reasonable.

The organization simply hasn’t built the capabilities required to deliver it.

Strategy defines where you want to go. Capability determines whether your organization can get there.

The good news is that connecting the two doesn’t need to be complicated.

Here are three conversations leadership teams can start having today.

1. Translate Strategic Priorities Into Capability Questions

Most strategies tell us what an organization wants to accomplish.

Grow into new markets.

Improve customer experience.

Increase innovation.

Adopt AI.

Reduce costs.

But each of those priorities creates another question:

What must we become exceptionally good at for this strategy to succeed?

If the strategy calls for expansion into new markets, the organization may need to improve its ability to understand and adapt to new customers.

If customer experience is the priority, teams may need to improve their ability to work across functional boundaries.

If AI adoption is critical, employees may need to become better at redesigning workflows and making decisions alongside new technology.

If innovation is the goal, the organization may need to become better at experimenting, learning quickly, and making faster decisions.

These are capability questions.

And they shift the conversation from:

What do we want to achieve?

to:

What must we become capable of doing?

That’s an important distinction.

Because every strategic priority creates a capability requirement.

2. Understand the Gap Between What You Need and What You Have

Once you’ve identified the capabilities your strategy requires, the next question is simple:

How capable are we today?

This is where organizations sometimes move too quickly.

A capability gap is identified, and the immediate response is training.

But organizational capability is bigger than employee skill.

It comes from the combination of several things:

People. Process. Structure. Technology. Leadership.

Take innovation as an example.

An organization might decide it needs to become more innovative and invest heavily in innovation training.

Employees learn new tools and techniques.

But approvals still take months.

Teams don’t have authority to experiment.

Funding processes favour certainty.

Leaders discourage failure.

The organization may have improved individual skills without improving its ability to innovate.

The same thing happens with many strategic priorities.

Customer experience isn’t only a customer-service skill.

AI adoption isn’t only a technology skill.

Agility isn’t only a mindset.

Collaboration isn’t only a behaviour.

Each depends on the broader organizational environment supporting it.

If you diagnose a capability problem as only a skills problem, you’ll probably build the wrong solution.

Before investing in a solution, look at the whole system.

What’s helping this capability today?

What’s getting in the way?

And what would need to change for the organization to become consistently good at it?

3. Put Capability on the Leadership Agenda

Organizations routinely review business performance.

Revenue.

Costs.

Projects.

Risk.

Operational metrics.

Progress against strategic priorities.

But leadership teams should also be asking whether the organization itself is becoming more capable of delivering the strategy.

That doesn’t require another complicated dashboard.

Start with three questions:

What capabilities are most critical to our strategy?

Where are our biggest capability gaps?

What are we doing to close them?

Those questions change the conversation.

Capability building stops being something delegated to HR, Learning and Development, or another support function after the strategy has been created.

It becomes part of strategy execution.

Because building capability may require investment in people.

But it might also require changing a process.

Redesigning a structure.

Clarifying decision rights.

Introducing new technology.

Changing leadership behaviour.

Or removing something that is making it unnecessarily difficult for people to perform.

Building organizational capability isn’t something HR does after the strategy is created. It’s part of how leaders execute the strategy.

From Strategy to Capability

The connection can be surprisingly simple:

1. DEFINE: What must we become great at?

2. DIAGNOSE: Where are we today?

3. BUILD: What needs to change?

The answers won’t always lead to a new program or initiative.

Sometimes the most important capability-building decision a leader can make is removing a barrier that’s preventing people from doing what the strategy already requires.

Final Thought

Strategies change.

Markets change.

Technology changes.

Customer expectations change.

And every time they do, the capabilities an organization needs change with them.

That’s why strategy conversations can’t end with priorities, targets, and initiatives.

They also need to ask:

What does our organization need to become capable of doing that it can’t consistently do today?

So the next time your leadership team reviews its strategy, don’t just ask:

Are we making progress against our priorities?

Ask something harder:

Are we becoming the organization capable of delivering them?

Because strategy can tell you where you want to go.

Capability determines whether you can get there.