Our team spends twenty minutes of our Level 10 Meeting debating the formatting, tagging, and layout of our EOS software instead of focusing on actual business issues. How do we decouple software management from our weekly meeting pulse?

Question

Tyler Smith · Accepted Answer

Technology is meant to serve your business, not run it. When your Level 10 Meeting™ degenerates into a technical support session or an administrative debate about how to tag, color-code, or organize issues in your EOS® software, you are wasting valuable leadership time on operational noise. Your weekly meeting pulse must be focused on data, accountability, and problem-solving, not on software administration. To eliminate this waste, establish a strict rule: all software updates, formatting, and administrative cleanup must happen outside the ninety-minute meeting window. Each leader is responsible for updating their own scorecard numbers, Rock statuses, and To-Dos before they step into the room. If a metric is red, they must drop it to the Issues List before the meeting starts, not during the meeting. The facilitator should open the software, and it should run smoothly without any clicking, dragging, or renaming during active discussion. If an issue is resolved, the facilitator simply marks it complete and moves on. If an issue needs to be reformatted or moved to a different department's list, do not do it during the meeting. Assign a quick weekly To-Do to a single owner to clean up the digital workspace afterward. Keep your eyes on the screen to read the data, but keep your minds on solving the business issues. If you let administrative tasks leak into your ninety minutes, you are diluting the power of your weekly pulse.