Meridian Infrastructure Group — Infrastructure services, mixed portfolio of 18 active projects

PMO Diagnostic Report

Prepared by Meridian Infrastructure Group using Delivery Signal

Verdict

The PMO is helping the organisation see the portfolio, but it is not yet consistently helping teams move work through the portfolio.

Executive summary

Meridian Infrastructure Group's PMO is providing clear enterprise value, particularly through portfolio visibility, risk escalation, executive reporting and improved consistency across the active project portfolio. Sponsors and enterprise support functions report that the PMO gives leadership a clearer view of delivery health, emerging risk and cross-project dependencies than existed before the PMO was established.

The main finding is not that the PMO lacks value. It is that the value is being delivered through a model that has become too heavy for many delivery teams and project managers. Reporting effort, duplicated data entry, unclear governance pathways and inconsistent prioritisation processes are creating friction at the point where the PMO should be making delivery easier.

The PMO is strongest when it aggregates delivery information for enterprise decision-making. It is weakest where project teams experience PMO requirements as compliance activity rather than practical delivery support. This creates a mixed but important result: the PMO is helping the organisation see the portfolio, but it is not yet consistently helping teams move work through the portfolio.

PMO Value vs Burden

The PMO sits in the High Value / High Burden quadrant. This means the organisation is receiving meaningful benefit from the PMO, but the effort required to interact with it is materially higher than it should be.

The value score is supported by strong portfolio visibility, risk and dependency management, benefits focus and delivery improvement capability. These results show that the PMO has created useful enterprise structure and has improved leadership's ability to understand the delivery portfolio.

The burden score is driven by critical feedback on systems, data and reporting effort, supported by weaker scores for project team value and governance flow. This indicates that the PMO is adding value at the top of the organisation, but some of that value is being funded by extra effort from delivery teams. The next maturity step is to preserve enterprise visibility while materially reducing the delivery friction required to produce it.

Value = average of Project Team Value, Governance and Decision Flow, Portfolio Visibility, Risk/Issue and Dependency Management, Benefits and Outcomes Focus, and Delivery Capability and Continuous Improvement. Burden = 100 minus the average of Systems/Data and Reporting Burden, Project Team Value, and Governance and Decision Flow.

Recommended management focus

1. Reduce duplicated reporting effort across the portfolio. Consolidate status reporting, risk updates, dependency tracking and financial reporting into a smaller number of required inputs. Prioritise removing repeated manual updates across slide packs, spreadsheets and system fields.
2. Clarify the decision rights for portfolio and project governance. Define which decisions sit with sponsors, steering committees, the PMO, project managers and executive leadership. Make escalation routes explicit so projects do not lose time waiting for unclear approvals.
3. Reset prioritisation and demand management around capacity, not just urgency. Introduce a visible portfolio intake and prioritisation rhythm that considers business value, resource availability, delivery risk and competing operational demand before work is approved.
4. Reposition the PMO as a delivery enablement function, not only a reporting function. Shift PMO effort toward removing blockers, improving planning quality, supporting sponsors and helping teams navigate governance. Treat reporting as one output of delivery support, not the centre of the PMO’s role.
5. Use role-group feedback to redesign PMO touchpoints. Run focused follow-up sessions with project managers, delivery teams and business sponsors to identify which PMO artefacts, forums and controls are useful, duplicated or unclear.

Suggested diagnostic rerun: 10 to 12 weeks after reporting simplification and governance changes have been implemented.

PMO Risk Signals

The PMO's main risk pattern is concentrated around delivery friction. Meridian's PMO is not seen as irrelevant or low-value. The stronger scores for visibility, risk management and benefits focus show that respondents recognise a real contribution. The risk is that the PMO's operating model has become too administratively expensive for the teams it is meant to support.

Systems, data and reporting burden is the clearest concern. Respondents described repeated updates across multiple tools, inconsistent templates, manual consolidation and status reporting that is often prepared for governance forums rather than used to improve day-to-day delivery. This is creating a credibility issue with project managers and delivery teams, who appear less confident than executives that the current reporting load is proportionate.

The second risk is prioritisation. The portfolio appears visible, but not always actively managed against capacity and strategic trade-offs. This creates a pattern where new work can be approved before the organisation has fully resolved what should be stopped, delayed or resourced differently.

Governance and decision flow is also a watch area. Governance forums exist, but respondents indicate that decision pathways are not always clear or fast enough. This is important because slow decisions compound the burden problem. When teams are asked to report extensively but do not see timely decisions in return, PMO activity can be interpreted as oversight without corresponding support.

This is the most significant risk in the result. Respondents indicate that reporting has become too manual, too duplicated and too disconnected from practical delivery decisions. The issue is not simply the existence of reporting. It is the amount of effort required to produce reporting that many delivery respondents do not see as directly helping them manage work.

This creates a structural problem for the PMO. Enterprise reporting is one of its most valued contributions, but the current process appears to rely on inefficient collection and consolidation practices. If left unresolved, this may reduce project manager engagement, weaken data quality and encourage teams to treat reporting as a compliance exercise.

The PMO should urgently simplify reporting inputs, remove duplicate templates and define a single source of truth for core delivery data.

Meridian has reasonable visibility of the portfolio, but the check indicates that visibility is not yet translating into disciplined prioritisation. Respondents suggest that projects are often assessed individually rather than as competing claims on shared capacity, sponsor attention, technology resources and operational change bandwidth.

This creates risk across the full portfolio. Projects may be approved with insufficient regard for delivery constraints, or remain active even when their value, timing or feasibility has changed. Delivery teams and support functions are likely to experience this as overload, shifting priorities and unclear trade-offs.

The PMO should strengthen the portfolio intake process and introduce clearer criteria for starting, pausing, sequencing or stopping work. Prioritisation should be treated as an active management process, not a periodic reporting activity.

Governance structures are in place, but respondents do not consistently experience them as fast, clear or enabling. This suggests a distinction between governance presence and governance effectiveness. The PMO has established forums and escalation mechanisms, but decision rights and approval pathways may not be sufficiently clear to the people trying to move work forward.

This matters because governance friction can undermine PMO value even when the PMO's intent is sound. If project teams are asked to provide more information without receiving faster decisions, governance can feel like a checkpoint rather than an enabler.

The PMO should map common project decisions, clarify who can make each decision and define expected timeframes for escalation and resolution. Governance should be judged partly by whether it helps teams make timely decisions.

Other At-Risk Dimensions

No additional At Risk or Critical dimensions outside the three priority areas. Project Team Value remains a Watch area and should be monitored closely because it is closely linked to the burden result.

PMO Strengths

Meridian's PMO has created strong portfolio visibility and a materially improved enterprise roll-up. Respondents indicate that leadership has a clearer view of project health, risks, dependencies and overall delivery status than would likely exist without the PMO. This is a meaningful strength and should be protected during any simplification effort.

Risk, issue and dependency management is also strong. The PMO appears to provide a useful escalation structure and a consistent way to identify delivery risks across projects. This is particularly valuable in a portfolio of 18 concurrent initiatives where dependencies and competing resource demands can otherwise remain hidden until they create delays.

Benefits and outcomes focus is sound. This suggests that the PMO is doing more than tracking activity, although there is still room to strengthen the link between approved work, expected benefits and realised outcomes.

Delivery capability and continuous improvement is also sound. The PMO has a credible platform to improve delivery practice. The opportunity is to focus that improvement effort on simplifying the delivery experience for project teams, not only improving executive visibility.

Dimension Scores

Role Group Comparison

The role-group comparison shows a clear split between those who consume PMO outputs and those who produce the information required to create them. Executive leadership, portfolio sponsors and enterprise support functions are the most positive groups. They see the PMO as improving visibility, risk management and confidence in the delivery portfolio.

The PMO team also scores the function strongly, particularly on visibility, risk management and delivery improvement. This suggests the PMO has a clear view of its intended value and believes its operating model is contributing to better delivery control.

Project and program managers, delivery teams and workstream leads are materially less positive. Their lowest scores are concentrated in reporting burden, prioritisation and governance flow. This indicates that the PMO's value is not being experienced evenly across the organisation. The further respondents are from executive reporting and the closer they are to delivery execution, the more likely they are to experience the PMO as administratively heavy.

Business sponsors sit between these groups. They appear to value improved visibility and risk escalation, but are less confident that prioritisation and governance are helping them make timely trade-offs.

This pattern supports the overall quadrant result. Meridian's PMO is valuable, but the operating model needs to be redesigned so that enterprise visibility is created with less friction for the people delivering the work.

Role group comparisons only appear where groups meet the minimum anonymity threshold.

Respondents

Start your own check

Find out where your PMO is adding value — and where it is adding weight.

The PMO Diagnostic surfaces the gap between how the PMO's value is experienced at leadership level and how it is experienced by the teams delivering the work.

Run a fast, anonymous PMO Diagnostic. Invite executives, sponsors, the PMO team, project managers, delivery teams and support functions. Get a scored diagnostic report that shows where the PMO stands and what to do next.