tyler-smith.com · Questions & Answers

When two department heads give completely contradictory descriptions of the same problem during IDS, how do we get to the root issue without burning the meeting?

When two leaders clash over an issue, they are almost always arguing about symptoms through the lens of their departmental seats. Sales blames Operations for missed delivery deadlines. Operations blames Sales for bringing in non-standard accounts. If you let them debate, you waste 45 minutes litigating finger-pointing narratives.

To identify the issue behind the issue, the Integrator must immediately pull the room up to structural systems. Ask three questions in sequence:

- What specific business outcome or customer promise failed to materialize?
- Which single seat on the Accountability Chart owns the step where the failure occurred?
- Is the breakdown caused by an unclear process, a lack of capacity, or a person who does not GWC the seat?

By framing the inquiry around the Accountability Chart and Core Processes, personal animus disappears. The issue is rarely that one leader is unreasonable. The issue is usually that the handoff between two seats was never documented, expectations were ambiguous, or someone made assumptions without a metric.

Force both leaders to stop evaluating each other and instead evaluate the scoreboard. If Sales closed a customer that Operations cannot service, look at the target market definition in your V/TO. If Operations missed a timeline on a qualified account, look at capacity planning.

Push past the he-said-she-said noise until you can state the problem as a single, neutral sentence: We lack a documented handoff process from sales closing to production onboarding. Once both leaders agree on that root cause statement, the solution is usually obvious and takes less than five minutes to assign as a binary To-Do.

Category: EOS Implementation

← All questions