A company says speed is part of its strategy, but an unusual customer request still waits two days for approval.
A hotel promises personal service, but only its most experienced staff know what to do when a guest problem becomes complicated. Another organization says innovation matters, yet a small experiment has to pass through three meetings before anyone can try it.
The strategy may be clear. People may even agree with it.
But the organization still cannot reliably do what the strategy requires.
This is where capability becomes a strategic question.
Not, “What training should we provide?” Not, “What new process should we install?” Those may become part of the answer later.
Start with a more demanding question:
What does our strategy require us to be able to do reliably that we still cannot do without delay, escalation, inconsistency, or heroics?
That question brings strategy closer to the work.
Your Strategy Makes a Promise the Organization Has to Keep
Consider a resort that wants to win through warm, responsive service.
The promise sounds straightforward. Guests should feel cared for, particularly when something goes wrong.
Most days, the staff perform well. They greet guests warmly, answer questions, arrange transportation, and respond to ordinary requests. Customer feedback is generally positive.
Then a family arrives after a long trip and discovers that the room they reserved is not ready.
The children are tired. The parents are frustrated. The front-desk associate understands the problem and wants to fix it. She can offer refreshments and apologize, but the most useful recovery—a room upgrade and meal credit—requires a manager’s approval.
The manager is in another meeting.
So the family waits.
At that moment, the resort’s strategy is being tested.
The issue is not whether the employee remembers that the resort values service. She does. The issue is whether the organization can actually deliver its promise when delivering it requires judgment, authority, information, and action.
That is the point of a must-have capability.
A capability is something the organization can reliably do when it matters.
If warm service is part of how the resort intends to win, service recovery cannot depend on whether the right manager happens to be available.
Capability Is Not the Same as Skill
This distinction matters because capability problems are often turned too quickly into training problems.
Suppose the front-desk associate is excellent with guests. She knows how to listen, acknowledge frustration, explain what happened, and calm an emotional conversation.
She has skill.
Suppose the resort also teaches a simple response for common service failures: acknowledge the problem, take responsibility when the failure is ours, offer an approved recovery option, and confirm what will happen next.
Now the employee has a practical play she can call when the moment appears.
But the organization does not yet have a reliable service-recovery capability if the employee still lacks authority to offer the recovery, cannot see the guest history, or knows that a manager may punish a reasonable decision afterward.
Skill lives partly in the person.
A play gives the person a useful response in a recurring moment.
Capability appears when people, judgment, authority, information, tools, routines, and support work together well enough that the organization can repeatedly produce the result.
That is a much higher standard.
It also explains why organizations can employ very capable individuals without possessing the capability themselves.
Maria may be the person everyone calls when a customer becomes angry. Ramon may be the only supervisor who can rescue a delayed project. Lea may know exactly how to work around a difficult system because she has been there for fifteen years.
The organization looks capable while these people are present.
Then Maria goes on leave.
Ramon gets promoted.
Lea resigns.
Performance drops.
What disappeared was not merely talent. The company discovered that important work had never become an organizational capability.
If success still depends on heroes, the capability is not yet built.
Find the Moment Where the Strategy Has to Work
Leadership teams sometimes identify capabilities by sitting in a room and creating a list.
“We need customer centricity.”
“We need agility.”
“We need innovation.”
“We need strategic thinking.”
Those words may point in useful directions, but they are still too broad to build.
A better way is to start from the strategic choice and locate the real moment where that choice has to become visible.
For the resort, the strategic promise is warm, responsive care.
Where is that promise most seriously tested?
Not when a guest asks where breakfast is served.
The harder test comes when something has gone wrong and the employee has to recover trust.
Now we can ask a more precise question:
What must the organization be able to do in this moment for the strategy to remain true?
The answer might be:
Frontline staff must be able to resolve common service failures quickly, within clear boundaries, without waiting for a manager.
That is far more useful than “build customer-service capability.”
We can test it.
Can staff across different shifts do it? Can a new but prepared employee do it, or only the veterans? Does it still work when the lobby is busy? Can people make reasonable decisions without being second-guessed afterward? Does the supporting system provide what they need?
This is the Capability Test:
Name the strategic promise. Locate the moment that tests it. Define what the organization must be able to do there. Test whether that ability is reliable. Then find what prevents reliability.
That final question is where useful design begins.
Do Not Jump Straight to Training
Suppose the resort runs the Capability Test and discovers that service recovery is inconsistent.
The immediate response might be: “We need customer-service training.”
Perhaps.
But look closer.
Some employees do not know how to respond when a guest becomes angry. That is a capability-development issue where practice and coaching may help.
Others know exactly what to do but cannot authorize the recovery. That is an authority issue.
Some have authority but cannot see whether the guest has experienced earlier service failures. That is an information issue.
Another shift has a manager who supports reasonable frontline judgment. A different manager routinely reverses employee decisions, so people there have learned to escalate everything.
That is a manager-support issue.
One visible failure can therefore contain several different conditions.
This is why Make Strategy Clear cannot end with naming the aspiration or strategic choices. Leaders eventually have to ask what those choices require the organization to become able to do.
And it is why Make Execution Daily has to include more than exhorting people to perform. Desired behavior needs conditions that allow it to survive in real work.
Training earns its place when skill, judgment, or practice is part of the gap.
It should not be asked to compensate forever for missing authority, broken handoffs, inaccessible information, conflicting measures, or leadership routines that pull people back toward the old behavior.
Build the Capability Where It Has to Be Used
Return to the resort.
Instead of sending everyone to another general customer-service seminar, the leadership team redesigns one recurring moment.
They identify the most common service failures. Frontline staff receive a small number of recovery options they can use without approval, with clear financial and operational limits. They practise several realistic situations so they can exercise judgment instead of memorizing scripts.
Managers also change their role.
When an employee makes a reasonable decision inside the agreed boundary, the manager does not take the decision back simply because they would have handled it differently. Unusual cases are discussed during a short review so the team can learn where the boundaries or plays need adjustment.
The guest-information system is also changed so the front desk can see relevant service history.
No single intervention created the capability.
Together, they changed what the organization could reliably do.
A month later, another family arrives and discovers that its room is not ready.
The situation is still unpleasant.
But this time the employee does not disappear into the back office looking for a manager. She acknowledges the failure, checks the available options, offers an appropriate recovery, and confirms what will happen next.
The guest does not experience the organization’s training.
The guest experiences the capability.
That is the difference that matters.
Reliability Is the Proof
Leadership teams sometimes declare a capability built because people attended the program, a new process was launched, or the technology went live.
Those are implementation milestones.
They are not yet proof of capability.
The proof is whether the organization can now produce the needed response with greater reliability.
For the resort, leaders could follow a small number of signals: how many common service failures are resolved without unnecessary escalation, how long guests wait for resolution, whether performance is consistent across shifts, how often managers have to rescue routine cases, and whether repeat complaints decline.
The purpose is not to create a massive dashboard.
It is to answer a practical question:
Can we now do what the strategy requires more reliably than before?
There is another useful test.
Remove the hero.
If your best front-desk associate is absent, does the service still work? If the senior manager is travelling, can appropriate decisions still be made? When a new employee has been properly prepared, can they use the same system successfully?
A genuine organizational capability becomes less dependent on extraordinary rescue.
That does not make great people less valuable. It allows their expertise to improve the organization instead of forcing them to save it repeatedly.
Build What the Strategy Actually Needs
Not every desirable capability deserves equal investment.
Organizations can create long lists of things they would like to become good at: better communication, stronger teamwork, innovation, coaching, data literacy, customer experience, project management, collaboration, strategic thinking.
The list can quickly become another wish list.
Return to the strategy.
If the strategy is true, where must the organization perform differently?
What recurring moments will determine whether the promise becomes real?
Which ability must become reliable there?
Then begin with the capability whose absence most often breaks the strategic promise.
For one organization, that may be rapid service recovery. For another, it may be making commercial decisions closer to the customer. Another may need supervisors who can turn priorities into clear daily direction. A company pursuing innovation may need to run small experiments without forcing every idea through a long approval chain.
The capability should be specific enough that you can recognize it in action and follow whether it is becoming more reliable.
That gives leaders a much better starting point than asking what program to launch next.
Ask This Before the Next Initiative
The next time someone proposes a new training program, process improvement, technology platform, or transformation initiative, do not reject it.
Ask what capability it is supposed to create.
Then go one step further:
Where does our strategy require that capability to show up in real work?
Find the moment.
Describe what the organization must be able to do there.
Then look at what currently prevents it: skill, judgment, authority, information, tools, routines, measures, manager support, or some combination of them.
Build what is missing and return to the same moment.
If the work now moves differently—more reliably, across more people, with less dependence on rescue—you are not merely running an initiative.
You are building capability.
And that is the question worth bringing back to the leadership team:
What does our strategy require us to be able to do reliably that we still cannot do without heroics?
