Having enough people is not the same as having what the work requires.
A portfolio review shows that next quarter's engineering demand is 9,600 hours and available engineering capacity is 10,200 hours. On paper, the organisation has room.
But what if half the available hours sit with people who have never worked with the technology? What if only one engineer can sign off the safety-critical design? What if the project needs systems integration capability that the organisation has never built? What if operations cannot absorb the new solution after delivery?
The capacity number is technically correct and strategically misleading.
This is why portfolio leaders need to distinguish capacity from capability.
The Strategic Context
The supplied Week 4 material, drawing on the 2017 edition of PMI's Standard for Portfolio Management, makes the distinction clearly. Capacity addresses what resources are required, how many are required and when they are required. Capability addresses the attributes, competencies, skills and organisational support associated with those resources.
The difference appears simple, but organisations frequently collapse the two concepts in practice.
Resource plans count people, hours, budget, equipment or external contractors. These measures are essential because no strategy can be executed without sufficient capacity. But they are only a first approximation of delivery readiness.
Capability exists at several levels. Individual competence matters, but so do processes, systems, leadership, information, integration mechanisms and organisational support. A portfolio may have enough people while lacking the conditions that allow those people to perform effectively together.
For executives, the consequence is significant: capacity tells you how much work the system may absorb; capability tells you what kinds of work the system can execute reliably.
What Leaders Commonly Misread
The most common error is to treat resources as fungible.
A spreadsheet may show ten engineers, five project managers or three procurement specialists. Yet those people may have very different experience, authority, networks and technical depth. One person's absence can create a greater delivery risk than the loss of several generalist roles.
The same problem occurs with money. A budget allocation provides financial capacity, but the organisation may still lack qualified suppliers, appropriate technology, regulatory knowledge or the internal ability to govern the work.
External resources can create another illusion. Contracting a specialist may solve a short-term capability gap but leave the enterprise dependent on external knowledge it does not own. That may be acceptable for a temporary need. It may be strategically dangerous if the capability is central to future competitiveness.
Related article: Capacity Is a Strategic Constraint: Match Ambition to What the Organisation Can Absorb
Reframing the Issue
A better question than “Do we have enough resources?” is:
Do we have the right combination of capacity, competence, systems and organisational support to execute this portfolio at the required level of performance?
This reframes resource planning as a delivery-readiness decision.
It also reveals why capacity and capability are inseparable at portfolio level. The portfolio creates a pattern of demand. That demand is not only quantitative. It has a technical and organisational profile.
A digital portfolio may demand cybersecurity architects, change leaders and product owners. A manufacturing portfolio may require tooling expertise, controls engineering, supplier development and quality capability. A defence portfolio may require security-cleared personnel, configuration management and specialised systems engineering. The number of people available matters, but the composition matters just as much.
Capability Is More Than Skill
Competence is necessary, but not sufficient
Individual knowledge and skill are foundational. If the organisation lacks expertise in a critical domain, performance will be constrained regardless of how many people are assigned.
But individual competence must be converted into organisational performance. That requires role clarity, interfaces, decision rights, appropriate technology, information flows and repeatable ways of working.
A highly capable individual inside a dysfunctional system may spend more time overcoming organisational friction than creating value.
Systems can amplify or suppress human capability
Capability is partly encoded in the operating system of the enterprise.
Well-designed processes make expertise reusable. Shared tools improve coordination. Good data reduces rework and decision latency. Standards capture lessons. Governance allows risks to be escalated early. Knowledge-management systems reduce dependence on memory.
Conversely, poor systems can neutralise strong people. If teams cannot access reliable information, if decisions are delayed or if interfaces are unclear, individual competence does not automatically become portfolio capability.
Integration capability is often the hidden constraint
Many initiatives fail not because each specialist discipline is weak, but because the organisation cannot integrate them.
Engineering, procurement, operations, IT, finance and change management may all be competent in isolation. The program still struggles because no one has sufficient authority or skill to manage the interfaces.
This is particularly important for transformations where benefits depend on coordinated changes across processes, technology and behaviour.
Related article: The Portfolio Manager Is an Enterprise Integrator, Not a Senior Project Manager
Operational absorption is part of capability
A project team may have the capacity and competence to deliver a new system while the receiving organisation lacks the capability to use it.
That is not a project-success issue alone. It is an enterprise capability gap.
Portfolio leaders should therefore look beyond delivery teams. What new skills, maintenance arrangements, data disciplines, operating procedures or support structures will be required after implementation? If these are absent, the project may produce an output without creating sustainable value.
Single Points of Failure Distort Capacity
One of the most dangerous portfolio conditions is apparent capacity resting on fragile capability.
A business may employ 30 engineers, but only one person understands a legacy control system. It may have a large procurement team, but only one commercial manager has negotiated the specialist contract type. It may have several project managers, but only one has delivered work in the regulated environment.
These are capability concentration risks.
They are often invisible in headcount reports because the resource category appears healthy.
A mature capacity-and-capability assessment therefore identifies critical roles, rare skills, succession exposure, supplier dependencies and knowledge concentration. The question is not simply “How many?” but “How replaceable?”
Decision Framework
A practical delivery-readiness assessment can be structured across five layers.
1. Volume. Do we have enough time, people, funding, assets and external supply to meet the expected demand?
2. Competence. Do the people and partners have the required technical, commercial, leadership and domain skills?
3. System. Are the processes, tools, data, technology and governance mechanisms adequate for the work?
4. Integration. Can different functions, suppliers and teams coordinate decisions and manage interfaces effectively?
5. Endurance. Can the capability be sustained through the full delivery period and into operations, or does it depend on temporary heroics and single individuals?
The fifth layer is often where optimistic resource plans fail.
From Strategy to Execution
Immediate action should move portfolio resource reporting beyond aggregate headcount or FTE. Identify the critical capabilities required by major initiatives and map them against current availability, depth and concentration risk.
Medium-term capability building should create capability profiles for recurring strategic work. These profiles should combine roles, skills, systems, decision rights and operating support. Portfolio reviews can then distinguish between a genuine quantity shortage and a structural capability gap.
Long-term strategic positioning requires deliberate decisions about which capabilities the organisation should own, which it can partner for and which can remain external. The answer should reflect strategic importance, frequency of need, intellectual-property value, security, speed and supply risk.
Related article: Project Manager Career Paths Are Capability Architecture, Not HR Administration
Signals to Monitor
Capacity may be masking a capability problem when:
- the same specialists are assigned across many initiatives despite apparently healthy headcount;
- external contractors repeatedly perform the organisation's most strategically important work;
- project schedules assume rapid productivity from people new to the technology or domain;
- quality or rework problems rise even though staffing targets are being met;
- operational teams are not involved until late delivery;
- critical knowledge resides with one person, supplier or system;
- resource plans count availability but do not distinguish proficiency or authorisation levels;
- the organisation repeatedly hires more people without reducing the bottleneck.
These signals suggest that the constraint is not simply capacity.
Questions for the Leadership Team
- Which of our portfolio's critical capabilities are genuinely abundant, and which only appear abundant because we count broad resource categories?
- Where are we dependent on one person, one supplier or one technology platform?
- Which strategic initiatives require capabilities that we have never successfully demonstrated at scale?
- Do our resource plans include the receiving operations and change capability needed to realise benefits?
- Which capabilities should we own because they are strategically differentiating, and which can remain external?
- Are we measuring people availability, or actual delivery readiness?
Closing Perspective
Capacity and capability answer different questions.
Capacity asks whether the organisation has enough resources to attempt the work. Capability asks whether the organisation can convert those resources into the required result.
Leaders who manage only the first question can approve a portfolio that looks feasible on paper and is structurally undeliverable in practice.
The strongest portfolios are not those with the most resources. They are those whose commitments match what the organisation can genuinely do well.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.