What if our leaders hear the same EOS presentation but disagree about which component we need most?
Use the disagreement to clarify the business problem rather than forcing everyone to select the same component. EOS introduces Vision, People, Data, Issues, Process, and Traction as parts of a system. Different leaders may notice different aspects of the same recurring difficulty.
Ask each person to describe an observable example behind their choice. A leader asking for clearer processes and another asking for stronger accountability may both be reacting to the same failed handoff. Alternatively, they may be describing genuinely different problems. The examples help the team distinguish those situations.
Ask the presenter how the components relate in those examples. That keeps the conversation focused on understanding EOS instead of turning it into a competition among departments for attention or resources.
Avoid treating the discussion as a formal diagnosis. The introduction provides a way to explore fit, but a brief exchange does not establish which part of the business needs the most work or in what order implementation should proceed.
My recommendation is to capture both the common ground and the unresolved differences. Leaders do not have to rank every problem identically to understand the system together. They do need enough shared understanding to explain what they hope EOS would improve and what questions remain before the team can support a next step.
Category: What Happens in the Meeting