Change management in operations is the discipline of planning, approving, rolling out and verifying changes to how work gets done, while helping the people who do that work adopt the change. It has two halves: controlling the technical change (procedures, equipment, systems) and guiding the people through it. Leaders who run only one half usually watch the change fade within a quarter. This guide covers both halves, the steps that matter, and how to tell whether a change has stuck.
TL;DR
- Operational change has a technical side (what changes in the process) and a people side (who has to work differently). Strong operations leaders manage both.
- A workable process runs: define the change, assess risk, assign an owner, communicate and train before go-live, verify, then update the standard.
- Most changes fail after go-live, when nobody measures adoption or owns the new standard.
- Measure in four tiers: engagement, learning, behavior and business results.
- Write every step so a floor manager can act on it Monday morning.
Table of Contents
- What change management in operations means
- Management of change versus the people side of change
- The change process, step by step
- Using Kotter's eight steps on the floor
- Ownership, communication and preparing your people
- A real example: Delta's seating decision
- Why operational changes fail
- How to measure adoption and sustain the change
- Our perspective
- Where to start if you are leading a change now
- FAQ
- Sources
What change management in operations means
In an operating company, change shows up as a new scheduling system, a revised pick-and-pack flow, a different quoting process, a reorganized shift pattern or a new service-level promise. Each one touches procedures, training, forms, systems and records. Operations change management is the structured way of requesting, reviewing, approving, implementing and verifying those changes so responsibility, risk and recovery stay visible. One practical workflow describes it as applying the right level of scrutiny before a change affects safety, quality, service, compliance, customers or continuity.
That is narrower than the broader field. The Project Management Institute defines change management as a cyclic, structured approach for moving individuals, groups and organizations from a current state to a future state with intended business benefits, and it stresses that the work must cover people, culture, processes, infrastructure and technology, not only the people side.
The practical takeaway: when you hear "change management" in a boardroom, ask which problem is on the table. Is it a technical change that needs control, or a people change that needs adoption? Usually it is both.
Management of change versus the people side of change
Industrial plants have long separated two ideas that share a name. According to a Plant Services article, management of change (MOC) reviews proposed changes to equipment, raw materials, processes and procedures before implementation to evaluate impact and risk. Change management (CM) deals with the people side, moving individuals and organizations from the current state to a desired future state. The same piece argues that the most successful organizations handle both.
A simple way to hold the distinction:
| Management of change (MOC) | People-side change management (CM) | |
|---|---|---|
| Core question | Is this change safe, approved and documented? | Will people actually work this way? |
| Typical artifacts | Change request, risk review, backout plan, updated SOP | Communication plan, training, coaching, feedback loops |
| Who drives it | Process owner, operations manager | Executive sponsor, front-line leaders |
| Failure looks like | Undocumented changes, surprises, rework | Workarounds, old habits, quiet resistance |
Companies at the $5M to $50M stage often have neither in writing. Changes happen because someone senior asked, and they survive only as long as that person keeps asking.
The change process, step by step
Frameworks differ in vocabulary but agree on the arc. APQC describes four steps: plan, design, implement and sustain. In the plan step, you identify the change and its end goals, assess the current state and detail the desired future state so it aligns with strategy. HBS Online frames it as three phases: preparation, implementation and follow-through.
For day-to-day operations, here is a sequence that translates those frameworks into something a team can run:
- Submit a structured change request. Describe what changes, why, who is affected and what the success measure is. Name a single change owner on the request.
- Assess risk and approve. Match the scrutiny to the stakes. A label change on a shelf needs less review than a new dispatch workflow that touches customer commitments.
- Plan the rollout and the backout path. Decide the go-live date, the sequence and exactly how you would reverse the change if it misfires.
- Communicate and train before go-live. Identify which teams and outside parties need notice or new instructions, and which documents, checklists and approval rules must be updated.
- Implement, with a support window. Define how questions, exceptions and feedback are handled while the change settles.
- Verify, close and update the standard. Confirm the change did what it was meant to do, then update procedures, training material, forms, systems and records.
The last step is the one most companies skip, and it is the reason SOPs drift away from reality. The sequence above follows the operational change workflow described by one operations practitioner publication.
If your process documentation is thin, start by mapping the work as it is actually done. Our guide to process mapping steps for operations leaders shows how to do it without a six-month project.
Using Kotter's eight steps on the floor
John Kotter's model is the most cited people-side framework. The U.S. Agency for Healthcare Research and Quality summarizes it in its change implementation guide: steps one to four unfreeze the status quo, steps five to seven introduce new practices, and step eight grounds the change in a new culture so it lasts.
Translated for an operations team:
- Create urgency. Tie the change to a number the team recognizes: late orders, rework, overtime, margin leakage.
- Build a guiding team. AHRQ's summary calls for leadership, credibility, communication skills, authority, analytical skills and urgency in that group. In practice, include at least one respected supervisor, not only managers.
- Communicate for understanding and buy-in. Say what is changing, what is not, and what it means for each role.
- Remove barriers. If the new process needs a form, a login or a schedule change, fix that before asking for compliance.
- Produce short-term wins. A visible improvement in two or three weeks buys patience for the rest.
- Don't let up. Keep the cadence of reviews going after the launch excitement ends.
- Anchor the change. Update the standard, the scorecard and the onboarding so new hires learn the new way as the only way.
You do not need to use all eight labels. You need the sequence: urgency, a team, clear communication, cleared obstacles, early proof and a durable standard.
Ownership, communication and preparing your people
Three decisions at the start of any change prevent most confusion.

One named owner. The change request should carry a single change owner and the training and communication details. Committees do not own changes; people do.
A communication map. Before go-live, list every group that needs to know: affected shifts, adjacent departments, customers, carriers, suppliers. For each, write what they need to hear and who tells them. When leaders skip this, employees fill the gaps with their own interpretation and the rumors become the plan.
Engagement tied to daily work. APQC notes that during implementation the change team should focus on tactics that build trust, set behaviors and link employees' day-to-day work to organizational goals and performance. A supervisor who can explain how the new pick sequence reduces tomorrow's overtime is worth more than a launch email.
The Plant Services piece makes a point worth repeating to executives: real change occurs from the inside out, because people change themselves rather than being changed by others. Your job is to make the new way easier, clearer and better supported than the old one.
For a longer treatment of the adoption side, see our 60-day change adoption plan, and if your team is already worn down by back-to-back initiatives, read about stopping change fatigue.
A real example: Delta's seating decision
A useful case comes from the early pandemic. A Purdue case study reports that Delta stopped selling middle seats, leaving it with 9% fewer seats to sell than competitors, yet its revenue ran 12% above the average of American, United and Southwest combined. The study credits quick, effective communication across operations: flight attendants, gate staff and corporate communicators were given tools to explain the safety plan and carry out the new rules.
The lesson for a mid-market operator is not about airlines. A policy change is only as good as the front-line tools that let people apply it consistently. The people at the gate needed words to use and rules to follow, and they got them at the same time as the policy.
Why operational changes fail
Three patterns come up repeatedly in the research and in our own work.
No data after go-live. SHRM's primer on leading change warns that a common barrier to sustaining change is the lack of data collection to assess momentum. Without it, leaders learn that a change failed only when a customer complains.
The change team disbands too early. The same SHRM document notes that sustaining change gets more complex over time: conditions inside and outside the company shift, the initiative may need adapting as it expands, and the change team may be disbanded while systems still need to stay aligned with the original aims.
Resistance is treated as a character flaw. Harvard Business Review's guidance on choosing a change strategy, as summarized in the research behind this article, lists common sources of resistance: fear of losing value, misunderstanding, a belief that the change makes no sense and low tolerance for change. Communication, education and participation address most of those. Orders from the top address few.
BCG makes a related argument: transformations often fail when they rely on short-term, top-down pressure to change behavior rather than building capability and sustainable motivation.
The common thread is that the failure is rarely in the plan. It is in the weeks after, when attention moves to the next fire. If that sounds familiar, our piece on operational alignment explains how to keep strategy connected to daily execution.

How to measure adoption and sustain the change
The Association for Talent Development describes a laddered approach to measuring change with four tiers tracked over time: engagement, learning, behavior (adoption) and business outcomes. Behavior signals tell you whether people are executing; business outcomes tie results to the change itself.
Applied to a new dispatch process, the ladder might look like this:
| Tier | What you check | Example signal |
|---|---|---|
| Engagement | Did people show up and take part? | Training attendance, questions raised in huddles |
| Learning | Do they know the new steps? | Quick floor check on the new checklist |
| Behavior | Are they doing it? | Percent of jobs dispatched using the new form |
| Business outcome | Did results move? | On-time delivery, rework rate, overtime hours |
Set checkpoints at fixed intervals, such as two weeks, 30 days and 60 days after go-live, and put them on the calendar before launch. Blend operational KPI data with qualitative feedback from supervisors, and look at adoption by team, location and role. That mix, according to a change management article on post-go-live measurement, makes success claims credible and shows where persistent gaps need a fix.
To make it last, build the change into the management system itself: scorecards, weekly meeting cadences, coaching routines. Our guide to the management operating system covers how those pieces fit together.
Our perspective
We built TKD Consulting around one observation: most companies do not lack a strategy, they lack a way to get it done on the floor. Change management in operations is where that gap shows up first.
Having run warehouse operations, home services, solar and consumer products organizations, I have seen both halves fail. I have seen beautiful change plans that no supervisor could explain, and I have seen well-run floors where a new process died because nobody updated the standard or checked adoption.
That is why our engagements do not end with a slide deck. We map the people, processes and performance systems against your stated goals, then write a prioritized action plan the team can execute. The scorecards, meeting cadences, coaching frameworks and accountability mechanisms are part of the work, because those are what keep a change from evaporating once we leave.
Our approach is built to transfer systems and capability to your team, so results hold without us. Every recommendation is written so a floor manager can pick it up on Monday morning.
David
Where to start if you are leading a change now
If you are an owner, COO or VP of Operations with a change already in motion, or one you keep postponing, we suggest a short diagnostic before more activity. Our 90-Day Operations Audit is a fixed-price, structured assessment of your people, processes and performance systems, priced at $3,500. It is designed to give your team a prioritized action plan with the implementation runway attached, so the changes you choose have owners, cadences and measures from day one.

If you want to talk through the problem first, a paid discovery call is $500, and our Fractional COO Partnership starts at $7,500 per month for companies that need senior operational judgment without a full-time hire. You can see the full list of engagements on the TKD Consulting site. For a wider view of how we handle execution, read our guide on getting execution in 60 days.
FAQ
What is a good example of change management in operations?
Delta's decision to stop selling middle seats during the pandemic is a well-documented one. The change worked because flight attendants, gate staff and communications teams were given tools to explain and enforce the new rules quickly. A smaller version is a warehouse introducing a new receiving checklist with a named owner, pre-go-live training and a 30-day adoption check.
What does MOC mean in change management?
MOC stands for management of change. It is a structured process for reviewing proposed changes to equipment, raw materials, processes and procedures before they are implemented, so impact and risk are evaluated first. It covers the technical side of change, while change management covers the people side.
What are the main steps of the change management process?
APQC lists four: plan, design, implement and sustain. HBS Online groups the work into preparation, implementation and follow-through. In daily operations, that translates into a change request, risk review, rollout and backout plan, communication and training, go-live, and verification with an updated standard.
How do you measure whether an operational change worked?
Track four tiers over time: engagement, learning, behavior and business outcomes. Behavior shows whether people follow the new process, and business outcomes show whether results moved. Schedule checkpoints before launch and combine KPI data with supervisor feedback.
Sources
- Operations change management workflow
- Managing change in organizations, Project Management Institute
- Management of change vs. change management, Plant Services
- What is the change management process? APQC
- What is organizational change management? HBS Online
- Implementation change management, AHRQ
- Managing change in uncertain times: a case study, Purdue
- Leading effective change: a primer for the HR professional, SHRM
- A laddered approach to measuring change, TD magazine
- After go-live: why change programs lose momentum
