The best practice that matters most in a project management office is deciding what the PMO is for, writing it down, and refusing the work that does not serve it. Everything else follows from that. A PMO that cannot say in one sentence which decisions it exists to improve will drift into administration, and an administrative PMO is the first thing cut when budgets tighten, because nobody outside it can describe what would be lost.
This page is about running a PMO well. If you are standing one up, start with how to set up a PMO. If you want the catalog of things a PMO can do, see PMO functions. What follows assumes the office already exists and the question is whether it is any good.
Key takeaways
- Define the PMO's purpose as a set of decisions it improves, not a list of services it offers.
- Measure the PMO on portfolio outcomes (throughput, benefits, decision speed), never on its own output (reports produced, templates published).
- Standardize the minimum that makes projects comparable, then stop. Every extra mandatory field is a tax collected from delivery teams.
- Own the intake queue. A PMO that cannot influence what enters the portfolio is a reporting function.
- Report exceptions and the decisions needed, not a compendium of everything that happened.
- Publish a data set the organization cannot get anywhere else. That, not authority, is what makes a PMO permanent.
What are PMO best practices?
PMO best practices are the operating habits that make a project management office improve decisions rather than collect paperwork: a written mandate tied to specific decisions, a minimum viable standard for project data, ownership of portfolio intake and prioritization, exception-based reporting, honest capacity planning, and metrics that measure portfolio outcomes instead of PMO activity.
The 12 PMO best practices
1. Write a mandate in terms of decisions, not services
"We provide governance, reporting, and delivery support" describes a cost center. "We decide which projects start, we tell leadership when the portfolio is over capacity, and we own the benefits data" describes an office with teeth. The mandate belongs in a PMO charter, signed by a sponsor with budget authority, and it should name the decisions the PMO owns, the ones it informs, and the ones it stays out of.
2. Pick a PMO type deliberately
A supportive PMO offers templates and coaching and holds no authority. A controlling PMO sets standards and enforces compliance. A directive PMO employs the project managers and delivers the work. Most PMOs fail by claiming one type while being resourced for another: handed a controlling mandate with supportive staffing, they spend their days chasing compliance they cannot enforce. Our guide to PMO structure covers the three models and how to choose between them.
3. Standardize the minimum, then stop
The purpose of a standard is comparability. You cannot prioritize a portfolio whose projects estimate cost differently. So mandate the fields that make projects comparable (cost, benefit, strategic objective, capacity demand, dependencies, risk) and leave the rest to the delivery team. Every additional mandatory field is a tax, paid by people who could be delivering, collected in exchange for a report nobody reads. Ask of each template: which decision changes if this field is blank?
4. Own intake, or accept that you are a reporting function
This is the practice that separates PMOs with influence from PMOs with dashboards. If work can reach delivery teams without passing through a defined project intake process, then the portfolio is set by whoever has the loudest sponsor, and the PMO's job shrinks to counting the damage afterward. Intake does not require a power of veto. It requires that every request is captured, sized, and scored against the same criteria before anyone starts.
5. Prioritize with an explicit, published model
Scoring is not about arriving at a mathematically correct ranking. It is about making the trade-off visible, so that a senior leader who overrides it has to do so in public. Publish the criteria, the weights, and the resulting order. Our guides to project prioritization criteria and the project scoring model cover the mechanics. The governance value sits in the audit trail, not in the arithmetic.
6. Plan capacity against real availability, not headcount
A five-person team does not deliver five person-months a month. Once you subtract leave, support duty, meetings, and the operational work that never appears in any plan, deliverable capacity sits well below headcount, and that gap is where portfolio commitments go to die. Measure your own ratio and use it. Resource and capacity planning is the highest-return analytical thing a PMO does, because it is the only evidence that converts "we are too busy" into a number leadership can act on.
7. Report exceptions and decisions, never a compendium
The test of a portfolio report is whether removing it would change any decision. Lead with what is off track, what decision is needed, from whom, and by when. Put the full inventory in an appendix nobody has to read. A forty-page monthly pack that arrives three weeks after the data was true is a ritual, not reporting. Our guide to PMO reporting and portfolio dashboards covers the cadence.
8. Stop projects on purpose, and say so out loud
A portfolio in which nothing is ever cancelled is a portfolio in which nothing is genuinely prioritized. Build a stopping decision into the review cycle: at each gate the question is not only "is this on track" but "would we fund this today if it arrived as a new proposal". The first cancellation is the hardest and the most valuable, because it proves the governance is real. See the stage gate process and the portfolio review meeting.
9. Track benefits after handover, when nobody wants to
Projects are approved on promised benefits and closed on delivered outputs, and the gap between the two is where organizational learning is supposed to happen. A PMO that owns benefits realization holds the only feedback loop that makes next year's business cases more honest than this year's. It is unpopular work. It is also the clearest available demonstration that the PMO serves the organization rather than the project managers.
10. Make the PMO the source of data nobody else has
Authority can be revoked. A data set cannot. If the PMO is the only place that knows what the organization is working on, what it costs, who is committed where, and what was promised, then removing it is structurally difficult regardless of who is running finance this year. Build that data set early and keep it accurate, even when a report nobody requested has to wait.
11. Serve delivery teams, not only leadership
A PMO seen as an audit function receives audited answers. Project managers will tell you whatever keeps you away, and your portfolio data quietly becomes fiction. Give the teams something they want: fast escalation of blockers, dependency chasing taken off their plate, estimating history they can reuse, and a defense when the portfolio is over capacity. The accuracy of your data is a direct function of how the people entering it feel about you.
12. Review the PMO itself on a schedule
Put an annual item on the governance calendar: what did the PMO decide this year, what changed as a result, and what should it stop doing. Volunteer to retire the reports that no longer drive a decision. A PMO that regularly proposes cutting its own output is one that will still exist in five years. Use the PMO maturity model to frame the assessment.
PMO best practices checklist
Score your own office. Anything you cannot answer with evidence is a no.
| Area | The question | Evidence that it is true |
|---|---|---|
| Mandate | Can you name the decisions the PMO owns? | A signed charter naming them, dated within 24 months |
| Sponsorship | Does your sponsor control budget? | They have funded or cancelled something on the PMO's advice |
| Intake | Can work start without passing through intake? | Every active project has an intake record and a score |
| Prioritization | Are the criteria and weights published? | A ranked list exists, and overrides are logged |
| Capacity | Do you know deliverable capacity, not headcount? | A measured availability ratio, refreshed each quarter |
| Standards | Can you justify every mandatory field? | Each one maps to a decision it informs |
| Reporting | Does the report lead with decisions needed? | Page one is exceptions, not an inventory |
| Stopping | Has anything been cancelled in the last year? | A named project, a date, and the redeployed budget |
| Benefits | Is anyone measuring benefits after handover? | A benefits register holding post-handover actuals |
| Trust | Do project managers bring you bad news early? | Red statuses appear before the deadline, not after it |
Why do PMOs get shut down?
Rarely for incompetence. The pattern is consistent, and it is a failure to articulate value rather than a failure of quality.
- The PMO measures itself on its own output. Reports issued, templates published, compliance rate. Every one of those can rise while the portfolio delivers less. When the cost review arrives, the office can describe its activity but not its effect.
- It optimizes for the executive audience only. Delivery teams experience it as overhead, so when the PMO needs defenders it has none.
- It confuses process compliance with governance. Every gate attended, every template filed, and no project ever stopped. Governance that never says no is theater, and everyone in the organization knows it.
- It never chose a type. It offers coaching, demands compliance, and holds authority to enforce neither, so it does all three badly.
- Its data is wrong and everybody knows. Once a portfolio report has been contradicted twice in a leadership meeting it stops being consulted, and an unconsulted report is a line item awaiting deletion.
The countermeasure to all five is the same. Tie the PMO's reported measures to portfolio outcomes, and make sure at least one uncomfortable decision each year visibly traces back to the PMO's analysis.
How do you measure PMO success?
Measure the portfolio, not the office. Useful measures are throughput (projects completed per quarter), cycle time from intake to start, forecast accuracy, the share of the portfolio aligned to a named strategic objective, benefits realized against benefits promised, and the number of initiatives stopped. Avoid counting reports produced, templates adopted, or compliance rates, each of which can improve while delivery gets worse.
Choose four or five and hold them for a year. A PMO that changes its scorecard annually is a PMO that has not yet found a measure it is willing to be judged on. Our guide to PPM KPIs and portfolio metrics works through the definitions and the traps hiding in each one.
Do PMO best practices change by PMO type?
The principles hold. The emphasis shifts.
| PMO type | Where the value is | The practice that matters most | The failure mode to watch |
|---|---|---|---|
| Supportive | Making good practice easy to adopt | Serve delivery teams (practice 11) | Producing assets nobody uses |
| Controlling | Comparable data and enforced standards | Standardize the minimum (practice 3) | Compliance theater and quiet workarounds |
| Directive | Consistent delivery under one accountability | Capacity planning (practice 6) | Becoming a resourcing pool with no strategic voice |
| Enterprise (EPMO) | Connecting strategy to funded work | Own intake and prioritization (practices 4 and 5) | Distance from delivery reality |
An enterprise PMO reporting to the CEO or CFO has a different job from a departmental PMO reporting to an IT director, and copying the enterprise playbook into a departmental office produces an office with strategic language and no strategic authority. Match the practice to the mandate you actually hold. The same logic applies to a program management office, whose value comes from coordinating across projects that share a benefit rather than from standardizing the whole estate.
Frequently asked questions
What makes a PMO successful?
A successful PMO improves specific decisions and can prove it. That requires a written mandate naming those decisions, a sponsor with budget authority, ownership of portfolio intake, accurate capacity data, and metrics tied to portfolio outcomes rather than to the PMO's own output. Offices that cannot name the decisions they improve tend not to survive a budget review.
What are the most common PMO mistakes?
Measuring PMO activity instead of portfolio results, mandating templates that inform no decision, reporting an inventory rather than exceptions, never stopping a project, and serving leadership while treating delivery teams purely as data sources. Each one degrades the accuracy of the portfolio data the PMO depends on to be useful at all.
How long does it take for a PMO to show value?
The first credible value usually arrives within a quarter, and it is almost always the same deliverable: an accurate, complete list of active work with its cost, its owner, and the strategic objective it serves. Organizations building that list for the first time routinely find work with no live sponsor or no current business case. Deeper measures such as benefits realization take a year or more.
What is the difference between PMO standards and PMO best practices?
Standards are the rules a specific PMO mandates: which templates, which fields, which gates. Best practices are the general habits that make those standards worth having. A PMO can enforce its standards perfectly and still be a poor PMO if the standards inform no decision. Standards are local. The practices behind them travel.
How many people should a PMO have?
There is no defensible ratio, because it depends entirely on the mandate. A supportive PMO serving thirty projects can run on two or three people. A directive PMO that employs the project managers scales with the portfolio. The useful question is not headcount but whether the office has capacity left for analysis, since a PMO fully consumed by report production has no time to improve any decision.
Should the PMO report to the CIO or the CEO?
It should report to whoever owns the decisions in its mandate. A PMO governing IT delivery belongs under the CIO. An enterprise PMO allocating investment across the whole organization needs a sponsor who controls that investment, typically the CEO, COO, or CFO. Reporting one level below the decisions you are meant to influence is a structural handicap that no amount of good practice corrects.
Related reading: PMO roles and responsibilities, project portfolio governance, and lean portfolio management for the agile funding model.