Your business does not need to be broken to work better

Most operational problems do not arrive as a single dramatic failure. Nobody wakes up to find the business broken. Instead, friction builds gradually: another spreadsheet to cover a gap, another manual handover because two systems do not talk to each other, another exception process that quietly becomes the normal process.

None of these decisions looks wrong at the time. Each one is a reasonable response to a specific, immediate problem. The trouble is what happens when you add them together across a few years of growth.

The gap between "working" and "working well"

Work still gets done. Orders still go out, invoices still get raised, customers still get served. That is precisely what makes this kind of friction hard to spot: the business is not failing, so there is rarely a moment that forces anyone to stop and look at the whole picture.

What tends to be true, instead, is that it takes more effort than it should. More chasing. More checking. More reliance on the two or three people who happen to know how things really work, as opposed to how the org chart or the process document says they work.

There may be no single crisis, only a persistent sense that the business is harder to run than it should be.

That sense is worth taking seriously. It is usually a reasonably accurate read of the underlying operating cost, even when nobody has measured it directly.

Why "that is how we have always done it" is a red flag, not a defence

"That is how we have always done it" is often said as an explanation, but it is rarely a justification. It describes history, not value. A workaround introduced to solve a problem in one quarter, with one team, using the systems available at the time, is not automatically still the right way to do that piece of work three years and two systems later.

The phrase hides two different things, and it is worth telling them apart:

• Cost: the manual re-entry, the reconciliation, the time spent by skilled people on work that adds no value a customer would recognise or pay for.
• Risk: the dependency on individual knowledge, the single point of failure when that person is on leave or leaves the business, the inconsistency that shows up the moment volume increases or a new person joins.

Neither of these tends to show up cleanly on a profit and loss statement. They show up as a general sense that the business is harder to scale than it should be, and as a leadership team that is busier than the size of the business would suggest.

An illustrative example

Consider a business (illustrative, not a specific client) that grew from a handful of people to several dozen over a few years. Sales, delivery and finance each adopted their own way of tracking work, because each solved their own immediate problem well. Nobody sat down and designed how information should flow between the three. By the time growth slowed enough for anyone to look up, it took a full day each month to reconcile what had actually been sold, delivered and invoiced, not because any one system was bad, but because nobody owned the journey between them.

That is a workflow and ownership problem, not a technology problem, and it is a common one. Buying another system on top would not have fixed it.

What this means in practice

You do not need a visible crisis to justify looking at how the business actually operates. The more useful question is simpler: does work move through the business as smoothly as its size and ambitions require, or has growth quietly outpaced the ways of working that got you here?

Answering that well means looking across the business rather than at one department in isolation, being honest about where effort is going, and being willing to change a habit that has simply outlived its usefulness. That is the starting point for any operational improvement, whether or not there is an obvious problem to point to yet.