OCM Maturity Model: Where Does Your Organization Actually Stand?

by Kevin Rillo, Vice President, OCM Center of Excellence, Judge Learning Solutions

September 8, 2026

Every leader I talk to believes their organization is “pretty good” at managing change. Then we start a transformation together, and within the first few weeks it becomes clear whether that belief was earned or just untested. The gap between how organizations rate their own change capability and how they actually perform under pressure is one of the most consistent patterns I’ve seen in 30 years of doing this work.

That gap is exactly what a maturity model is supposed to close. Not as an academic exercise, but as an honest, practical gut check: when the next transformation lands on your desk, is your organization actually ready for it, or has it just never been tested?

Why Maturity Matters More Than Methodology

I’ve written before about taking a methodology-agnostic approach to change management. Whether an organization runs on ADKAR, Kotter, Bridges, or a custom hybrid, the framework matters less than how consistently and how well it’s actually executed. Maturity is the missing piece in that equation. Two organizations can use the exact same methodology and get completely different results, because one has built real organizational muscle around it and the other is still improvising every time a new program starts.

Maturity isn’t about whether you have a change management framework on paper. It’s about whether change capability is built into how your organization operates, or whether it gets reinvented from scratch every time a new initiative comes along.

The Five Stages of OCM Maturity

Here’s a basic model I use with clients to have this conversation honestly. There are similar models which apply labels to each stage., e.g., Prosci. I try to avoid those so that the labels do not influence the assessment. I ask clients to read through each stage and be candid about which one actually describes their organization today, not the one they are aspiring to be.

Stage 1

Change management happens inconsistently, if at all. Each program team decides for itself whether to invest in stakeholder engagement, communications, and training, usually depending on whether someone on that particular team happens to care about it. There’s no shared language, no shared framework, and no institutional memory carried from one initiative to the next. Every transformation starts from zero.

What this looks like in practice: Communications get built the week before go-live. Training is an afterthought bolted onto the technical rollout plan. Nobody can tell you how the last major change initiative actually performed, because nobody measured it.

Stage 2

Pockets of good practice exist, usually wherever a strong individual practitioner or program sponsor happens to prioritize it. But there’s still no consistent, organization-wide approach. Success depends heavily on who happens to be running a given program, which means results are unpredictable from one initiative to the next.

What this looks like in practice: One business unit runs excellent change programs. Another, doing similar work, has never heard of a stakeholder map. Leadership can’t reliably predict how the next transformation will go.

Stage 3

The organization has adopted a consistent methodology and applies it across most major initiatives. There’s a shared vocabulary, a standard set of deliverables, and some degree of executive sponsorship for change as a discipline. This is the stage where most organizations plateau, and it’s a meaningfully better place to be than Stage 1 or 2.

What this looks like in practice: Every major program includes a change plan. Templates exist and get used. Change management is recognized as a workstream, not an afterthought.

Stage 4

Change capability is measured, not just practiced. The organization tracks adoption metrics, sentiment data, and support volume across initiatives, and uses that data to actively adjust programs in flight rather than waiting for a post-mortem. Change management has a real seat in program governance, not just a line in the project plan.

What this looks like in practice: Leadership gets regular adoption dashboards, not just status updates. Programs get real-time course corrections based on data, not gut feel, before problems compound.

Stage 5

Change management is embedded in how the organization operates, not treated as a separate function that gets activated per project. Managers at every level are trained and expected to reinforce change as part of their core leadership responsibility. Lessons from every initiative feed forward into the next one. The organization can run multiple concurrent transformations without change fatigue collapsing adoption across all of them.

What this looks like in practice: Change readiness is part of how new initiatives get scoped and budgeted from day one, not something considered after the technology decision has already been made. Change capability is treated as a competitive advantage, not overhead.

A Quick Self-Assessment

Before you place your organization on the model above, ask these questions honestly:

Consistency: Does every major transformation in your organization follow a defined change approach, or does it depend on who happens to be leading the program?

Measurement: Can you produce adoption and sentiment data from your last major initiative, or would you be estimating?

Governance: Does change management have a real seat at the program governance table, or is it a workstream that reports up after decisions are already made?

Manager engagement: Are your managers trained and held accountable for reinforcing change, or are they treated as a communications channel to broadcast through?

Institutional memory: Do lessons from your last transformation actually inform how the next one is planned, or does each new initiative start from a blank page?

If you answered “it depends on the program” to more than two of these, you’re likely sitting in Stage 2 or 3, regardless of how mature your organization believes itself to be.

Why This Matters for Your Next Transformation

Research and our own program data consistently show what happens when change management is under-invested: 30 to 40% productivity loss in the early go-live period, a 2 to 3x spike in support tickets, shadow processes that outlive the “official” new process, and adoption delays that push benefits realization out by months. None of that is a technology failure. It’s a maturity gap showing up at the worst possible moment, mid-transformation, with leadership confidence and budget both on the line.

Knowing your maturity stage before you start a major initiative changes how you plan for it. An organization at Stage 2 attempting an enterprise-wide ERP rollout needs a very different level of external support and internal preparation than one operating at Stage 4. Skipping that honest assessment is how organizations end up surprised by resistance they should have seen coming.

The Bottom Line

Maturity isn’t a badge you earn once. It’s a snapshot of how your organization actually behaves under the pressure of change, and it’s worth an honest look before your next transformation, not during it. The goal isn’t to reach Stage 5 for its own sake. It’s to know exactly where you stand today, so you can close the gap between your current capability and what your next initiative is going to demand of it.

Want a real assessment of where your organization stands, and what it would take to close the gap? Connect with our OCM Center of Excellence — we’ll walk through it with you.