Every company runs on an operating system. Most never designed theirs.
Introducing the Requisite Operating System (ROS)
Your phone runs on an operating system you never think about — until it slows down, drops calls, or refuses an update. The operating system is the invisible architecture that decides how everything else works. You only notice it when it stops serving you.
Every company runs on one too. Not software — the real operating system of a business is the way work actually gets assigned, decisions actually get made, priorities actually get set, and people actually get led. Most founders never sat down and designed theirs. It accreted, one workaround at a time, out of the founder’s instincts and the team’s shared history. For a while, that works beautifully.
I’m writing from experience. I used these principles to turn around a multinational specialty-chemical company — about half a billion dollars in revenue — that I led as president and CEO, and I’ve spent the years since helping founders build the same thing into their own companies.
The strain every growing company hits
As a company scales, complexity multiplies. Decisions pile up, coordination gets harder, and the informal habits that carried the early years begin to strain. What once ran on personal effort and tribal knowledge no longer holds.
Most leaders feel this as friction before they can name it. They work harder and feel less effective. Managers get overloaded. The best people quietly become shock absorbers, compensating for a structure that no longer fits. Employees grow frustrated by unclear priorities and decisions that seem to change with the weather. In response, companies often reach for control — more process, more oversight — and accidentally trade away the trust and speed that made them good in the first place. Performance may tick up briefly. It rarely lasts.
The instinct here is to hunt for the missing fix — the one hire, the one tool, the one policy. But most struggling companies aren’t missing a single fix. They’re missing an integrated system.
What “requisite” means
This is where the word requisite earns its place. A Requisite Operating System (ROS) is not just an operating system — it is the operating system a particular organization actually requires in order to work at its best.
Requisite carries two meanings at once: what is necessary, and what is fitting. The ROS is the architecture that fits the work the company is trying to do — sized to its complexity, its stage, and its people. Anything less leaves the organization compensating for the gap. Anything more buries it in bureaucracy. The goal is the right system, properly sized and properly maintained: the ideal operating system for this company, at this stage of its life.
The word isn’t chosen casually. It comes from Requisite Organization, the body of management science developed by Elliott Jaques over more than five decades of research. Jaques found that healthy organizations aren’t held together by personality or charisma alone. They’re held together by fit — the right number of management layers, roles sized to the right level of work, authority matched to accountability, and people whose capability fits the complexity of what they’re asked to do. When those conditions are met, an organization becomes requisite, rightly arranged for the work at hand. When they’re not, no amount of effort, training, or culture work fully compensates.
An operating system — but a living one
This is where the software metaphor reaches its limit — and where the most important part of the idea lives. A phone’s operating system is a machine. A company is not. It is a living system of people, relationships, and judgment — closer to a body than a device. So a Requisite Operating System is engineered with real rigor, but built for something alive: the discipline of an operating system, fitted to the reality of a living organization. That fusion is the whole point — it’s why the seven components have to stay in balance the way the systems of a body do, and why the seventh, how people are led, carries as much weight as the other six.
Seven components, one system
A Requisite Operating System has seven interlocking components:
- Mission, values, and culture
- Strategies and goals
- Accountability and structure
- Meeting cadences and communications
- Metrics and dashboards
- Systems and processes
- Principles and behaviors
They’re designed to work together, and this is the part most frameworks miss: strength in one component cannot compensate for neglect in another. Weak structure shows up as overworked managers. Broken communication shows up as rework and confusion. Thin processes show up as constant firefighting. The pain almost always surfaces somewhere other than its source, the way strain in one part of a body shows up in another — which is exactly why treating symptoms brings only temporary relief. Lasting health comes from strengthening the underlying system and keeping its parts in balance.
| Layer | Component | Purpose | Key question it answers |
| Direction & meaning | Mission, values, & culture | Why we exist, what we stand for, how we behave | Why do we do this work, and how should it feel to work here? |
| Strategies & goals | Long-term direction and near-term priorities | Where are we going, and what matters most right now? | |
| Execution & integration | Accountability & structure | Roles, levels of work, and ownership | Who is accountable for what, and at what level? |
| Meeting cadences & communications | Integrates work, decisions, and people | How do we align, decide, and stay coordinated? | |
| Metrics & dashboards | Level-appropriate data for decisions | How do we know if we’re winning — or drifting? | |
| Enablers & reinforcement | Systems & processes | Consistent, scalable execution | How does work reliably get done end-to-end? |
| Principles & behaviors (RMS) | How leaders lead and grow others | How are leaders expected to think, act, and develop their people? |
The seventh component is different
Six of the components are things you build. The seventh — principles and behaviors — is different. It’s how people lead and treat one another while building the other six. It isn’t a box on the org chart; it’s a thread that runs through all seven.
We call this component the Redemptive Management System (RMS). “Redemptive” is a deliberate word, and a precise one: to recover something and restore it to its proper purpose. Every organization drifts. Roles blur, accountability slips, good people end up misplaced. The manager’s real job is to notice where the system has drifted out of fit and to restore it — one correction at a time.
This isn’t the “soft” part of the framework. It’s the same science as the rest of it. The discipline of leading people well — clear expectations, fair authority, honest accountability, the right person in the right role — is what actually protects them. Which points to the conviction underneath the whole system: high performance and human flourishing are not a trade-off. A growing company doesn’t have to choose between results and people. It needs a system deliberately built to serve both.
Does it actually work?
When I took over that specialty-chemical business, it had grown 0.2% in seven years. We started by getting the strategy right, then rebuilt the structure to fit it — matching the complexity of each role to the capability of the person in it, and making sure each strategy was handed to the level of the organization that could actually execute it.
We didn’t do it by hiring and firing; we did it by repositioning the talent already there, and no one was terminated. Growth reached double digits in the first year and stayed there for more than five years, with an 11% sales increase across three market segments and a 22% rise in profit, in an industry where 5% is a good year. The only interruption came when the 2008 financial crisis slipped growth to 6%, before it climbed back to double digits the next year.
In the years since, I’ve watched the same approach produce the same kind of results in companies that look nothing alike — a startup, a growth-stage firm, a scaling mid-market business — across different regions, languages, and cultures. The same operating system, fitted each time to the company in front of it.
The same operating system, proven across sizes, sectors, and regions.
Built to scale — by design
Most operating systems for growing companies do real good and then hit a ceiling. They bring cadence, scorecards, and discipline, and they work well up to a point — but with no account of levels of work, layers end up misaligned, accountability outruns authority, and once again the best people are left compensating for the gap.
The Requisite Operating System is built to scale from the start, because you install it in stages. You don’t rip out what’s already working and replace it wholesale. You begin with mission, values, culture, and strategy, and add the remaining components as the business grows into them. Progress matters more than perfection; the system strengthens month by month as you apply, review, and refine it. You grow into an operating system built to scale — you don’t outgrow it.
That’s the difference between a business that runs on heroic effort and one that runs on a system requisite to the work, the people, and the moment: intentional rather than reactive, accountable rather than chaotic, and demanding in a way that strengthens its people rather than depleting them.
Comments are closed