Self Implementing EOS: How to Run Traction Without an Implementer, and the Three Places It Breaks

By Andreas Pettersson, Founder, Leaders ADAPT

A founder reads Traction on a flight. By Monday there is a Scorecard in a spreadsheet and an L10 on the calendar.

By the third quarter, the founder is running the meeting, writing the Rocks and deciding every issue. The system is in place. The Integrator is not.

That is not self implementing EOS. That is control with an agenda.

I ran EOS for years at Arcules and run it now at Leaders ADAPT. I have helped skeptical owners get started on their own, then recommended an implementer once they saw the benefits. This guide covers how to start, who runs the meetings, and the three places it breaks. It sits under my independent EOS review.

Self implementing EOS means a leadership team installs the Entrepreneurial Operating System from the book and public tools, with an internal facilitator instead of a paid implementer.

Can you self implement EOS?

Yes. It is a good way to start. I am not sure it is the long term path.

My honest position: "Personally, not a big fan of self implementation, because it's often driven by a Visionary who doesn't want to give up control to the Integrator." Not because the book is hard. Because the person who bought the book is usually the person who has to change most.

The numbers point the same way. Grow Exceptional reports that over 70 percent of its clients tried to self implement EOS for up to two years before engaging them (FAQ page, modified May 2022). Their clients, their claim. An EOS implementer I spoke with put the timeline plainly: plan on two years to really get it, self implemented or not.

Self implementation works best in three conditions. The CEO is genuinely willing to hand decisions to the Integrator. Someone on the team has run a disciplined weekly meeting before.

And the team is honest enough to put the CEO's own habits on the issues list. An EOS self implementer missing all three is buying a book, not a system.

So you can implement EOS without an implementer if you want to. Just decide in advance what would make you stop.

How do you implement EOS yourself in the first 90 days?

Do not install everything at once. Install the rhythm first.

In my experience, getting into the weekly L10 rhythm is one of the biggest wins. Then the culture fit work. Then writing up the Vision/Traction Organizer. Rocks come early too, but keep them few.

If you are asking how to implement EOS yourself, here is a sequence in that order for owners who want to start without an implementer. It describes what each tool does, in plain words. For the official versions, go to EOS Worldwide.

Two rules sit on top of the table. If you are more than three people, you need this. And every person gets at most one supporting Rock. "A huge failure is when organizations try to set 10 rocks and fail at all." One to three company Rocks worked for us then, and it works now.

Week 13 deserves its own rule. Prep people, and do not trick people into things.

Tell them straight up, ahead of time, what the quarterly session will decide, and send the pre work weeks ahead so nobody arrives stressed and unprepared. Then set the follow up rhythm the moment you are back in the office. Otherwise it is just a meeting.

Who should run the meetings when you self implement?

Not the CEO by default.

Hold the L10 whether people are there or not. Rotate who runs it. I am all for the Integrator owning the meeting, but I have seen what happens when the Integrator cannot attend: the meeting dies. Rotation keeps it alive, and it cascades the skill down the organisation.

Whoever runs it this week follows four rules:

1. Start on time and end on time, even if the CEO is late.
2. The person running the meeting keeps the agenda and does not solve the issue.
3. Anything not on the issues list waits for next week.
4. Every to do leaves the room with one owner and a date.

When L10s work, they work amazingly. You can reduce the number, frequency and length of 1:1s, because the leadership team is already aligned. We wrote up how we score our own meetings in score your meetings with AI.

Where does self implementing EOS break?

The three break points are the places self implementation usually stalls: authority that never moves from the Visionary to the Integrator, hard issues nobody outside the team forces, and people decisions left longer than 30 days. Each one is a leadership problem that looks like a process problem.

Break point 1: the Visionary keeps the authority

This is the one I know from the inside. At Arcules I handed the Integrator role over from a responsibility perspective, not from an authority perspective. The board and Canon expected me to be the authority, including the power to fire the Integrator. That forced consensus decisions where the Integrator should simply have decided.

Self implementation makes this worse. The CEO who bought the book runs the meeting, sets the agenda and makes the call. The Integrator becomes a note taker.

L10s fail when the Visionary does not delegate authority. I have kept the process and let the Integrator decide, even when I wanted another direction. That is what the seat costs.

Break point 2: nobody outside the room forces the hard issue

Every leadership team has an elephant on the issues list. Everyone knows which one. A good implementer will not let the room move on until it is solved. An internal facilitator who reports to the CEO rarely has that freedom.

What a good outside facilitator does is narrow. They make sure the conversation happens. They calm the room when it gets heated.

They never step in and do the work for you, and they never interfere in the business. That combination is very hard to play from inside the reporting line.

Here is what happens instead: the issue gets discussed for four weeks, parked, and renamed. Motion isn't progress.

Break point 3: people decisions wait

The EOS implementer I spoke with described it well. Most of us hang on too long with hope, they said, and they called it smoking hopium. On a self implemented team, nobody outside the reporting line says it out loud.

My rule came from getting this wrong.

"Every time I stalled more than 30 days it was painful for the organization and an unnecessary tax."

Cut bait and move on pretty quickly. Sometimes it is the right person in the wrong seat, so move them.

There is a great company for every individual. It just may not be yours. The conversation itself is covered in how to fire a leader well.

When should you stop self implementing?

Set the exit criteria on day one. Four signals mean it is time for outside help:

1. The same three issues have been on the list for two quarters.
2. The CEO facilitates every meeting and also makes every decision.
3. A known people problem has waited more than 30 days.
4. Rocks are missed two quarters in a row and nobody is surprised.

When you do hire, hire for fit rather than proximity, and keep the right to change implementers if the first one does not work out. The system stays. The facilitator can change.

Then compare the spend honestly. The EOS implementer cost page has dated session fees and the two year math. If the problem is the leader rather than the tools, read EOS implementer vs business coach vs executive coach first.

Where AI fits when you self implement EOS

Self implementation has an AI twin, and it fails the same way.

Companies self implement AI too. They do not put validation frameworks in place, they do not turn repeated work into skills, and things go off the rails. I have walked into an organisation where a vibe coder had built a CRM as a single HTML file with over 12 million lines of code. Too much information in the hands of people who do not understand context can send a whole organisation in the wrong direction.

Used with rules, AI is a gift to a team running EOS on its own. It pulls Scorecard numbers, chases Rock status, drafts the pre read and turns the transcript into to dos.

These stay with the team, self implemented or not:

• Deciding who sits in each seat.
• Reaching the decision in IDS.
• Following through when a commitment slips.
• Choosing the strategic commitments.
• Holding performance conversations.
• Making promises to customers and the board.

Read what not to delegate to AI, and see the component by component view in AI for companies running EOS.

What self implementation does not fix

The book teaches the tools. It does not teach the leader.

"If people have implemented EOS and moved on, it's because leadership was never really established in the proper way to begin with." Self implementation hides that longer, because there is no outsider to notice. The team gets good at the meeting and stays weak at delegation, accountability, 1:1s and feedback.

That is the part of the job covered in leadership team development.

Common questions about self implementing EOS

Can you self implement EOS?

Yes. A leadership team can self implement EOS using the book Traction and the tools EOS Worldwide publishes, with an internal person facilitating the meetings. Many companies start this way. Progress tends to be slower than with an outside implementer, mainly because nobody outside the team forces difficult issues and people decisions onto the agenda.

How long does it take to implement EOS yourself?

EOS Worldwide describes full implementation as taking 18 to 24 months with an implementer (read September 2026). Self implementing EOS usually takes at least as long, because the team learns the tools by trial across several quarterly cycles. A reasonable plan is to have the weekly meeting, scorecard and quarterly priorities running within 90 days and the rest within two years.

Who should run the Level 10 Meeting when you self implement?

The Integrator is the natural owner of the weekly Level 10 Meeting, but many teams rotate the facilitator. Rotation keeps the meeting alive when the Integrator is absent and teaches the skill further down the organisation. The CEO or Visionary is usually the weakest choice, because it concentrates both the agenda and the decisions in one person.

What does self implementing EOS cost?

Self implementing EOS removes implementer session fees, which public implementer pages put at roughly $4,500 to $6,600 per full day in 2026. The remaining costs are the book, meeting software if used, and the leadership team's time. The hidden cost is duration: Grow Exceptional reports most of its clients self implemented for up to two years before hiring help.

When should you hire an EOS implementer instead of self implementing?

Consider hiring an implementer when the same issues return quarter after quarter, when the CEO facilitates every meeting and also makes every decision, when a known people problem has waited more than 30 days, or when quarterly priorities are routinely missed. These signs usually mean the team needs an outside facilitator rather than more tools.

What tools do you start with when self implementing EOS?

Most teams start with four: a weekly leadership meeting with a fixed agenda, a short scorecard with one owner per number, one to three quarterly priorities, and a running issues list. A role chart and a written vision usually follow in the first two quarters. Describe each tool in your own words and keep the first version short.

Your next question

• Is EOS worth it? The stage by stage verdict, including when self implementing EOS is enough.
• EOS implementer vs business coach: who to hire when you stop doing it alone.
• Do I need an executive coach? When the break point is the person, not the process.