How to Manage Employees Who Won’t Follow the Process
You documented the process. You trained the crew. You even laminated the checklist and stuck it on the wall. And still, Mike does it his own way every single time.
If you’re a trades owner wondering how to manage employees who won’t follow the process, you’re not alone. This is one of the most common—and most frustrating—issues I see in HVAC companies, plumbing shops, electrical contractors, and construction firms. The owner finally takes the time to systematize something, and half the crew ignores it like it’s a suggestion rather than a standard.
Here’s what I’ve learned after 25 years of operations leadership: the employee who won’t follow the process is rarely the root problem. They’re a symptom. And if you want to fix it for good, you need to figure out whether you have a process problem, a people problem, or—most often—a management problem.
Why Employees Don’t Follow Processes
Before you can fix non-compliance, you have to understand what’s actually driving it. In my experience, there are five main reasons employees ignore documented processes:
1. They don’t know the process exists. You wrote it down. You mentioned it in a meeting three months ago. But did you actually train them on it? Did you verify they understood it? In trades companies especially, information gets lost between the office and the field. Your install crews might never have seen the checklist your office manager printed out.
2. The process doesn’t work in the field. This one’s hard to hear, but sometimes your process is the problem. It was designed in the office by someone who hasn’t been on a job site in years. It adds steps that don’t make sense when you’re standing in a crawl space or working against a deadline. Your best technicians ignore it because following it would actually make them worse at their job.
3. They weren’t involved in creating it. People support what they help create. When you hand down a process from on high without any input from the people who have to follow it, you’re asking for resistance. Your senior techs have been doing this work for fifteen years. They have opinions. If you didn’t ask for those opinions, they’re going to express them through non-compliance.
4. There are no consequences for ignoring it. Be honest with yourself here. When Mike skips steps on the install checklist, what happens? If the answer is “nothing,” you’ve told him the process is optional. Every time you let non-compliance slide, you’re training your whole team that processes don’t actually matter.
5. Management doesn’t follow the process either. This is the big one. If your dispatcher doesn’t fill out the job ticket completely, why would your techs? If your project manager skips the pre-job walkthrough, why would your crews do their safety checklist? Your team watches what you do, not what you say.
Process Problem vs. People Problem
When someone isn’t following the process, you have to diagnose the real issue before you can solve it. I use a simple framework: Is this a process problem, a training problem, or a people problem?
It’s a process problem if: Multiple people struggle with the same step. The process works in theory but fails under real job conditions. Following the process takes significantly longer than not following it with no clear benefit. Experienced employees consistently find workarounds.
It’s a training problem if: New employees struggle but veterans don’t. The employee seems willing but confused. They follow some steps but miss others consistently. When you show them again, they correct immediately.
It’s a people problem if: One person struggles while everyone else succeeds. They’ve been trained multiple times with no improvement. They know the process but choose not to follow it. Their non-compliance comes with attitude or pushback.
This distinction matters because each type requires a different solution. If you fire someone for a process problem, you’ll just fire the next person too. If you keep retraining someone with a Core Values issue, you’re wasting everyone’s time.
Rolling Out a Process So Employees Actually Follow It
Most process rollouts fail before they start because owners skip the setup work. Here’s how to do it right:
Involve your people in creating it. Before you finalize any process, get input from the employees who will actually use it. Not approval—input. Ask your best tech: “What would make this easier to follow in the field?” Ask your dispatcher: “What information do you need from crews that you’re not getting?” When people see their ideas in the final process, they own it.
Explain the why. Don’t just tell people what to do—tell them why it matters. “We’re using this install checklist because our callback rate is costing us $4,000 a month. When we miss steps, customers call back, we eat the labor, and nobody’s happy.” People follow processes they believe in. They resist processes that feel like busywork.
Train properly. A meeting where you talked about the process is not training. Real training means walking through it step by step, having them do it while you watch, correcting in real time, and following up in the first week to answer questions. For field crews, this might mean riding along on the first few jobs after a process change.
Get explicit agreement. This is the step most owners skip. After training, look your employee in the eye and ask: “Do you agree to follow this process starting Monday?” Wait for a verbal yes. This transforms an expectation into an agreement. It’s much harder to ignore something you explicitly committed to.
The Agreement Conversation
In the Business Operating System framework I use with clients, we focus on turning expectations into agreements. The difference is accountability.
An expectation is what you hope will happen. An agreement is what you both committed to making happen.
When you roll out a new process—or when you’re having a correction conversation about an existing one—make it explicit: “Here’s the process. Here’s why it matters. Do you agree to follow it?” If they say yes, you have an agreement. If they say no or hedge, you’ve surfaced resistance before it becomes non-compliance. Either way, you’ve made the invisible visible.
The power of an agreement is what happens when it’s broken. Instead of “you should have followed the process,” you can say “you agreed to follow the process.” That’s a much clearer conversation.
When Non-Compliance Becomes a Values Issue
Sometimes the employee who won’t follow the process has a deeper problem. They’re not confused about the process—they don’t respect the process. Or they don’t respect you. Or they believe they’re above the rules that apply to everyone else.
This is a Core Values issue, and it requires a different approach.
If one of your company values is “team player” or “do it right” or “follow through,” persistent process non-compliance is a values violation. The conversation shifts from “here’s how to do it” to “this behavior isn’t consistent with who we are.”
You’ll know it’s a values issue when: the employee has been trained multiple times with no improvement; they’re dismissive or defensive when confronted; their attitude affects other team members; they follow the process only when they know they’re being watched.
Values issues don’t get better with more training. They get better with clear consequences, or they get better when that person works somewhere else.
The Consequence Framework
Here’s the progression I recommend for handling process non-compliance:
First conversation: Clarify and recommit. “I noticed you didn’t follow the install checklist on the Smith job. Help me understand what happened.” Maybe there’s a reason. Maybe the process needs adjustment. If not: “We agreed you’d follow this process. Are you still committed to that?” Reset the agreement. Document that you had this conversation.
Second conversation: Formal warning. “This is the second time we’ve talked about the install checklist. We agreed you’d follow it, and it’s not happening. I need you to understand that this is serious. If it happens again, we’ll need to discuss whether this role is the right fit.” Put it in writing. Have them sign it.
Third conversation: Performance plan or exit. At this point, you’ve been clear, you’ve been patient, and nothing has changed. Either this person goes on a formal 30-day performance plan with specific milestones and consequences, or you part ways. The choice depends on whether you believe they can change and whether you can afford to find out.
The key is consistency. Every employee, every time. If you let your top producer skip steps while holding everyone else accountable, you’ve destroyed the whole system.
The Real Reason Employees Don’t Follow Process
I saved the hardest truth for last. In most companies I work with, the biggest reason employees don’t follow process is that management doesn’t enforce it consistently.
You made a rule. Someone broke it. You were busy, or you avoided conflict, or you told yourself you’d address it next time. Except next time never came. And your employee learned that the rule doesn’t really apply.
Then you did enforce it with someone else—maybe a newer employee or someone you don’t like as much. Now you’ve got inconsistency, which breeds resentment, which breeds more non-compliance.
If you want employees who follow the process, you have to be the person who enforces the process. Every time. Even when it’s uncomfortable. Even when it’s your best tech. Even when you’re tired.
The process is only as strong as your commitment to it.
Signs Your Process Compliance Problem Starts with You
- You can’t remember the last time you addressed process non-compliance directly
- Different employees follow different standards and you’ve accepted it
- Your managers don’t follow the same processes they enforce
- You have processes documented that nobody—including you—has looked at in months
- When someone ignores a process, your first instinct is to let it go “this one time”
- Your top performer plays by different rules than everyone else
If you nodded along to three or more of these, your process compliance problem isn’t about your employees. It’s about creating a culture where processes actually matter—and that starts with you.
Ready to Build a Team That Actually Follows the Process?
If you’re tired of repeating yourself and watching your documented processes gather dust, let’s talk. In a 30-minute call, I can help you figure out whether you’re dealing with a process problem, a people problem, or a leadership problem—and what to do about it. A quick conversation costs nothing and could save you months of frustration.
For managing process accountability across your team, I use Ninety.io — try it free for 30 days. It keeps agreements visible, tracks who’s doing what, and makes accountability conversations a lot easier.
