No System Is a System

The most common operating model in business has no name, no owner, and no design document. It is the one you built by habit, and it is the one you might be running right now.

Samuel Koh · 2 October 2026

It's all about the people. Our culture. Our values. That line opens most strategy decks and most honest conversations about why performance is slipping. It feels like a diagnosis. It usually isn't.

Every organisation already runs a system. The question is not whether one exists, but whether anyone has mapped it or taken responsibility for how it behaves. Usually nobody has. The system is there, doing the work and producing the results. Nobody drew the diagram.

The system with no name

What most organisations operate is best described as "no system." Not a broken system. Not a legacy system. A system that formed the way sediment forms: layer by layer, decision by decision, habit by habit. The workaround that saved the deadline became the procedure. The exception granted to one team became the expectation of three. The meeting that was supposed to be one‑off is now the Tuesday that nobody questions.

The absence of a design document does not mean the absence of a design.

The moment a habit forms, a system forms with it. That's not a metaphor. A system is any set of parts that work together and produce the same pattern of behaviour over time. If the same three people keep settling the same argument the same way, that's a system. If the same report goes out every month with the same gaps, that's a system. The design was simply made bit by bit, by everyone, with no shared record.

You are the system

The producers, the managers, the directors in the room are not outside the system. They are operating it. Every decision made under time pressure, every shortcut that became normal, every conflict settled by putting it off rather than sorting it out, added another piece. They built the system the way you build a language: by using it, without a grammar book.

Paul Taylor, writing about the people-versus-system debate, cites W. Edwards Deming's claim that 95% of variation in a system's performance, the swing between a good result and a poor one, is caused by the system itself, with only 5% down to the individuals within it. Taylor questions how precise that number is, noting that where staff change dramatically, people can account for more than that. But he accepts the core point: "the system always wins." The system shapes behaviour more than behaviour shapes the system.

If you don't map it, you own it.

— Author

That leaves a gap in accountability. When results disappoint, the instinct is to look outside the structure for the cause: a bad hire, a weak leader, a shift in the market. But if the structure is just the habits of the people in the room, piled up over time, the cause sits inside, spread across everyone. No one person can be held responsible, because no one person made the decision. Everyone did. That is what makes "no system" so hard to shift. Swapping out a person will not fix it. Nor will a new framework. It has to be made visible first.

The companies that made it visible

Nine of the most valuable companies in the world are technology companies, and they are built system-first in a very literal sense. They run on a large inventory of systems that are written down: who gets to decide what, how feedback travels, what happens when something fails, how data moves, who a problem goes to next. Each one has an owner. When something breaks, there is a name for the process that failed, a person accountable for it, and a record of what changed.

The gap between these organisations and the rest is a question of visibility and ownership, not talent or ambition. The tech giants built a larger set of systems and gave each one an owner. The rest of the market is running the same habits, the same workarounds, the same unexamined Tuesday meetings, and calling it culture.

The question that matters

So which system are you running, and who owns it? The honest answer is often "all of us and none of us," because no one set it up on purpose. Mapping it is the first act of design. You can't redesign what you can't see.

"No system" isn't something that happens to you. It's a choice made thousands of times by people who thought they were just getting the work done. The work is done and the system is running. What's left is for the people operating it to map it, own it, and change it.