Skip to main content

A PMO that measures decisions, not status.

Portfolio data is a decision instrument. What to measure, what the workbook already knows, and why cycle time beats percent complete.

Updated 7 min readMarkdown
A PMO that measures decisions, not status.

One question ends most portfolio reviews quickly: which decision is late, who owns it, and how long has it waited? The answer is usually a status colour. The decision in front of a PMO this quarter is whether to keep measuring activity or start measuring decisions. The test: if your pack cannot name the oldest open decision and its owner, what is the weekly meeting for?

What the evidence says

  • The portfolio is a list, not an instrument. The index carries 58 line items, each with a category, a system, a code, a mapping code, a budget owner and a project type. A line without a mapping code is invisible to whoever holds the money.
  • The allocation logic is documented and checked against itself. The workbook reports 129 of 152 allocation lines (85%) reproduced by rule, with 23 exceptions. Recurring and one-off investment differ: a 15-year allocation produces an annual figure, a five-year contract divides by five, and the first year counts only its remaining months.
  • Responsibility is already mapped. The task catalogue, version 16, dated 14 September 2026, lists 16 tasks across 8 people, with an R, S and K matrix, monthly time shares, a backup per person, renewal alerts at 90, 60 and 30 days, and minutes within 24 hours.
  • The operating model assumes single owners. The squad playbook dated 17 October 2026 assigns product scope to the product owner, technical design to the tech lead, architecture principles to the enterprise architect, risk acceptance to the risk director and budget to the product council.
  • The old model's timing is the problem being solved. Five to seven departments in sequence, 9 to 18 months to market, against a target of 30–50% faster — a target, not a measurement.
  • Governance has moved from gates to guardrails. The playbook replaces stage-gate approval with architectural and risk guardrails, and asks for three metric layers: business outcome, delivery health including DORA measures, and risk.

The decision framework

Pick measures that change behaviour. Weights assume a bank where a slow decision is paid for next quarter.

# Criterion Weight What "high" looks like
1 Decision latency 20% Median days from "needed" to "decided"; the oldest open decision named, owned and dated weekly
2 Cycle time 20% Lead time from funded idea to production, not phase-by-phase percent complete
3 Dependency age 15% Every cross-team dependency has an owner, a promised date and an age; the oldest ten published
4 Variance to plan 15% Variance explained by driver, re-forecast monthly, not at quarter end
5 Change and rework rate 10% Incoming changes priced at intake; equal-size swaps cost nothing; larger ones go to committee
6 Outcome per decision 10% Each funded item names the outcome it buys and the date that outcome is checked
7 Traceability 10% Every number traces to a source line, with one named owner per number

Two things make this work: a decision log with four fields only — what, who, due, made — and a chair with authority to close items. The playbook's test is whether a product owner can say no without penalty.

The benchmark is mundane. An initial credit rating runs to 11 steps, with a majority vote, a 48-hour appeal and publication within 24 hours. If a rating process can publish its clock, a PMO can publish one for a change request.

Options and trade-offs

Option Strength Risk Three-year cost shape
Status pack (today) No new tooling; familiar to sponsors Measures activity; decisions stay invisible; drift is found late Low cash cost, high management time, rising cost of late decisions
Decision log plus latency metrics Live within a quarter on existing tools; changes behaviour first Decays if the chair cannot close items, or if the numbers are gamed Mostly effort and discipline; the cheapest credible option
Portfolio data platform One traceable number from index to allocation; the pack builds itself Two to three quarters of build; automates politics if rights stay vague Highest build, lowest manual reporting

Run the second; start the third only where the same number is reconciled by hand monthly.

The numbers

  • Portfolio scale: 58 line items, 152 allocation lines, 129 reproduced by rule (85%), 23 exceptions. Counts from the workbook, not estimates.
  • Catalogue scale: 16 tasks, 8 people, one matrix, one backup per person, three renewal alerts per contract.
  • Team shape: squads of 5–9 people lasting 18–36 months; 4–6 squads for a mid-size bank, 8–15 for a large one; 10–20% of budget reallocated each quarter.
  • Targets, not measurements: 30–50% faster time to market against a 9–18 month baseline. Hypotheses until a baseline exists.
  • Effort: the sources carry no person-day estimate for a PMO rebuild. The first quarter is instrumentation on data already held: analyst work, not platform work.

What I would do in 30 / 60 / 90 days

Next 30 days — measure what you already have

  • Publish four numbers on existing data: decision latency, oldest dependency age, cycle time per value stream, variance with drivers. One page.
  • Open a decision log with four fields, backfilled one quarter so the first median is real.
  • Name the chair and quorum for each decision type in the playbook's list.

Days 30 to 60 — stop reporting activity

  • Retire percent complete. Replace it with dates: committed, forecast, and when the forecast last moved.
  • Put an owner and a promised date on every open dependency; publish the ten oldest.
  • Reconcile the task catalogue against squads of 5–9 people, so matrix and organisation agree.

Days 60 to 90 — move money on evidence

  • Move to a quarterly product review with 10–20% reallocation, showing what each decision bought.
  • Publish the decision log to the steering committee instead of the status narrative.
  • Keep the 23 exceptions visible. A rule that explains 85% of the lines is useful; one that is quietly overridden is not.

What I would not do

  • Not measure percent complete. It moves when people talk, not when work finishes.
  • Not count decisions as throughput. A busy log of trivial items is how expensive decisions get deferred.
  • Not build the dashboard before the decision rights are written. You will automate an argument you have not settled.
  • Not let a five-year total stand in for a plan. The allocation model is a reconciliation tool, not a commitment.

For the non-technical sponsor

The PMO's job is not to tell you a project is amber. It is to tell you which decision is late, who owns it, and what it delays. Ask three numbers: how long decisions wait, how old the oldest dependency is, how far the forecast has moved. If the pack cannot produce them, it is activity reporting with better typography.

Sources

Personal views. Client and employer details are anonymised. Figures are third-party estimates, not vendor quotes, and are dated November 2026.

No comments yet. Be the first to comment.