At our Annual Retreat last year, one of our top builders pulled me aside at the bar in Mexico. A few tequilas in, he started venting about something that a lot of serious builders run into once they've done the hard work of systemising their business.
He'd spent months documenting his processes. Videos, written SOPs, the lot. His building company was about as systemised as it gets. But his team still wasn't following through. Processes were being skipped, steps were missed, and he couldn't figure out why putting in all that effort wasn't translating into consistent results on the ground.
The frustration wasn't unusual. When you've invested heavily in building systems, watching your team bypass them feels like a personal failure. It can also push you toward micromanaging, which creates a different set of problems entirely.
The conversation that night led us to a tool we call exception reporting. The concept is straightforward. Instead of monitoring everything, you only report on what isn't being done or isn't being done correctly. It lets you zero in on the specific gaps, whether that's a process being skipped, a step being misunderstood, or a gap where no process exists at all.
He left the retreat, implemented it, and three months later things were ticking along well.
But when I called him last week, the picture had changed.
The exception reports were piling up. He was getting inundated with flags across multiple areas of the business, and rather than dig into what was causing them, he was considering winding back the reporting altogether. His reasoning was that the volume was overwhelming him and he wanted to focus on what mattered most.
This is a mistake a lot of builders make when systems get uncomfortable.
The volume of exception reports wasn't the problem. It was a symptom. Switching off the reporting would be like pulling out the smoke detector because the alarm was too loud. The fire doesn't go away.
What he needed to address was the underlying cause, and it usually comes down to one of two things.
If your entire team is struggling to follow your processes consistently, the most likely explanation is that the processes haven't been communicated clearly enough, or that training hasn't been thorough enough to make the behaviour repeatable.
This isn't a criticism of the builder. It happens a lot. You can have a perfectly well-designed system that still falls apart in execution because the people meant to follow it haven't been shown how, or haven't been given the support to do it consistently. That's a leadership and communication problem, and it's fixable.
If, on the other hand, your issue is isolated to one or two people who are repeatedly dropping the ball while everyone else performs, the problem is different. You may have someone in a role they're not suited to.
That's a harder conversation, but an important one. Keeping the wrong person in a role because it feels uncomfortable to act quickly ends up costing the entire business. It affects delivery, morale, and ultimately your bottom line.
Widespread non-compliance across the team points to training and communication. Isolated, repeated failures from the same individuals points to a people fit issue.
Both are solvable. But they require different responses, and confusing one for the other wastes time and compounds the damage.
Systemising your building company is one of the most valuable investments you can make. But the systems only do their job if your team follows them. That means being willing to train properly, communicate clearly, and give your people a genuine opportunity to perform.
And if that still doesn't produce results with a particular individual, you need to move quickly. The longer you hold on, hoping things will improve without changing anything, the more it costs you in profit, productivity, and the confidence of the rest of your team.
Your systems are only as strong as the people who carry them out.
Ready to get your team actually following your processes? Book a strategy session with our team and we'll help you work out exactly where the gap is and what to do about it.