Will the presenter explain all six EOS components, or focus only on the problem that brought us in?
Use the meeting to understand all six components, while asking the presenter to connect them to the problem that brought you in. EOS brings structure through Vision, People, Data, Issues, Process, and Traction. Evaluating only one component can leave your team with an incomplete picture.
For example, missed commitments might look like a follow-through problem. But the discussion could also reveal unclear priorities, uncertain responsibilities, or a lack of useful information. Those are possibilities to examine, not diagnoses the presenter should declare without understanding your business.
Ask for plain-language explanations of each component:
- Vision: Are we clear about where we are going?
- People: Do we have the people and responsibilities the business needs?
- Data: What information helps us manage objectively?
- Issues: How do we surface and resolve problems?
- Process: How do we make important work consistent?
- Traction: How do we turn plans into disciplined execution?
The introduction does not need equal time on every component. It does need enough coverage for leaders to understand how the parts support one another.
My recommendation is to use your biggest frustration as an entry point, not as the entire agenda. Ask each leader which component seems most relevant and why. Different answers can reveal where the team needs more clarity before deciding whether EOS fits.
Category: What Happens in the Meeting