Managing Change in the Middle

After the Beginning and Before the End

Change often begins with energy. Leaders announce a new direction. The kickoff meeting is polished. The slide deck is clear. The case for change sounds persuasive. People nod. Questions are answered. A timeline appears. A training calendar is published. Early adopters show enthusiasm. The project team feels relief because the work has finally moved from planning to launch.

Then reality arrives.

The first week brings questions nobody anticipated. The second week reveals that the new process takes longer than expected. The third week exposes gaps in training. Managers interpret the change differently. Employees return to old habits when workload rises. Customers ask questions the implementation team did not prepare for. The data does not fit cleanly. The template is confusing. The system works in the demo but not under live pressure. People who seemed supportive become quiet. People who were quiet begin complaining. The project team starts hearing, “Are we still doing this?” or “This is not working.”

This is the messy middle of change.

The messy middle is the period after the launch but before the new way of working becomes normal. It is where enthusiasm fades, practical problems surface, and people discover the distance between the idea and the work. Many change efforts lose momentum here, not because the change was wrong, but because leaders underestimate what happens after the announcement.

A launch creates awareness. It does not create adoption. A kickoff explains the direction. It does not build fluency. Training introduces new behavior. It does not guarantee that people will use the behavior under pressure. The middle phase is where change either becomes embedded in daily work or quietly dissolves into another unfinished initiative.

Managing the messy middle requires patience, structure, and visible reinforcement. It also requires leaders to stop treating the launch as the finish line.

Why Momentum Drops After Launch

Momentum drops for several predictable reasons.

First, the emotional energy of the announcement wears off. A kickoff can create a temporary sense of possibility. People may feel hopeful, curious, or at least willing to listen. But once the event is over, employees return to full inboxes, customer demands, deadlines, staffing gaps, and daily routines. The new change now has to compete with the real work already in motion.

Second, the change becomes harder when people try to apply it. A process may look simple in a diagram and feel complicated in practice. A new system may make sense during training and feel clumsy during a live customer interaction. A new reporting format may seem logical until the writer has to decide what belongs in each section. The gap between concept and use creates frustration.

Third, old habits are stronger than new instructions. People do not abandon familiar routines simply because a new process exists. Under stress, people return to what they know. If the old spreadsheet, email path, approval shortcut, or informal workaround still functions, people may use it when the new method feels slow.

Fourth, managers may not be aligned. Employees listen to their direct managers more than they listen to launch messages. If managers reinforce the change, adoption improves. If managers are confused, skeptical, silent, or inconsistent, employees receive mixed signals.

Fifth, early problems can damage confidence. If the first few days bring system errors, unclear instructions, duplicate work, or unanswered questions, people may conclude that the change was poorly designed. That conclusion may be premature, but it spreads quickly.

Sixth, people may not see progress. If leaders do not share evidence that the change is working, employees may assume it is not. In the absence of visible results, inconvenience becomes the dominant story.

These factors do not mean the change is failing. They mean the change has entered the hard part.

The Launch Is Not the Change

One of the biggest mistakes organizations make is confusing communication with implementation. They announce the change, hold the meeting, send the email, publish the guide, and assume the change has happened.

It has not.

A launch tells people what is supposed to happen. Implementation is what happens when people try to do it. Adoption is what happens when the new behavior becomes the expected way work gets done.

Those are three different stages.

For example, announcing a new client-update process is a launch. Teaching employees how to write updates, giving them examples, creating a template, answering questions, and reviewing early drafts is implementation. Seeing client updates consistently written in the new format without constant reminders is adoption.

Announcing a new project-management system is a launch. Migrating tasks, training users, defining naming conventions, closing old trackers, and coaching managers to use the new tool is implementation. Employees using the system as the normal place for assignments, status, and deadlines is adoption.

Announcing a new feedback model is a launch. Practicing the language, helping managers prepare for real conversations, observing what happens, and coaching them after early attempts is implementation. Managers using the model naturally in everyday coaching is adoption.

The messy middle exists because organizations often invest heavily in launch and lightly in adoption.

People Need Repetition After the Announcement

Leaders often tire of repeating the message before employees have fully heard it. The project team may have lived with the change for months. By launch day, the rationale feels obvious to them. For employees hearing the details for the first or second time, the change is still new.

After launch, people need repetition. Not the same announcement copied and pasted. They need practical repetition that answers the questions emerging from use.

Early messages may need to restate:

• Why the change is happening.
• What behavior is expected.
• What should stop.
• What should continue.
• Where to find help.
• Which deadline applies.
• Who owns which decision.
• What has changed based on feedback.
• What is not changing.

For example, during the first week after a new intake process launches, people may need a reminder:

“Beginning today, all new requests should be entered through the intake form. Do not send new requests by email. Existing requests already in progress do not need to be reentered.”

A week later, the message may need to become more specific:

“We are seeing three common errors in the intake form: missing client name, unclear deadline, and no project owner. Please review those fields before submitting.”

That kind of repetition supports adoption because it responds to what people are experiencing.

The Middle Exposes Design Problems

The messy middle is where the design is tested. Leaders should expect problems to surface. That does not mean the planning was poor. It means live use reveals details that planning cannot fully predict.

The form may need another field. The approval path may need an exception process. The training may need a job aid. The timeline may need adjustment. The communication may need simpler language. The system may need a cleaner dashboard. The managers may need stronger talking points.

The worst response is defensiveness.

If leaders treat every problem as resistance, employees will stop sharing useful information. If leaders insist the design is perfect, people will develop workarounds. If leaders say, “Just follow the process,” when the process contains a flaw, the change loses credibility.

A better response is disciplined listening.

Ask:

• “What is confusing?”
• “Where is the process taking longer than expected?”
• “Which questions keep coming up?”
• “What step are people skipping?”
• “What are customers noticing?”
• “What are managers hearing?”
• “What needs clarification?”
• “What can we adjust without changing the purpose of the change?”

This does not mean reopening every decision. It means improving implementation based on real evidence.

A good message might sound like this:

“We are not changing the decision to use the new intake process. We are adjusting the form because the first week showed that the deadline field was not specific enough.”

That distinction is important. The direction remains steady, while the implementation improves.

Managers Carry the Messy Middle

Managers are the most important layer during the middle phase. They are where broad direction becomes daily behavior. They answer the repeated questions. They notice who is using the new process and who is avoiding it. They interpret leadership messages. They correct misunderstandings. They manage frustration. They explain priorities. They hear the private complaints.

If managers are not prepared, the middle becomes chaotic.

Managers need more than the announcement. They need practical support:

• Talking points.
• Expected questions and answers.
• Examples of the new behavior.
• A list of what employees should stop doing.
• Guidance for handling resistance.
• Clear escalation paths.
• Authority to adjust local workflow when appropriate.
• Data showing adoption.
• Time to discuss what they are seeing.

Managers also need to be aligned with one another. If one manager enforces the new process and another ignores it, employees will notice. If one department keeps using the old template and another has moved to the new one, the organization sends mixed signals. If senior leaders use the old process while expecting employees to use the new one, the change loses authority.

During the messy middle, leaders should meet regularly with managers and ask:

• “What are you hearing?”
• “What is unclear to your team?”
• “Where are people returning to old habits?”
• “What support do you need?”
• “What are you reinforcing this week?”
• “What should we escalate?”

Managers are not simply messengers. They are adoption leaders.

Old Workarounds Must Be Closed

Many changes fail because the old path remains easier than the new one. People may support the change in principle, but under pressure they will use the path that gets the work done fastest.

If employees are told to use a new project platform but old assignments still arrive by email, the platform becomes optional. If a new report template is introduced but managers accept the old format, the template becomes decorative. If a new customer communication process is announced but employees can still bypass it without consequence, the process becomes one more suggestion.

To move through the messy middle, leaders need to identify and close old workarounds.

Ask:

• What old forms should be removed?
• What old links should be disabled?
• What old templates should be archived?
• What old meeting should end?
• What old approval path should close?
• What old spreadsheet should stop being updated?
• What old language should no longer be used?
• What old exception has become routine?

This is often uncomfortable because the old way may still feel useful. However, keeping both old and new systems alive creates duplicate work and weak adoption. If the old process must remain temporarily, define the end date.

For example:

“The old tracker will remain available for reference through May 31. Beginning June 1, all new status updates must be entered in the project platform.”

That gives people transition support without leaving the organization in two systems forever.

Training Needs Reinforcement

Training is often treated as a one-time event. People attend the session, receive the slides, and are expected to perform. That may work for simple changes. It rarely works for behavioral, technical, or process changes that require judgment.

The messy middle reveals what people did not absorb during training. They may understand the concept but struggle with real examples. They may know where to click during the demo but forget under pressure. They may understand the policy but not know how to explain it to a customer. They may know the new feedback model but freeze in a difficult conversation.

Reinforcement should be built into the middle phase.

Useful reinforcement may include:

• Short refresher sessions.
• Office hours.
• Job aids.
• Examples and nonexamples.
• Manager coaching.
• Peer review.
• Practice scenarios.
• Frequently asked questions.
• Quick videos.
• Side-by-side comparison of old and new methods.

For example, if employees are learning a new report format, do not rely only on training. Provide a sample report, a checklist, and a review of early drafts. If customer service representatives are learning new language for policy exceptions, give them sample dialogues and practice time. If managers are learning to conduct stay interviews, let them practice questions before using them with employees.

People rarely master new behavior from explanation alone. They need practice, feedback, and repetition.

The Middle Needs Visible Wins

During the messy middle, people need evidence that the change is producing value. Otherwise, inconvenience becomes the story.

Visible wins do not need to be dramatic. They need to be credible.

Examples:

• “Since the new intake form launched, missing deadline information has dropped by 40 percent.”
• “The revised customer email reduced repeat questions about next steps.”
• “The new meeting format cut average meeting time from sixty minutes to thirty-five.”
• “The pilot team completed status updates two days earlier than last month.”
• “Managers report fewer clarification emails after using the new report template.”
• Share wins carefully. Do not exaggerate. Do not say, “Everyone loves the new system,” if people are still struggling. People will dismiss the message.

A better approach is balanced:

“The first two weeks have surfaced some issues, especially around duplicate entry. We are addressing that. At the same time, the new process has reduced missing client information in requests, which was one of the main goals.”

That kind of message builds trust because it acknowledges the mess while showing progress.

Watch for Quiet Nonadoption

Not all resistance is loud. Some of the most damaging resistance is quiet. People attend training, say little, and continue working the old way. They may not object openly. They simply do not adopt.

Quiet nonadoption may show up as:

• Old templates still being used.
• New fields left blank.
• Data entered late.
• Managers not asking for the new behavior.
• Employees saying they “did not realize” the change applied to them.
• Work moving through side channels.
• People asking questions that were already answered.
• Teams treating the change as optional.

Leaders should look for these signs early. Quiet nonadoption is easier to correct in the first few weeks than after the old behavior has reestablished itself.

Start with curiosity:

“I noticed the old template was used for the last two updates. What got in the way of using the new one?”

If the issue is confusion, clarify. If the issue is skill, support. If the issue is capacity, adjust. If the issue is refusal, address it directly.

After expectations have been communicated and support has been provided, leaders may need to say:

“The new template is now the required format. Beginning next week, reports submitted in the old format will be returned for revision.”

That is not harsh. It is how adoption becomes real.

Keep the Purpose Visible

In the messy middle, people often lose sight of why the change exists. The daily inconvenience becomes louder than the original reason. Leaders need to reconnect the work to the purpose.

For example:

• “We are using the new documentation standard so customers do not have to repeat their issue each time the case transfers.”
• “We are changing the approval process so decisions are visible and fewer requests stall without ownership.”
• “We are moving to the new reporting format so senior leaders can see risks and decisions faster.”
• “We are using the new scheduling process so field teams receive assignments earlier and with fewer last-minute changes.”

Purpose should be concrete. “Improve efficiency” is too vague. “Reduce duplicate data entry” is better. “Enhance communication” is vague. “Make action owners and deadlines visible in every project update” is better.

The purpose becomes especially important when people are tired. They may not enjoy the transition, but they are more likely to continue if they understand what the work is supposed to improve.

Do Not Add Unnecessary Change During the Middle

Once a major change is in the messy middle, leaders should be careful about adding more. Additional changes may be necessary, but they should be weighed against the adoption work already underway.

Too many overlapping changes weaken focus. People begin treating everything as temporary. Managers cannot reinforce all of it. Training calendars fill. Employees stop distinguishing between serious expectations and passing initiatives.

Before launching another change during the middle, ask:

• Does this need to happen now?
• Does it affect the same people?
• Will it compete with adoption?
• Can it wait until the current change stabilizes?
• Can it be combined with existing work?
• What should stop if this starts?

This is not a request for organizational paralysis. It is a request for sequencing. Adoption requires attention. Attention is limited.

Use Feedback Loops

Feedback loops are essential during the messy middle. Leaders need information from the people trying to use the change.

A useful feedback loop is short, regular, and practical. It does not require a long survey every time. It may be a weekly manager huddle, a shared question log, office hours, a short pulse survey, or a standing agenda item.

Ask:

• “What is working?”
• “What is confusing?”
• “What is taking too long?”
• “What errors are repeating?”
• “What should we clarify?”
• “What support is missing?”
• “What should we stop doing?”
• “What should we adjust?”

Then close the loop. Tell people what you heard and what will happen next.

For example:

“You told us the new form did not make it clear when a request was urgent. We added an urgency field and definitions for standard, priority, and emergency requests.”

Closing the loop builds trust. People are more willing to give feedback when they see it used.

Reinforce the Change Through Systems

A change becomes durable when systems reinforce it. If the organization relies only on reminders, adoption will fade.

Systems may include templates, dashboards, workflow tools, performance expectations, manager checklists, meeting agendas, job descriptions, onboarding materials, quality reviews, and customer communication standards.

For example, if the organization wants clearer project updates, the standard meeting agenda should include status, risk, decision needed, owner, and deadline. If the organization wants managers to coach more consistently, the performance-management process should include coaching documentation and manager check-ins. If the organization wants customer service representatives to document cases differently, the case-management system should prompt the required fields.

The messy middle is the time to ask:

“What system needs to change so the new behavior becomes easier than the old behavior?”

If nothing in the system changes, old habits will return.

Recognize the Emotional Dip

People may feel embarrassed, irritated, anxious, or tired when they are learning a new way of working. Experienced employees may dislike feeling clumsy. High performers may resent losing speed. Managers may feel pressure because their teams expect answers. Newer employees may wonder why the process changed just as they were learning the old one.

This emotional dip is normal.

Leaders should not overdramatize it, but they should acknowledge it.

A useful message:

“We expect the first few weeks to feel slower. That does not mean the change is failing. It means we are learning the new process. Please raise issues early so we can correct them.”

This kind of message helps people interpret discomfort correctly. Without that framing, they may assume frustration means the change is wrong.

The emotional dip also reminds leaders to look for support needs. People may need practice time, manager coaching, clearer job aids, or permission to slow down temporarily while learning.

Make the Next Step Smaller

In the messy middle, people can become overwhelmed by the full scope of change. Leaders can help by making the next step smaller.

Instead of saying:

“Everyone needs to fully adopt the new process.”

Say:

“This week, focus on entering all new requests through the form. We will address reporting next week.”

Instead of:

“Managers need to reinforce the new customer-experience standard.”

Say:

“In this week’s team huddle, managers should review the new opening language and listen to one call with each employee.”

Smaller next steps reduce anxiety and increase follow-through. They also allow leaders to measure progress.

A large change may need to be broken into phases:

• Awareness.
• Training.
• First use.
• Corrected use.
• Consistent use.
• Measured adoption.
• Reinforcement.

Each phase needs different communication and support.

Avoid Blaming People for the Mess

When the middle gets hard, leaders may blame employees for resisting, managers for failing to reinforce, trainers for not preparing people, or project teams for missing details. Some accountability may be appropriate, but blame alone does not improve adoption.

Instead, diagnose the system.

Ask:

• Was the purpose clear?
• Were managers prepared?
• Was training practical enough?
• Were old tools removed?
• Were expectations specific?
• Was capacity protected?
• Were employees given examples?
• Were questions answered quickly?
• Was feedback used?
• Were priorities clear?

These questions reveal where the implementation needs strengthening.

People are responsible for adopting reasonable changes after proper support. Leaders are responsible for creating the conditions that make adoption possible.

End Notes

The messy middle of change is where good intentions meet daily work. It is the space between announcement and habit, between training and consistent performance, between agreement and adoption. It is also where many change efforts lose momentum.

Momentum drops after launch because the emotional energy fades, practical problems surface, old habits return, managers vary in reinforcement, and early confusion can damage confidence. None of that means the change is doomed. It means the organization has reached the part where leadership discipline counts most.

Do not treat the launch as the finish line. Repeat the message in practical ways. Listen for design problems. Prepare managers. Close old workarounds. Reinforce training. Share credible wins. Watch for quiet nonadoption. Keep the purpose visible. Avoid piling on unrelated changes. Use feedback loops. Build the new behavior into systems. Acknowledge the emotional dip. Make the next step smaller. Diagnose before blaming.

The messy middle is not a sign that change is failing. It is the phase where change becomes real. Organizations that understand that phase are more likely to finish what they start.