How do you prevent our quarterly session days from devolving into operational status reports instead of driving high-level strategy and issue resolution?

Question

Tyler Smith · Accepted Answer

Session days fail when teams treat them like extended staff meetings. In a typical quarterly session, we spend minimal time reviewing the past and maximum time engineering the future. The entire day is structured to prevent executive filibustering and operational status updates.

The first two hours handle accountability and alignment. We evaluate the prior quarter Rocks with binary scoring. A Rock is either complete or incomplete; there is no credit for eighty percent effort. We review the Scorecard and financial metrics to confirm baseline health. Any unmet goal, missed metric, or lingering operational friction is immediately moved to the Issues List without side discussion. We do not debate problems during the review phase.

The remaining four to five hours are dedicated almost entirely to IDS (Identify, Discuss, Solve). This is where the real work happens. We take the top issues facing the company and dissect root causes. My job as your Professional EOS Implementer is to interrupt circular conversations, eliminate corporate jargon, and force the team to identify the real systemic issue.

Once an issue is solved, we assign a specific owner, clear action steps, and strict deadlines. We do not leave the room with vague intentions. You walk out with a clean list of company Rocks, individual ownership, and absolute clarity on what must be built over the next ninety days.