FLOW ECONOMICS / INSIGHTS

What is the difference between resource management and capacity planning?

Project manager gesturing at color-coded resource allocation whiteboard with capacity timelines in a modern London consulting office.

Resource management and capacity planning are related but distinct disciplines. Resource management is about allocating the right people to the right work at the right time. Capacity planning is about understanding whether your organisation has enough of the right skills to take on the work it is considering. In practice, organisations often conflate the two, and that confusion is one of the quieter reasons delivery programmes underperform. The sections below unpack each discipline, explain where they break down together, and show how a portfolio economics lens changes the picture.

What does resource management actually involve?

Resource management is the practice of assigning people to active work. It answers the question: given the projects already running, who is doing what, when, and at what utilisation? The discipline sits at the execution layer, matching named individuals or skill groups to scheduled tasks across a live portfolio.

In most organisations, resource management covers three core activities:

  • Maintaining a register of available people, their skills, and their current commitments
  • Resolving conflicts when two projects claim the same person at the same time
  • Tracking utilisation to ensure teams are neither overloaded nor idle

The discipline is inherently reactive. It responds to demand that has already been approved and projects that have already started. A resource manager at Harbour Engineering, for example, is not deciding whether to take on a fourth transformation programme. She is deciding how to allocate the three senior architects already committed across the three that are running.

That boundary matters. Resource management keeps work moving. It does not decide what work to start, or in what order, or what a delay to one project costs the business relative to another. Those questions belong to a different layer.

What does capacity planning actually involve?

Capacity planning is the practice of comparing anticipated demand against available supply before work is committed. It answers the question: do we have enough of the right skills, at the right time, to take on what we are considering? The discipline sits between strategy and execution, informing intake decisions rather than managing active assignments.

Where resource management looks at what is running now, capacity planning looks forward. A portfolio team at Whitfield Infrastructure might use capacity planning to assess whether the three programmes approved for next quarter can actually be staffed given current headcount, known attrition, and skills that are already committed to live work.

Done well, capacity planning produces a realistic picture of available throughput before commitments are made. It surfaces bottlenecks in advance rather than discovering them mid-delivery, and it gives decision-makers the information they need to sequence work intelligently, defer lower-priority initiatives, or resolve skill gaps before they become delivery failures.

The challenge is that capacity planning requires a degree of forecasting that most organisations find uncomfortable. Demand is often uncertain, project scopes shift, and the skills most in demand are the ones whose future availability is hardest to predict. As a result, capacity planning is frequently done at a level of aggregation that obscures the specific constraints that actually govern delivery speed.

Why do organisations that do both still struggle with delivery?

Organisations that practise both resource management and capacity planning still underperform because the two disciplines, even when done well individually, do not answer the question that governs portfolio performance: in what order should constrained resources work across competing projects, and what does the wrong order cost?

This is the gap that Flow Economics calls the shared resource system, the layer between strategy and execution where the same few specialists carry multiple projects simultaneously. Each project has its own resource plan and its own governance. What no plan captures is the interaction effect: when a specialist at Calder Digital is shared across four programmes, she is someone's top priority four times over. Each project reports on schedule while it waits for her. The waiting appears in nobody's report, but the clock on all four programmes keeps running.

Resource management resolves the conflict in the moment, usually by seniority or by whoever escalates loudest. Capacity planning may have flagged the overload in advance, but it rarely attaches an economic value to the sequencing decision. The result is that organisations invest heavily in governance and visibility, yet the order in which constrained resources work is still decided by persuasion rather than by the value at stake.

This is what Flow Economics describes as the Project Illusion: the belief that if individual projects are well planned and well governed, portfolio performance will follow. In reality, portfolio performance depends on how projects interact when they compete for the same constrained resources. When those interactions are invisible, better project management does not fix the problem. It just makes the individual pieces look healthier while the whole system underdelivers.

When should capacity planning drive portfolio intake decisions?

Capacity planning should drive portfolio intake decisions at every stage gate where new work is being considered for approval. The right moment to surface a capacity constraint is before a commitment is made, not after a project has started and is already competing for the same specialists as three other live programmes.

In practice, this means capacity planning needs to be connected to the portfolio intake process in a specific way. Before a project is approved, the portfolio team should be able to answer three questions:

  1. Which skills does this initiative require, and when does it need them most intensively?
  2. Are those skills already committed to other work during the same window?
  3. If we approve this now, what does it do to the flow of work already in the system?

The third question is the one most intake processes skip. Adding a new project to a constrained system does not just create a new workstream. It adds load to the specialists every other project is already waiting for. If those specialists are the system's binding constraint, the new project slows everything else down, and the cost of that slowdown is rarely calculated before the approval decision is made.

Capacity planning that informs intake decisions well is not just a headcount exercise. It requires understanding which roles are genuinely scarce, what the queue of demand on those roles looks like, and what the economic consequences of adding to that queue are. That is a more demanding standard than most capacity planning processes currently meet, but it is the standard that separates planning as a reporting activity from planning as a decision-making tool.

What's the relationship between capacity planning and portfolio performance?

Capacity planning is a necessary condition for strong portfolio performance, but it is not sufficient on its own. Portfolio performance depends on how well an organisation manages the flow of value through its constrained resources, and capacity planning only sets the stage for that. The connection between the two runs through sequencing and economic prioritisation.

An organisation that plans capacity well knows what it can take on. But knowing what you can take on does not tell you in what order to do it, or what a day of delay to a high-value initiative costs relative to a day of delay to a lower-value one. Those are economic questions, and they require a different kind of analysis.

The concept of drag cost, developed by Stephen Devaux, gives this analysis a practical foundation. Drag cost is the cost that a project's duration imposes on the portfolio by consuming constrained resources that could otherwise be advancing other value-generating work. When capacity planning is connected to drag cost thinking, sequencing decisions stop being administrative and start being economic. The organisation can see not just whether it has capacity, but what the best use of that capacity is across the full portfolio.

This connection between capacity, flow, and economic value is what moves an organisation from structured portfolio governance (where dashboards and intake processes exist, but sequencing is still decided by seniority) toward flow-based portfolio optimisation, where the constraint sets the order of the work. The journey is described in the Flow Economics Maturity Model, which maps six levels of how organisations manage work involving shared people, from activity focus at level one to constraint value optimisation at level six.

How Flow Economics approaches resource demand and capacity

Flow Economics addresses the gap that sits between resource management and capacity planning: the shared resource system where the order of work is decided and where most portfolio value is either realised or lost. The framework brings three things together that most organisations manage separately.

  • Visibility of the constraint: Flow Economics makes the binding constraint explicit, identifying which skills or roles are limiting throughput across the whole portfolio, not just within individual projects
  • Economic sequencing: Drawing on drag cost (Stephen Devaux) and return on remaining investment, the framework attaches a cost to delay and a value to each sequencing decision, so the order of work reflects economics rather than escalation
  • Portfolio-level decision-making: Rather than treating projects as independent delivery items, Flow Economics manages them as investments competing for constrained capacity, giving leaders a basis for intake, deferral, and prioritisation decisions that capacity planning alone cannot provide

The result is a way to balance resource demand and capacity that goes beyond headcount planning. Leaders can see what the wrong sequencing costs, test decisions before making them, and move toward a portfolio that delivers on its economic potential rather than just its project plans. If you want to explore how this applies to your portfolio, the Flow Economics course walks through the framework in full, with a working simulator you can use to test sequencing decisions against your own portfolio. You can also get in touch to discuss how the framework applies to your organisation's specific context.

Related Articles

GO DEEPER

See the bigger picture.

Explore practical ideas for understanding portfolio performance, shared resources and the economics of delivery.