Webinar recording

From Project Police to Strategic Partner: How PMOs Become the Value Engine that Leaders Respect

From Project Police to Strategic Partner: How PMOs Become the Value Engine that Leaders Respect webinar thumbnail

About this recording

One organisation ranked 800 projects from first to last. All 800 were still running. Stijn Janssens uses the example to show that a priority order is not yet a choice about what the organisation can support. Alongside Alexander David and TransparentChoice's Dan Dures and Stuart Easton, he explores what it takes for a PMO to help leaders make those choices while retaining the confidence of the people delivering the work.

Define value in the organisation's own terms

Alexander wants PMOs to move beyond status reports and RAG ratings to the outcomes an investment is meant to create. In commercial organisations, that may mean financial return, profitability or customer measures. Stijn draws on public-sector experience to make the counterpoint: better public services, such as patient care, matter even when their value is difficult to express in money. Both argue that project benefits need to connect with the organisation's goals, rather than expecting executives to value methodology for its own sake. Dan also raises the delay between project delivery and benefits realisation; Stijn explains how accountability can weaken when people move on before the benefits arrive.

Alexander distinguishes the outcomes the organisation receives from the PMO's own contribution. How long does an idea take to become a started project? Is the same governance applied to a small change and a major investment? Is reporting helping people make decisions? Establish baselines for measures like these, then test whether the PMO is making work easier and decisions better, not merely producing more reports.

Diagnose the causes before adding controls or software

Alexander begins with three possible barriers: skills, willingness and behaviours. A skills problem may need training. A lack of willingness may mean people do not understand the purpose or business benefit. Behaviour problems can arise when people have not been informed or involved in designing the processes they must follow. He uses stakeholder conversations and interviews to find the underlying causes before deciding what needs to change.

After diagnosis, Alexander applies POPIT, covering people, organisation, processes, information and technology, to design a solution across the connected dimensions. A new governance board needs a clear decision-making purpose, supporting processes, accountable people and usable information. Technology can then amplify those foundations rather than substitute for them.

Stijn uses maturity assessment to understand the organisation's starting point. He also describes training as a way to turn initial frustration with formal methods into a shared understanding of what better practice could look like locally. Both favour designing the PMO's services with the people who will use them. The aim is a PMO operating model that provides appropriate assurance and practical support, not more control for its own sake.

Decide what is worth funding, then what can be delivered

Alexander treats prioritisation as two successive filters. First, establish the strategic and financial case: what the organisation wants to achieve, how initiatives contribute to its objectives and KPIs, and what it can afford. Then test deliverability: are the necessary skills available in-house, how long would delivery take, and does the required technology exist to buy or need to be built? Each filter narrows the choices until the organisation has a priority list it can realistically deliver.

Stijn identifies three prerequisites for a credible assessment: a clear strategy, an understanding of available investment funding, and the organisation's risk appetite. An initiative can look attractive while carrying risks the organisation is not prepared to accept.

Alexander also uses run, grow and transform categories to distinguish essential operations from business growth and more fundamental change. Stuart identifies three common ways to divide a large portfolio: by these different purposes, by shared people and dependencies, or by initiative size. Stijn emphasises the shared-people test: portfolios drawing heavily on the same teams cannot make independent commitments. Stuart adds the leadership decision that follows: how much funding and scarce capacity should each portfolio receive? Ranking within separate groups does not answer that question. The choices must reflect shared capacity and sequencing constraints.

Turn the list into choices about what starts, waits or stops

Alexander describes working with an unnamed UK insurer that had a large initiative list but little clarity about its strategic purpose. He first sought to establish what the business was trying to achieve, then challenged the work he called zombie projects: initiatives still attracting people's time without a clear explanation of their value. He separated run, grow and transform work, clarified the distinction between projects and business-as-usual activity, and brought people together to calibrate priorities. That definitional step matters because, in his experience, the distinction is sometimes blurred through confusion and sometimes deliberately to hide projects from scrutiny.

Working with finance, Alexander then established an affordability line: which initiatives could receive support now, and which belonged below the line. The PMO's job was to keep sight of both the work being delivered and the deferred backlog, bringing initiatives forward when the time was right.

Stijn's 800-project example exposes what happens when prioritisation never changes commitments. He offers a hypothesis about how organisations reach that point: an initial top-ten or top-twelve list gradually accumulates exceptions, while management steps back from the growing list. Alexander recognises a related problem from his experience of committees: many people contribute opinions, but nobody feels confident enough to say no, so the list keeps growing.

For Stijn, the consequence is felt by delivery teams. If every project remains active, a ranking does little to reduce competing demands on the same people. Prioritisation helps only when leadership changes what proceeds, waits or stops.

Win executive support without losing delivery-team trust

Stijn advises showing leaders what overloaded commitments cost the organisation, then making the exchange tangible. If a sponsor gives up one project, one of their other worthwhile projects should be able to move faster because capacity has been released. Recognise the sponsor for contributing to the wider organisation, and avoid concentrating all the sacrifices on one person's portfolio. Dan adds that people are more willing to accept difficult choices when they believe the process is rational and fair.

Alexander approaches the problem through executive incentives. Where leaders are rewarded for achieving separate functional objectives, each has a reason to defend their own projects. He begins by exposing those conflicting objectives and agreeing shared business outcomes. In an extreme case, he describes aligning executive bonuses with shared objectives so that success depends on working together rather than protecting individual departments.

Both sides of the PMO's relationship matter. Executives need concise, decision-relevant insight rather than every detail in a status report. Delivery teams need timely decisions, proportionate governance and someone who will help remove obstacles. Stijn warns that when project managers see the PMO chiefly as police, they may withhold difficult information, leaving leadership with an unrealistically reassuring picture. A strategic PMO must be credible to the people supplying the facts as well as to those making the choices.

Research in context

Can tighter oversight make reporting less reliable? That is the risk behind Stijn's warning. A 2014 study of nine IT projects in one US state government, based on 118 interviews, found that in some projects teams saw auditors' scrutiny as unfair and responded with defensive reporting. Auditors interpreted that behaviour as deception or incompetence and increased their scrutiny, deepening the distrust.

So what for a PMO? If delivery teams become defensive, adding another reporting check may leave leadership less informed, not more. The study examined auditors rather than PMOs, but it helps explain why the PMO needs the trust of the people providing its information, not just the executives receiving it.

How this connects to TransparentChoice

What could actually run? That's the question Stijn's 800-project example leaves unanswered. Stuart adds the decision that often gets skipped: how funding and people should be divided between portfolios that draw on the same resources.

TransparentChoice helps leaders test those trade-offs rather than stopping at the priority list:

  • Work out what fits. Compare feasible combinations against leadership priorities, funding, team or skill capacity and dependencies, including how resources are divided between portfolios.
  • See what each choice displaces. Change priorities, constraints or allocations and compare which initiatives are included, excluded or displaced.

Leadership decides what to support, defer or stop.

See how the software works →

Learn more

How can a PMO earn executive support for a more strategic role?

Alexander David argues for starting with strategic portfolio management, then putting the right controls and tools behind it. Alongside David Dunning and Dan Dures, he explores how to build the case for change and secure broader leadership support. Watch: Is Your PMO a Cost Centre or Value Generator?

Why can executives approve a priority list without owning the trade-offs?

A priority list can hide leadership choices inside criteria, assumptions and protected commitments. This article shows how a PMO can bring those choices back to leadership. Read: When Executives Approve the Portfolio but Don't Own the Trade-Offs.

What happens when almost every project is treated as top priority?

Energinet classified 60 of 80 IT projects as top priority. Its customer case describes how shared strategic criteria and regular review helped identify obsolete work that could be stopped. Read: Energinet's project prioritisation case study.

Speakers in this recording

Alexander David, Founder and CEO at Value Matrix
Alexander David
Founder & CEO, Value Matrix

Alexander David is a strategic portfolio management and PMO leader with extensive experience in driving transformation, carve-outs, and change leadership. As CEO of Value Matrix, he helps organizations achieve operational excellence and sustainable growth through strategic planning, organizational transformation, and digital innovation.

Stijn Janssens, PMO Architect, Trainer and Consultant
Stijn Janssens
PMO Architect, Trainer & Consultant, Apropo Management Services

Stijn Janssens is a PMO architect, consultant, and trainer who helps organisations improve portfolio governance, align investments with strategy, and build PMOs that drive better business outcomes.

Dan Dures, VP of Customer Success at TransparentChoice
Dan Dures
VP of Customer Success, TransparentChoice

Dan Dures is VP of Customer Success at TransparentChoice. With senior leadership experience at Just Eat, dunnhumby, and Home Retail Group, he brings expertise in data, strategy, and customer insight. He helps PMO leaders focus on projects that deliver real strategic value.