During an initial complimentary EOS Overview with a Professional EOS Implementer®, leadership teams often imagine what it would be like to finally run their business with clarity, discipline, and traction. They envision repeatable systems, fewer fire drills, and a leadership team operating as a true unit.
What they’re usually not asking, though many are quietly wondering, is this:
If we hire an EOS Implementer, what does the off-ramp look like?
It can feel like an awkward question, almost like bringing up a prenup on a first date. And so it often goes unspoken.
Thankfully, the EOS process itself is very explicit about this. During that initial meeting, Implementers explain that most teams work with them for roughly two years—the time it typically takes to fully roll out EOS across an organization. There is no long-term contract, no retainer, and no obligation to continue beyond the value being delivered. When a team feels confident running EOS on its own, the engagement ends: a milestone many Implementers refer to internally as “graduation.”
EOS Implementers also guarantee their work. If a team feels it did not receive value from a session, they do not pay for that session. From the start, the model is designed to create clarity, choice, and mutual accountability.
What if expectations begin to diverge?
As time goes on, acknowledging that expectations may no longer be aligned can feel uncomfortable. Leadership teams often come to see their EOS Implementer as an extension of the team, and raising the subject may feel less like a transition and more like “firing” someone.
But that framing misses the point.
As Priya Nalkur writes in her December 2025 Harvard Business Review article, When You’ve Stopped Growing with Your Executive Coach:
“Coaching isn’t meant to last forever. It’s meant to expand your capacity—to make you more capable of self-coaching over time.”
Nalkur describes three common signals that it may be time to end—or evolve—a coaching relationship:
- The learning is integrated, and the client wants space to practice independently (e.g., EOS graduation).
- Dependence has crept in, where the coach is expected to do the thinking rather than help the client learn how to think (e.g., expecting the EOS Implementer to do the team’s homework).
- The work no longer aligns with the organization’s long-term priorities (e.g., continuing a full EOS implementation/rollout is no longer the right strategic focus).
Importantly, Nalkur emphasizes that ending a coaching relationship does not mean failure. It’s a transition and one that deserves thoughtful closure.
Before concluding that true misalignment exists, however, there’s one additional question worth asking.
Mark O’Donnell, CEO of EOS Worldwide®, has encouraged leadership teams to be honest not only with their EOS Implementer, but also with themselves. He challenges teams considering a change to reflect on whether the desire for something different is rooted in genuine misalignment—or in the discomfort that naturally accompanies meaningful change. Often, it takes an open conversation to tell the difference.
EOS is designed to surface hard truths, increase accountability, and challenge leadership teams to do work they may have postponed for years. That process is rarely comfortable in the short term. Wanting change doesn’t automatically mean the relationship is no longer serving the team—but it does signal that a conversation is worth having.
Seen this way, graduation, recommitment, or change are not judgments. They’re outcomes of discernment.
How do you broach this conversation with your EOS Implementer?
Nalkur offers a simple three-step dialogue framework for initiating conversations like this with a coach:
- “I’ve noticed…” (Offer an observation.)
- “What I need is…” (State a clear need.)
- “Can we try…” (Propose a conversation or experiment.)
Example conversation starter:
“I’ve noticed that our team’s progress has stalled. What I need is for the leadership team to continue growing its ability to run the business without my direct involvement. Can we explore whether EOS coaching is still the right fit—or whether a different Implementer or form of support might better serve us at this stage?”
EOS Implementers are trained for exactly this kind of conversation. Their goal is not retention for retention’s sake, but what is best for the client. If that means graduating, changing Implementers, or engaging a different subject-matter expert, most Implementers have deep networks and are happy to help make those connections.
The off-ramp is simpler than it feels
When a leadership team has gone through enough Quarterly and Annual offsites with their Implementer to continue effectively on their own, and the rest of their company is operating on the same framework, it’s time to celebrate the team’s graduation – or continue working with their EOS Implementer as an ongoing trusted advisor/facilitator for leadership team performance. When an EOS engagement no longer seems to be working, the very conversation teams are tempted to avoid may be the key to unlocking stalled progress. Sometimes it leads to renewed commitment. Other times it leads to a change in support or a pause in the company’s EOS implementation.
As Nalkur notes, a well-handled ending includes a final conversation focused on:
- Reflecting on the progress the team has made
- Identifying what conditions will sustain that progress
- Clarifying what the next season of support might look like
The EOS off-ramp is ultimately straightforward: graduate, change Implementers, or discontinue. What matters most is that the leadership team continues making those small, consistent improvements—regardless of how the relationship evolves.
And that conversation with your EOS Implementer?
It’s not awkward. It’s your team continuing to improve.