Ask a leadership team what capabilities it needs and the list can become generic very quickly: leadership, teamwork, innovation, communication, digital skills, customer focus. Most organizations would benefit from these. That is exactly why they are weak strategy answers. A strategic capability matters because the choices the organization made require it.
Playing to Win treats core capabilities as one of the choices that support where to play and how to win. The workshop should therefore identify capabilities because the strategy requires them—not because they are generally desirable.
Do not let the capability list become an HR wish list
Imagine the strategy says the company will win through reliable recovery when customer operations are disrupted. The first capability brainstorm produces familiar answers: leadership, teamwork, communication, customer service, digital skills. Nobody can disagree with the list, which is why it does not yet tell the organization what to build.
Work backward from the strategic promise. To recover reliably, frontline teams may need real-time information, authority to make certain decisions, access to technical specialists, a process for cross-functional escalation, and judgment about which customer consequences matter most. Together, those elements form a capability the organization can either perform reliably or fail to perform.
Only after that capability is visible should the group ask what to build, buy, redesign, partner for, or train. Otherwise every strategic gap risks becoming a training request.
Work backward from how you intend to win
Take one how-to-win choice and ask, “What must become reliably possible for this to work?” If the strategy depends on exceptionally reliable delivery, what combinations of information, process, technology, judgment, supplier coordination, and recovery capability make that promise credible? The answer should point to an organizational ability, not merely a training topic.
Generate possible capabilities, then rank them by dependence. Which capabilities would cause the strategic bet to fail if they remained weak? Which are merely useful but not distinctive? Which already exist strongly enough?
A short list creates investment choices. A long list becomes another competency catalog.
Capabilities often live across functions. Fast recovery may depend on frontline judgment, real-time data, decision rights, supplier relationships, and a management routine that escalates only unusual cases. No single department owns the whole capability. This is why strategy capability work should not automatically be handed to HR.
A capability is what the organization can reliably accomplish through a combination of people, processes, technology, information, relationships, and judgment. A software platform may support a capability, and a competency may be part of it, but neither is automatically the capability itself. This distinction matters in facilitation because it stops the group from solving every gap with training or procurement.
Ask, “If this capability stays weak, can our how-to-win choice still work?” If the answer is yes, it may be useful but not must-have. If the answer is no, explore exactly where the strategy would break. That question tends to reduce long wish lists and expose cross-functional dependencies.
Map capability gaps without jumping to solutions
Once the must-have capabilities are visible, assess the current state honestly. Is the capability strong enough, uneven, missing, or dependent on one exceptional individual? This is where the leadership team can see whether the strategy is asking the organization to do something it cannot yet do reliably.
Resist the urge to solve each gap immediately. A capability may require process redesign, technology, partnerships, new roles, leadership behavior, or training. Diagnosis comes before the intervention.
Cross-functional capabilities often fail because every department owns a piece and nobody owns the whole. Identify who is accountable for making the capability reliable across boundaries, even when delivery remains distributed.
That person does not become the sole doer. The role is to see the whole chain and notice where the capability breaks.
Build the capability map from the strategic promise
Write the how-to-win choice at the top of a page and ask, “What must the organization be able to do repeatedly for this promise to be credible?” Capture verbs before departments: recover a failed service within two hours, price complex work profitably, detect risk before a customer is surprised, integrate new suppliers quickly. Verbs keep the group focused on organizational ability rather than ownership politics.
Then unpack each ability. What people judgment does it require? What process has to work? What information must be available? What technology or relationship supports it? Only after the combination is visible should the leadership team discuss ownership and investment. This often reveals that the most strategic capability crosses several departments and cannot be solved by one function alone.
When the capability list becomes strategic
The final capability list is clearly connected to the chosen way to win, and leaders can explain why each capability is strategically necessary. At least one investment, ownership question, or development priority changes because of that link.
Capabilities need an environment that sustains them. That is the work of management systems.
Use one test on every proposed capability: if this stays weak, can our how-to-win choice still work? Once the must-have capabilities are clear, continue to Build the Management Systems the Strategy Needs.