PMO Improvement and Value Orientation
Value is decided by the customer, not the PMO
Improvement and value orientation connect PMO activity to organizational outcomes. Start from a value proposition: which problems does the PMO solve, for whom, and how is that measured? Build a small indicator set spanning delivery performance (predictability, cycle time, quality), governance quality (decision timeliness, gate compliance), capability growth, and customer perception. Pair efficiency measures with effectiveness and outcome measures so the PMO is not rewarded merely for being busy.
Improvement runs as a cycle: baseline, prioritize gaps by value and feasibility, pilot, measure, standardize, then review whether each service should be scaled, changed, or retired. Roadmaps are sequenced by dependency and capability, not by ambition.
Traps. Confusing maturity level with value delivered; counting projects, reports, or training hours as outcomes; declaring improvement with no baseline to compare against; chasing a model's top level when the organization only needs a stable, modest service; and never retiring anything, so the catalog grows while quality falls. Another trap is measuring only internally - sponsor and delivery-team perception is data too.
Worked example. A PMO claims value from a new template suite. Better: baseline schedule variance and change-request cycle time before launch, then show movement over two quarters and link it to a decision such as faster funding approval. If nothing moves, the templates are a cost, not a benefit.
Rule of thumb: every PMO service should have a named customer, a metric, and a decision or outcome it influences. Review the catalog at least annually and remove what no longer earns its keep.