For a fully remote company that only meets in person for quarterly offsites, what software stack and meeting norms do you require us to use for our weekly Level 10 Meetings to maintain traction?

Question

Tyler Smith · Accepted Answer

Distributed teams struggle when operational tracking lives scattered across Slack channels, shared spreadsheets, and task managers. To make the weekly Level 10 Meeting work in a remote environment, you must consolidate your Scorecard, Rocks, To-Dos, and Issues List into a single dedicated software platform designed for EOS, such as Ninety.io or Bloom Growth.

Video is mandatory for every participant. Cameras must stay on, and multitasking is unacceptable. When a leader turns off their camera or types in the background during IDS, psychological safety and candid debate evaporate. The Integrator facilitates the ninety-minute meeting strictly on schedule, while one designated person serves as the scribe to capture dynamic notes, document To-Dos, and log new issues.

Between weekly meetings, asynchronous communication must support the tools rather than bypass them. If an operational roadblock emerges mid-week that does not require an immediate emergency response, do not start a thirty-message chat debate. Drop it directly onto the leadership team Issues List so it can be prioritized and solved during the next weekly meeting.

Treat the remote Level 10 Meeting with the exact same level of reverence as an in-person boardroom session. Start on time, end on time, follow the agenda without alteration, and give it undivided attention every seven days.