tyler-smith.com · Questions & Answers

One of our strongest operational leaders is vocally pushing back on the Level 10 Meeting™ structure, calling it too rigid and corporate for our entrepreneurial culture. How do we handle this direct resistance without breaking the system?

When a strong leader openly resists the Level 10 Meeting™ structure, you must address it head-on. Do not tolerate exceptions or allow them to run their own modified version. That compromise signals to the entire company that your core operating system is optional.

First, determine if this is a capability issue or a cultural alignment issue. Use the GWC™ tool. Does this leader truly understand the value of the meeting, do they want to do it, and do they have the capacity to lead it effectively?

Often, resistance stems from a fear of accountability. The Level 10 Meeting™ exposes performance gaps through the weekly Scorecard and quarterly Rocks. If their metrics are red, there is nowhere to hide.

Sit down with the leader privately. Explain that the rigidity of the agenda is intentional; it is designed to save them time, not waste it. It prevents status-report drift and forces real problem-solving through IDS®.

Challenge them to run the exact Level 10 Meeting™ agenda for ninety days with absolute compliance. If their operations and team communication do not improve after three months of disciplined execution, then you can discuss adjustments. Almost always, once they experience the efficiency of a true IDS® session, the resistance disappears. If it does not, and they continue to fight the system, you have a Right Person, Right Seat issue.

Category: EOS Implementation

← All questions