You can feel that your business is running below what it could be. Call it 70% of full speed if you want a number for it. The symptoms are there even when you can’t name where the loss is going. Quotes take longer to close than they used to. Customers don’t come back at the rate they once did. New hires take longer to be productive. Margins slip a percent or two each quarter. None of it screams. All of it is real money.
The missing 30% lives in the gaps between the parts of your business. The bit nobody planned, drew on a whiteboard, or wrote a procedure for. That’s where most of the friction in a growing SMB lives, and it isn’t visible from inside any one department.
This is what systems thinking is about. It’s also what most “improvements” miss.
A system is its connections, not its parts
When most people hear the word “system”, they picture a thing. A piece of software. A documented procedure. The accounting system, the booking system, the HR app nobody updates.
That’s not quite right.
A system is a set of parts working together to produce something the parts cannot produce on their own. The defining feature isn’t the parts. It’s the interactions between them.
Remove the engine from a car. You still have an engine. You don’t have a car. A car is what the engine, the transmission, the wheels, the steering, the brakes, the fuel and the driver all do together when they’re connected. An engine on its own is just a heavy lump of metal that doesn’t go anywhere.
Your business is the same. The parts are obvious: people, departments, processes, customers, suppliers. The system is what those parts do when they interact. That is where the actual behaviour of your business comes from.
Your business is a system of systems
Inside the business, smaller systems sit nested within larger ones.
Sales is a system. The way leads come in, get qualified, get followed up, become quotes, become wins or losses. Delivery is its own system, with its own internal flows: project initiation, resource allocation, communication with the customer, invoicing.
Then there are the systems nobody planned. Most owners don’t realise they’re there. The way a customer actually experiences your business from first enquiry to final invoice. How information about a problem in delivery makes its way back to sales for next time, or doesn’t. Whether a complaint teaches the business something, or just gets handled and forgotten.
Nobody drew these on a whiteboard. Nobody wrote a procedure for them. They formed at the boundaries where teams met, in the gaps where official processes stopped. They run a meaningful slice of your business, and they’re invisible until they fail.
None of these systems are the tools you use. The tools are the “how”. They’re the by-products of a way of working that already exists. The system is the way the work actually flows: what gets decided, by whom, with what information, and what changes as a result of each decision.
Confuse the two and you’ll spend years upgrading tools and never fix what’s actually wrong.
How each part can be running at 100% and the whole still fail
This is the bit that surprises most owners.
Sales hits its number. Delivery hits its number. Finance closes the books on time. Customer service maintains its CSAT. Every individual scorecard says the business is healthy.
But customer churn is creeping up. Margins are leaking each quarter. The team is working harder than ever and the business doesn’t feel like it’s growing in proportion to the effort.
Each part is doing its job. Yet, the whole is failing.
This happens because the goal of each part has drifted away from the goal of the whole. Sales is measured on closed deals, so it pursues the closeable, even when the closeable deal isn’t profitable. Delivery is measured on utilisation, so it accepts work that fits the schedule, even when the work was poorly scoped. Finance reports against the targets it was given, not the targets that would actually predict trouble. Customer service is measured on response time, not on whether the underlying issue ever gets fixed.
Each part optimises for what it can see. The system as a whole pays the cost. And because the cost shows up at the boundaries between teams, no individual team owns it. No individual team can fix it.
The most reliable signal that a business has a systems problem isn’t that something looks broken. It’s that everything’s running, and nothing’s improving.
Feedback, and what silos break
The reason a healthy business stays healthy is feedback between its parts.
When sales books work that delivery struggles to ship, delivery tells sales, and sales adjusts what it sells. The information loop closes. The system corrects itself.
When customer service sees the same complaint three weeks running, it goes back to delivery, who finds the underlying issue and stops it happening again. Loop closes.
These feedback loops are how a business notices things that no individual part can see.
Silos break the loops. Not dramatically. Nobody declares independence; nobody refuses to talk to other departments. It’s quieter than that. Each team gets clear about what it’s responsible for, builds tools and routines that make its own work efficient, hits its own metrics. The pride point becomes “we have it covered.” The unintended consequence is that the team stops needing to interact with the rest of the business in any meaningful way.
When sales has it covered, sales doesn’t ask delivery what would help. When finance has it covered, the conversations between finance and operations get shorter every quarter.
The silos aren’t built by ill-will. They’re built by competence.
The parts keep functioning. The system stops adapting. It doesn’t fail dramatically; it just stops getting better.
The symptom is the same in every business that gets here: the parts work, the whole doesn’t, and nobody can quite say why.
When the whole isn’t humming at 100%
A system that’s failing at the boundaries rarely shows up as a failed system. It shows up as a system that’s running, just not running well.
The team is busy. Numbers are mostly hit. Customers are mostly happy. From any one vantage point, things look fine.
But fewer customers come back than used to. Quotes take longer to turn into closed work. Margins slip a little. New hires take longer to be productive than the last cohort. None of these are emergencies. All of them are symptoms of the same underlying issue: the connections aren’t doing their work, and the gap lives between the parts where nobody owns it.
On the technology side, the same pattern shows up. Each team has its own tools, sitting in their own silo. Sales lives in the CRM. Operations runs on a job management platform. Finance has its own world inside the accounting tool. Each was chosen by the team that uses it, and most don’t talk to anything outside their department.
So the same customer details exist in three places, with small differences in each. Handovers between teams happen by email or, more often, by someone re-typing what one tool said into the next. Every report needs reconciling before anyone trusts it. Every meeting starts with five minutes of “is that the latest figure?”
Pick any 30-person Australian SMB and the shape is the same. A professional services firm: timesheets in one tool, project costs in a second, invoicing in a third, end-of-month consuming half a week because nothing reconciles automatically. A construction business with 25 staff: jobs quoted in a spreadsheet that never sees the job-costing system, so the margin on each project only becomes clear two weeks after it’s finished. Different industries. Same gap.
None of that is the system. All of it is the visible debris left behind when the system stops working at the boundaries.
If the business were a car, every component would pass its individual inspection. The car would still drive like it has a slow leak somewhere.
Why most “improvements” don’t move the needle
When owners decide to do something about it, the default move is to look at events. A bad month. A lost customer. A specific complaint. They fix the event.
Then it happens again, in a slightly different form, somewhere else in the business.
Events come from patterns. Patterns come from structure. Structure comes from how the system is wired together and what feedback flows through it.
Most “improvements” target the events. A new checklist for handovers. A new status meeting on Mondays. A new tool to track complaints. The events stop happening, briefly. The structure underneath is unchanged. New events appear in a slightly different shape.
This is why so many SMB owners feel like they’re playing whack-a-mole with the same kind of problems for years. The mole isn’t the problem. The structure of the system is producing moles.
The same pattern shows up in the technology stack. Most SMBs end up with ten tools doing the work of three, each bought to solve a specific event. The owner can name every tool. The team can list what’s wrong with each. But the structural problem, that none of them are connected and the same data lives in three places at once, is what keeps generating the events.
A new tool rarely closes the gap. It usually adds another silo to the pile.
It will take more than a new tool to fix this. It will take a clear look at the system itself. Where the connections are. Where the feedback is missing. Where each part is doing its job at the cost of the whole.
That work has rarely been done in the SMBs we meet. Not because it’s hard. Because nobody has been looking at the business this way.
Once the system is clear, the technical answer often is too. Sometimes it’s a properly chosen integration between tools you already have. Other times it’s a thin layer of custom software bridging a gap a vendor left. Occasionally it’s consolidating ten tools down to three. The right answer depends on the system, and the system has to be understood before any tool decision makes sense.
What systems thinking actually looks like in practice
Systems thinking isn’t a framework or a methodology. It’s a habit of asking different questions.
When something goes wrong, instead of asking “who messed up?” or “which tool failed?”, ask: what about the system made this likely?
When two parts of the business can’t agree on the facts, instead of arbitrating between them, ask: what feedback is missing between these two that’s letting them see different things?
When a metric is improving in one team but the business overall isn’t getting better, ask: what is this team optimising at the cost of the whole?
When the same kind of issue keeps recurring across different events, ask: what structure is producing this pattern?
These aren’t difficult questions. They’re just different from the questions most businesses are in the habit of asking. Businesses that get good at asking them stop spending money on improvements that don’t stick, and start spending it on changes that compound.
Where this goes
The work most SMBs need isn’t a new tool. It’s looking at the system underneath: how the parts are connected, where the feedback is missing, what the silos are quietly costing, and where each part has drifted from the whole.
Once you can see that, the right tools become obvious. So do the right processes and the right conversations. The hard part was never the doing. It was the seeing.
For a more concrete self-check, Five Signs Your Business Has Outgrown Its Systems walks through five recognisable scenarios you can spot in your own business inside ten minutes. If two or three of them ring true, you’re in the territory this article is about.
At Encubed Solutions, this is the work we do first. Our Engage, Enable, Enrich approach starts with mapping the actual system: the official one, the unofficial one, the workarounds, the silos that nobody intended but everyone is living with. Only after that do we touch tools or processes. The order matters.
If you don’t know where to begin, that’s exactly what a Process Audit is for. We map how work actually flows through your business, find the two or three critical processes where it’s leaking the most time and money, and hand you a ranked roadmap to get unstuck. You leave with a clear, costed picture you own and can act on, with us or without us. We’d rather help you see the system clearly than sell you a tool that won’t fix it.