Project Portfolio Management: Matching Work to Capacity

Score every project on the same four dimensions: expected impact, effort required, dependency risk, and whether it's tied to a hard external deadline like a contract or a compliance date. Keep the scoring simple, a one-to-three scale is enough, because a complicated scoring model just becomes something people game to justify a project they already wanted approved.

The point of the worksheet isn't to produce a perfect ranking. It's to force a conversation about tradeoffs using the same criteria for every project, instead of whichever team argues loudest getting funded first.

Next to each project, estimate the hours or person-weeks it actually needs, pulled from people who've done similar work before rather than from whoever is pitching the project. Then total the demand across every project marked active or approved, and compare it against the hours your team genuinely has available, not against a headcount number that ignores vacation, support work, and the maintenance that keeps existing systems running.

Most portfolios are over capacity the moment you do this math honestly. That's the point of doing it: the overcommitment is usually invisible until it's added up in one place.

A high-impact project that consumes half your team's capacity for a quarter can be a worse choice than three smaller projects with the same combined impact spread across less time, because the smaller projects free capacity sooner for whatever comes next. Rank by impact divided by effort, not by impact on its own, and the ordering often changes in ways that surprise the people who pitched the biggest project.

This is also where dependency risk earns its place in the scoring. A medium-impact project that unblocks two other initiatives waiting behind it deserves a higher effective rank than its raw impact score suggests, because delaying it delays everything downstream of it too.

Once the worksheet shows you're over capacity, sequencing alone won't fix it, something has to actually come off the list. This is the step most portfolio reviews skip, because deferring a project quietly feels easier than telling a team their initiative isn't happening this period.

Say you're carrying twelve active projects against capacity for eight. Deferring four to the next planning period, clearly and in writing, is a better outcome for everyone than running twelve at seventy percent speed and delivering all of them late.

Run the capacity check in this order:

1. Estimate the hours or person-weeks each project needs, using people who have done similar work before.
2. Total the demand across every project marked active or approved.
3. Compare that total with the hours your team genuinely has, after vacation and support work.
4. Rank the projects by impact divided by effort, then cut whatever remains beyond capacity.

A portfolio worksheet that gets built once and never revisited drifts back into the same overcommitment within a quarter, as new projects get approved without anyone re-running the capacity math. Set a fixed point, monthly or at the start of each planning cycle, to refresh both the project list and the capacity estimate.

A tool like ClickUp or Process Street can hold the live version of this worksheet so it updates as projects close and free up capacity, rather than living in a spreadsheet that's accurate the day it's built and stale a month later. Assign someone specific to own the refresh, too. A worksheet with no owner tends to survive exactly one planning cycle before everyone assumes someone else is keeping it current, which is how the same overcommitment quietly reappears.