The CoreOS method
What is a business operating system?
Last updated 5 July 2026 · Reviewed by Nick Thorpe
The short answer
A business operating system is the repeating rhythm a business runs on: clear goals, a small set of numbers reviewed weekly, regular meetings with fixed agendas, named accountability for every result, and documented systems for the work that repeats. Without one, the business runs on the owner's memory and effort instead.
What does a business operating system actually mean?
A business operating system is the set of repeating routines a business uses to decide what matters, measure whether it is happening, and fix it when it is not. It is a rhythm rather than a document. Write it down by all means, but it only counts as an operating system once it runs every week.
It has five working parts:
| Part | What it is | The question it answers |
|---|---|---|
| Goals | A short list of priorities for the quarter and the year, written down and visible | What are we actually trying to do? |
| Numbers | A weekly scoreboard of the handful of figures that show business health | Is it working? |
| Meetings | A fixed cadence with fixed agendas, weekly and quarterly | When do we look up from the work? |
| Accountability | One named owner for every goal and every number | Who is on the hook? |
| Systems | Documented ways of doing the work that repeats | How do we do it the same way twice? |
None of these parts is exotic. The value is in running all five together, every week, whether or not anyone feels like it.
Why do owner-led businesses drift without one?
Because without an operating system, the owner is the operating system. Priorities live in one head. Standards live in one head. Every decision routes through one person, so the business moves at the speed of that person’s diary.
Drift follows a predictable pattern. Goals set in January that nobody can recite by March. Numbers checked when cash feels tight instead of every week. Meetings called when something breaks. A team working hard on whatever seems loudest that day. None of that is laziness. It is simply what happens by default when no structure is doing the remembering.
| Running on the owner | Running on an operating system |
|---|---|
| Priorities live in the owner’s head | Priorities are written, visible and reviewed |
| Numbers get checked when something feels wrong | A fixed scoreboard is reviewed every week |
| Meetings happen when there is a crisis | Same meeting, same day, same agenda |
| The owner chases everything | Every result has a named owner |
| A holiday means the phone never stops | The rhythm holds while the owner is away |
Which business operating systems have names?
The best known internationally is EOS, the Entrepreneurial Operating System, set out in Gino Wickman’s book Traction and delivered through licensed implementers. In the UK, CoreOS is the operating framework Nick Thorpe built for his own companies and now applies with coaching clients: strategy, accountability, mindset and systems. If you want the two side by side, read CoreOS vs EOS.
Plenty of owners also assemble their own version from books and trial and error. That works, provided somebody holds the rhythm when it gets inconvenient.
What does a working operating system look like week to week?
In a normal week it is short, repetitive and slightly boring, which is the point. A typical cycle runs like this:
- The scoreboard lands on the same day each week: a handful of numbers, each with an owner, each marked on or off track.
- The leadership team meets at a fixed time with a fixed agenda: numbers first, then last week’s actions, then the biggest issues.
- Every off-track number leaves the meeting with a named action and a named owner.
- Issues that cannot be solved in the meeting go on a list, get ranked, and get taken in order.
- Once a quarter, the team steps back for a longer session: goals reset, scoreboard pruned, systems reviewed.
The test is your absence. If the rhythm holds for a fortnight while you are away, you have an operating system. If it stops the day you leave, you were the operating system. Accountability is what keeps the whole loop honest, and there is a longer piece on that in why accountability is still the only strategy that works.
Do you need one?
If your business is established, has a team, and still cannot run for two weeks without you, yes. If you are pre-revenue, or a one-person business with no plan to build a team, a full operating system is more machinery than you need. A simple weekly review will serve you better.
The quickest way to see where you stand is the CoreOS Scorecard: 12 questions, an instant score, free. If the score stings and you want the rhythm installed with someone holding you to it, that is the work Momentum was built for.
Nick Thorpe
16 years a British Army officer, then a decade building his own companies. Coaches business owners on the CoreOS framework. The story.