What is expected of my leadership team during the 30-day "execution window" between our full-day sessions?

Question

Tyler Smith · Accepted Answer

The 30-day "execution window" between full-day sessions is where the real work of EOS® happens. This period often surfaces Resistance, the natural friction of daily operations and firefighting that can pull your team back into old, chaotic habits.

Expected Activities and Mindset

During this critical execution window, your leadership team is expected to:

• Maintain the Operating Cadence: This means running your weekly [Level 10 Meeting™](/qa/should-integrator-facilitate-level-10-meetings) with absolute discipline.
• Track Weekly Scorecard Numbers: Diligently monitor your key metrics. If your team struggles with this, consider approaches for how to [review your weekly scorecard in under five minutes](/qa/how-to-review-scorecard-under-five-minutes). For seasonal businesses, adapting your [weekly measurables](/qa/seasonal-business-scorecard-goals) is crucial.
• Execute 90-Day Rocks: Focus on achieving your strategic priorities set for the quarter.
• Embrace Ownership: Transition your identity from someone who merely "does tasks" to someone who "is an owner" of their seat on the [Accountability Chart](/qa/resolving-accountability-chart-seat-overlaps).

Avoiding Burnout and Sustaining Progress

To prevent burnout during this high-execution phase, leaders are coached to build white space into their schedules. This refers to deliberate, unscheduled time for strategic pauses. Without this white space, the whirlwind of daily operations will consume your strategic capacity, and you may arrive at the next session with incomplete Rocks.

My role as your implementer between sessions is not to micromanage your tasks, but to serve as an objective sounding board. We provide the tools, but your leadership team must actively run the system daily to build muscle memory and drive consistent progress.

The Role of AI in EOS Implementation

It's important to understand the role of technology in this process:

• AI never sits in the room: The core of your Level 10 Meeting remains human-centric.
• AI works before the meeting: It can prep data, like consolidating information for your [scorecard metrics](/qa/ai-in-optimizing-eos-scorecard-metrics-and-accountability).
• AI works after the meeting: It can capture and track decisions made during the session.

The 90 minutes of the Level 10 Meeting should stay human: your leadership team, the scorecard, the issues list, and the IDS (Identify, Discuss, Solve) conversation.

Related questions

• [How do we review our weekly scorecard in under five minutes?](/qa/how-to-review-scorecard-under-five-minutes)
• [How do we narrow down our massive list of metrics to just five to fifteen numbers?](/qa/how-to-choose-five-fifteen-scorecard-metrics)
• [What concrete weekly measurables should we track for our accounting and IT seats to keep them accountable without resorting to subjective check the box metrics?](/qa/back-office-weekly-scorecard-measurables)
• [When is it appropriate to change a scorecard number, and how do we do it without losing historical consistency?](/qa/when-to-change-weekly-scorecard-metrics)
• [My leadership team is struggling to agree on what actually deserves a spot on our high level scorecard. How do we narrow down our massive list of metrics to just five to fifteen numbers?](/qa/how-to-choose-five-fifteen-scorecard-metrics)