“We need to regain control of our projects: should we hire a PMO or a project manager?” The question is put in these terms by a department opening a position, or reviewing its organisation after a series of delays. It assumes that the two roles are two possible answers to the same need. They answer two different needs.
The difference between a PMO and a project manager lies in what each is accountable for. The project manager answers for a project: its result, its timescale, its budget. They lead the team and decide within the limits delegated to them. The PMO, understood here as the person or small team performing the function, answers for the reliability of management information and the application of a common framework, on a large project, a programme or a portfolio. It does not deliver the project and does not decide in place of those who lead it. Choosing between the two therefore comes down to naming what is missing: someone to answer for a result, or someone to make projects readable and comparable.
What each answers for before senior management
The project manager is the person the sponsor calls when the date slips. They hold the plan, lead the team, deal with the supplier, handle risks and issues, and ask for the arbitrations that go beyond their delegation. This delegation has limits: the PRINCE2 method calls them tolerances, and the project manager only alerts the board if they forecast exceeding them. In a matrix organisation, they also lead people who do not report to them.
The PMO is the person senior management calls when it no longer knows which project is really late. Its object is information that is honest and comparable from one project to another: the same milestone definitions, the same rules for moving from green to amber, the same format for an arbitration request. It prepares committees, follows up the application of their decisions and raises the alert when a project’s declared status no longer matches the facts. Its authority, when it has any, concerns method. The content of the project remains with the project manager.
The ISO 21502:2020 standard on project management in fact devotes two separate headings, in its part on project organisation and roles, to the “Project manager” (4.5.6) and the “Project office” (4.5.7). The acronym PMO also refers to the structure, with its responsibilities and variants: our entry on the definition of the PMO presents them, and we do not return to them here.
Difference between a PMO and a project manager: the two roles side by side
| Project manager | PMO | |
|---|---|---|
| Scope | One project, from launch to closure | A large project, a programme or a portfolio, depending on where it sits |
| Accountability | Delivering the expected result, within the agreed timescale and budget | Providing reliable management information and enforcing the common framework |
| Decisions | Decides within delegated limits, proposes beyond them | Investigates options, raises alerts, follows up application; does not decide on project content |
| Deliverables | Project plan, schedule, budget, progress reports, arbitration requests | Consolidated view, dashboard, committee files, decision logs, common templates |
| Authority | Over the project team, most often without a reporting line | Over method, if the mandate provides for it |
| Duration | That of the project | That of the programme, or permanent at portfolio level |
| Reports to | Sponsor or steering committee | Programme director, CIO or executive management, depending on scope |
The “Decisions” line is where confusion costs the most. A PMO that arbitrates the scope of a project it does not answer for, or a project manager who expects the PMO to make up their delay: in both cases, no one any longer answers for the result.
The situations that call for a project manager
The need is for a project manager when an important project has no one to answer for it. Several situations signal this. The project is run “on the side” by a business manager or a technical expert whose main job is elsewhere. Contributors each move forward on their own part, and integration, dependencies and acceptance testing belong to no one. The supplier has no counterpart able to accept, refuse or arbitrate. Requests go straight up to the sponsor, for lack of anyone to investigate them.
One test is enough: ask whom the sponsor would call if go-live had to be postponed. If the answer includes several names, or none, a project manager is missing. Adding a PMO at this point would only produce a better-documented delay.
The signs that a PMO is missing
The need changes in nature when each project has its manager and the difficulty lies between projects, or above them. Senior management receives as many report formats as there are projects, and can neither compare nor add them up. The same experts are booked by several projects without anyone seeing the total workload. Decisions taken in committee are not acted upon, because no one is responsible for checking.
One case concerns a single project. When it is large enough for its manager to spend their days maintaining the schedule, the budget and committee preparation, a project PMO takes over this load, under their authority, and gives them back the time to lead.
The mandate, reporting line and size of the function are then decided case by case: our page on setting up a PMO describes how to settle them, starting from the decisions senior management wants to be able to take.
When both are needed: a written boundary
On a programme or a very large project, the two roles coexist, and the boundary is settled object by object. The schedule belongs to the project manager; the PMO consolidates it with those of the other projects and checks its consistency. The risk register is maintained by the PMO, while each risk keeps its owner in the project. For the committee, the PMO prepares the file, the project manager presents the status of their project and their requests, the sponsor decides.
One rule protects both roles. The PMO does not publish a status on a project that the project manager has not seen. In the event of disagreement, both readings are presented to the committee, each under its author’s name.
Outside the case of a directive PMO, whose mandate entrusts it with managing project managers, neither is the superior of the other. They report to the same person, each on their own subject. On a programme, that person is the programme director, who decides and answers for the overall result: our page on programme management describes this third role, often confused with the other two.
The confusions that cost a hire
The first consists of hiring a PMO and expecting it to “move projects forward”. Without authority over the teams or accountability for the result, it can chase; arbitration is beyond its reach. Senior management ends up blaming it for delays it had no means of dealing with.
The second is symmetrical: entrusting a project manager with consolidating neighbouring projects. Their own project suffers, and their peers see in them a colleague who evaluates them.
The third has to do with job titles. Calling a project manager’s assistant post “PMO”, or calling a coordinator who decides nothing “project manager”, announces an accountability that the mandate does not give. Candidates are mistaken about the post, then teams about who they are dealing with.
Before publishing the advertisement, the decision to be taken fits in two lines: what the person hired will answer for, and what they will be able to decide alone. If the first line names a result to be delivered, the post is that of a project manager. If it names information to be made reliable so that others can decide, it is a PMO, and it remains to check that each project already has its manager.