three examples of when It's Not a People Problem. It's a Systems Problem.
There’s a mindset shift that comes up again and again when I work with business owners — and once you see it, you can’t unsee it. It changes how you lead, how you manage, and how you build your business.
When something goes wrong, the first instinct is almost always to blame the people.
Have you ever caught yourself saying:
- Why can’t they follow instructions?
- I’ve shown them three times, why am I doing it again?
- This same mistake keeps happening.
- Why is the team getting annoyed with each other?
- That person never takes responsibility.
- I just can’t get good people.
Having a team can be extremely frustrating. But most of the time, those moments aren’t happening because your people are lazy, careless, or incapable. They’re happening because the systems around them aren’t clear.
When expectations haven’t been laid out, mistakes will happen. People start winging it. Frustrations bubble up. And the same problems keep showing up on repeat.
Let me show you what I mean with three examples that might sound familiar.
1. The guy who drove back for the key.
He rolls in, grabs a coffee, has a smoke, fills his water bottle, jumps in the ute – and halfway to the job realises he’s left without the access key. Back he goes. Ten, fifteen, twenty minutes lost. And it keeps happening.
Frustrating? Absolutely. But this person didn’t have a clear start-of-day routine. He’s relying on memory and habit, and both of those are going to let him down eventually.
What to do instead.
Document a simple pre-departure checklist that lives somewhere your team can actually use it — on the wall at the depot, in a job management app, or printed on the back of the worksheet. It doesn’t need to be fancy. It just needs to cover:
- What needs to be checked before leaving (vehicle, fuel, tools, PPE)
- What needs to be collected for today’s specific jobs (keys, access codes, materials, paperwork)
- Who to contact if something is missing
- The expected start time at the first job
The win here isn’t the checklist itself. It’s the fact that you’ve replaced “hope he remembers” with a repeatable standard. The next person you hire doesn’t have to learn this the hard way; they get the checklist on day one, and they’re up to speed in minutes.
2. The new starter who keeps doing things wrong.
A new team member is given a task with verbal instructions and a rough idea of the expected outcome. They do their best, but the result isn’t what was needed. Time and money are lost because the job has to be redone, and everyone’s frustrated.
What was missing? A clear onboarding process and documented standards for what “good” looks like.
If it’s not written down, the new starter can only guess. And if they forget what they were shown – which is inevitable in the first few weeks – they start to make it up. Inconsistency is the only guaranteed outcome when training happens verbally and standards live in someone’s head.
What to do instead.
Start with the tasks they’ll be doing most often. For each one, capture how it’s done at best practice by the person who already does it well. The easiest way is to film them doing the task once, talking through what they’re doing as they go. That recording becomes the foundation of your documented system.
From there, you (or a team member who’s good at this kind of thing) turn the video into a simple step-by-step guide with the standards clearly laid out. What the finished result should look like, common pitfalls to watch out for, and where to go if something doesn’t quite work out.
Now your new starter has something to refer back to when they forget. They can self-correct without interrupting you or another team member. And every new hire after them gets the same training, without you having to repeat yourself.
This is the principle at the heart of SYSTEMology: capture the knowledge once, document it well, and use it forever.
3. The team member who keeps stepping on toes.
A receptionist or admin person is brilliant at what they do, but nobody has ever clearly mapped out where their role begins and ends. So they do what any keen, well-meaning person would do: they try to help.
They gather information, answer questions, and before long they’re having conversations they’re not really equipped to have; quoting prices, making promises, and trying to close jobs that should have been handed over to a more qualified salesperson.
The result? Clients receive the wrong information early on. By the time the job reaches the sales team or the next department, someone is scrambling to correct what was said, reset expectations, and the client ends up being double-handled.
It’s not a performance problem. It’s a role clarity problem.
What to do instead.
Map the client journey from first contact through to job completion, and identify the exact point where each role hands off to the next. Then document, for each role:
- What this role is responsible for
- What this role is not responsible for
- Exactly what information needs to be gathered before handover
- Who the work is handed to next, and how
For the admin example, that might look like a simple intake script with a defined set of questions. Once those questions are answered, the file is passed to the salesperson. Full stop. No quoting. No price discussions. No promises. Just a clean handover with all the information the next person needs to do their job well.
When everyone knows their lane, the whole business runs more smoothly. Your admin person feels confident in their role. Your salesperson gets warm leads with the right information. Your client gets a consistent experience. And you stop being the referee.
So is it a people problem or a system problem?
In all three situations, the missing system is the problem.
When you document the way things are done — the steps, the standards, the handoffs — you remove the guesswork. Your team knows what’s expected. Mistakes happen less often. And when they do, you fix the process once and solve the problem for good.
That’s why we systemise. Not for the sake of it. Not to add bureaucracy or to micromanage. But to build a business that runs consistently and reliably — whether you’re on-site, in a meeting, or on a beach somewhere without your phone ringing every hour.
A systemised business is a scalable business. It’s also a far less stressful one to run.
If you’re ready to start building a smooth-running, scalable business that doesn’t depend on you to hold it all together, book a free discovery call here.
not sure if systems are right for you. start here
Unblock your 3 most critical bottlenecks in a 90 minute power up session.