The First 90 Days With an EOS Implementer, Week by Week

The most common reason a leadership team stalls on hiring an implementer is not price and it is not skepticism about the framework. It is that nobody has told them concretely what happens. They are asked to commit the leadership team's calendar to something described in abstractions.

So here is the sequence, in weeks, with what the team does in between and what tends to go wrong. Implementers vary in pacing and the timing flexes by a week or two, but the structure is the published one and most follow it closely.

Week 0: the 90 minute meeting

A ninety-minute session where the implementer walks your leadership team through the six components a business has to strengthen, demonstrates the core tools, and answers questions. Most offer it at no charge, though that is each practice's decision.

The purpose is a decision, and it is the team's rather than the founder's. A worthwhile version includes the implementer saying out loud what the commitment costs in calendar time, and being direct about when the answer should be no. If the team agrees in the room and grumbles in the parking lot afterward, do not start. That will surface in week six anyway and it is cheaper to handle now.

Week 1 or 2: Focus Day

A full day with the leadership team, and the day that changes how the next quarter runs. Four things come out of it:

The Accountability Chart. Structure first, then names. This is where most teams discover that two seats are held by one person, or that a function everyone assumed was owned is owned by nobody. Expect it to run long and to be the most uncomfortable part of the day. That discomfort is the day earning its keep.

Rocks. Each leader leaves with a small number of ninety-day priorities, generally three to seven, each written as a finished outcome rather than an activity, with one owner.

The Scorecard. Five to fifteen weekly numbers, each with an owner and a goal. Your first draft will be wrong. It is supposed to be.

The Meeting Pulse. The weekly leadership meeting goes on the calendar, same day and time every week, standard agenda, starting that week.

You also start an issues list: every problem and stuck thing the team has been carrying, written in one place. For many teams that is the first moment of relief, because what has been weighing on people turns out to be a finite list.

Weeks 2 to 5: running the weekly meeting badly

Your first three or four weekly leadership meetings will not go well, and knowing that in advance is useful. The segue runs long, the scorecard review turns into explanations instead of a simple on-track or off-track, the Rock review becomes status updates, and the issues segment starts thirty minutes late so you solve one issue out of nine.

None of that means the system does not fit. It means the team has never run a meeting this way. By the fifth or sixth week most teams clear the opening segments in the intended time and the issues segment becomes the bulk of the meeting, which is the entire point.

The implementer is generally not in these meetings. You run them. Most will attend one early on to observe and give feedback, and are available between sessions for short calls with the Integrator.

Weeks 5 to 6: Vision Building Day 1

The second full day, about thirty days after Focus Day, and it is about the long view. Core values, articulated as the handful of behaviors that describe your best people rather than words everyone can agree with. The core focus: why the organization exists and the specific thing it does. A ten-year target. The marketing strategy, meaning who you are for and what you are promising them.

Two things worth knowing. Core values work is slow and frequently produces a statement that indicts somebody currently on the team, which a good implementer will not rush past. And the day usually reopens the Accountability Chart, because the structure drawn on Focus Day predates any agreement about what the business is trying to become. Reopening it is normal.

Weeks 6 to 9: the scorecard starts telling the truth

Between the two vision days the weekly rhythm continues and the scorecard goes through its shakedown. Expect to rewrite several lines. By week eight you know which numbers are produced on time, which nobody can produce without a manual reconciliation, and which move but do not predict anything.

Issues change character too. The early list is full of operational irritants. Around week six to eight the real ones appear: a seat that is wrong, a customer segment losing money, a partner disagreement unaddressed for two years. Writing those down is the signal that the meeting has become safe enough to be useful.

Weeks 9 to 10: Vision Building Day 2

The third full day. The three-year picture, described specifically enough that the team would recognize it if they walked into it. The one-year plan with a small number of measurable goals. Then the next quarter's Rocks, set against that plan rather than against whatever felt urgent. Most teams set better Rocks on this day than on Focus Day, because they have watched themselves miss a few.

Weeks 10 to 13: the first real quarter, then the quarterly session

From here the rhythm is steady: weekly leadership meeting, Rocks worked between meetings, issues solved as they arrive. At the end of the quarter, a full-day session to review the year to date, check Rock completion, work the accumulated issues, and set the next quarter. Then it repeats, four a year, one of which is a two-day annual session.

What the implementer does not do

This is the most common misunderstanding, so it is worth stating plainly. An implementer is not a consultant. They do not write your strategy, build your financial model, restructure your department, or do your Rocks. They facilitate, teach the tools, and coach the team, and the working definition of a successful engagement is that the team eventually runs the system without them.

They also do not manage your people. If there is a wrong-seat problem, the implementer's job is to make the structure and the standard clear enough that the team cannot avoid the conversation. Having it is yours.

What tends to be hard, honestly

People issues surface early, usually between weeks three and eight. A clear chart and a scorecard with owners make ambiguity impossible to hide behind. Some teams change composition in the first two quarters. That is a real cost, and it should be weighed before starting rather than discovered.

The founder's own seat is the hardest conversation. In owner-led businesses the structural issue is frequently that the owner occupies three seats and will not let go of two. No framework resolves that on its own.

The calendar commitment is real. Four full days in the first quarter, a weekly ninety-minute leadership meeting, and a full day each quarter after. Teams that treat the quarterly as optional when things get busy generally lose the system within a year.

How this changes when it is run remotely

The sequence is the same. The full days get restructured, because eight hours on video does not work: a Focus Day becomes two half days on consecutive days, or three shorter blocks. Pre-work matters more, materials live on a shared board, and the technical setup gets tested before the first session rather than during it.

For a team spread across states, that is the difference between doing the work and postponing it. Sector shapes the specifics: how this runs for a construction leadership team with people on active job sites is not how it runs for financial firms scheduling around client and compliance calendars, and a trades business whose owner is also the best technician has a capacity problem to solve before the calendar problem.

If you want to know what the first ninety days would look like against your own calendar, tell us how your leadership team is set up and we will map it out.