An owner arrives saying he has a money problem. The bank balance drops, payments get tight, and the conversation begins and ends in accounting. Expenses get reviewed, something gets cut, a payment term gets renegotiated. Three months later the balance drops again.
It was never a money problem. It was a collections problem nobody called by that name, because collections doesn't appear in any financial statement as a function. It appears as a number that has already gone wrong.
The symptom talks, the cause stays quiet
This isn't a metaphor. It's a property of how systems behave. Money is the last layer of a business: everything that happens before it — what you sell, to whom, at what margin, through what process, with which people — eventually drains into it. That makes money an excellent detector and a terrible diagnosis. It tells you something is wrong somewhere. It does not tell you where.
The same holds for almost every visible pain in a company. People leaving is rarely a people problem; it's usually expectations set badly at hiring, or a supervisor nobody ever trained to supervise. Late deliverables are rarely an operations problem; they're a salesperson promising dates nobody validated with the team that has to meet them. Software nobody uses isn't a technology problem; it's a process that was never designed and was bought ready-made instead.
In every case, the department where it hurts is the one taking the hit, not the one causing it.
Why instinct goes to the wrong place
When something hurts, attention goes to the pain. That reflex is healthy in a body and expensive in a company, because the area where the symptom shows up is also the one least able to fix it. Asking finance to solve a collections problem is asking it to correct, a month late and without authority, decisions that were made in sales.
There's a second reason, less comfortable. Looking where it hurts is easier than looking where the decision was made. A late payment gets fixed with a phone call; the commercial policy that produced it gets fixed by having a conversation with someone who has been selling that way for years. We almost always pick the work that doesn't create friction.
What to do instead
Before acting on a symptom, three questions are worth asking, in this order.
First: is this an event or a pattern? One client paying late is an event. Thirty percent of your receivables paying late is a pattern, and patterns don't get fixed one at a time. It's worth looking at twelve months before concluding anything, because a bad month can be bad luck and a bad year is always a design.
Second: who made the decision that made this possible? Not who executed — who decided. Someone set the payment terms. Someone set the client profile. Someone set the pricing structure, or worse, nobody did and it was inherited. That person and that moment are the real site of the intervention.
Third: if this gets fixed, what else changes? A business is a connected system, and that cuts both ways. Tightening collections can recover cash and drive off the three clients who carry the year. Raising prices can fix the margin and break operations if the team can't sustain the service level the new price promises. Isolated decisions produce local improvements and general damage.
The starting point isn't a to-do list
The temptation after reading this is to make a list of everything that needs reviewing. That list exists in almost every company and almost never gets executed, because a list without hierarchy is indistinguishable from noise.
What orders the list isn't urgency. It's understanding how the seven parts of the business — finance, strategy, leadership, operations, people, technology and growth — are connected, and which one is constraining the rest. There is almost always one. And it is almost never the one that hurts.
That is exactly what Business 360 does: look at all seven at once, not to hand you a grade, but to tell you where to start when everything looks urgent.