FIELD NOTE 01
PMO design
The light PMO: minimum viable governance for complex delivery
Enough structure to create control, without turning project managers into administrators.
A light PMO is not a smaller version of a traditional PMO. It is an operating system designed around the few decisions, signals, and routines that materially improve delivery.
Start with the decisions, not the templates
PMOs often begin by standardizing documents. That can create consistency, but consistency is not the same as control. The better starting point is to identify the decisions leaders and project teams must make repeatedly: which risk needs escalation, which milestone is threatened, which change is commercially exposed, and where a constrained resource should move next.
Once those decisions are clear, the minimum useful data becomes obvious. The template is then a consequence of the operating model, not the operating model itself.
Five registers are usually enough to begin
For a growing technical portfolio, a practical first version can be built around five connected views. Each one must have an owner, a review cadence, and a clear purpose.
- Portfolio master: the authoritative view of project health, phase, forecast, and accountable leadership.
- Action log: commitments with one owner and one due date, not a transcript of the meeting.
- Risk register: uncertainty translated into exposure, response, trigger, and escalation path.
- Change register: scope, schedule, and commercial impact kept together from identification through disposition.
- Lessons learned: reusable decisions and patterns, captured while the context is still fresh.
Cadence creates the management system
A register without a cadence becomes a digital filing cabinet. Weekly project reviews should focus on exceptions and commitments. Monthly portfolio reviews should compare projects, expose systemic constraints, and decide where leadership attention is required. The PMO adds value by making those conversations faster and more fact-based.
The test is simple: if a field does not support a recurring decision, an obligation, or a useful trend, remove it. Every unnecessary field taxes adoption and weakens data quality.
Measure adoption through behavior
A light PMO is working when risks surface earlier, owners close actions with less chasing, forecasts become more stable, and teams can explain variance without assembling a new presentation. Those behaviors matter more than the number of completed templates.
Governance should feel like better visibility and faster support. When the system consistently helps teams make decisions, standardization follows naturally.