The pattern
Thirty-five years. Same story.
A few years ago I walked into Seattle Public Schools with a mandate to move a 15-person HR team from a paper-based world into a modern system. Every aspect of how they worked was going to change. The project had a plan. Communications were drafted. Training was scheduled. By every project metric, things were on track.
Nobody was moving.
The team wasn't rebellious. They were waiting. Waiting to see whether the people at the top actually believed in what they were asking everyone else to do. Getting the Seattle School Board off the sidelines wasn't a governance conversation. It was a values conversation. Once they understood and trusted that this was the right thing for the kids and the district, the organization moved. Not because the communication plan got better. Because leadership got real.
"In thirty-five years, I have never seen a transformation fail because the technology was wrong. I have seen hundreds struggle because the people responsible for leading the change were endorsing it instead."
Why it keeps happening
Three breakdowns. Every time.
PMO and OCM are almost universally stood up as separate functions. The PMO owns delivery. OCM owns adoption. Nobody owns the seam between them.
The portfolio overloads the organization silently
The PMO sees how many initiatives are in flight. OCM sees how much change the target population can absorb. When those two views never meet, executives make launch decisions with half the information.
Adoption risk never makes it onto the risk register
PMOs track budget, schedule, and technical risk. Behavioral risk lives in the OCM status report executives rarely read. By the time adoption failure is visible, recovery costs three times what early intervention would have.
Sponsor accountability falls through the gap
OCM designs the engagement model. The PMO runs the governance meetings. Neither function owns the follow-through when the sponsor goes quiet. And sponsors go quiet.
The model
PMO governs the system. OCM makes the strategy live inside it.
Instead of asking "is the project on track?" and "are communications out?", ask one question: is the organization actually moving, and is the delivery keeping pace with it?
That question requires both functions in the same room, looking at the same data, producing one recommendation. Seven disciplines. One operating system. Change enablement is the sixth, where strategy becomes adoption. Without it, the other six produce accurate reporting on a transformation that isn't happening.
What this looks like
The first thing I do is find the sponsor.
Not to evaluate them. To understand them. Are they leading or endorsing? Have they been told the truth about where adoption stands, or have they been protected from it? The sponsor question almost always answers itself quickly. And the answer tells me where everything else is.
The Sponsor
Leading or endorsing? Do they understand what active sponsorship actually requires?
The Seam
Where does delivery accountability end and adoption accountability begin? What is falling through?
The Portfolio Load
What else is hitting this population right now? Is the change volume honest or optimistic?
The Readiness Signals
What does the behavioral evidence actually say? Not the status report. The actual data.
From the field
The goal is never dependency. It is capability. An organization that understands its own integration failure is already most of the way to fixing it.
The PMO + OCM Integration Brief
Full document · Six sections · Field-tested proof points
If something here named a problem you are living with, that is the place to start. ccognasso@gmail.com · 360.951.7433