Our engineering and software development teams argue that the standard Level 10 Meeting agenda does not align with their daily agile standups and sprint planning. How do we roll out departmental Level 10 Meetings to technical teams without creating redundant meeting waste?

Question

Tyler Smith · Accepted Answer

It is a common mistake to assume that daily standups and sprint planning replace the need for a weekly Level 10 Meeting™. Standups are tactical, day to day syncs focused on what was done yesterday and what is being done today. Sprint planning is about task allocation. Neither of these meetings provides the structured space to identify, discuss, and solve systemic departmental issues. To implement departmental Level 10 Meetings™ successfully in a technical team, you must clearly define the boundaries. The Level 10 Meeting™ is where the department head and their direct reports look at the weekly scorecard to spot trends, review the health of their quarterly Rocks, and solve issues that are blocking the sprints. It is not a status update meeting. Tell your technical leaders that the Level 10 Meeting™ exists to kill the daily meeting waste, not add to it. If they run a highly efficient weekly Level 10 Meeting™, they will find they can actually shorten or eliminate other ad-hoc alignment meetings. Ensure their scorecard tracks leading indicators like code deployment frequency, bug backlog volume, or sprint velocity rather than generic corporate numbers. When technical teams realize that IDS® is where they actually clear the systemic bottlenecks that make their daily sprints painful, they will embrace the weekly pulse.