I’ve been seeing a trend lately that I want to address directly.

More and more articles are popping up with takes like “EOS is too rigid,” “the 10-year vision is unrealistic,” and “AI has made operating systems obsolete.” Some of these are written by people who’ve never implemented EOS. Others are written by people who tried it once and moved on.

I get it. It’s a compelling narrative. Frameworks are an easy target, and nuance doesn’t get clicks.

But here’s what these takes almost always get wrong: they’re critiquing EOS the way it was misimplemented, not the way it actually works when a committed team runs it with discipline.

Let’s be honest about what “EOS didn’t work for us” usually means.

It usually means one of three things:

  1. The leadership team never fully committed. They liked the vocabulary but not the discipline.
  2. It was rolled out as a top-down mandate without genuine buy-in from the leadership team.
  3. They implemented it themselves using the book and a YouTube video, hit a wall, and called it a framework problem.

EOS isn’t complicated. But it is demanding. It requires a leadership team that’s willing to be honest with each other, show up consistently, and do the work between meetings — not just during them.

The criticism I take most seriously: EOS doesn’t integrate well with modern technology.

That one has some truth to it.

EOS One — the official software from EOS Worldwide — has gotten better. But the tools themselves (Scorecard, V/TO, Accountability Chart, Issues List) were designed to be simple and analog on purpose. That simplicity is a feature — but it also means that companies running EOS often find themselves toggling between spreadsheets, project management tools, and meeting software to actually execute.

Where I’ve seen this play out practically: companies that run their Scorecard in a spreadsheet, track Rocks in whatever project tool the team already uses, and keep the V/TO in a Google Doc that nobody opens between sessions. The system fragments, and the operating rhythm starts to drift.

But the solution isn’t to abandon the framework. It’s to integrate it properly. EOS is an operating system, not a software product. The tools are interchangeable — but the framework and the discipline are not.

As for AI making operating frameworks irrelevant — I’d argue the opposite is true.

AI is going to create more noise, more velocity, more options, and more distraction than most founding teams have ever experienced. The companies that win won’t be the ones with the best AI tools. They’ll be the ones with the clearest vision, the tightest alignment, and the most disciplined operating rhythm.

EOS doesn’t compete with AI. It’s the structure that lets you deploy AI without losing your mind.

What I tell every founder I work with:

The goal of EOS isn’t perfection. It’s traction — real, consistent, measurable progress against a shared vision. Every quarter, you get a chance to reset, refocus, and recommit. That rhythm is the engine.

If your team is struggling to agree on priorities, losing key people, constantly firefighting, or stuck below the ceiling of complexity — those are not framework problems. Those are operating problems.

And operating problems have operating solutions.

If you’re a founder or CEO running a team of 10 to 250 people and you’re wondering whether EOS is right for you — I’ll give you 90 minutes, no strings attached, to find out. That offer stands.