Strategy is not executable until the organisation has the capacity to carry the commitments it creates.
Strategic planning often begins with opportunity: what markets to pursue, what capability to build, what costs to remove, what technology to modernise.
Execution begins with constraints.
The supplied EY portfolio-management material explicitly identifies organisational capacity to absorb change as a portfolio challenge and asks how supply and demand should be matched. The course material similarly places portfolio capacity and capability management alongside governance as a core field of study.
These are not operational details to be solved after the strategy is approved. They shape what strategy is feasible.
The Strategic Context
Organisational capacity has several forms.
Financial capacity determines what can be funded.
Delivery capacity determines what project and technical teams can execute.
Decision capacity determines how much change executives and governance forums can sponsor effectively.
Operational capacity determines how much implementation activity the business can support while continuing to serve customers.
Change capacity determines how much new behaviour, process and technology people can absorb.
Capability capacity concerns whether the organisation has the skills and systems required at all.
A portfolio can be affordable and still be impossible.
What Leaders Commonly Misread
The first error is treating resource capacity as headcount. Ten available people are not equivalent to ten people with the required capability, authority and timing.
The second is assuming utilisation should be maximised. Systems operating at near-total utilisation often become slow because any variation creates queues and delays.
The third is ignoring leadership attention. A portfolio can overload sponsors just as easily as technical teams.
The fourth is separating operational workload from project capacity. Many critical project resources are also responsible for business-as-usual performance.
Reframing the Issue
Capacity should become a strategic design parameter.
Before committing to a portfolio, leaders need to know which capabilities are scarce, which can be acquired, which take time to build and which cannot realistically be expanded.
That leads to a more disciplined question:
Given our current and buildable capacity, what sequence of strategic commitments creates the highest value?
This may produce a different answer from selecting projects only on individual attractiveness.
Capacity and Capability Are Different
Capacity is how much work the system can handle.
Capability is whether it can perform the required work effectively.
An organisation may have spare project-management capacity but lack systems engineering, procurement, data architecture or change-leadership capability. Hiring more generic resources will not solve the actual constraint.
Portfolio decisions should therefore identify both.
Persistent constraints may justify strategic capability development. Temporary constraints may justify sequencing, contracting or scope reduction.
The Constraint Is Often Hidden in the Operating Model
A useful capacity discussion has to move beyond the project office. Consider a hypothetical manufacturer undertaking a plant upgrade, an ERP change and a quality-system redesign at the same time. Each initiative may have an adequately staffed project team, yet all three may depend on the same production supervisors for requirements, trials, acceptance and training. The constrained resource is not project-management labour. It is operational attention.
The same pattern appears in digital transformation. A technology function may be able to build several systems concurrently, but the business may have only one credible data-governance group, one cyber-assurance pathway or a small number of product owners capable of making timely decisions. Adding developers can increase local output while leaving the system bottleneck untouched.
This is why capacity data should be interpreted through cause and effect. Leaders should ask where work actually waits, where decisions queue and where repeated hand-offs create delay. Those observations are often more useful than nominal utilisation percentages.
Capacity decisions also involve trade-offs. Building internal capability can improve resilience and strategic control but takes time. External contracting can add speed but may introduce integration, knowledge-transfer or supplier-dependency risk. Sequencing can protect flow but delay some benefits. Reducing scope can preserve time to value but may weaken the original outcome. Portfolio leadership is the discipline of making those trade-offs explicit rather than allowing overloaded teams to absorb them informally.
Decision Framework
Use a four-layer capacity review.
Layer 1: Critical capabilities. What expertise or authority is indispensable?
Layer 2: Time-phased demand. When does each initiative require those capabilities?
Layer 3: Credible supply. What capacity remains after operational commitments and known variability?
Layer 4: Absorption limit. How much simultaneous implementation can the target organisation adopt safely?
Then classify the response.
- Sequence when the capability exists but timing conflicts.
- Build when the constraint is strategically persistent.
- Buy when external capacity can be integrated effectively.
- Simplify when scope is creating unnecessary demand.
- Stop when the initiative does not justify the capacity it consumes.
Related article: Too Many Projects Is a Strategy Failure, Not a Scheduling Problem
From Strategy to Execution
Immediately, identify the resources most frequently named in project escalations. Those are candidates for portfolio-level constraints.
In the medium term, integrate resource and change-capacity analysis into approval. An initiative should not receive full authorisation merely because funding exists.
Longer term, capability investment should be linked to strategic direction. If future strategy consistently requires expertise the organisation does not possess, capacity building becomes part of the portfolio rather than a background HR issue.
Signals to Monitor
Watch for the same specialists assigned to many critical paths; long decision queues; implementation windows repeatedly missed because operations cannot release people; multiple transformations targeting the same workforce simultaneously; and portfolios that add projects faster than they complete them.
Another warning sign is when leaders respond to capacity pressure only by shifting dates while keeping every commitment active.
Questions for the Leadership Team
- What are the five scarcest capabilities in our current strategy?
- Which constraints are temporary and which are structural?
- How much executive sponsorship capacity do our major initiatives consume?
- Where is business-as-usual demand competing with change demand?
- Which capabilities should we deliberately build because future strategy depends on them?
- What work should be deferred rather than forcing all initiatives through the same bottleneck?
Closing Perspective
Capacity is not a reason to lower ambition. It is a reason to sequence ambition intelligently.
A strategy that ignores constraints creates overloaded portfolios, delayed benefits and organisational fatigue.
A strategy that recognises constraints can invest in capability, focus resources and move faster where it matters most.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.