Our remote leadership team operates across four different time zones, and executives keep requesting that we shift the Level 10 Meeting schedule week to week to accommodate personal travel and varying work hours. How do we protect the weekly pulse in a distributed company?

Question

Tyler Smith · Accepted Answer

The Meeting Pulse is non-negotiable. The moment you start moving your Level 10 Meeting around calendars, you destroy the operational heartbeat of the business. EOS requires same day, same time, same agenda, and starting and ending on time. If you treat the meeting as movable, your leaders will treat their preparation and accountability as optional.

Pick a fixed 90-minute window that works across all time zones and lock it permanently. If a leader travels, they join from the hotel or airport lounge. If an executive takes planned paid time off, the meeting happens without them; their Scorecard numbers and Rock updates must be submitted before the meeting starts.

A distributed company actually needs a rigid meeting rhythm far more than a business where everyone sits under one roof. In an office, passive osmosis keeps people informed. In a remote model, the Level 10 Meeting is the single anchor that prevents the organization from drifting into operational isolation.

When executives ask to reschedule because of client calls or flights, the answer from the Integrator must be a polite no. You do not shift the cadence of the entire leadership team for one person. Protect the pulse, protect the start and stop times, and make attendance an operational requirement of holding a seat on the Accountability Chart.