Our engineering and operations managers claim the weekly Level 10 Meeting structure conflicts with their daily agile standups. How do we reconcile technical workflows with pure EOS cadence?

Question

Tyler Smith · Accepted Answer

Agile standups and Level 10 Meetings serve completely different organizational functions. Confusing the two is a common operational mistake that causes friction when cascading EOS into technical departments.

A daily agile standup is a micro-coordination tool. It answers three immediate tactical questions: what did you do yesterday, what are you doing today, and what is blocking your current sprint task. It operates at the ground level and takes ten to fifteen minutes.

A Level 10 Meeting operates at the structural leadership level. It does not manage daily tickets, code commits, or tactical customer service tasks. It evaluates whether the department is hitting its weekly Scorecard numbers, verifies whether 90-day Rocks are on track, and spends sixty minutes using IDS to solve root-cause organizational barriers that standups cannot address.

Do not abandon either framework. Instead, establish hard boundaries between them. The daily standup remains the engine for daily execution. The weekly Level 10 Meeting serves as the governing cadence where team leaders look up from the keyboard, review high-level metrics, and solve chronic workflow defects.

When technical teams realize the Level 10 Meeting is where they bring permanent structural fixes for the recurring blockers they complain about in daily standups, resistance disappears.