Diagnose before you fix

Why off-the-peg operating systems don’t fit every business.

Off-the-peg operating systems like EOS and Scaling Up work well in businesses that already have what they assume – a settled leadership team, clear roles and room for a steady rhythm. Where those foundations aren’t there yet, the framework can drift within a quarter. Mallard’s view is to diagnose first, then borrow only what fits.

By Simon Wakeman, Principal Consultant & Fractional COO
· 4 minute read

You might know the pattern. You paid for the EOS implementer, or bought everyone a copy of Scaling Up. You ran it religiously for a quarter. The meetings felt sharper, the priorities clearer. Then a big client issue landed, the weekly meeting got pushed, then skipped. By the following quarter nobody mentioned it.

If that happened to you, it probably wasn’t a failure of effort or belief, and it’s worth understanding why before you reach for the next framework.

They’re the two best-known operating frameworks for growing businesses, and they’re popular because they give founders something concrete when everything feels messy.

EOS, the Entrepreneurial Operating System, was created by Gino Wickman and set out in his book Traction. It gives a leadership team a small set of tools. There’s a one-page vision and plan, an Accountability Chart and a weekly Scorecard. There are quarterly priorities called rocks, and a weekly Level 10 Meeting for solving issues.

Scaling Up comes from Verne Harnish, who also founded EO, the global peer network for entrepreneurs. His book Scaling Up is subtitled “Rockefeller Habits 2.0”, and the methodology is built around four decisions every growing company has to get right: people, strategy, execution and cash. It leans on one-page tools such as the One-Page Strategic Plan.

Both offer a shared language, a regular rhythm and a way of making priorities visible. Those are real benefits. For a leadership team that has never had any of them, that alone can feel like a breakthrough for a while.

When do off-the-peg frameworks work well?

When the business already looks roughly like the one the framework assumes. In practice that usually means:

  • A settled leadership team. People in clear seats, each owning a function.
  • A founder ready to step back from running the day to day and let others integrate the business.
  • Enough stability to protect the rhythm. A weekly meeting and a quarterly planning cycle that survive a busy month.

If that describes your business, a well-run EOS or Scaling Up implementation can add a lot of discipline. Plenty of founders run them for years and wouldn’t go back. This isn’t an argument against either one.

Why does it fade after a quarter?

Because in many founder-led scale-ups of roughly 15–75 people, those foundations aren’t there yet. Roles have grown up around people rather than being designed. Decisions still route through the founder, however much they’d like them not to. Knowledge lives in a few heads.

Drop a framework on top of that and a familiar sequence follows. The first quarter goes brilliantly, because the shared language and fresh structure release a lot of pent-up clarity. Then real life arrives. Rocks need owners who can actually decide, but they can’t without checking with the founder. Scorecards need clean numbers, but the data lives in five tools. The weekly meeting needs protecting, but the founder is pulled into a client fire and misses two in a row.

One by one the practices start to feel like extra work on top of the real work. People go through the motions. Then they quietly stop.

The framework didn’t fail, exactly. The operating system underneath it wasn’t ready to carry it. New practices grafted onto unchanged decision-making tend to fade, especially once the person championing them gets busy.

A common response is to blame the framework and look for a better one. That’s understandable. It’s also how a business cycles through three methodologies in three years and keeps the same underlying problems.

What does a tailored operating system look like?

Think of the difference between off-the-peg and a tailored suit. Off-the-peg is cut for an average body. It fits some people perfectly and most people roughly. A tailored suit starts with measurements.

A business operating system is how your people, practices and technology work together as an integrated whole. A tailored one starts from how your business wins and delivers work, what your team can do today and where you are in your growth. It can happily borrow rocks, a scorecard or a one-page plan. The difference is that you choose them because they fit, not because they came in the box.

It also means building the minimum that works and then stopping. A scorecard with fifteen metrics and eight priorities per person adds overhead rather than clarity. A short list of numbers the leadership team genuinely looks at each week will do more.

What should you do with the framework you’ve got?

Whether it faded or you’re about to start one, don’t throw it out or double down yet. Start here:

  1. Keep what survived. One or two pieces, often the issues list or the shared vocabulary, usually outlast the rest. They’re worth keeping.
  2. Check the foundations. Are roles clear enough that each priority has an owner who can decide without you? If not, that’s the first job, ahead of any framework.
  3. Look at who skipped it, and when. If the rhythm died in a busy month, or the leadership team treated meetings as optional, that tells you what needs to change for anything to stick.
  4. Cut it back. Strip the system to the few practices that genuinely help, then run those consistently for a quarter before adding anything.

Where do you start if off-the-peg hasn’t worked?

With an honest picture of the business as it is today, before choosing any solution. The guide to working out what’s really holding your business back walks through how to do that yourself.

That’s also why Mallard starts every engagement with diagnosis rather than a template. The Find diagnostic measures your business across people, practices and technology over 14 days, so whatever you build next – borrowed, tailored or both – is cut to fit.

Some commonly asked questions from founders…

Is EOS a bad system?

No. EOS, created by Gino Wickman and set out in his book Traction, is a practical, well-tested system. It offers simple tools for priorities and accountability, a common vocabulary and a steady weekly and quarterly cadence. Plenty of businesses run it well for years. Like any framework, it works best when certain foundations are already in place.

When do EOS and Scaling Up work well?

They tend to work best when the leadership team is settled, roles are reasonably clear, the founder is ready to step back from running the day to day and the business is stable enough to protect a weekly meeting and a quarterly planning cycle. In that setting the structure adds discipline rather than overhead.

Why did our EOS rhythm fade after a quarter?

Usually because the framework was sitting on foundations that weren’t ready. Rocks need owners who can actually decide. Weekly meetings need a business calm enough to protect them. When roles are blurred and decisions still route through the founder, the practices start to feel like extra work and quietly stop.

What’s the difference between EOS and Scaling Up?

Both give a growing business a structured operating rhythm. EOS centres on a small set of simple tools, such as rocks, a scorecard and the weekly Level 10 Meeting. Scaling Up, from Verne Harnish, is organised around four decisions – people, strategy, execution and cash – with one-page planning tools.

Should we drop EOS if it isn’t working?

Not necessarily. Work out why it isn’t working first. Often the useful parts, like a shared language or a weekly issues list, are worth keeping while you fix the foundations underneath. Dropping it without that diagnosis usually means repeating the same pattern with the next framework.

What does a tailored business operating system mean?

It means designing how your people, practices and technology work together around the way your business wins and delivers work, rather than adopting someone else’s template. It can borrow tools from EOS or Scaling Up, but only the ones that fit your stage, your team and your way of working.

How is Mallard’s approach different from EOS or Scaling Up?

Mallard doesn’t hand over a framework. It starts with a diagnosis of the business as it really is, then builds operating logic specific to that business, alongside the team. EOS and Scaling Up suit some businesses well. Mallard is for founders whose business needs something cut to fit.

Stop being a bottleneck in your own business

Book your free 30 minute
founder review call