Running an Adoption Review When Use Is Low

Low use numbers put a customer success manager in an uncomfortable spot. The dashboard says one team adopted a new workflow and the rest did not, and the easy move is to treat that gap as a discipline problem. It rarely is. An adoption review works when you treat the numbers as a starting question, not a verdict, and connect them to the actual shift routines that shape whether an agent picks up a new step or skips it under pressure.

Why This Conversation Goes Wrong

Most adoption reviews fail before anyone opens their mouth, because the person running the review walks in with a number and a conclusion already attached to it. Usage is low, so the team must be resistant, untrained, or careless. That framing puts the contact center leader on the defensive immediately. They start protecting their team instead of helping you find the real cause.

The other common failure is treating the dashboard as complete. A usage report tells you what happened. It does not tell you why an agent chose the old path over the new one during a busy call, or whether the new disposition step even appears where an agent can see it under time pressure. When you present a chart as the whole story, you invite a defensive answer instead of a useful one. The contact center leader will either agree politely and change nothing, or push back and the meeting turns into an argument about whose fault the number is.

A third problem is scope. Some reviews try to explain every team's adoption gap in one sitting. That produces a long list of maybes and no clear next step. A review works better when it picks one team, one pattern, and follows it far enough to find something concrete.

How To Prepare Before The Review

Before you sit down with the contact center leader, pull the usage record broken out by team, shift, and contact type. A single overall percentage hides the pattern you need. A workflow can look abandoned overall while it is actually working fine on the day shift and dead on the night shift, or working for billing calls and ignored for technical ones. Find the specific slice where use is lowest, and note anything unusual about that slice. Did the team lose a supervisor. Did the training happen before a system change. Did the workflow launch during a hiring surge when half the team was new.

Check training records and knowledge access next. Confirm who actually attended training, not just who was invited. Confirm the reference material an agent needs mid call is easy to find, not buried three clicks into a knowledge base. A workflow that only lives in a slide deck from a training session two months ago will fade fast.

Also think through what you will not do in this meeting. Do not bring individual agent names or agent level data into an executive review. That data belongs in a coaching conversation between a supervisor and an agent, not in a room where a leader might use it to single someone out. Aggregate the pattern to the team or shift level and keep it there.

Finally, decide what a good outcome looks like before you walk in. You are not trying to force full adoption in one meeting. You are trying to identify one team, one barrier, and one owner who will check back in after trying a specific fix. If you keep that outcome in mind, you will resist the urge to solve everything on the spot.

What To Say In The Room

Start with the number, but do not stop there. Jordan, a customer success manager, opens with, "Only one team is consistently using the new disposition path. I want to understand what's different about the teams that aren't."

Priya, the contact center leader, says, "Honestly I assumed everyone just needed more time."

Jordan asks, "What does the usage record show when we break it out by team, shift, and contact type." Priya checks and says the night shift received training back when the workflow launched, but their supervisor moved to a different role a few weeks later and the replacement never went through the same session.

Jordan responds, "That gives us something specific to look at. Could we talk to the current night shift supervisor and two agents from that shift about where the path adds work or where the instructions run out." Priya asks, "Can you just make it mandatory and have everyone use it." Jordan says, "Making it mandatory without fixing what's missing usually gets you the same result with worse morale. Adoption needs a supervisor who can answer questions and a process that actually works on a busy call. Let's find the specific blocker on that shift, agree on a support plan with the new supervisor, and check the usage record again in a few weeks to see if it moved."

That exchange works because Jordan never treats the dashboard as a verdict. Each answer becomes the next question, and the conversation ends with a person, a specific action, and a date to check back, not a vague promise to do better.

Mistakes That Derail The Review

Watch for a few patterns that turn a useful review into a wasted meeting. Accepting the first explanation without checking it against the usage record is one. If Priya had said the team just doesn't like change, and Jordan moved on, the real cause, a supervisor gap, would have stayed hidden.

Naming individual agents in front of an executive is another. It shifts the conversation from process to blame, and it damages trust with the frontline team once word gets back to them, which it always does.

Trying to fix everything in one meeting is a third mistake. If Jordan had also tried to diagnose the billing team's adoption gap and the technical support team's gap in the same conversation, none of the three would have gotten enough attention to produce a real answer.

Last, treating the follow up as optional undermines the whole exercise. An adoption review without a scheduled check back is just a status update. The value comes from returning to the same measure after a specific change and seeing whether it moved.

How To Practice And Score This Conversation

If you manage customer success managers, run this as a role play before someone faces it live. Play the contact center leader and lean on a dashboard as if it explains everything. Say things like "the numbers speak for themselves" and see whether the person across from you pushes past the surface number or accepts it. Score them on whether they ask about breakdowns by team, shift, and contact type, whether they connect the gap to a real change like a staffing shift or a supervisor departure, and whether they end the conversation with one team, one observed barrier, and one named owner who will report back.

This kind of exercise gets sharper with repetition, which is the idea behind DealSpeak. You can rehearse the adoption review, the pushback about making a workflow mandatory, and the follow up conversation as separate scenarios, and get scored on how well you handled each one before you run it with a real leader. The Contact Centers practice conversations cover this scenario alongside related ones, including how to discuss service continuity during an acquisition and how to think about including agent acceptance in a contact center pilot.

An adoption review is not about defending or attacking a number. It is about turning a flat usage figure into a specific, fixable story about one team's daily work. Do that well and the next review becomes a check on progress instead of another round of guessing.