Webinar recording

Building a High-Impact PMO

Building a High-Impact PMO webinar thumbnail

About this recording

Dr Tony Prensa joins Stuart Easton to discuss what makes a high-impact PMO useful to the business rather than merely busy administering projects. Tony's central diagnosis is that a PMO loses its place when it fails to demonstrate value. Problems such as poor stakeholder engagement, bureaucracy or misalignment may contribute, but he argues that the underlying issue is whether the organisation sees value in what the PMO does.

Tony identifies four defining traits: strategic alignment, agility and adaptability, value-focused delivery and cross-functional influence. He stresses that the PMO's customers and stakeholders define what value means to them, whether that is revenue growth, market share, operational efficiency or reputation.

Stuart distinguishes the value of PMO services to their internal customers from the business impact of the projects themselves. His ducks-and-eggs analogy illustrates the second point: the business does not care about the duck for its own sake; it wants the eggs. Delivering projects and maintaining processes matter because of the business results they help produce.

Become a student of the business

Tony asks PMO leaders to understand how their company makes money, how it competes in its market and what its executives are trying to achieve. That means looking beyond internal project activity to the pressures leaders face, including competition, policy, technology and external changes such as tariffs. The PMO needs to understand those concerns before deciding how to contribute.

Stuart adds that PMO leaders cannot always wait for a complete strategy to be handed to them. They may need to investigate the organisation's goals through available strategy documents, leadership conversations and the business context.

Understand problems and co-create solutions

Tony challenges the reactive approach of asking executives what they want and simply taking notes. Executives do not always know what they need, so a PMO leader who only records their requests may record the wrong things. Understanding the business puts the PMO in a better position to ask useful questions and help people define the real problem.

He illustrates co-creation with a consulting assignment in which he brought managers together to identify their problems and propose solutions. Tony facilitated the exercises but did not prescribe the answers. He presented the managers' conclusions to senior leadership, who supported them. The managers were committed to the resulting actions because they had helped develop them, rather than receiving a consultant's recommendations from outside.

Stuart points to Laura Barnard's IMPACT Engine approach as a way to structure conversations around business problems and develop a PMO vision through engagement, with progress made in 90-day cycles rather than waiting years for a complete transformation.

Build a PMO that can evolve

Tony describes the PMO as a business unit, not merely a department that reacts to requests for project support. It should understand the organisation's business and take an active role in helping it succeed.

His five-element framework starts with a vision and mandate connected to the organisation's purpose. Its remaining four elements are an appropriate governance structure, a maturity path for growing capability, a value-delivery model with KPIs and benefits tracking, and continuous evolution as business needs change.

The maturity path matters because the PMO cannot acquire every capability immediately. Tony advocates an evolution roadmap that develops what the organisation needs over time, while continuing to adapt people, processes and technology.

Apply the four-stage alignment roadmap

For the specific challenge of aligning PMO objectives with strategic goals, Tony presents a four-stage roadmap:

  1. Strategic discovery. Review the organisation's strategy, engage executives and other stakeholders, assess existing PMO services and capabilities, and identify the main strategic themes and gaps. If formal strategy documents are unavailable, use conversations and observation to discover what matters.
  2. Objective definition and alignment. Update the PMO's vision and mission, develop PMO-specific strategic objectives, map those objectives to services and define success measures. This turns strategic alignment from a general ambition into something the PMO can act on and assess.
  3. Execution enablement. Connect those objectives to portfolio prioritisation, resource and capacity alignment, fit-for-purpose governance and communication with the business. These are the structures and practices needed to turn priorities into action.
  4. Review, refine and evolve. Monitor performance, maintain feedback loops with executives, learn from results and adapt PMO services as organisational priorities, technology and circumstances change.

Tony advises PMO leaders not to implement every framework at once. Start with the framework for the problem the organisation is struggling with. For example, if the difficulty is aligning PMO objectives with strategic goals, use the four stages, their activities and supporting tools to develop a practical roadmap or project plan.

He warns against spending so long designing the perfect PMO that the business sees no progress. He advocates short iterations that deliver visible value and urges PMO leaders to "make noise" about what they are accomplishing. If tangible results take too long, people may forget what the PMO does and question why they need it.

Measure business value, not just project completion

Stuart distinguishes business KPIs, such as growth, productivity and customer satisfaction, from PMO KPIs that measure how effectively the PMO operates. Tony argues that completing every project is not sufficient evidence of business value. PMO measures need to connect to outcomes the organisation actually cares about.

Tony offers a list of sample KPIs rather than one universal set. He advises leaders to choose the measures that apply to their organisation and consider what behaviour they want those measures to encourage across the business. His car-dashboard analogy illustrates the principle: many readings are available, but a driver pays particular attention to those that help them reach the destination safely.

Who is responsible for the benefits?

An audience question challenges the suggestion that the PMO should be responsible for delivering benefits when the senior responsible owner or executive sponsor is accountable for them.

Stuart's position: His road-trip analogy makes the sponsor the driver, responsible for reaching the destination, while the PMO builds the road and ensures that it connects. The sponsor has the power to make changes within the business, although that does not make the sponsor a change-management expert. Stuart explicitly says the executive sponsor is still accountable. He nevertheless gives the PMO an extensive responsibility: doing "anything and everything" needed to help the business obtain the benefits, from capturing strategy and selecting projects through delivering outcomes, managing risks, reporting and tracking benefits. He describes maximising the business return from investment in projects as the PMO's fundamental job.

Tony's position: Tony uses the driving analogy differently: he describes the PMO as "the driver", whereas Stuart gives that role to the executive sponsor. He argues that the PMO should drive the journey through continuous conversation, feedback and engagement with the business. He also warns against taking responsibility for doing everything, because that can disconnect the PMO from the people whose participation is needed. His emphasis is on active leadership through co-creation rather than acting alone.

Speak the language of the business

Tony closes with practical advice for earning executive attention. Talk about the business priorities and outcomes leaders care about, not just project terminology and PMO activity. Keep an elevator pitch ready for an unexpected conversation with an executive, and anticipate and rehearse likely objections so that they become opportunities for a more useful discussion.

He also reminds PMO leaders that establishing the function is not the end of the journey. The roadmap needs regular reconsideration as the business changes.

Research in context

PMI's 2026 PMO research: In Bridging the Gap: Positioning PMOs as Indispensable Partners in Strategy Execution, based on the 2025 Global PMO Survey of 1,905 senior leaders and PMO leaders, 78% of senior leaders said strategic alignment should receive high or top priority in PMO resource allocation. Among PMO leaders, 68% reported that it currently receives high or top priority.

The two figures answer different questions: where PMO resources should go and where they go now. That gives PMO leaders a practical test when they map objectives to services in Tony's roadmap: do the PMO's resources back the services that support strategic alignment?

How this connects to TransparentChoice

In the execution-enablement stage of Tony's four-stage roadmap, the PMO connects its objectives to portfolio prioritisation and resource and capacity alignment. That raises a practical question: when several worthwhile initiatives compete for limited funding or people, which combination can the organisation actually support?

TransparentChoice software helps leaders find and compare feasible combinations rather than stop at a ranked list. It brings leadership priorities together with funding, capacity, dependencies and other constraints, so leaders can see which work each option includes, what it leaves out and the funding and capacity it requires. When priorities or assumptions change, they can rerun the comparison to test whether the previous choice still holds.

Learn more

How can a PMO start with business problems and keep showing progress?

Laura Barnard's IMPACT Engine develops the business-first approach Stuart mentions, with a six-stage framework and 90-day cycles of visible progress. Explore Laura Barnard's IMPACT Engine webinar.

What does business-led prioritisation look like in practice?

The Harbor Foods case describes how a developing PMO involved business leaders in setting priorities and assessing an accumulated project backlog. Explore the Harbor Foods PMO case.

Speakers in this recording

Dr Tony Prensa, CEO of TP Global Business Consulting
Dr Tony Prensa

Tony Prensa helps organizations turn strategy into execution. With 35+ years in project leadership and AI-enabled transformation, he builds high-performing PMOs that align portfolios to business goals, accelerate delivery, and prove value. He is the author of The Digital Project Playbook and a long-time educator and mentor.

Stuart Easton, Founder & CEO at TransparentChoice
Stuart Easton
Founder & CEO, TransparentChoice

Stuart Easton is Founder & CEO of TransparentChoice. He works with leaders and portfolio teams on decisions about which investments and initiatives to fund, continue, change, defer or stop when priorities compete for limited funding and capacity. His work combines structured decision-making with practical portfolio choices.