Why project portfolio management disappoints
In many organisations, project portfolio management exists on paper. There is a list, a tool, sometimes a committee. But the list only grows, every project on it is a ‘priority’, and the committee rubber-stamps launches already decided elsewhere. The portfolio describes what is being done. It decides nothing.
The symptoms are familiar to all who endure them. Teams work on too many topics in parallel and spend their time switching context. Scarce skills (architects, data experts, security specialists) are booked by every project at once. Lead times lengthen everywhere without any one project being precisely at fault.
The cause is almost always the same: the organisation knows how to say yes, but has no mechanism for saying no, later or not like this. Launching a project takes a signature. Stopping one takes courage, facts and a body with the mandate to do so. This is the mechanism our consultants help you establish.
The four mechanisms of a portfolio that decides
A useful portfolio rests on four mechanisms that hold together. The definition of PPM in our glossary details the vocabulary. Here we focus on putting them into practice.
Prioritisation. It translates strategy into explicit criteria, known to those who propose projects. Several methods exist, and they do not suit the same situations.
| Method | Principle | Suitable when | Limitation |
|---|---|---|---|
| Weighted scoring grid | Each project is scored on a few criteria (value, risk, urgency, effort) | Projects are numerous and comparable | Gives an illusory precision if the scores are not discussed |
| Strategic envelopes | The budget is divided between categories before projects are ranked | The portfolio mixes obligations, maintenance and development | Requires a leadership decision on the split |
| Cost of delay | Projects are ordered by what deferring them costs, relative to their duration | Requests arrive as a flow and capacity is stable | Assumes value and duration can be estimated |
| Forced ranking | The committee orders projects one by one, with no ties | The portfolio is small and the committee cohesive | Hardly practicable for a large number of projects |
Capacity. Prioritising without knowing your resources amounts to ranking wishes. Capacity is read at a coarse but reliable level: by critical skill and by period, not by person and by day. It is almost always a few scarce profiles that constrain the entire portfolio.
Arbitration. A body, a rhythm, submissions presented as options. The portfolio committee decides on admissions, deferrals and stops. It does not examine the progress of each project: that monitoring falls to the project office, or PMO, which prepares its submissions.
Value. Each project enters the portfolio with written benefit assumptions and a business owner. These assumptions are reread at every review. A project whose justification has disappeared along the way must be able to be stopped without anyone losing face.
Our approach: making the portfolio arbitrable before optimising it
Our consultants work within your teams; decisions remain yours. We do not start with a sophisticated scoring model. We start by making the portfolio readable, then we help hold a first real arbitration.
See. We take stock of all projects, including those that appear in no tool, and describe them on a common record. This step generally reveals duplicates, projects with no sponsor and initiatives everyone believed were finished.
Agree on the criteria. We help the members of the executive committee build the grid, testing it on the real portfolio. If the resulting ranking contradicts leadership’s intuition, it is the discussion that has value: it brings implicit criteria to light, which must then be written down.
Compare with capacity. We establish the workload requested and the capacity available for the skills that really constrain the portfolio. The result is a waterline: above it, the projects the organisation can carry out; below it, those that wait.
Decide. We prepare and facilitate with you a first committee that rules on this basis. The arrangement is then adjusted, and repeated at a fixed rhythm.
Tooling comes afterwards. When several projects in the portfolio are linked by a common objective, we recommend grouping them and running them using the methods of programme management.
Five traps we help you avoid
- Taking the score for a decision. A grid informs a committee; it does not replace it. A ranking applied mechanically is circumvented as soon as the first poorly scored ‘strategic’ project comes along.
- Planning capacity by the day. A named workload plan over many months is wrong as soon as it is published and costly to maintain. A coarse grain, kept up to date, serves decision-making better.
- Forgetting ongoing activity. Maintenance, support and change requests consume the same capacity as projects. A portfolio that ignores them overestimates what it can commit to.
- Leaving back doors open. If a project can be launched without going through the committee, the most influential requesters will take that route, and the official portfolio will no longer reflect reality.
- Never rereading the benefits. A business case that no one reopens after launch encourages promising a lot. Rereading after delivery makes subsequent promises more measured.
How to measure the success of portfolio management
We agree with you on a few observable signs, tracked from one arbitration cycle to the next.
- The share of projects under way that have gone through the decision channel.
- The number of projects run in parallel, relative to the capacity of critical skills.
- The existence of explicit decisions to defer or stop, and their actual application.
- The stability of priorities between two reviews: priorities that change at every committee signal poorly framed criteria.
- The share of delivered projects whose benefits have been reread with the business owner.
- The time between a project request and the answer given to it.
None of these indicators measures the committee’s activity. All of them measure the same thing: the organisation’s ability to concentrate its resources on a number of projects it can finish.