Most companies are drawn as boxes.
Marketing. Sales. Product. Operations. Finance. Support.
The boxes are useful. They tell you who sits where, who reports to whom, which budget pays for which work.
They do not tell you how the business actually moves.
A customer does not experience a box. They experience a sequence: they hear about you, they try to understand you, they buy or they leave, they get what they paid for, they tell you what happened — or they go quiet.
That sequence is the business. The boxes are labels we put on parts of it.
What a system is
A system is not a collection of parts. It is parts plus the relationships between them.
Something arrives. Something is done with it. Something leaves. Something comes back. The next round is different — or it isn’t, which is also information.
That is the whole idea, said slowly:
If nothing comes back, you still have activity. You do not have a system that can get better at working.
If something comes back and nothing changes, you have a loop with a broken last step. The company is busy. It is not learning.
Diagram · Two pictures of the same company
The org chart
Names, reporting lines, departments. Useful for people. Silent about flow.
The system
What enters, what happens, what leaves, what returns, what improves. This is the business.
You can have a clean chart and a messy system. Customers only meet the second one.
Departments are not the problem
I am not arguing for a company with no roles.
Someone has to own brand. Someone has to own delivery. Specialists exist because depth is real.
The mistake is treating the department as the unit of truth.
Marketing can “hit its number” while sales inherits leads that cannot convert. Product can ship while support drowns. Finance can close the books while nobody knows which offer actually pays.
Each box can look healthy. The system can still be sick — because the sickness lives in the handoff, not in the box.
Interactive · Two ways to see a company
Ask: who owns this? The answer is a name and a team. Useful on Monday morning. Incomplete by Friday, when the customer has crossed three teams and none of them saw the whole trip.
Ask: what arrived, what did we do, what left, what came back, what will we do differently? The answer is a loop. Now you can find the constraint — which is usually a connection, not a person.
You already run loops. Most of them are accidental
A founder who jumps on every WhatsApp is closing a loop by hand.
A salesperson who hears the same objection ten times and never feeds it back to the page is running a process with no improvement step.
A support inbox full of the same question is feedback. If the product or the website never changes, that feedback is being thrown away.
The work of this book is to make those loops visible, then deliberate.
Once you can see input → process → output → feedback → improvement, you can look at any function — strategy, brand, sales, finance, AI — and ask the same five questions.
That is how a modern business should be designed. Not as a stack of departments that occasionally meet. As a system that learns.