Ray Moller
Technical Director – Portfolio and Program Management
No Content Set
Exception:
Website.Models.ViewModels.Components.General.Banners.BannerComponentVm
Traditional maturity assessments and P3M frameworks are useful. They give a checklist and a roadmap, but they miss the point if they don’t start with how decisions are made and escalated in your organisation. Organisations that control delivery effectively don’t always call it a PMO. They embed PMO principles into governance and operational routines: structured end-of-month (EOM) reporting, monthly WIP calculations, tolerance bands and appropriate decision escalation paths. That practical operating model is the foundation of a “directive” PMO in effect, even if it isn’t named that way.
Designing the right PMO is a practical exercise. Start by answering three governance questions:
Who holds the decision rights for scope, cost and schedule changes? If executive decision rights are centralised and routinely exercised, a directive PMO with delegated authority can work. If authority resides in functional leads across a matrix, a directive PMO will struggle.
What metrics do executives need, and when? Organisations that use traditional end-of-month metrics including WIP, debtors, OH, T&S, G&A and gross/net revenue as part of monthly controls require a PMO that enforces data discipline and a single trusted source.
How are escalations triggered and acted upon? Tolerance bands (costs, time, scope and risk) must map to an escalation path that people follow. Without that, visibility doesn’t translate into control.
The purpose of a PMO must follow organisational context:
Directive PMO: appropriate where executive decision rights are clear and can be delegated; the PMO enforces standards, approves change and drives delivery outcomes. This resembles the PMO behaviours often embedded in commercial organisations and contracted delivery partners.
Controlling PMO: enforces processes and reporting but relies on established escalation paths rather than direct approvals.
PMO: provides templates, coaching and tools where functions retain outcome authority; common in heavily matrixed engineering organisations where discipline leads impact program delivery streams.
A properly rightsized PMO balances people, process and technology against the governance model and scale of the portfolio. In practice:
Lean, digitally enabled PMOs can do more with fewer people when governance is clear and data sources follow established best practice and are integrated.
Large PMOs (more than 12 people) often expand into operational roles and risk losing focus on governance and control unless their mandate is well scoped. RPS’s approach starts with a governance and digital health check: centralise validated data sources, confirm decision rights and create the visualisations that make governance operational.
If you want to see a PMO produce tangible control, focus on routines that convert data into decisions:
A single monthly group of cost and value with standard definitions
An optimised executive dashboard with tolerance bands for cost, schedule and quality
A defined escalation protocol that shows who acts when a metric breaches tolerance
A single source of validated portfolio, program and project data (digital backbone) so everyone speaks to the same numbers
Matrixed organisations often get visibility but not control: engineering streams, commercial teams and product functions each hold delivery levers. You can shine a light on issues without being able to fix them. That’s why governance clarity, not more dashboards, is the highest value intervention. It allocates decision rights, clarifies accountabilities and allows the PMO to either command where appropriate or enable where necessary.
Score each item 0/1/2 (0 = no, 1 = partial, 2 = yes).
Executives receive a single group of numbers linked with P&L performance and tolerance in a dashboard each month
Decision rights for scope/time/cost changes are documented and followed
Escalation triggers are defined and used in practice
One validated digital source feeds your reporting
The PMO mandate is aligned to your operating model (directive/controlling/supportive)
RPS takes a staged approach:
Governance and digital health check: validate the data flows and decision points
Rightsizing and roadmap: align PMO mandate and staff footprint to the governance model and scale
Implementation: implement the single source of truth, EOM routines and escalation triggers, plus handover and change management
If your executive team struggles to turn visibility into controlled outcomes, governance is likely the missing piece. We’ve distilled a short one-page executive snapshot and a 30-minute governance diagnostic to map your decision rights to a recommended PMO construct. Get in touch to request the snapshot or book the diagnostic. We’ll come with a one-page tailored roadmap you can use in a board discussion.
Technical Director – Portfolio and Program Management