Don't Let Perfect Be the Enemy of a Good EOS Rollout

I've seen a lot of things derail an EOS rollout. Resistance. Confusion. A leadership team that hasn't fully bought in. But if I'm being honest, the biggest rollout killer I see again and again isn't any of those things.

It's waiting.

Waiting until the vision feels perfect. Waiting until every question has an answer. Waiting until the timing finally feels right.

Here's the truth: the timing is never going to feel right. And your team doesn't need a perfect rollout. They need a real one.

Why Perfectionism Stalls EOS Rollouts

When Marisa Smith and I were writing ROLLOUT, this was one of the patterns we kept coming back to. Leadership teams learn EOS at the top. They get aligned. They get excited. And then they pause, because now they have to bring it to the rest of the organization, and that feels like a much bigger lift.

So they wait. They want the V/TO to be airtight before they share it. They want to finish one more quarter before rolling out the meeting pulse. They want to figure out exactly how to explain rocks to a team that's never heard of EOS.

Meanwhile, the momentum they built at the leadership level starts to quietly fade.

The problem isn't that they care about doing it well. The problem is that they've confused doing it well with doing it perfectly. Those are not the same thing.

Progress Over Perfection in EOS

One of the core ideas in ROLLOUT is simple: progress over perfection. Small, steady improvements beat dramatic changes that don't stick. A rollout that starts messy and builds over time is worth more than a perfectly designed rollout that never actually launches.

This isn't a permission slip to be careless. It's a reminder that your team doesn't need you to have everything figured out before you start. They need context. They need direction. They need to understand where the company is going and how their role fits into it. You can give them that now, even if the plan isn't finished.

What to Do Instead of Waiting

Start before you feel ready. Pick one tool, one team, one layer of the organization, and begin. You will learn more in the first 30 days of a real rollout than in six months of planning one.

Stay consistent after the excitement fades. This is the part most teams underestimate. The initial launch gets energy and attention. What sustains a rollout is the quiet, repetitive reinforcement that happens in every L10 meeting, every one-on-one, every time a manager uses EOS language naturally.

Figure out the rest as you go. Rollout is not a one-time event. ROLLOUT is designed to be a reference you return to, not a checklist you complete once. The questions you can't answer today will surface in the work, and you'll be better equipped to answer them in real time than in a conference room trying to anticipate them.

The Real Risk Isn't Starting Too Early

A lot of leaders worry about rolling out EOS before they're ready and confusing their people. That's a real concern, but it's manageable. What's harder to manage is a team that's heard EOS language for two years but still doesn't understand why it matters, or a culture where the tools live only at the top and never quite make it to the people doing the day-to-day work.

Done imperfectly and moving beats perfect and sitting still every time.

If you're waiting for the right moment to start your rollout, this is it.