Running an Adoption Review When One Clinic Falls Behind

An adoption review meant to unblock one lagging clinic can turn into a demand for enforcement in under five minutes. The strategic account manager who lets that happen loses the one thing that actually solves the problem, which is an honest account of what is happening inside that clinic. This piece walks through how to run the review so it produces a real answer instead of a scapegoat.

Why This Conversation Goes Wrong

Adoption numbers roll up to a scorecard somewhere, and one clinic sitting at the bottom draws attention fast. By the time a strategic account manager gets asked to run a review, an internal stakeholder like an ambulatory director has usually already decided the problem is compliance, not workflow. That framing feels efficient. It is also almost always wrong, or at least incomplete, and it sets up two bad outcomes.

The first bad outcome is that the account manager agrees to play enforcer. They tell the clinic to fall in line, which is not their job, damages trust with clinical staff, and treats a vendor relationship like a chain of command. The second bad outcome is that the account manager gets defensive, promises a fix without knowing the cause, and leaves the room with no more information than they walked in with. Both outcomes skip the actual diagnostic work. Adoption gaps at a single site usually trace back to something concrete, a staffing change, a scheduling conflict, a training gap, a local policy question, or a workflow that never got mapped to how that clinic actually operates day to day. You cannot fix any of those from a video call by asking people to try harder.

How to Prepare Before the Review

Walk into the review with facts, not talking points. Pull the original adoption commitment from the initial rollout or renewal conversation, so you know what the clinic actually agreed to and by when. Pull any usage or training data your team already has, and separate what you can verify from what someone told you secondhand. If your account records are messy or out of date, clean them before the meeting rather than during it. A separate post on Cleaning Up Account Data Before a Health System Contract Review covers how to do that without stalling the relationship.

Next, figure out who actually owns the answer. The ambulatory director in front of you owns the relationship, but they rarely own the day to day workflow at the clinic level. You need the clinic manager who runs daily operations, the education lead who ran or should have run training, and possibly a support contact who has fielded tickets from that site. This is the same principle behind identifying the right people for a renewal conversation, covered in Finding the Right Owners for a Health System Contract Renewaland it applies just as directly here. An adoption gap, like a renewal, gets solved by the people who touch the workflow, not by the person who signed the contract.

Before the meeting, write down three things, what evidence exists for the gap, what changed since training happened, and which named person can describe the clinic's current process. Bring those three questions into the room instead of an opinion about whose fault this is.

What to Say in the Room

An ambulatory director opens the review with the frustration you expected. "The clinic agreed to this months ago," they say. "I need you to make them follow the process."

You respond by naming what you can actually do, not what you cannot. "I cannot make the clinic do anything, and I do not think that is what fixes this," you say. "What I can do is help us find out what is actually happening on the ground there. Can we get thirty minutes with the clinic manager and the education lead, so we can walk through the current workflow, what training actually happened, and whether anything changed since rollout."

The director pushes back. "We do not have time for another meeting, we already trained them," they say. You hold the line without escalating. "I understand the pressure. A short meeting now is faster than another quarter of the same numbers," you say. "If training happened and something else is blocking adoption, we need to know that before we can fix it. If training did not fully happen, that changes what we ask the clinic to do next. Either way, we need someone from the clinic to tell us, not guess from here."

Once you get that meeting, ask direct questions of the clinic manager and education lead. Ask what the current process looks like step by step. Ask what changed since training, including staff turnover, new hires, or a schedule change that broke the old routine. Ask what would need to be true for the workflow to run the way it was designed. Close the loop by writing down one blocker, one owner, and one date, and confirm all three with the group before you leave the room.

Mistakes to Avoid

A few habits sink this conversation every time.

1. Agreeing to enforce the workflow yourself. You do not manage the clinic's staff, and offering to sounds helpful but sets an expectation you cannot meet.
2. Accepting the director's diagnosis without checking it. Resistance is a story, not a fact. Ask for the evidence behind it before you act on it.
3. Skipping the local owners. A conversation with the ambulatory director alone will not surface what is actually happening at the clinic level. You need the people doing the work.
4. Leaving without a concrete next step. A general sense that things need to improve is not a plan. Name the blocker, the owner, and the date before the meeting ends.
5. Implying that using the product correctly is the same as good patient care. Adoption is a workflow question. Keep it there, and do not let the conversation drift into clinical judgment that is not yours to make.

How to Practice and Score This

This conversation is easy to rehearse and easy to get wrong live if you have not. Build an agenda ahead of time with four columns, evidence, local owner, dependency, and next action, and fill in what you already know before the meeting starts. Then have a peer or manager play the frustrated director and push you to promise enforcement. A strong response asks for the operating fact that would change the support plan, and it names who can verify it. A weak response either caves and promises control you do not have, or gets pulled into an argument about whose fault the gap is.

DealSpeak's Medical Devices practice conversations let you run this scenario against an AI counterpart that plays the director realistically, including the push for enforcement and the impatience about scheduling another meeting. Score yourself, or have your manager score you, on three things, whether you redirected the conversation to verifiable facts, whether you identified the right people to include, and whether you left with a named blocker, owner, and date. Practicing this once before you need it in a real review is the difference between reacting to pressure and running the meeting on purpose.

An adoption gap at one clinic is rarely about willingness. It is about a workflow that broke somewhere between training and daily use, and your job is to find where. Run the review with the right people in the room, and you get a fix instead of a fight.