1 | A company's operating system: a practical model for scaling organizations

Thomas Vonwil

11 Jan 2026 • 5 min read

When companies scale, founders and builders often share a similar frustration: teams grow, but not much more gets done. What used to be simple and fast starts to slow down. Decisions take longer. Priorities blur. Coordination overhead rises.

We will explore why this happens in more detail in the next post. Here the short version for now: as your company grows, its operating system starts to show its limits.

Every company has an operating system, either by design or by accident. It determines how work gets done: how people coordinate, make decisions, and turn effort into results. If the operating system is strong, the organization can scale with focus, ownership, and speed. Teams stay in control, proactive, and aligned, instead of slipping into reactive firefighting.

Scaling without descending into chaos or bureaucracy sounds useful to many. Fewer connect that ambition to deliberately shaping the organization's operating system. But if it is not shaped deliberately, it will emerge by accident: through habits, personalities, and local optimizations. That can work early on, but scaling magnifies weaknesses. Few things derail a growing organization more reliably than a weak operating system.

I believe that if leadership teams treated the operating system with the same discipline that Finance applies to the P&L or Sales to the funnel, companies would run far more effectively. People would also enjoy working in them much more.

How to build a strong operating system (and keep it strong as your company grows) is the core of this blog.

What a company's operating system is

First, what a company's operating system is not: it is not software. This is not about your ERP or CRM. This is also not just about your org chart.

A company's operating system is what converts its aspiration into results. It is the set of elements that determine whether your organization can actually do what it sets out to do.

"A system is an interconnected set of elements that is coherently organized in a way that achieves something." – Donella Meadows

People use different terms (e.g. management system, operating model) and emphasize different elements (e.g. culture, strategy, structure, processes), but they all share common themes. And while I mostly write about "the company" here, the same principles apply at any level: business units, functions, and teams. That is because a good operating system is fractal. You can start from wherever you are today.

Several models describe how organizations get work done (some linked in "further reading" below). However, when we looked for a model to apply in practice at u-blox (the Swiss tech company I work for), none fit our needs well enough as-is. We therefore adapted and combined existing ideas into our own operating system framework. Below you see it in its most condensed form.

A strong operating system enables you to aim high and move fast

These six elements cover what matters to describe and shape how your organization gets work done – complete enough that nothing important gets missed, and coherent enough that the elements reinforce rather than work against each other. Much of what an operating system actually does emerges from the interactions between elements. But to better understand those interactions, we need to start with the elements themselves.

The top three help you aim high: the right people, a clear strategic direction, and focus on what matters most. The bottom three help you move fast: clear roles and decision-making, effective processes, and the right data and tools.

Over time, this blog will dive into each of these elements in detail, but as a start, here the summary:

People: The values and behaviors that underpin your culture, and the talent system that determines who you work with. When this is weak, culture becomes whatever the loudest people make it, hiring is inconsistent, and your best performers quietly leave.
Strategy: An integrated set of choices (including where to play and how to win) that compels desired customer action (Roger Martin's definition). When this is weak, every opportunity looks attractive, teams pull in different directions, and "how we win" gets answered differently depending on who you ask.
Priorities: Your mid-term direction (guardrails and roadmap), your most important short-term measures (KPIs) and goals (e.g. OKRs), and your capacity allocation. When this is weak, everything feels urgent, capacity is chronically over-committed, and KPIs may (or may not) appear in reports but do not steer work.
Structure: How you organize people (org, roles, workplace), information (decision-making, information flow), and time (operating rhythm). When this is weak, ownership blurs, decision-making slows down, and the same issues get re-litigated meeting after meeting.
Processes & initiatives: How you organize both the repeatable work that delivers value today ("run") and the improvement work that builds tomorrow ("change"). When this is weak, repeatable work gets reinvented every time, change initiatives pile up without finishing and creating value.
Information technology: The data, applications, and infrastructure that underpin your organization. If this is weak, people cannot find what they need, data contradicts itself across tools, and the tech stack slows the organization down instead of helping it move.

Why this becomes important once you grow

In small teams, you can get away without thinking much about the operating system. Everyone knows each other, often sits close, and roughly knows what is going on. But once you move beyond a few dozen people, this stops working. Priorities (and narratives) diverge, ownership blurs, and informal coordination breaks down.

That is the point where deliberately investing time and effort into your operating system becomes critical. Many companies miss it. And when they do, they do not just become slower and less effective, they also build up organizational debt.

Like technical debt, organizational debt makes everything built on top of it harder and more expensive. And like financial debt, it compounds: the longer you wait to address it, the more you have to repay, and the more of your future capacity goes to servicing the debt rather than creating new value.

Why I care about this

I remember my struggle 10 years ago as a freshly minted COO of a scale-up. We were around 70 people back then and I was living with the constant feeling that things were somehow slipping through our fingers. That we were not really in control. That we were constantly pushed into reactive mode, even for things that should not have come as surprises at all.

As much as I loved this job, I hated that feeling. It stressed me out. It robbed me of sleep. And I knew this issue stopped us from living up to our full potential.

I want this to become the blog I wish I had back then: something that provides structure and practical explanations for how to organize a company in the middle of scaling. How to regain control, stay on track, and increase speed. If you are building an organization and want it to scale without descending into chaos or bureaucracy, I hope this blog will be useful to you.

What comes next

This post is the starting point: outlining what a company's operating system is, why every organization already has one, and why it is worth working on deliberately.

In the next post, I look at why scaling organizations develop what Alex Komoroske calls the coordination headwind – why growth so often leads to complexity, slowness, and the loss of start-up mojo – and why deliberately shaping your operating system can make a big difference.

Because scaling is not just about more revenue, customers, or products. It is also about ensuring that the systems underpinning your organization can keep growing with you.

What a company's operating system is

Why this becomes important once you grow

Why I care about this

What comes next

Further reading