How do we run departmental Level 10 Meetings™ in highly technical divisions like software development or engineering without letting the agenda devolve into deep-dive technical specs?

Question

Tyler Smith · Accepted Answer

Highly technical departments often struggle with Level 10 Meetings™ because technical professionals naturally want to solve complex, granular problems rather than focus on operational traction. To prevent their weekly meetings from turning into long code reviews or product design sessions, you must enforce a strict boundary between operational issues and technical architecture.

The facilitator of the departmental meeting must hold the team to the standard EOS® agenda. When a technical issue is brought to the table, the team must first define the operational impact of the problem. For example, the issue is not how to write a specific API integration. The issue is that the integration is delayed, which threatens a key project milestone.

If the discussion during IDS® begins to drift into technical specifications, coding logic, or architectural design, the facilitator must intervene immediately. The solution to a technical issue is almost always a To-Do for two or three specific people to meet offline and solve the technical problem.

The Level 10 Meeting™ is designed to identify, discuss, and solve the operational bottlenecks of the department, not to serve as a collaborative engineering workspace. By keeping the focus on accountability, timelines, and business metrics, the department head can build a highly disciplined team that delivers technical results on schedule without wasting collective hours in the meeting room.