Our leadership team is split across multiple global time zones, making a synchronous ninety-minute Level 10 Meeting incredibly painful for at least half the team. Is there a way to adapt the weekly meeting pulse for an asynchronous or hybrid setup without losing the accountability and connection of the EOS framework?

Question

Tyler Smith · Accepted Answer

The weekly ninety-minute Level 10 Meeting is non-negotiable because the real-time friction of the IDS process cannot be replicated asynchronously. However, when you have a globally distributed leadership team, you must design your schedule and meeting mechanics with extreme intentionality to avoid burning out your team.

First, identify a single, consistent window of overlap where everyone can meet live. Even if it is early morning for one leader and late evening for another, that ninety-minute block must be fiercely protected on everyone's calendar. To make this fair, some global teams choose to rotate the meeting time every quarter, sharing the burden of the off-hours slot.

Second, you can streamline the live portion by handling the status-oriented sections asynchronously beforehand. Have your team update and review the Scorecard, Rock progress, and To-Do list in your shared software platform prior to the meeting. Any red metrics or off-track Rocks must be flagged and dropped to the Short-Term Issues List before the live session starts. This allows you to immediately segue and dive straight into the live IDS process, maximizing the precious ninety minutes of real-time collaboration and problem-solving. This disciplined approach ensures global alignment while respecting individual capacity and energy levels.