{"id":26025,"date":"2025-02-17T22:13:36","date_gmt":"2025-02-17T22:13:36","guid":{"rendered":"https:\/\/www.psoda.com\/global\/?p=26025"},"modified":"2025-02-18T01:55:17","modified_gmt":"2025-02-18T01:55:17","slug":"pmo-transformation-gatekeeper-partner","status":"publish","type":"post","link":"https:\/\/www.psoda.com\/global\/2025\/02\/17\/pmo-transformation-gatekeeper-partner\/","title":{"rendered":"The PMO Paradox \u2013 Gatekeeper or Partner"},"content":{"rendered":"

Few organisational entities generate as much passionate debate as PMOs<\/a>, or Project Management Offices to give them their formal title. For some, the mere mention conjures up images of bureaucratic nightmares with endless templates, rules and checklists. For others it\u2019s completely different. The PMO is seen as a crucial support system that enables project success. Why the difference? It comes down to whether they are a gatekeeper or partner PMO.<\/p>\n

The Tale of Two PMOs<\/span><\/h2>\n

Consider the following two scenarios, both of which play out daily in organisations worldwide.<\/p>\n

The Gatekeeper PMO<\/span><\/h3>\n

In organisation A, project managers dread the start of the week. Mondays find their inboxes full of automated reminders about overdue status reports, upcoming gate reviews and mandatory process training sessions.<\/p>\n

Project managers spend nearly 30% of their time maintaining multiple reporting templates; one for the PMO, one for the executives and one for their business unit.<\/p>\n

When a project manager proposed an agile approach for a time sensitive project they faced weeks of back and forth with the PMO. \u201cWe need to follow our waterfall methodology\u201d was the response, accompanied with a 50 page process document. By the time approval to proceed was granted the project was already weeks behind schedule.<\/p>\n

The PMO\u2019s monthly project review meetings are seen as interrogations instead of discussions. Project managers present using a mandatory 30 page slide deck regardless of project size or complexity. Questions focus on compliance with process rather than actual project challenges or risks. Innovation is discouraged and lessons learned gather dust in a SharePoint repository that nobody ever accesses.<\/p>\n

Projects repeat the same mistakes over and over again.<\/p>\n

The Partner PMO<\/span><\/h3>\n

Contrast that with organisation B where the project managers have a very different experience. Their PMO is headed up by a former project manager and operates on a simple principle: Our success is measured by our project managers\u2019 success.<\/p>\n

When a new project manager joins the organisation the PMO sets up a one on one meeting with them. This meeting is designed to get to know the new project manager, understand their experience level and their immediate needs. At this meeting they are given a simplified set of templates that are tailored to their project\u2019s size and complexity. They\u2019re also introduced to a mentor who can guide them through the first few months in the new organisation. Rather than enforcing a one size fits all approach they adapt their processes to each project.<\/p>\n

The PMO team regularly attend project team meetings, not to police them but to observe and identify common challenges and improvement opportunities. During these meetings the PMO picked up that resource allocation is a common problem. In collaboration with the project managers the PMO developed a resource management solution that would actually be used.<\/p>\n

The monthly PMO reviews focus on helping projects succeed. Instead of rigid presentations they use the time to facilitate problem solving discussions. When projects have problems the PMO team\u2019s first response is \u201chow can we help?\u201d rather than \u201cwhy didn\u2019t you follow the process?\u201d<\/p>\n

Most telling is their approach to lessons learned. Rather than wait for projects to finish the PMO facilitates regular \u201clearning moments\u201d sessions where project teams share their challenges and solutions. These insights are captured in a searchable knowledge base with practical, context rich summaries. The PMO team actively curates this information and they connect project managers facing similar problems with their colleagues who have dealt with similar issues in the past. They even organise informal \u201cwar stories\u201d lunches where project managers share their stories over pizza, building both knowledge and, more importantly, community.<\/p>\n

The PMO also maintains a \u201cquick wins\u201d database where project managers can find solutions to common problems as well as templates and strategies that have worked in similar situations. When new projects are initiated the PMO proactively shares relevant lessons and connects new project managers with experienced colleagues who have handled similar initiatives.<\/p>\n

The Impact on Project Success<\/span><\/h2>\n

The difference in results from the two approaches is stark.<\/p>\n

In organisation A, the control focused approach has lead to:<\/p>\n