A project can fit the strategy perfectly and still be the wrong investment if the organisation lacks the capability to execute, absorb and sustain it.
Strategic alignment is one of the most common tests used in project selection. The logic is reasonable: scarce resources should support the organisation's objectives rather than fund unrelated activity.
But alignment can create false confidence.
A project may support the strategy, produce an attractive business case and still fail because the organisation does not possess the people, systems, knowledge, operating discipline or change capacity needed to turn the idea into a working capability.
The supplied internal-scanning material and Week 4 study notes make this problem visible. They distinguish resources from capabilities and show that organisations compete not merely through what they own, but through how resources are combined and used. The notes also observe that projects compete for access to core resources.
This is the execution question that project-selection processes often underweight.
The Strategic Context
Strategy describes where an organisation intends to compete, what it wants to become and how it expects to create value.
Execution requires a different set of conditions.
A manufacturer may decide that advanced automation is strategically important. That does not mean it currently possesses the controls engineering, data architecture, maintenance capability, process discipline and workforce readiness required to operate an automated system reliably.
A government agency may decide that digital service delivery is strategically necessary. That does not guarantee that legacy systems, procurement arrangements, data quality, policy settings and internal capability can support the transformation.
A professional-services firm may decide to enter a new advisory market. The opportunity may be real, but the organisation may lack credibility, subject-matter expertise, methods, sales capability or delivery infrastructure.
Strategic intent and organisational capability therefore need to be tested separately.
The stronger portfolio question is:
What must the organisation be capable of doing for this investment to produce the intended value?
What Leaders Commonly Misread
The first misreading is to treat resource possession as capability.
Owning equipment does not prove that the organisation can operate it effectively.
Having talented people does not prove that they can work together at the scale, speed or quality the strategy requires.
Holding data does not prove that the data are accessible, reliable or usable.
Having capital does not prove that the organisation can absorb the operational change associated with spending it.
The second misreading is to assume that missing capability can always be purchased.
Some resources can be bought quickly. Others are path-dependent. Tacit knowledge, customer trust, operating routines, cross-functional coordination and specialised judgement may take years to build.
The third misreading is to treat strategic projects as if they consume only dedicated project resources.
Many transformations depend heavily on operational experts whose primary responsibility is running the existing business. Their availability can therefore become the real portfolio constraint.
The fourth misreading is to assume that every capability gap should be solved before the project starts.
That can be equally unhelpful. Some projects are themselves vehicles for building capability. The relevant question is whether the capability-development pathway is explicit, credible and sequenced into delivery.
Reframing the Issue
Project selection should include a capability feasibility test alongside strategic and financial appraisal.
The supplied resource-based material identifies a broad set of resources:
- financial resources;
- physical assets;
- human skills;
- organisational systems;
- knowledge;
- innovation capability;
- reputation and brand.
The study notes then make the important distinction that resources are bundled together to produce capabilities.
This means a portfolio decision should ask more than whether the organisation has enough money.
It should ask whether the necessary bundle of resources can be assembled and coordinated in time.
Related article: Capital Budgeting Is Strategy Expressed Through Investment Choices
The Capability Architecture Behind Delivery
A useful capability assessment considers at least six dimensions.
1. Availability
Does the organisation actually have the resource when the project needs it?
A specialist engineer who is already committed to three strategic projects is not truly available merely because the organisation employs that person.
2. Quality
Is the capability strong enough for the complexity of the work?
A basic internal IT function may support routine systems while being insufficient for a major cybersecurity or cloud transformation.
3. Integrability
Can separate resources operate as one system?
Projects frequently fail at interfaces rather than within individual disciplines. Engineering, procurement, operations and finance may each be competent while coordination between them remains weak.
4. Durability
Will the capability remain useful long enough to justify investment?
The Wheelen and Hunger material examines the sustainability of resources and competencies, including how quickly they can be imitated, substituted or eroded.
For project selection, the equivalent question is whether the capability being built will remain strategically relevant.
5. Transferability
Can capability move from consultants, contractors or a temporary project team into the operating organisation?
A transformation is not complete when an external delivery team can operate the solution. Value requires the organisation to sustain it.
6. Absorption
How much simultaneous change can the organisation realistically take on?
A portfolio can contain individually sensible projects that collectively overwhelm the same operational teams.
That is not a project-level failure. It is a portfolio-capacity failure.
Strategic Adjacency Matters
The study notes categorise projects according to how far they sit from the organisation's existing objectives and activity envelope.
That concept is strategically valuable even if the examples are simplified.
A project close to current operations may use familiar resources and routines.
A project adjacent to current capability may require targeted development.
A project far outside the existing activity envelope may demand a fundamentally different business model, skill base or governance system.
The further the move, the less credible it is to assume that the organisation can execute using existing capability unchanged.
That does not mean distant opportunities should be rejected.
It means leaders should recognise capability distance as part of investment risk.
A radically different project may require partnership, acquisition, staged experimentation or a separate operating model rather than conventional internal delivery.
The Hidden Portfolio Competition for Capability
Projects do not merely compete for budget.
They compete for:
- executive attention;
- specialist knowledge;
- operational access;
- project controls;
- procurement support;
- legal review;
- change-management capacity;
- and decision bandwidth.
This matters because many of these resources cannot be scaled quickly.
An enterprise may approve five projects that all require the same process engineers in the same quarter.
Each business case may be valid. The combined portfolio is not.
This is why resource allocation should be treated as strategy in action, not as an administrative exercise after project approval.
The Week 4 material explicitly positions management attention and human resources alongside financial resources in corporate resource allocation.
That is the correct enterprise lens.
Decision Framework
Before approving a strategic project, test seven capability questions.
| Test | Leadership question |
|---|---|
| Strategic fit | Which enterprise objective does the project advance? |
| Capability requirement | What must the organisation be able to do that it cannot do reliably today? |
| Resource availability | Which scarce resources are required and when? |
| Capability distance | How far is the work from current operating experience? |
| Acquisition path | Will capability be built, bought, partnered or transferred? |
| Absorption | Can the operating organisation absorb this change alongside other initiatives? |
| Sustainability | Who will own and maintain the capability after project closure? |
A proposal should become harder to approve as capability assumptions become more speculative.
The purpose is not to eliminate ambitious projects. It is to make the capability-development investment visible.
From Strategy to Execution
Immediate action
Add a capability assessment to major investment proposals.
Identify the small number of resources and capabilities that are genuinely critical to success.
Do not list everything the organisation owns. Focus on what the project cannot succeed without.
Medium-term capability building
Create a portfolio-level capability map showing where multiple strategic initiatives depend on the same scarce expertise or infrastructure.
Use this map to sequence projects.
Where capability must be built, define explicit transition milestones rather than treating learning as an informal by-product of delivery.
Long-term strategic positioning
Invest in capabilities that create strategic optionality across multiple future projects.
A specialist data platform, systems-engineering capability, procurement model or operational-excellence discipline may enable an entire portfolio rather than one initiative.
This is where capability investment becomes a strategic asset rather than project overhead.
Related article: A Transformation Portfolio Must Be Sequenced as a System
Signals to Monitor
Capability problems are emerging when:
- the same specialists are named as critical resources across many projects;
- contractors can operate the new capability but internal teams cannot;
- business cases assume rapid recruitment into scarce labour markets;
- project delays repeatedly arise from operational access rather than technical work;
- strategic initiatives depend on systems or data that are known to be unreliable;
- projects finish but benefits are delayed because operating teams are not ready;
- or the organisation repeatedly approves work outside its capability envelope without changing its delivery model.
Questions for the Leadership Team
- What must we be capable of doing for this strategy to work?
- Which required capabilities already exist at sufficient scale and quality?
- Which capability gaps are being treated as assumptions rather than investments?
- Where are projects competing for the same scarce expertise or management attention?
- What should be built internally, and what should be bought or partnered?
- Who owns the capability after the project team leaves?
- Are we selecting projects faster than the organisation can learn?
Closing Perspective
Strategic alignment is essential, but it is not a licence to ignore execution reality.
The organisation must possess, acquire or develop the capabilities that connect strategic intent to operating performance.
That includes more than people and money. It includes routines, systems, knowledge, interfaces, governance and the capacity to absorb change.
The strongest portfolio is therefore not the one with the greatest number of strategically aligned projects.
It is the one whose ambitions are matched by the enterprise's ability to execute them.