EPMO
Enterprise strategy · reports to the C-suite
Guide
What is an EPMO?
The Enterprise Project Management Office explained: what it does, how it differs from a PMO, and how to set one up.
The EPMO, defined.
An Enterprise Project Management Office (EPMO) is a central function that governs project portfolio management across the whole organisation. It reports to executive leadership and connects strategy to delivery.
Where a PMO makes sure projects are done right, an EPMO makes sure the right projects are done. It decides what gets funded, keeps portfolios aligned to strategy, and gives the C-suite one real-time view of all work in flight.
IT PMO
Programs & projects
Capital works PMO
Programs & projects
Business PMO
Programs & projects
The EPMO sits above departmental PMOs, connecting them to strategy.
EPMO vs PMO.
Both bring discipline to project work. The difference is altitude.
| Comparison | PMO | EPMO |
|---|---|---|
| Scope | One department, division or program | The whole organisation |
| Reports to | Department or program leadership | C-suite, often the CEO or CFO |
| Focus | Delivery: on time, on budget | Strategy: the right work, funded right |
| Decisions | How projects get done | Which projects get done |
| View | Project and program level | Portfolio and enterprise level |
What an EPMO does.
-
01
Strategic alignment
Keep every program and project aligned to organisational strategy. Kill work that no longer serves it.
-
02
Portfolio governance
One governance framework across the enterprise. Consistent stage gates, approvals and escalation paths.
-
03
Resource optimisation
Balance demand and capacity across all portfolios, not one department at a time.
-
04
Benefits realisation
Track whether finished projects actually deliver the value they promised.
-
05
Standards and methods
Common methodology, templates and tooling. Comparable data from every team.
-
06
Enterprise reporting
Real-time visibility for executives across every portfolio, program and project.
Do you need one?
An EPMO earns its keep when project work outgrows departmental lines. The signals are consistent:
- ✓Multiple PMOs or portfolios with no single view across them
- ✓Projects that finish on time but don’t move strategy
- ✓Resource conflicts settled by seniority, not by data
- ✓Executives asking for one report and getting five
Setting up an EPMO.
-
01
Secure an executive mandate
An EPMO without C-suite authority is a PMO with a longer name. Reporting lines and decision rights come first.
-
02
Define the operating model
Directive, controlling or supportive. Decide how much authority the EPMO holds over portfolios.
-
03
Standardise before you centralise
Common methods, data structures and reporting come before pulling everything into one office.
-
04
Build enterprise visibility
One source of truth across every portfolio. Real-time, not month-end.
-
05
Mature the practice
Move from tracking delivery to steering strategy: prioritisation, benefits realisation, portfolio optimisation.