A programme is not a big project
Programme management most often fails for a simple reason: the programme is run like a very large project. Its plan is the sum of the project plans. Its committee reviews the projects one after another. Its dashboard aggregates progress figures. Everything that happens between the projects, which is to say the essential part, belongs to no one.
The consequences appear late. Each project meets its milestones, but the deliveries do not fit together. The new system is ready before the organisation that is meant to use it, or the reverse. The benefits announced at launch are claimed by no business department, because none committed to them. The sponsor, meanwhile, discovers the trade-offs once they have become emergencies.
Managing a programme therefore means holding on to a question that project managers do not have to ask: will what we deliver, put end to end, produce the effect for which the programme was launched?
Project, programme, portfolio: what changes for the person in charge
The three levels call for neither the same decisions nor the same instruments.
| Project | Programme | Portfolio | |
|---|---|---|---|
| Purpose | Deliver a defined product or service | Achieve an outcome that several projects produce together | Choose which projects and programmes to run |
| Horizon | Bounded, set at launch | Bounded, revised at each stage | Permanent |
| Success criterion | Scope, time, cost, quality | Benefits realised | Good use of resources in light of the strategy |
| Central question | Are we delivering what was planned? | Will the deliveries produce the expected effect? | Are we committing to the right initiatives? |
The portfolio level is covered on a separate page, dedicated to project portfolio management. The programme level is described by several frameworks, notably the PMI’s Standard for Program Management; the same institute’s PgMP certification is presented in our entry on PMI certifications, and the MSP framework (Managing Successful Programmes), from the same family as PRINCE2. We use them as toolkits, without imposing their vocabulary on your teams.
What programme management keeps hold of
Governance
A sponsor who champions the programme before the executive committee, a programme director who is accountable for the outcome, project managers responsible for their deliveries. Between them, written delegation thresholds: what each decides alone, and what is escalated.
The trajectory
A programme is broken down into stages. Each stage delivers a usable capability and ends with a decision: continue, adjust or stop. A trajectory with no intermediate stage postpones all the value, and all the risk, to the end.
Dependencies
Each dependency between two projects is a commitment: a provider, a recipient, an expected item, a need-by date. It is tracked like a milestone. Dependencies on parties outside the programme (other projects, suppliers, regulatory deadlines) are the ones most often forgotten.
Benefits
Each benefit is linked to the deliverables that make it possible and to the change in practice that produces it. It has an indicator, a due date and a business owner, who does not belong to the programme team.
Cross-cutting risks
The programme register is not the sum of the project registers. It carries the risks that no one else sees: an organisation saturated with change, a supplier shared by several projects, a cutover that two teams are preparing separately.
Stakeholders
Business departments, operations, employee representatives, suppliers, supervisory authorities: programme management knows who can block it and who can carry it, and maintains those relationships itself.
Our approach to programme management
We work in one of two ways: supporting your programme director, or taking on this role on your behalf alongside the sponsor. In both cases, the assignment follows the life of the programme.
Before launch, we help the sponsor write the mandate: the target outcome, what is in scope and what is not, the stages, the benefit assumptions. A programme whose mandate fits on one readable page is already off to a better start than most.
At mobilisation, we set up governance and the programme office. Its design falls under our offering for setting up a PMO: we do not go over it again here.
In steady state, we keep a short cycle: synchronising projects on dependencies, reviewing cross-cutting risks, preparing trade-offs. The programme committee receives choices to make, set out with their consequences, rather than a progress review.
At each stage, we prepare the decision to continue and the handover: operations teams and the business receive what has been delivered, with the means to use it. Adoption is prepared using the methods of change management, built into the programme plan from framing onwards.
The pitfalls we help you avoid
- The never-ending programme. Without stages and closure criteria, the programme becomes a permanent structure that absorbs new topics as it goes.
- The absent sponsor. A sponsor who delegates their presence at the committee deprives the programme of its only power to arbitrate between departments.
- The spectator committee. A body that listens to presentations without deciding anything sends decisions back into the corridors, where they are taken without a trace.
- Orphan benefits. A benefit owned by the programme director will never be measured: they will have left the stage before the due date.
- The single cutover. Concentrating every go-live on a single date turns each delay into a crisis. Progressive cutovers cost more organisation and much less risk.
How to recognise a well-managed programme
Some signs can be observed without waiting for the end of the programme. Stages deliver capabilities that are used, not just documents. Dependencies are honoured by their need-by date, or their slippage is known early enough to be dealt with. Trade-offs requested from the committee are decided in the cycle in which they are presented. Cross-cutting risks have an owner and an action under way.
The most telling sign concerns benefits: at each stage, a business owner comes to report on them in person. When that moment exists, the programme has stopped being a matter for the project function and has become a matter for the organisation.