A system is just a set of things that work together to produce a result. Every business is made of them. The trouble is that half of them are invisible, and that half is where the real problems live.
The situation
A founder called me about a contract-manufacturing business doing about ฿140M a year. Forty staff. Healthy order book. He could describe his sales process, his production schedule, and his Monday operations meeting in clean detail. On paper the company looked well run.
But he was working twelve-hour days and could not say why. Every time we traced a delay or a dropped ball, it led back to a decision that had quietly routed through him. He was not slow. He was the single point every important thing passed through, and he had never noticed because none of it was written down.
The first read
When I read a business, I separate what it can describe from what it actually runs on. The first question is never "is this a good process." It is "where does this decision really get made, and who has to be in the room for it to happen."
In his company, the describable systems were fine. The invisible ones were the problem. The way a price got approved, the way a production exception got resolved, the way a new hire learned who to ask: none of it existed on paper. It existed in his head. So the company could not run a day without his head in it.
The frame: two systems
When I say "systems," I mean both kinds. An owner who keeps getting pulled into decisions he should be delegating is not failing at delegation. He is operating inside an invisible system where delegation does not work yet. The intention loses to the structure every time.
The working
We spent two weeks writing the invisible system down. Not inventing new process, just making the existing one legible: who decides a price, inside what band, and when it has to come up to him. Who owns a production exception. What a new buyer needs to know in week one. The change was small in effort and large in effect.
| Before | After | |
|---|---|---|
| Price approvals routed through owner | All of them | Above ฿200K only |
| Decisions that needed him in the room | Most | A handful |
| New buyer time to independence | ~5 months | ~6 weeks |
| Owner hours per week | ~60 | ~45 |
Nobody worked harder. The work that used to require him simply stopped requiring him, because the system around the work could now hold it.
Why I talk about systems so much
Not because it is a consulting habit. Because almost every business problem I have seen, traced far enough, is a systems problem. The product is rarely the issue. The team is rarely the issue. The system those people are operating inside is the issue. When the system changes, behavior changes, without anyone having to try harder.
Change the system and behavior usually follows. That is most of the job.
What I do is diagnose both layers, then build a describable system that can slowly absorb the invisible one. That is what I mean by systems.