EOS Pros and Cons: 12 Things Nobody Tells You Before You Run on Traction

By Andreas Pettersson, Founder, Leaders ADAPT

The loudest criticism of EOS is that it is a cult. It is not. The real cons are quieter, and they cost more than the implementer's invoice.

I ran EOS for years at Arcules, a company I founded, scaled to 150 people and sold to Canon, and I run it today at Leaders ADAPT with about 10 people. I am a big fan. I recommend Traction and Rocket Fuel to a lot of founders. That is exactly why I want to give you the EOS pros and cons nobody on the sales side will write down.

This is a spoke of my independent EOS review. If you only want the verdict, start there.

EOS, the Entrepreneurial Operating System, is a set of tools and meeting rhythms from the book Traction that a leadership team uses to set a vision, track numbers, solve issues and commit to quarterly priorities. Six things it does well. Six things it does not.

What are EOS pros and cons, in one table?

Here is the operator version. Each line pairs what the pro or con looks like inside a leadership team with what to do about it.

What are the pros of EOS?

At Arcules, EOS fixed things that would otherwise have become real problems. Accountability. Clearer roles and responsibilities. Focus on the right targets, the Rocks, every quarter. And, maybe most valuable, "a framework to say no to a lot of things." If it was not for EOS, a lot of things would have become an issue.

Focus is the first pro because it is the rarest. A growing company does not die from lack of ideas. It dies from starting all of them.

Named owners come second. When every number on the Scorecard has one name next to it, the conversation changes. It stops being "sales is behind" and becomes a person you can ask.

The weekly Level 10 Meeting is the third. It surfaces issues while they are still small and cheap. When L10s work, they can work amazingly, to the point where you can cut the number, frequency and length of 1:1s, because the leadership team is already aligned.

Clear roles are the fourth. The Accountability Chart draws the seats before it draws the names, so two people stop sharing one seat and nobody has to guess who decides.

The fifth pro is the one I value most as a Nordic leader.

In Nordic leadership we talk about separating the problem from the human. EOS surfaces issues as issues. IDS, the identify, discuss, solve routine, puts the problem on the wall instead of putting a colleague on trial. EOS works great for that.

And it works small. My rule: if you are more than three people, you need a framework, and you also need to work on your leadership. Thinking in Rocks and an issues list from the first few hires pays off later.

What are the cons of EOS?

Most EOS problems trace back to how the system is installed, not to the tools themselves. None of the EOS cons below is a reason to avoid EOS. All of them are reasons to go in with your eyes open.

It is rigid in the beginning

There is too much rigidity in EOS at the start. It is also the fairest EOS criticism on the list.

What matters first is getting into the L10 rhythm, then the culture fit part, then writing up the Vision/Traction Organizer. The rest can wait.

I am less hardcore about Rocks. You should be able to change things in between when the business changes. OKRs are nicer there, and I take inspiration from them for measurement. See EOS vs OKRs for that comparison.

The quarter can follow the implementer's calendar

This one I lived.

With one implementer, I came to believe the push to hold every quarterly target exactly as set had more to do with the implementer's schedule, a visit every third month, than with what our business needed. We had legitimate reasons to pivot. The rhythm did not bend.

My fix is simple: if an implementer is not working, cut them and move on to the next one. The EOS implementer cost is too high to pay for a calendar.

Too many Rocks

"A huge failure is when organizations try to set 10 rocks and fail at all." We were most successful with one to three per quarter, then and now. Every person gets at most one supporting Rock. The best quarter is one company wide Rock with everything else a subdivision of it, or preparation for next quarter's Rock.

It collides with board and parent company cadences

At Arcules we reported quarterly to Canon. Canon ran a big company mindset with mature, long planning processes, the opposite of a startup's fail fast rhythm. We spent a lot of time extrapolating data that was not naturally caught in our daily business rhythm, just to satisfy the parent.

In the beginning we did not time EOS against that. It created a lot of friction, and it created a lot of concern about whether EOS was the right model.

The fix was sequencing. Close last quarter and set next quarter's Rocks before board prep begins. By the time the board slides get built, the leadership team is already aligned.

It does not teach the how of leadership

This is the big one, and it gets its own section below.

It was built before AI

EOS was designed before AI arrived. These days AI is a massive culture change, and EOS needs to evolve so it does not miss that shift. The tools still assume a human pulls every number and writes every note.

Is EOS a cult?

No. "I'm not a big fan of calling this a cult. It's not."

A thread titled "EOS is a cult which will destroy your team" sat in the top five Google results for this exact search when we checked in September 2026. I understand where it comes from. Some people are fanatic about EOS, but that is because they finally found the structure they were looking for.

It is cookie cutter. That works for a lot of companies and does not work for others. The system is not the cult. The rigid application is.

Why does EOS fail in some companies?

Because the leadership came second.

"I don't believe that the system should mold the leader. The leader should be able to cope regardless." Many companies start with EOS in order to move ahead and do not succeed, because the leadership was poor. When people implement EOS and then drop it, in my experience it is usually because leadership was never properly established to begin with.

Here is what happens with a weak leader on EOS.

The system is worth very little. Or a little, because now the mediocre leader can get away with it. Maybe that buys a plateau to get better from. A plateau is not a plan.

The second reason why EOS fails is authority.

L10s die when the Visionary or CEO does not delegate authority to the Integrator. I have been in the CEO seat wanting to go a certain direction, and chose to keep the process and let the Integrator decide. That is the price of the system working. Many of the EOS limitations people blame on the tools are really this one decision, not made.

Where AI fits when you run EOS

AI belongs in the preparation and the tracking, never in the judgment.

My favourite use: the team scores its own L10, and we ask AI to score it too against the meeting rules and tell us what to improve. We wrote up the method in how to score your meetings with AI. Beyond that, AI can pull Scorecard numbers, collect Rock status, draft pre reads and capture to dos from the transcript.

Keep these with people:

• Who sits in which seat, and who leaves.
• The solve in IDS, not only the capture.
• What happens when a commitment is missed.
• The strategic commitments on the plan.
• Every performance conversation.
• Any promise made outside the building.

The longer version lives in what not to delegate to AI, and the full map of AI across the six EOS components is in AI for companies running EOS.

What EOS does not fix

EOS tells you who owns the number. It does not tell you how to have the conversation when the number is red for the third week.

Where EOS is lacking, in my words, is the how when it comes to leadership. Teams running it get the operating side. They do not get the detail of how to delegate, how to hold people accountable, how to run 1:1s, how to give feedback. That gap is why I built the 5 Minute Leader, which sits on top of EOS and works amazingly with it.

Leadership first. System second. The people problems every framework surfaces and none of them solve are covered in leadership team development.

Common questions about EOS pros and cons

What are the main EOS pros and cons?

The main EOS pros are sharper focus through a few quarterly priorities, named owners for every number and priority, a weekly meeting that surfaces issues early, and clear roles. The main cons are rigidity in the first year, dependence on the implementer's rhythm, Rock overload, friction with board cadences, little guidance on leadership skills, and a design that predates AI.

Is EOS a cult?

EOS is not a cult. It is a prescriptive set of tools and meetings, and some owners become strong advocates because it gives them structure they lacked. The criticism usually reflects the cookie cutter design, which suits many companies and frustrates others, and leaders who apply the tools rigidly instead of adapting them to the business.

Why does EOS fail?

EOS most often fails when the leadership team is weak before the system arrives. The tools expose missed commitments, unclear roles and avoided people decisions, but they do not teach leaders how to delegate, give feedback or hold peers accountable. Other common causes are too many Rocks, a CEO who will not hand authority to the Integrator, and poor timing against board reporting.

Is EOS too rigid?

EOS can feel rigid in the first year, because the quarterly Rock cycle and the fixed meeting agenda are taught strictly. Many companies relax it once the weekly rhythm is established, for example by allowing a Rock to change mid quarter when the business changes. Frameworks such as OKRs are often used alongside EOS for more flexible measurement.

What size company is EOS good for?

EOS Worldwide describes 10 to 250 employees as the sweet spot (read September 2026). Andreas Pettersson, who ran EOS at 150 people and at 10, uses a wider operator rule: EOS from about 2 to 250 people, with frameworks such as Scaling Up added on top once a company grows past a few hundred.

Does EOS work with AI?

EOS works with AI when AI handles preparation and tracking, such as pulling Scorecard numbers, collecting Rock status, drafting meeting pre reads and capturing to dos. People decisions, issue solving judgment and accountability stay with the leadership team. EOS was designed before generative AI, so companies have to decide these boundaries themselves.

Your next question

• Is EOS worth it? The verdict by company stage, after you have weighed these EOS pros and cons.
• EOS alternatives: what to run instead, in one decision table.
• How to choose an executive coach, when the con that bites is leadership, not process.