My team crossed their arms. Then I changed one thing.
Same program, two markets, very different days. Here's what I showed the team before the vendor started talking.
The Presenter Was Late. The Rollout Went Better.
FIELD NOTE 007
Question: When we bring a new tool to our team, are we starting with the tool or with the problem they already feel?
Health Path: Team + Practice
Status: A lesson from two rollouts; now testing it on purpose
From the field
I have a confession that many of you will recognize.
I go to an event. I see a new technology or training program that looks like it solves one of the dozen problems keeping me up at night. I get a demo. I make the purchase.
Then I bring it home to the team.
It's not that the tools are bad. Many are excellent. But dentists are overwhelmed right now, and a good demo can feel like relief.
That happened to me recently. We invested in a treatment communication training program, along with an AI tool that drafts chart notes and helps us see how well we're putting the training into practice.
Our first rollout was with our Texas team.
The presentation was great. The trainer was clear and experienced.
And within minutes, I watched arms cross.
Comments started: Why this won't work here. How we already do this. What happens when the schedule is packed. I suspect there was a quieter question underneath some of it, too—if a tool can write the notes and score the conversations, what does that mean for me?
We spent a good part of the day working through objections. By the end, I could tell the path to full adoption was going to be a long one.
I chalked it up to typical resistance. Fear of change. People being people.
Before the next market, we talked about how to improve our messaging. We had some ideas.
Then the Illinois rollout went sideways in the best possible way.
The presenter was delayed by travel. I had a room full of team members and time to fill.
So, impromptu, I pulled up the Patient Path to Health for our Springfield locations.
I showed them where our patients were getting stuck. Where they stalled between diagnosis and treatment. How many people were sitting at each stage, not yet benefiting from the care they needed.
I reminded them of something they already knew too well: when it's time to reach out and help a patient get back on the path, our notes often don't tell us enough. We can't tell what was discussed, what the patient was worried about, or what the next step was supposed to be.
We talked about the time spent on notes. The overwhelm. The days when team members stay after hours to finish documentation.
Then I showed them what it could look like to get that time back—and use it, with this new way of communicating about treatment, to help more of those stuck patients move forward.
When the presenter arrived, the room was different.
No crossed arms. No hour of objections. Just focus on the expertise and tools we were all gaining.
Same company. Same program. Same tool. Very different day.
The Health Progress question
I had called the Texas reaction resistance.
I don't think that was fair.
This was not a failure of our team. It was a failure of how we introduced the change.
In Texas, we started with the solution. The team heard about a new framework and a new tool before anyone had reconnected them to the problem it was meant to solve. Without that, a new tool sounds like one more thing to learn, one more thing to be measured on, and maybe one more thing that could replace them.
In Illinois, we started with the patients. And with the team's own pain.
Traditional rollouts are organized around the tool: its features, its training plan, its go-live date.
Progress-focused rollouts are organized around the gap: where patients are stuck, what is making the team's work harder than it needs to be, and how this change helps close that gap.
People don't resist progress they can see. They resist change they can't connect to anything.
Without planning it, I had done a version of what we call Map the Path—for the team. Showing them where patients stall made the purpose of the tool obvious before anyone explained a single feature.
Fear of being replaced
I want to address that quieter question directly, because I hear it from other doctors constantly.
When a tool drafts notes or analyzes conversations, some team members reasonably wonder whether their role is shrinking.
Reassurance alone doesn't answer that. What helped in Illinois was being specific about where the freed-up time goes: back to the conversations with patients that only a person can have.
The point of the tool was never to need fewer people.
It was to give our people more time for the part of the work that actually moves patients toward health.
If we can't explain that clearly—and then actually protect that time—the fear is rational.
What we're trying—and learning
We are turning the accidental Illinois version into a deliberate one. Three changes so far:
1. Preview the vendor presentation before the team sees it.
The vendor knows the tool. Our operations director or office manager knows our team.
Before a rollout, we now want the presenter to walk through the material with that leader first, to assess how it will land. Sometimes that leads to small adjustments. Sometimes it means our director translates the content and trains the team directly, rather than the vendor.
2. Start with the problem the team already feels.
Before any features: remind the team of the specific challenges they're living with right now. The after-hours notes. The patient outreach that goes nowhere because nobody knows what was discussed. The frustration of seeing care stall.
3. Show the patients who aren't benefiting yet—then narrow the focus.
Show where patients are getting stuck, how many of them there are, and the opportunity to help them. Then be explicit about exactly what this new solution is meant to improve. Not everything. One or two things.
What's still hard:
One good day is not full adoption. Illinois started better, but we are still early in integrating the training and the tool into daily habits in both markets.
We also have to go back to Texas. Starting over with the "why" after a rough first impression is harder than getting it right the first time. We're working on that.
And honestly, this lesson applies to me as much as the team. The best time to ask what problem a tool solves is before I buy it—not when I'm standing in front of my team trying to explain it.
Try this in your practice
Before your next tool, program, or process rollout, run this exercise with the leader closest to the team:
Write one sentence: "This change is meant to help patients who are stuck at ______ and team members who are frustrated by ______." If you can't finish it, you're not ready to roll out.
Pull your data. Find one view of where patients are stalling—unscheduled treatment, overdue recare, incomplete plans. Count them.
List three current frustrations the team would name without prompting. Ask a few team members if you're not sure.
Preview the presentation with your office manager or director. Ask: "Where will this lose people?"
Open the rollout with steps 2 and 3. Introduce the tool only after the room agrees the problem is real.
Afterward, compare it to your last rollout. How much time went to objections? How many questions were about the patient versus about the tool?
Compare notes
Think about the last new tool or program you brought to your team. How did it land?
And what do you wish you had shown them before the presenter ever started talking?
—Josh