Value per Constrained Resource Hour

Value per constrained resource hour is the single number that ranks work by what it returns on your scarcest resource. It is the measure that turns project prioritization from "everything is important" into a defensible order of priority.

Every portfolio has a constraint: a specific team, skill set or asset that limits how much the organization can actually deliver, no matter how much other capacity is available. Work that does not touch the constraint can be scheduled freely. Work that does touch it is competing for the most valuable hours in the business. Value per constrained resource hour prices that competition.

Value per constrained resource hour is the economic value a piece of work returns for each hour it consumes of an organization's scarcest resource, the constraint. It ranks competing projects by return on that scarce time rather than by total size, turning a vague sense that everything is important into a defensible order of priority.

How it works

The idea is borrowed from the economics of any bottlenecked system: when one resource limits throughput, the right thing to maximize is not output per project or utilization per person, but value produced per hour of the constraint's time.

For a given piece of work, you take the economic value it produces and divide it by the hours of constrained resource it consumes. A high number means the work returns a lot for every scarce hour it uses. A low number means it is an expensive way to spend the constraint, however attractive the project looks in isolation.

Why does this change project prioritization?

Conventional project prioritization ranks projects by their total value or their strategic score. That systematically over-rates large projects that are heavy users of the constraint, and under-rates small pieces of work that release or feed the constraint cheaply.

Scoring models are not useless. They force a conversation about value and strategic fit, which is better than ranking by whoever asks loudest. What they miss is the one fact that decides what a portfolio can deliver: every project competes for the same scarce hours. Project prioritization that divides value by those hours ranks work by what it returns on the constraint, not by how big or how strategic it looks on its own.

Ranking by value per constrained resource hour flips several intuitions. A modest project that barely touches the bottleneck can outrank a flagship program that monopolises it. Getting the right work to the constraint sooner can be worth more than starting the highest-value project first. It is the measure that makes sequencing an economic decision rather than a political one, and it sits at the center of running a portfolio at the top of the Flow Economics Maturity Model.