Why Your Team Isn't Following Your Systems
Great Systems Don't Create Accountability. Great Leadership Does.
There are two types of frustrated dental practice owners I see all the time. The first has almost no systems. Everything is communicated verbally, expectations live inside the owner's head, and the team is expected to remember how everything is supposed to work. There is very little consistency, so naturally there is a lot of chaos.
The second owner looks completely different. They have put a tremendous amount of effort into building their practice. They have SOPs, checklists, morning huddles, meeting agendas, and written expectations. They have probably even bought a laminator and laminated half the practice. They have explained the systems to the team and may have spent hours preparing meetings to teach them. Yet a few weeks later, they look around and realize nobody is doing what they agreed to do.
Two completely different practices can end up with the same result: chaos. One because there are no systems, and the other because nobody follows the systems they have.
This is one of the most frustrating realizations for a practice owner because it feels like you did everything you were supposed to do. You created the system. You trained the team. You explained the expectations. What else are you supposed to do?
The answer is accountability. Systems create the way you want things done. They do not create the follow-through required to make those behaviors stick.
The Problem Usually Happens After the Meeting
Most practice owners put a lot of energy into the launch of a new system and very little energy into what happens afterward. We introduce something at a team meeting, explain why we are changing it, answer everyone's questions, and walk away believing the system has been implemented.
Then real life happens.
Someone forgets to do it on Tuesday. You notice, but you are busy, so you let it go. It happens again Thursday. The following week, a few other people stop doing it too. You notice that as well, but there are patients to see and problems to solve. Eventually, a month goes by and you are back at another team meeting talking about the exact same thing.
This is where accountability breaks down in so many dental practices. The team did not simply decide the system was unimportant. Leadership unintentionally taught them it was unimportant by watching it not happen for several weeks without saying anything.
Delayed accountability normalizes the behavior. If I tell my team something matters on Monday but watch them ignore it Tuesday through Friday, my actions are communicating something very different from my words. By the time I finally address it three weeks later, I am frustrated because nobody followed the system, while the team is confused about why something I tolerated for three weeks has suddenly become a major problem.
That is when accountability starts feeling emotional. The owner has been quietly accumulating frustration while the team had no idea anything was wrong. Instead of a small conversation about one missed expectation, we now have resentment on one side and defensiveness on the other.
The solution is not stronger confrontation. It is earlier conversation.
Accountability Should Be Timely, Calm, and Consistent
When we hear the word accountability, we often imagine a serious conversation behind a closed door. That is part of the problem. If every accountability conversation feels like someone is getting called into the principal's office, both leaders and team members are going to avoid them.
Most accountability should be much smaller than that.
If I see something that is not happening the way we agreed, I want to address it that day. It might be a 30-second conversation. I am not angry. I am not trying to embarrass anyone. I simply want to understand what happened while the situation is still fresh.
The alternative is what I call accountability with anxiety. This happens when the owner waits until they are frustrated and then approaches the team with, "What the heck happened?" or, "We've talked about this before. You know better." The owner believes they are holding people accountable, but the team experiences the conversation as punishment.
That type of leadership may create short-term compliance, but it also teaches people to hide mistakes. If telling the truth means getting criticized, people become very good at making sure leadership does not hear the truth. You start getting defensiveness, excuses, avoidance, and disengagement instead of ownership.
We do not want people following systems because they are afraid of getting in trouble. We want them following systems because they understand why those systems matter. A closing checklist is not important because the doctor said so. It is important because it prepares the practice to take great care of patients tomorrow and makes responsibilities equitable across the team. When people understand who benefits and why the expectation exists, accountability becomes about maintaining alignment rather than enforcing obedience.
Use Curiosity Before Criticism
The accountability method I use with my team is something I call CVI: Curiosity, Validation, Invitation.
The first step is curiosity. When someone does not follow through, resist the temptation to immediately tell them what they did wrong. Ask what happened.
"Hey, I noticed this didn't get done. Help me understand what got in the way."
That question is very different from, "Why didn't you do this?" One feels like an investigation. The other can feel like an accusation.
This matters because we often make assumptions about why people are not following our systems. We assume they forgot because they do not care. We assume they are resisting the change. We assume they are lazy or unmotivated. Sometimes the explanation is much simpler. Maybe they really did forget. Maybe they were overwhelmed. Maybe the expectation was not as clear as you thought it was. Maybe there is something about the system that makes it extremely difficult to execute during a real clinical day.
You cannot coach the actual problem until you know what the actual problem is. Curiosity gives you that information.
This is especially important when you have spent a lot of time creating the system. We become attached to our solutions. When someone does not follow them, it is easy to interpret that as resistance. Sometimes your team is actually giving you valuable information about why the system does not work as well in practice as it did in your head.
Validation Is Not the Same as Agreement
After you get curious, the second step is validation. This is probably one of the most powerful communication tools a leader can learn.
If someone tells you they did not complete something because they were overwhelmed, you can say, "I get it. You had a lot going on today." If they forgot, you can say, "That makes sense. There were a lot of moving parts this morning."
That does not mean the expectation disappears.
Validation is not agreement. It is simply acknowledging that another person's experience makes sense from their perspective. That distinction matters because people have a very difficult time solving a problem while they are busy defending themselves.
Think about going home after a frustrating day and telling your spouse about something that happened. You explain why you are upset and the first thing they say is, "I think you overreacted."
What do you do next?
You probably do not thoughtfully consider their perspective. You start explaining why you absolutely did not overreact. Now the entire conversation is about defending your experience.
We do the same thing to our teams. Someone tells us why something did not happen and we immediately explain why their reason is invalid. "You weren't that busy." "You had plenty of time." "We already explained this." Now they are defending themselves instead of helping us solve the problem.
Validation lowers the guard. "I can see why that was difficult" allows the conversation to continue. Then we can still say, "We need to figure out how to make sure this happens next time."
You can be understanding and still hold a high standard. In fact, I believe people are much more receptive to accountability when they know their perspective will be heard.
Let Your Team Help Solve the Problem
The final part of CVI is invitation.
Once you understand what happened and have validated the person's experience, invite them to participate in the solution.
"What do you think we could change?"
"How can we make sure this happens next time?"
"What would make this easier to do consistently?"
This is where accountability begins creating ownership. Practice owners are used to solving problems for everyone. We see something that is not working, disappear into our office, create the solution, and then come out and announce the new system. The team immediately starts pointing out all the reasons it will not work.
When you invite them into solving the problem, something changes. Instead of evaluating your solution, they are helping create the solution. They now have some ownership in making it successful.
This does not mean every decision becomes a team vote. You are still the leader, and sometimes there is a specific standard that needs to be met. The invitation is about allowing the people closest to the work to help determine how the team can consistently meet that standard.
Curiosity helps you understand what is happening. Validation keeps the conversation safe enough to be productive. Invitation creates participation in the solution.
That is CVI.
Thirty Seconds Today Beats Resentment Three Months From Now
The real power of this approach comes from how frequently you use it. Accountability should not be something you save for the monthly meeting. If a system is introduced today, start checking it tomorrow.
If it is not happening, have the conversation.
Do not wait until you are irritated. Do not wait until you have enough examples to build a case. Do not wait until the next team meeting so you can address everybody at once.
Have the 30-second conversation while the issue is still small.
Over time, those conversations stop feeling uncomfortable because they become part of the culture. Your team understands that checking in is normal. Clarifying expectations is normal. Asking why something did not happen is normal. Admitting something did not work is normal. Making an adjustment and trying again is normal.
As your dental practice grows, this responsibility also needs to move beyond the owner. You cannot personally hold 30 people accountable for every system in the practice. Your office manager and department leads need to learn how to have these same conversations. You hold your leaders accountable, and they create consistent accountability within their teams. That is how you begin building a dental practice that can operate without the doctor being the answer person for everything.
The goal is not to create more confrontation. It is to make accountability so normal that it rarely feels confrontational at all.
The Bottom Line
If your practice has no systems, build the systems. You cannot create consistency when expectations exist only inside the owner's head.
If you already have the SOPs, checklists, meetings, and processes but your team still does not follow them, stop assuming you need another system. Look at what is happening after the system is introduced.
Are you checking on it tomorrow? Are your leaders following up? Are missed expectations addressed while they are still small? When something does not happen, are you getting curious or immediately becoming frustrated?
Use CVI. Get curious about what happened. Validate the person's experience without lowering the standard. Invite them to participate in the solution. Then follow up again.
Separate the person from the pattern. Focus on solving what is not working rather than making someone feel guilty for getting it wrong. When you see the team doing it correctly, recognize that too. People need to know leadership notices when things go right, not only when something goes wrong.
Great systems are essential to building a profitable, team-driven dental practice. They create clarity and consistency.
But the system sitting in your binder is not what changes your practice.
It is what your team consistently does after the meeting that matters.
