How to Handle Team Resistance to Following Systems

You Can’t Hold People Accountable Without a Process

Why isn’t your team following the process? Here’s the hard truth most business owners don’t want to hear: you probably haven’t given them a clear one.

Handling team resistance starts well before any tough conversation. It starts with having documented systems in place. You can’t get frustrated with someone for not meeting a standard you never wrote down. You can’t hold them to a method you never taught them.

That’s why the very first step is capturing what you’re doing. When expectations are written, visible, and accessible to every team member, you create a foundation for accountability. Without that foundation, every performance conversation turns into a he-said-she-said argument with no resolution. Once you’re clear on who is doing what, by when, and how, there’s nowhere to hide. That’s the level of transparency you should be aiming for.

The 3 Reasons Your Team Doesn’t Follow the Process

When someone on your team drops the ball, it’s almost always for one of three reasons. This diagnostic framework gives you a fast way to pinpoint the root cause and fix it.

They Don’t Know Why

Sometimes a team member genuinely doesn’t understand why a task matters. They haven’t connected the dots between their work and the bigger picture.

David shares a real example from his own business. A new sales assistant wasn’t entering data into the CRM. When asked about it, the response was simple: “No one told me that was part of my job.” Once David explained the chain reaction (no data means no reports, no reports means no decisions), the team member understood and changed course immediately.

This is exactly why every system should start with the “why.” Not a corporate mission statement. Just a plain-English explanation of what happens upstream and downstream when this task gets done right, or doesn’t.

They Don’t Know How

This one’s sneaky. A manager assigns a task, sets a deadline, and assumes the person knows how to do it. But if you haven’t shown them the method, and there’s no system they can reference, they have an easy out: “Nobody showed me.”

You can fix this by creating clear, step-by-step systems and training your team on them. The system covers the importance, the method, and the reporting. Once you’ve done that, you’ve removed the second excuse entirely.

They Don’t Want To

Here’s where it gets real. If someone knows why a task matters and knows exactly how to do it, the only reason left is motivation.

You have two options at this point. First, you can incentivise the action you want, making it worth their while to follow through. Second, if the task is simply part of the role, you can have a direct conversation: this is what the job requires. If they’re still not willing to do it, they may not be the right fit.

The Script That Makes Accountability Conversations Easier

Nobody enjoys confrontation. But there’s a way to address underperformance without it turning into a personal attack.

The approach is straightforward. When you notice someone isn’t meeting the standard, you say something like: “I’ve noticed you’ve underperformed here, and it’s a little bit unlike you.”

That one line does two important things. It calls out the behaviour, not the person. And it frames the issue as an exception to their normal standard, which keeps the conversation collaborative instead of adversarial.

From there, you walk them through the three reasons. Did they understand why it mattered? Did they know how? Usually, they’ll land on one of the first two. Nobody is going to tell their boss, “I just didn’t want to do it.”

You solve that issue together the first time. But here’s the real power of this approach: if the same problem repeats, you’ve already taken away the excuses. You can say, “We talked about this. You know the importance. You know the method. So what’s going on?” That second conversation is much more honest, and it’s much easier for the manager because the system is doing the heavy lifting.

What Happens When Resistance Persists

Sometimes, even after clear systems and honest conversations, someone keeps doing things their own way. This is what David Jenyns calls “persistent resistance,” and it requires a more structured response.

Before making any big decisions, evaluate the situation using the 4 C’s framework: Conduct (how severe is the resistance, and is it affecting others?), Coaching (have you actually provided enough support?), Commitment (are they showing any effort to change?), and Cost (what’s the real impact on the business?).

Sandra at Taking Care Mobile Massage faced this exact situation. A long-time team member resisted digital systems, refused to stop printing everything, and eventually couldn’t cope with the changes. After exhausting her coaching options, Sandra made the difficult decision to let her go and rebuild her support team. She started hiring specifically for adaptability and tech-savviness. The result? The business saw fourfold growth, going from 1,000 massage hours per month to targeting 2,000 to 3,000 hours.

The lesson from Sandra’s story isn’t “fire anyone who pushes back.” It’s that once you’ve removed every excuse and provided every opportunity, protecting your systems culture matters more than keeping one person comfortable.

Build a Culture Where Systems Are the Norm

The ultimate goal isn’t enforcing compliance. It’s building a workplace where following the system is just how things are done, as natural as driving on the correct side of the road. When a new team member joins and sees everyone around them working from documented processes, asking “is it in the system?” before asking a colleague, the culture does the heavy lifting for you.

Start with the framework. Document the why and the how. Remove the excuses. And when resistance shows up, meet it with a system, not emotion.

FAQs