Standing Up a PMO: The Common Mistakes Teams Make and How to Avoid Them
A Project Management Office (PMO) is a centralised function that standardises project management practices, provides project oversight, and in some organisations directly manages a portfolio of projects. When a PMO works well, it reduces the cost and risk of project delivery, improves visibility into project status across the portfolio, and builds project management capability across the organisation. When it does not work well, it becomes an administrative burden that project teams route around and senior leaders ignore.
In 2022, many organisations -- particularly those in public sector, infrastructure, and capital delivery -- are standing up or reforming their PMOs in response to project failures, audit findings, or governance requirements. Here are the common mistakes that derail PMO implementations and how to avoid them.
Mistake 1: Building a PMO Around Process, Not Value
The most common PMO mistake is building a function focused on process compliance rather than project outcomes. A PMO that measures its success by the percentage of projects following its templates and attending its gates is a compliance function, not a delivery improvement function. The question a PMO should be asking is not 'are projects using the right templates?' but 'are projects delivering the right outcomes?' Process compliance may be one input to that question, but it is not the answer.
Mistake 2: Staffing With Administrators Instead of Experienced Practitioners
PMOs are often staffed with project coordinators and administrators who have process skills but limited delivery experience. This limits the PMO's ability to provide the value that project teams most need: challenge and coaching on project decisions. An experienced project manager who has navigated a major scope change or a supplier failure is more valuable to a PMO than an administrator who can enforce template completion rates. Staff the PMO with people who have delivered projects, not just documented them.
Mistake 3: Implementing Everything at Once
A PMO that tries to standardise everything simultaneously -- methodology, tools, governance, reporting, resource management, benefits tracking -- overwhelms project teams and creates resistance. The implementation effort itself becomes a risk to the projects the PMO is supposed to support.
Start with the interventions that have the highest impact on the organisation's specific pain points. If the biggest problem is that projects run out of budget without warning, start with financial tracking and forecasting. If the biggest problem is late scope changes, start with change control. Build the PMO from the most urgent value backwards.
Set a 90-day horizon for the first meaningful outcome. A PMO that cannot demonstrate value within 90 days of standing up is unlikely to survive long enough to deliver it.
Mistake 4: Treating the PMO as Permanent Rather Than Adaptive
The project portfolio changes. The organisation's maturity changes. The PMO should change with it. A PMO designed for a phase of rapid project stand-up is different from a PMO designed for a phase of project delivery and close-out. Set a formal review of PMO scope, structure, and staffing at the 12-month mark and annually thereafter.
XNM provides project management office advisory services to public-sector and capital-project clients, including PMO design, setup, and governance. Reach out to XNM's program & project delivery advisory team to discuss PMO design and implementation for your organisation.