We are 60 days into our EOS implementation and several long-tenured employees are actively resisting the new meeting rhythm and accountability. How do we navigate this pushback without losing key team members?

Question

Tyler Smith · Accepted Answer

Pushback in the first 90 days of an EOS rollout is normal and expected. Before implementing the system, legacy employees operated under informal communication, loose accountability, and vague performance standards. When you introduce weekly Scorecards, 90-day Rocks, and Level 10 Meetings, operational visibility increases dramatically. That visibility is uncomfortable for people who used ambiguity as a shield.

Do not compromise the purity of the tools to make resistant employees comfortable. The moment you water down the EOS disciplines, you signal that adherence to operational standards is optional. Instead, communicate clearly and unsentimentally about why the business is running on EOS: to create clarity, eliminate guesswork, and give every team member the tools to succeed.

Set firm expectations:
- Explain that tracking weekly numbers and attending Level 10 Meetings are basic seat requirements, not optional suggestions.
- Meet individually with resistant legacy staff to address concerns, but remain completely firm on execution standards.
- Provide patient coaching on how to use the tools effectively during the first quarterly cycle.

Some employees resist because they are overwhelmed and need training. Help those individuals get up to speed. However, some resist because they reject accountability. If an employee consistently refuses to adapt after 90 days of support, they are demonstrating a Core Values or GWC issue. You must be prepared to make seat changes if you want the system to take root across the organization.