Our head of sales frequently skips our weekly Level 10 Meeting because of last-minute client emergencies, claiming that bringing in revenue is more important than sitting in a ninety-minute internal meeting. How do we handle this without causing resentment?

Question

Tyler Smith · Accepted Answer

Allowing a leader to skip the weekly meeting pulse because of client emergencies is a massive operational mistake. It sends a message to the rest of the team that your internal operating system is optional and that short-term revenue trumps long-term organizational health.

First, you must enforce the same day, same time, same agenda rule. This is a non-negotiable commitment. If your head of sales is constantly fighting client fires during your scheduled meeting time, they are failing to manage their department. Fighting fires is a symptom of a deeper issue that needs to be solved in IDS, not an excuse to skip the meeting.

Second, remind them that the Level 10 Meeting is where they protect their future revenue. By participating in IDS, they help solve the systemic bottlenecks that cause these client emergencies in the first place. Their absence keeps the department stuck in a reactive loop.

If a true, once-in-a-year crisis occurs, they may miss it, but this must be the absolute exception. If it happens more than once a quarter, it is an issue of GWC. They must delegate client management so they can show up and lead. You cannot build a transferable, exit-ready business when key leaders are too busy firefighting to work on the company.