We have a highly technical leader who insists on explaining the entire mechanical or software architecture of a problem before we can even begin the Identify phase of IDS. How do we shut down this background-loading?

Question

Tyler Smith · Accepted Answer

Background-loading is the enemy of efficient problem-solving. When a technical leader spends ten minutes explaining the history, software code, or mechanical nuances of an issue, the rest of the leadership team checks out mentally. They get lost in details they do not need to understand to help solve the problem. This behavior completely derails the speed of the Identify phase during IDS.

To stop background-loading, the facilitator must enforce the rule of the three-sentence setup. When an issue is brought to the table, the owner of the issue must identify the core problem in three sentences or less. They must state what the problem is, who is affected, and what the ideal outcome looks like. If they begin explaining how the system works or how the problem originated, the facilitator must intervene.

Use the phrase: State the issue, do not teach the issue. If the team genuinely needs more technical context to make a decision, they will ask targeted questions during the Discuss phase. Most of the time, however, the leadership team only needs to understand the business impact of the problem to help solve it. Keeping the setup short forces the owner of the issue to synthesize their thoughts before they speak, saving valuable minutes and keeping the entire room engaged.