The core problem
A PMO is not a reporting function. It is an operating system.
Most PMOs were built to report on work, not enable it. They track milestones, produce status reports, and enforce templates. And executives still wonder why, with all this governance, results aren't improving.
The problem isn't the absence of process. It's that the PMO is measuring the wrong things and enabling the wrong conversations. The PMO that earns its place gives executives decision confidence, not dashboard confidence.
"If your PMO disappeared tomorrow, would executives miss the reporting, or the decision confidence? That question defines everything."
What the guide covers
What a PMO actually is, and why most organizations get it wrong from the start
Why PMOs get shut down, and what the ones that survive do differently
Portfolio governance that produces real decisions, not compliance theater
Sponsor accountability, how to make it visible and how to enforce it
How a PMO earns influence without direct authority
The Minimum Viable PMO and the 90-day build model
Where PMO and OCM genuinely connect, and what falls through when they don't
What the PMO looks like in five years
From the guide
Three things executives actually care about.
Are we delivering what we committed to? Are we deploying capital against the right priorities? And are there any surprises coming that we should know about now?
The metrics that answer those questions are portfolio predictability, decision velocity, capacity utilization, and benefits realization. Not governance meeting attendance. Not template compliance rates.
From the field
At the Pentagon, I stood up the Army CIO's EPMO from scratch, building governance infrastructure for 16 strategic programs totaling $1.6B under congressional oversight. The discipline that worked wasn't the most sophisticated available. It was the most consistently enforced.
The PMO Field Guide
37 questions · 9 parts · Full practitioner reference
Questions? ccognasso@gmail.com · 360.951.7433