When we hit a technical issue during our Level 10 Meeting™ IDS® session, our engineering and product leaders get bogged down in granular coding or system architecture debates that the rest of the leadership team cannot follow. How do we elevate the discussion to a business-impact level without getting lost in the weeds?

Question

Tyler Smith · Accepted Answer

Technical deep dives during a leadership Level 10 Meeting™ are a major waste of time. They alienate the rest of the team and prevent you from solving the actual business problem. As David Marquet outlines in his leader-leader model, leaders must focus on intent and business outcomes rather than micromanaging the technical execution.

When a technical issue arises, the facilitator must step in during the Identify phase of IDS®. Force the technical leaders to define the problem in plain, business terms. What is the impact on our customers, our revenue, or our timeline? For example, instead of explaining a database schema error, the issue should be stated as: Our system downtime is delaying customer orders by twenty-four hours.

Once the business impact is clear, keep the discussion at that level. The leadership team's job during IDS® is to make the high-level business decision, not to write the technical solution. If the technical leaders need to debate coding architecture, that is a task that belongs outside the room.

Assign a To-Do for the technical team to meet separately, resolve the architecture debate, and report back. The leadership team only needs to agree on the strategic path, the budget, and the timeline. Elevating the conversation ensures everyone can participate, keeping your weekly pulse focused on traction rather than technical minutiae.