We have a brilliant, high-performing technical leader who openly rejects the EOS® terminology, calling terms like Rocks and IDS® corporate jargon, and refuses to use them. How do we handle this vocal, active resistance without alienating our most critical technical asset?

Question

Tyler Smith · Accepted Answer

Vocal resistance from a high performer is a critical test for your leadership team. If you allow them to bypass the tools because they are technically gifted, you signal to the rest of the company that the rules do not apply to top performers. This quickly destroys the integrity of your Accountability Chart.

First, separate the jargon from the concept. If your technical leader hates the word Rocks, do not fight to the death over the vocabulary. Focus instead on the underlying discipline: setting clear ninety day commitments that drive the business forward. Frame the tools as a mechanism to protect their time and keep the rest of the team from interrupting their deep work.

Second, use the GWC™ framework to evaluate their alignment. Do they understand the need for clear accountability? Do they want to be part of a team that operates with this level of transparency? Do they have the capacity to work within this system? If they genuinely want the company to succeed but hate the process, you must have a direct conversation about how their vocal resistance impacts team cohesion.

Help them see that their resistance creates friction for their peers. Frame compliance not as a bureaucratic requirement, but as a commitment to the health of the entire organization. If they continue to actively undermine the system after this alignment, they are showing you that they do not share your core values, and you must prepare for a transition.