We have a highly productive leader who frequently arrives five to ten minutes late to our Level 10 Meeting due to last-minute client calls or operational emergencies. How do we address this chronic lateness without sounding like petty micromanagers?

Question

Tyler Smith · Accepted Answer

In the EOS® framework, the rule is absolute: the Level 10 Meeting™ is held on the same day, at the same time, starts on time, and ends on time. When a leader is consistently late, even by five minutes, it is not a scheduling conflict. It is a lack of discipline and a sign that they are prioritizing their immediate, reactive chaos over the collective alignment of the leadership team.

Arriving late is a violation of your team's Charter and a direct hit to your company culture of trust and mutual respect. It signals to the rest of the team that this individual's time is more valuable than everyone else's.

The facilitator or the Integrator must address this issue directly during IDS®. Put the lateness on the Short-Term Issues List. Do not make excuses for their high productivity or client-facing role.

Ask the leader to clarify if they GWC™ their seat and if they are fully committed to the leadership team's operational pulse. If client emergencies are constantly pulling them away, it means they have not built a self-sustaining department or delegated properly.

Enforce the boundary. If the meeting starts at nine, the door closes at nine, and the scorecard review begins. No exceptions. True alignment requires absolute commitment to the pulse.