What You’ll Learn
- Why technology implementation fails before the purchase ever happens
- The difference between software training and true technology integration
- How to involve your team in technology decisions without creating chaos
- What practices that successfully optimize technology do differently
- The leadership framework that makes change actually stick
- Why your team’s resistance isn’t about the technology itself
The Pattern That Repeats in Every Practice
Carrie Webber has watched the same story unfold hundreds of times across 26 years at Jameson Management Group, one of the most respected dental consulting firms in the industry.
A doctor goes to a conference. They see a demo. They get excited. They buy the technology. The software company sends a trainer. The team sits through a few sessions. And six months later, everyone’s quietly doing things the way they always did.
“The doctor came home with the shiny new toy, they said we’re going to do this, and then they just turned it over to the team and expected them to make it fly,” Carrie told Adrian Lefler on a recent episode of the Byte Sized Podcast. “But there was no connection to why we were doing it, how it was going to help us, how we were going to work together to make sure it truly became part of our systems and processes.”
The technology wasn’t the problem. The implementation was dead on arrival before the purchase was ever made.
Software Training Isn’t Implementation
Most practices don’t realize that software companies train you on features. That’s not the same as integrating technology into how your practice actually works.
“The training might have been great,” Carrie said. “That rep may have done an amazing job walking the team through how to work the system. But that is a very different thing from true implementation and integration into the practice.”
Training teaches you which buttons to click. Implementation answers harder questions. How does this change our morning huddle? Who’s responsible for monitoring this dashboard? What happens when a patient asks about the new system? How do we handle the transition period when things are slower?
Most software companies don’t address any of that. It’s not their job. Their job is teaching you how to use the product. Your job is figuring out how the product fits into your practice.
“Very few of them do more than that,” Carrie said. “That’s all they’re really paid to do. They’re not there to help you think through the change management. They’re not going to be there to hold your hand when the team pushes back.”
| What Software Training Covers | What Implementation Requires |
| How to use features | Why we’re using this tool |
| Where to click | Who owns each workflow |
| Technical troubleshooting | Team communication and buy-in |
| Product updates | Adjusting existing systems |
| One-time sessions | Ongoing accountability |
The Failure Happens Before the Purchase
If your team finds out about a new technology the day it arrives, you’ve already lost.
“The practices that succeed with technology involve their teams early,” Carrie said. “Not necessarily in making the final decision, but in understanding what problem we’re trying to solve and why this tool might help us solve it.”
This doesn’t mean running every decision through committee. The doctor still leads. But there’s a difference between announcing a decision and building toward one.
Carrie recommends what she calls “pre-framing.” Before you buy anything, have a conversation with your team about the challenge you’re trying to address. Maybe it’s missed calls. Maybe it’s treatment acceptance. Maybe it’s hygiene reappointment rates.
“When they understand the why, they’re already mentally preparing for change,” Carrie said. “When you just drop something on them, their first reaction is fear. What does this mean for me? Am I being replaced? Is this going to make my job harder?”
Fear shuts down learning. Pre-framing opens it up.
Resistance Isn’t About the Technology
When teams push back on new technology, doctors often blame the team. They’re resistant to change. They’re stuck in their ways. They don’t want to learn new things.
Carrie sees it differently.
“Resistance is almost never about the software itself,” she said. “It’s about how the change was handled. It’s about feeling like something was done to them instead of with them.”
People resist when they feel unheard. When their concerns get dismissed. When they’re expected to figure things out without support. When the doctor’s enthusiasm doesn’t translate into actual resources for the transition.
“I’ve seen teams completely transform their attitude toward a technology when the doctor simply said, ‘I hear you, this is hard, and I’m going to make sure you have what you need to succeed,'” Carrie said.
That statement costs nothing. But most doctors never say it. They assume the team should just get on board because the decision’s been made.
The Leadership Gap
Here’s the uncomfortable truth is that most dentists weren’t trained to lead organizational change.
Dental school teaches clinical skills. It doesn’t teach how to communicate a vision, how to manage through uncertainty, or how to hold people accountable without damaging relationships.
“We’re asking doctors to be clinicians, business owners, HR managers, marketers, and change management experts,” Carrie said. “Most of them got zero training on the leadership side.”
This gap shows up every time new technology enters a practice. The doctor knows the tool is valuable. They can see the ROI. But they don’t know how to bring the team along.
Carrie’s advice: recognize that leadership is a skill, not a personality trait. It can be learned. And getting help isn’t weakness, it’s wisdom.
“The best practices we work with are the ones where the doctor says, ‘I don’t know how to do this part well, so I’m going to get support,'” she said. “That humility is actually what makes them successful.”
What Successful Practices Do Differently
After watching hundreds of implementations succeed and fail, Carrie has identified clear patterns in the practices that get it right.
They connect technology to outcomes. The team knows exactly what problem the tool solves and how success will be measured. It’s not “we’re using this because it’s cool.” It’s “we’re using this because we’re missing 35% of calls and losing patients because of it.”
They assign ownership. Someone on the team is responsible for the technology. Not just using it, but monitoring it, troubleshooting it, and keeping everyone accountable. Without ownership, tools drift into disuse.
They build in checkpoints. Implementation isn’t a one-time event. Successful practices schedule regular check-ins to assess what’s working, what’s not, and what needs adjustment. Weekly for the first month, then monthly after that.
They celebrate small wins. Change is hard. Acknowledging progress, even incremental progress, keeps momentum going. “Hey, we answered 12 more calls this week than last week” matters more than you think.
They stay patient. Carrie says real integration takes 90 days minimum. Practices that expect instant results get frustrated and quit too early. The ones that succeed commit to the long game.
The Accountability Structure Nobody Builds
Most practices have no accountability structure for technology adoption. Someone buys a tool. Someone else is supposed to use it. Nobody’s checking whether it’s actually happening.
“You’d be amazed how many practices have software they’re paying for monthly that nobody’s touched in six months,” Carrie said. “Not because it’s bad software. Because there’s no structure.”
Accountability doesn’t have to be complicated. It starts with clear expectations. Who’s using this tool? How often? What does success look like?
Then you build in visibility. Weekly check-ins. Dashboard reviews. Team conversations about what’s working and what’s not.
“If it’s not on the calendar, it’s not real,” Carrie said. “The practices that succeed put implementation on the agenda. They talk about it regularly. They make it part of their rhythm.”
The practices that fail treat technology like a one-time purchase. Buy it, train on it, move on. That’s not how habits form.
When to Bring in Outside Help
Some practices can manage technology implementation internally. Others need support. How do you know which camp you’re in?
Carrie says it comes down to capacity and capability. Do you have someone on your team who can own this process? Do they have time? Do they have the skills to manage change across the whole team?
“If the answer to any of those is no, you probably need help,” she said. “And there’s no shame in that. This is legitimately hard work.”
Outside consultants bring objectivity. They can see dynamics the team is too close to notice. They can have difficult conversations without the baggage of existing relationships. And they’ve done this before, so they know what works.
“We’ve seen every version of this story,” Carrie said. “We know where the landmines are. Sometimes just having someone who’s been through it before saves months of frustration.”
The investment in consulting often pays for itself by shortening the implementation timeline and preventing the slow death of expensive technology sitting unused.
AI Makes This More Urgent, Not Less
The stakes around implementation are rising. AI tools are entering dental practices faster than ever. Diagnostic AI, patient communication AI, treatment planning AI. The tools are powerful and getting more sophisticated every month.
But the implementation challenges haven’t changed. In fact, they’ve intensified.
“AI brings up even more fear because people think it’s coming for their jobs,” Carrie said. “So the change management piece becomes even more important. You have to over-communicate. You have to be even more intentional about involving the team.”
The practices that figure out how to implement technology well now will have a massive advantage as AI becomes more central to dentistry. They’ll be able to adopt faster, with less friction, because they’ve already built the muscles.
The practices that keep fumbling implementation will fall further behind. Every failed rollout makes the next one harder. The team gets more cynical. The doctor gets more frustrated. Eventually nobody wants to try anything new.
The Real Question Before Any Purchase
Before you buy any technology, Carrie suggests asking one question: are we ready to actually implement this?
Not “is this a good product?” Not “can we afford it?” Not “will this solve our problem in theory?”
Are we ready to do the work required to make this part of how we operate?
“If the answer is no, you’re better off waiting,” Carrie said. “A tool sitting unused is worse than no tool at all. It’s money wasted, and it’s a reminder to your team that change doesn’t stick here.”
The best technology in the world can’t overcome a broken implementation process. And a mediocre tool, fully integrated into your systems, will outperform a great tool that nobody uses.
“Fix the people system first,” Carrie said. “Then the technology has somewhere to land.”
In This Episode:
Carrie Webber, CEO of Jameson Management Group
Carrie Webber is the CEO of Jameson Management Group, one of the longest-running dental consulting firms in the industry, founded in 1990 by her parents, Dr. John and Kathy Jameson. A second-generation leader in dental practice consulting, Carrie works with practice owners on the leadership, communication, and change management systems that determine whether technology actually transforms a practice or simply adds to the overhead. She also co-hosts the Jameson Management podcast.
Adrian Lefler, CEO and Co-founder of My Social Practice
Adrian Lefler, CEO of My Social Practice, is a seasoned expert in the dental marketing industry with 14 years of experience. He is widely recognized for his engaging and informative presentations. Based in Suncrest, Utah, Adrian shares his life with his wife, four children, and a lively mix of pets. My Social Practice is a leading dental marketing company, and Adrian is passionate about helping dental professionals succeed in this dynamic field.
Frequently Asked Questions
Why does dental technology fail even when the software is good?
Most failures happen before the purchase. The team wasn’t involved in understanding the problem being solved, ownership wasn’t assigned, and no accountability structure was built. Software training covers features but doesn’t address the change management required for true integration of new dental technology.
How should I involve my team in technology decisions?
Use pre-framing. Before buying anything, have conversations about the challenge you’re trying to solve. Let the team understand the why before the what. You don’t need consensus on every decision, but people need context to mentally prepare for change.
What's the difference between software training and implementation?
Training teaches you which buttons to click. Implementation integrates the tool into your workflows, assigns ownership, builds accountability, and addresses the human side of change. Software companies typically provide training. Implementation is your responsibility.
How long does real technology implementation take?
Carrie recommends planning for a minimum of 90 days. Practices that expect instant results get frustrated and abandon tools too early. Successful implementation requires weekly check-ins initially, ongoing accountability, and patience through the learning curve.
When should a dental practice hire outside help for implementation?
When you lack someone with the capacity and capability to own the process internally. Outside consultants bring objectivity, experience with common pitfalls, and the ability to have difficult conversations without existing relationship baggage. The investment in a dental marketing company often pays for itself through faster, more successful adoption.
