Project Management

Please login or join to subscribe to this thread

What factors have contributed to the growing dichotomy between traditional PMOs and the emerging value-driven approach?

linkedin twitter facebook   PMO  
avatar
Fabian Crosa
Community Champion
PMO Leader | Speaker & Mentor | Content Leader – PMOGA Latin America Hub| Catholic University of Uruguay Montevideo, Montevideo, Uruguay
In today’s rapidly evolving business landscape, organizations are under increasing pressure to deliver not just outputs, but measurable value. This shift has exposed a growing divide between traditional PMOs — often centered on processes, compliance, and control — and modern value-driven models that prioritize adaptability, strategic alignment, and continuous improvement. As stakeholder expectations evolve and agility becomes a competitive necessity, many PMOs find themselves at a crossroads.

What factors have contributed to the growing dichotomy between traditional PMOs and the emerging value-driven approach?
Sort By:
avatar
Laura Lazzerini
Community Champion
Head of International Project Management Office| Deutsche Telekom Praha, Czechia
I would say that uncertainty and VUCA environment have contributed for sure. In addition to that the variety of ways of working (still linked to uncertainty) and therefore the need for a high customization
avatar
Francisco Herrera
Community Champion
Program Manager, PPM&PMO Specialist.| Coppel, Mexico. Culiacán, Sinaloa, Mexico
Fabian, that's a really interesting point about the shift in PMOs. In my company, we saw something similar. The PMO became very bureaucratic, and it seemed like they were only focused on status reports. Because of that, we even had to rebrand it so people would see it as a driver of results, not just a reporting and auditing group. I think the lack of real results, because they were just informing instead of contributing, was a big factor in that dichotomy.
I hope this helps, regards!
avatar
Svenja Merle Kassel, Germany
Hi Fabian,
a really interesting question! When I started at my current position the management expectation was "make it easy" - because project management had indeed become very bureaucratic as Francisco Herrera also describes.
So my daily business is balancing between
1> corporate project management standards and requirements
2> management expectations
3> project managers struggeling in real-life topics and that cannot be solved with a and/or 2
I do not see myself shifing between "traditional PMO" and "value-driven PMO" - me and my local PMOs are being everything at once ;-)

What is the situation like at your end, Fabian (marking you with @fabian did not work)?
avatar
Luis Branco CEO| Business Insight, Consultores de Gestão, Ldª Carcavelos, Lisboa, Portugal

Fabian Crosa
The growing dichotomy between traditional PMOs and value-driven PMOs stems from a confluence of internal and external factors that reflect the changing nature of work, stakeholder expectations, and competitive dynamics. Here are the key contributors:
- Shift from Project Outputs to Business Outcomes
Traditional PMOs have focused on delivering scope, time, and cost according to plan.
However, organizations now demand value realization—strategic impact, customer satisfaction, and measurable benefits.
This shift exposes the limitations of PMOs that prioritize control over contribution.

- Rise of Agility and Adaptive Delivery Models
Agile, hybrid, and lean approaches emphasize flexibility, learning, and iterative value delivery.
PMOs rooted in rigid methodologies struggle to support these models unless they reinvent themselves to become enablers of agility rather than gatekeepers of conformity.

- Evolving Stakeholder Expectations
Executives and sponsors now expect PMOs to act as strategic partners, not merely as administrative units.
Value-driven PMOs help connect portfolio decisions to strategy execution, emphasizing benefits realization and business agility.

- Technology Disruption and Digital Transformation
Digital technologies have shortened innovation cycles and raised the bar for responsiveness.
Traditional PMOs, designed for stability and control, often lack the speed and responsiveness required to navigate such environments.

- Cultural and Generational Shifts in the Workforce
The modern workforce values purpose, autonomy, and collaboration.
PMOs that cling to top-down control structures often clash with team expectations, while value-driven PMOs empower teams and promote a culture of learning and continuous improvement.

- The Maturity Gap in Value Measurement
Many traditional PMOs lack mechanisms to define, measure, and track value throughout the project lifecycle.
The inability to connect project activities to strategic value has widened the relevance gap.

In summary, this dichotomy reflects a broader organizational transformation.
Traditional PMOs focused on doing projects right; value-driven PMOs are focused on doing the right projects—and doing them in the right way for maximum value.

avatar
Mayte Mata Sivera PMO Leader | Speaker | Author Ut, United States
Several factors are contributing to the shift from traditional PMOs to more value-driven models as some other participants noted.
However, be careful on seeing it as a black-and-white choice. Some organizations need to start with traditional structures to build governance, establish priorities, and get visibility over delivery. That foundation can later evolve into something more strategic.
From experience, I’ve seen PMOs struggle when they were too rigid or process heavy. However, the ones that succeeded adapted to changing business needs and made a clear effort to align with strategy.

One of the biggest enablers? Where the PMO sits in the organization. A PMO reporting to the CIO or COO....or better, with a seat at the executive table... is more likely to be part of leadership conversations, which makes strategic alignment and value delivery much more natural.

Also worth noting: the rise of xMOs reflects this evolution. These models are designed to focus less on control and more on business outcomes, helping bridge the gap between delivery and strategy.
avatar
Mike Frenette Manager, IT PMO| Halifax Water (retired) Halifax, Nova Scotia, Canada

It may not be the case yet, but the emergence of PMI's "Project Management Offices - a practice guide", the Value Ring Framework it encapsulates and the new PMI-PMOCP certification will cause a sea change in the way PMOs are staffed and managed.

Some PMOs are process and policing PMOs, some are delivery PMOs with all PMs reporting to them, some are links between organizational strategy and program/project delivery, helping to manage the various organizational portfolios. And of course, some PMOs are some or all of these, or something else altogether.

The days of answering the question, "What type of PMO should you implement?" are coming to an end. There is no PMO Type. There are only PMOs that respond initially and then on an ongoing basis to the needs of their identified PMO Customers.

PMOs must deliver organizational value, or risk being the first to be cut when the going gets tough. And that value must be defined by the organization, not by the PMO Manager. It's much like a project, really. How many of us guess at user requirements and expected benefits? Not many these days (I hope!).

A great way to set up your change your PMO is to identify your PMO Customers (and surely the Senior Executive Team, their direct reports, project managers and project teams will be among them) and then survey them for their opinion to find out what they need.

But you don't start with a blank slate. Avoid asking your PMO Customers what they want the PMO to do. Ask instead what value they want to gain from the PMO.

Start with the thirty most common PMO Outputs identified in the Value Ring Framework, prioritize them, and start knocking them off one by one, just like a Product Backlog, considering a mix of low hanging fruit and long term needs that will keep your PMO off the chopping block. These outputs must not be confused with project outputs. They are PMO Outputs, and in the original rendition of the Value Ring Framework (called a methodology at that time), they were called Values. Once the priorities are set, the functions a PMO must perform become clear, because the twenty-six most common functions a PMO could perform form many-to-many relationships with the PMO Outputs.

Everything flows from there.

Sound easy? Well, its not! But it is structured while being flexible and it starts how we should always begin with in the PPM world - customer requirements resting on a business case.

And if your PMO Customers, when asked (and you must ask them) say you are not delivering value, it doesn't matter if you think you are. Because value, like beauty, is always in the eye of the beholder. So when you ask, listen up! And then change accordingly.

The good news is that existing PMOs don't have to be burned at the stake and new PMOs resurrected from their ashes! Existing PMOs need only pick up the PMO Practice Guide and start living the dream. ;)

Please login or join to reply

Content ID:
ADVERTISEMENTS

"If you work on a lobster boat, sneaking up behind people and pinching them is probably a joke that gets old real fast."

- Jack Handey

ADVERTISEMENT

Sponsors