Your Company Already Has an Operating System - The Well-Run Company Series/Article 1 of 9

During a turnaround at a company I was running, I started asking the leadership team a question that made everyone uncomfortable: describe how this company actually runs. Not the org chart. Not the product line. The system. How does a decision get made here? How does a priority get set? How does someone two levels down find out what matters this quarter? Who checks whether the thing we agreed on last month actually happened?

The room went quiet. These were smart, experienced people who could tell you everything about their customers, their equipment, and their margins. But nobody could describe how the company actually ran. They had never been asked to.

Since that turnaround, I have asked the same question inside companies that brought me in to help, and I have listened to owners struggle with it in peer advisory rooms for more than eight years. The answer is rarely clear.

Every company runs on a system

Every company already has an operating system. Yours does too. There is some way decisions get made, some way meetings happen, some way priorities get set, some way information travels, and some way people are or are not held to what they committed to. Those mechanisms exist in your business right now, this week, whether anyone wrote them down or not.

The question worth asking is who designed it. In most small and midsized companies, the honest answer is nobody. The system grew up on its own. It came from how the founder liked to work in the early years, got patched by whoever ran operations next, and bent around whoever pushes hardest today. Workarounds hardened into standard practice because nobody ever went back and looked at them.

I have written before that the outcomes you are seeing are the results your system is designed to produce. Nobody intended most of that design, and that is exactly the problem. The sentence tends to land hard with owners, because it removes the comfortable explanations. If the same problems keep coming back, they are output. The system is producing exactly what it is built to produce, with remarkable consistency, however good the people are and however the luck runs.

What an accreted system costs you

A system nobody designed still has costs. Meetings end without decisions, so the same topic comes back next week and the week after. Priorities get set by whoever spoke last or loudest, so the company quietly works on nine things and finishes none. Information moves by hallway conversation, so the people doing the work find out about the plan after it has already changed. Commitments evaporate because there is no point in the week where anyone checks.

None of that announces itself as a system failure. It shows up as an overwhelmed manager, a quarter that slipped, a customer who left, a good employee who quit without much of an explanation. So owners address what they can see. They replace the manager, push the team harder, or discount to win the customer back. But unless the underlying system changes, the same problems return.

What a designed system looks like

A designed operating system is not complicated, and it does not require a binder on a shelf. In every well-run company I have been part of or worked alongside, it comes down to a handful of mechanisms, each built on purpose.

Decisions have a place to happen and a person who owns them. Priorities are few, named, and chosen deliberately each quarter, so the whole leadership team can recite them without checking. There is a weekly rhythm where the team looks at real numbers, surfaces real issues, and leaves with decisions and owners. Information moves by design, so people hear what matters from their leaders before the rumor mill gets to it. And accountability is built into the calendar. There is a moment every week when commitments come back around, which means follow-through stops depending on anyone's memory or mood.

When those mechanisms exist, something changes that is hard to overstate. The business stops depending on the owner being in every room. Problems surface earlier, while they are still cheap. And the leadership team starts operating like a team running a company rather than a group of department heads defending territory.

Where to start

Redesigning the company comes later. The first step is seeing the system you already have. Describe it honestly, out loud, with your leadership team in the room. It costs nothing, and it requires no software and no reorganization. How does a decision actually get made here? How does a priority actually get set? How would we know if a commitment slipped? Write the real answers down, including the embarrassing ones. Especially the embarrassing ones.

That description is the finding. Most teams discover they cannot agree on the answers, which tells you the system lives in fragments inside individual heads. Others can describe it fine and do not like what they hear. Either way, you now know what you are working with, and you can start designing on purpose what has been running on its own for years.

Over the coming months I am going to walk through the pieces of that design one at a time: the environment leadership provides, ownership and accountability, the operating rhythm, what to measure, how to set direction, the financial levers every leadership team should know, and how to pressure-test big initiatives before you fund them.

Each piece stands on its own. Together they describe how a well-run company actually runs.

What I know about this comes from companies I ran, companies I was brought into as an advisor, and years of sitting with other owners while they worked on the same problems. The stories in this series come from all three, blended enough that no single company is on display. If this describes where your company is stuck, begin with the questions above. Get the real operating system out of people's heads and onto the table. Once you can see it clearly, you can redesign it on purpose.

And if an outside perspective would help your leadership team have that conversation, my door is open.