A strategy is not executable simply because the organisation can afford the project that represents it.
A leadership team may approve a transformation because the market opportunity is attractive, the business case is positive and the strategic intent is clear. Six months later, the organisation discovers that the scarce engineering capability is already committed, the operating teams cannot absorb the change, the required data is unreliable, critical supplier knowledge sits outside the firm, or the new model depends on coordination the current organisation has never demonstrated.
The project did not suddenly become strategically wrong. The original decision was incomplete because it treated financial feasibility as if it were organisational feasibility.
The supplied internal-scanning material provides the missing lens. Resources include financial, physical, human, organisational and intangible assets. Capabilities emerge from how those resources are combined. Projects compete for core resources, and not every resource has equal strategic value. Wheelen and Hunger's internal-scanning framework similarly moves strategy from external opportunity to internal capability: what can the organisation actually do, and which capabilities are sufficiently valuable and sustainable to support advantage?
The Strategic Context
Strategy creates demand on an operating system. New products demand engineering, supply chain, sales and support. Digital strategies demand data, architecture, cyber, product ownership and adoption. Expansion demands management depth, capital and local knowledge. Operational excellence demands process discipline and measurement capability.
If those capabilities do not exist, the enterprise has three choices: build them, buy them or change the strategy. What it should not do is assume that a project plan can create them automatically while simultaneously depending on them for delivery.
This is particularly important at portfolio level because capability is shared. One data platform team may support several transformation programs. One regulatory group may control the pace of multiple market-entry projects. One production line may be both the source of current revenue and the test bed for a major automation program. The limiting resource is not always visible in the capital budget.
What Leaders Commonly Misread
The first misreading is to equate headcount with capacity. Ten people with the wrong skills, fragmented authority or competing priorities do not represent ten units of useful capacity.
The second is to assume that external procurement removes internal capability requirements. Outsourcing can provide specialist delivery, but the enterprise still needs enough knowledge to define outcomes, integrate work, govern interfaces, accept risk and retain critical knowledge after the supplier leaves.
The third is to treat culture as soft context rather than a delivery variable. A strategy that depends on cross-functional collaboration will struggle in an organisation whose incentives reward functional optimisation. A transformation requiring rapid experimentation will move slowly if decision rights are highly centralised and failure is punished.
The fourth is to ignore capability decay. A resource can be valuable today but lose relevance as technology, markets or customer expectations change. The supplied resource-based material explicitly tests durability, inimitability, appropriability, substitutability and competitive superiority. The strategic question is not only whether a capability exists, but whether it remains valuable for the future being funded.
Reframing the Issue
Every major investment should be assessed through two parallel cases:
The market and value case: Is the opportunity worth pursuing?
The capability case: Can this organisation create and capture the value with acceptable risk?
These two cases interact. A strong capability can make an opportunity more valuable because the enterprise can execute faster or more reliably than competitors. A weak capability can make the same opportunity less attractive because the organisation must first fund learning, systems, recruitment or integration.
Capability is therefore not an implementation footnote. It is part of investment economics.
Strategic Analysis: The Capability Stack
Resources
The supplied study notes identify tangible resources such as cash, borrowing capacity, plant, equipment, location and workforce, as well as intangible resources including knowledge, intellectual property, reputation and innovative capability.
The first diagnostic is simple: what resources does the strategy actually require, and which of them are scarce?
Capabilities
Resources create value through combination. A factory, skilled engineers, data and supplier relationships are not independent advantages. What matters is whether the organisation can combine them into reliable design, production, service or innovation performance.
Capabilities should therefore be expressed as verbs: design, qualify, manufacture, integrate, sell, deploy, learn, scale, recover. This makes the operating requirement clearer than a static list of assets.
Interfaces
Many failures occur not inside functions but between them. Engineering and procurement, sales and operations, technology and business, project delivery and operational ownership may each perform adequately while the interfaces fail.
A capability assessment should examine handovers, decision latency, information quality and responsibility at boundaries.
Management system
Repeatable capability depends on governance, process, measurement and learning. If success relies on heroic individuals, the organisation has expertise but may not yet have institutional capability.
Capacity under load
A capability can exist and still be unavailable. The critical question is whether the capability has spare capacity when the project needs it. Portfolio decisions must therefore distinguish capability existence from capability availability.
Decision Framework
Before sanctioning a material strategic investment, test six conditions.
| Capability test | Question |
|---|---|
| Critical resources | Which resources are indispensable to value creation? |
| Availability | Are they available in the period the project requires them? |
| Quality | Do they perform at the level required by the strategy? |
| Integration | Can the organisation combine them across functional boundaries? |
| Sustainability | Will the capability remain valuable and difficult to substitute? |
| Ownership | Who will own, maintain and improve the capability after project delivery? |
The result should classify each required capability as ready, constrained, build, buy, partner, or redesign.
A 'build' classification should create an explicit capability-development workstream with funding, milestones and ownership. A 'buy' or 'partner' classification should define which knowledge must remain internal. A 'redesign' classification should change the investment architecture so the strategy no longer depends on a capability that cannot be obtained at acceptable cost or speed.
Related article: Organisational Structure Is a Project Risk
From Strategy to Execution
Immediately, add a capability section to major business cases. It should identify the small number of capabilities critical to value, the evidence that they exist and the competing demand from the current portfolio.
In the medium term, maintain a strategic capability map. This should not become an HR skills inventory. It should focus on capabilities that materially differentiate the organisation or constrain strategic execution.
Where repeated bottlenecks appear, portfolio leaders should fund capability as an investment in its own right. For example, a common integration platform, commissioning function or program-control capability may improve the performance of many future projects. Its value is portfolio-wide rather than confined to one business case.
Longer term, connect capability renewal to foresight. If technology or market structure is changing, ask which current capabilities will become less valuable and which must be developed before the organisation is forced to respond under pressure.
Signals to Monitor
Look for projects repeatedly delayed by the same specialist roles; excessive reliance on contractors for decisions the organisation should own; critical processes understood by a few individuals; strategic plans that assume major behavioural change without capability-building investment; and business cases that show capital demand but not organisational capacity demand.
Another warning sign is successful pilots that fail to scale. This often indicates that the project proved the technology or concept but not the enterprise capability required to operate it reliably at volume.
Questions for the Leadership Team
- Which capabilities must be true for this strategy to work?
- Which of those capabilities are genuinely available rather than theoretically present somewhere in the organisation?
- Where are several strategic initiatives competing for the same scarce expertise?
- Which knowledge can safely be outsourced, and which must remain inside the enterprise?
- What capability are we assuming the project will create while simultaneously depending on it for delivery?
- Which current strengths are likely to lose value as the external environment changes?
Closing Perspective
Leaders often ask whether the organisation has the money to pursue a strategy. The better question is whether the enterprise has—or can deliberately create—the system of resources, capabilities and interfaces required to realise the value.
Funding a strategy without testing organisational capability transfers uncertainty from the boardroom into execution. A capability test brings that uncertainty back into the investment decision, where it belongs.
Source Foundations
- Wheelen, T. L. & Hunger, J. D., “Internal Scanning: Organizational Analysis”, Chapter 5 of Concepts in Strategic Management and Business Policy, 11th ed., 2008 (supplied university extract).
- MPM416 internal organisational analysis and resource-based study notes (supplied course material).