What type of PMO should be set up: an office that helps project managers, an office that checks their work, or an office that directs the projects itself? The question concerns the criterion that separates the types of PMO: the authority entrusted to the office.
These types are indeed distinguished by what the office can require of projects. The supportive PMO, or support PMO, proposes a method, templates and advice that everyone remains free to follow. The controlling PMO sets a framework and checks that it is applied, without running the projects. The directive PMO runs the projects, with project managers who report to it. From one type to the next, the office gains power and takes a greater share of responsibility for the result.
A second classification, by scope (project, programme, portfolio), intersects with this one: our article on the role and responsibilities of the PMO is devoted to it.
The types of PMO on a scale of authority
| Supportive PMO | Controlling PMO | Directive PMO | |
|---|---|---|---|
| What it can require | Nothing: it proposes | Conformity with a common framework | The work itself: it assigns and directs |
| Position towards project managers | A service they call on | A checker, with no reporting line | Their line management |
| Who answers for a project’s result | The project manager and their department | The project manager and their department | The PMO, through the project managers it manages |
| What it needs to hold | Project managers who find it worthwhile | A written mandate from senior management and follow-through on variances | Project managers reporting to it and a sponsor who addresses it |
| Possible drift | A catalogue nobody opens | Superficial conformity | Business departments losing interest in their projects |
These three types form a typology from common usage, used here as a reference point. An office’s place in this table can be read in its written mandate. Our entry on the definition of the PMO gives the short version of this typology.
What separates one type from the next
Between support and control, the threshold is obligation. It can be recognised by one question: what happens when a project manager does not apply what the PMO has planned? If nothing happens, the office is a supportive PMO, whatever its name. If the variance is recorded and brought before an authority that draws a consequence from it (a milestone that is not passed, a budget that is not released), the office controls. The obligation comes from senior management, and the PMO is its checker.
Between control and the directive type, the threshold runs through the reporting line. A controlling PMO observes and reports, while the project manager continues to answer for their project to their sponsor. A directive PMO receives this responsibility: it appoints the project manager, validates their plan and reports on the result. In the first two types, the boundary between the two roles is the one described in our article on the difference between a PMO and a project manager.
Each threshold also changes the nature of the information. The supportive PMO sees what project managers choose to show it. The controlling PMO sees what the rule requires to be declared, at the risk of an embellished declaration. The directive PMO itself produces the status of the projects it runs: senior management no longer has a second reading, unless it asks someone outside the office for one.
Which situation each type answers
The supportive PMO fits when projects are run by experienced project managers, in departments that value their autonomy, and when executive management does not yet ask to compare projects with one another. It reaches its limit when a consolidated view is expected: optional practices can produce data that does not add up.
The controlling PMO answers this expectation. It is also justified when the same management failing recurs from one project to another, or when a third party (auditor, supervisory authority, customer) asks for proof that steps have been followed. It assumes a framework already tested, graduated according to the size and risk of the projects.
The directive PMO fits a set of projects that senior management wants to see run by a single hand: a programme whose failure is not acceptable, projects entrusted to novice project managers, an organisation that brings its project managers together in one team. The teams, for their part, can remain in their departments, as in the matrix organisation. This type has a cost: business departments lose the running of their projects and may lose interest in them, even though they remain the only ones able to say whether the result serves them.
In all three cases, the type governs how projects are run. The choice of projects to launch, postpone or stop belongs to senior management or its committee, whatever the office’s degree of authority: this is the subject of project portfolio management.
The same office can combine degrees
Authority is set for each service provided: an office can be directive on the programme senior management has entrusted to it, a checker on the commitment milestones of all projects, and simple support for the rest. A useful charter therefore writes the authority next to each service.
Two combinations call for a precaution. The first brings together support and control on the same object: the person who helped a project manager put together their milestone file cannot judge its conformity without judging themselves. Splitting the two roles between two people removes the difficulty. The second is that of the office that directs some projects and controls the others: project managers outside the office may doubt that its own projects are judged with the same rigour, and checking them is best entrusted to someone else.
How a PMO changes type
A PMO changes type through a decision by senior management, written and announced. It also happens that it changes type without a decision.
Towards more authority, each step has its prerequisite. Moving from support to control assumes that the framework has been used on volunteer projects, that senior management has said what becomes mandatory, and that it has planned the follow-through on variances. Moving from control to the directive type is a reorganisation, to be conducted as such: project managers change reporting lines, departments lose a responsibility.
The reverse movement exists. A directive office created for a programme can return to control when the programme ends, or when the project managers it has trained can run projects on their own.
Drifts without a mandate can be spotted through facts. A supportive PMO refuses a milestone when nothing authorises it to. A controlling PMO rewrites a project’s schedule and finds itself answering for it. A directive PMO, deprived of its project managers by a reorganisation, keeps its name and has only the power to advise. In each case, the written mandate and practice have diverged: our page on setting up a PMO describes how to settle this mandate with senior management.
Whether it gains or gives back authority, a PMO changes type on a date known to project managers, and the charter carries this date.