How EOS uses the Issues Component to solve problems permanently

Executive overview

Most leadership teams discuss issues at length but rarely resolve them — the same problems resurface week after week. The EOS Issues Component breaks this cycle by giving teams a structured place to surface problems and a disciplined process to eliminate them.

The core tool is IDS (Identify, Discuss, Solve): a three-step solving track that forces teams to find root causes, not symptoms, and assign concrete actions before leaving the room.

A well-defined issue is half solved.

Where issues come from in the EOS model

• Issues emerge naturally when Vision, People, and Data components are strong — openness and transparency flush out obstacles
• The Issues List is a shared, permanent place to capture obstacles, frustrations, opportunities, and ideas
• Getting issues out of heads and onto a list is itself valuable — reduces mental load
• Culture matters: every team member, not just leaders, should feel safe to raise an issue

IDS: the three-step solving track

• Identify — surface the real issue, not the symptom; ask clarifying questions before diving in
• Prioritise the top three issues to solve this week — focus prevents the team being overwhelmed by the full list
• Discuss — share input and perspective briefly; say things once; repeating yourself is politicking
• Solve — make a decision; assign a specific action to a named person with a due date; the issue comes off the list when the action is committed

Common failure modes

• Teams discuss for 30–60 minutes but leave without a clear owner or action
• The issue is written as a symptom — the root cause is never identified
• Meetings drift into tangents (one person's issue expands to include unrelated people or topics)
• Leaders solve issues for their teams instead of building team problem-solving capability

People issues

• People issues are the most common — often a right person in the wrong seat, or wrong person in the right seat
• Delaying people decisions costs more than making them swiftly
• Treating departing team members with psychological safety benefits everyone — the person, the team, and the culture
• People who move on often send positive feedback when handled well; the remaining team gains energy

Department-level meetings and issue culture

• IDS applies at every level of the organisation, not just the leadership team
• Leaders should ask each team member to bring at least one issue, idea, or opportunity to every meeting
• If the leader doesn't raise tough issues first, the team stays arms-folded and closed
• Going first as a leader signals it's safe — others follow
• Well-run departments can solve three, six, or nine issues per weekly meeting

Scaling issue resolution

• As teams get better at IDS, the number of issues solved per meeting grows — three becomes six, six becomes nine
• Solved issues are logged on a to-do list with owner and date; they stay closed
• Rocks (quarterly priorities) off track should immediately enter the IDS process
• Scorecard metrics with a concerning trend pattern should be identified and solved weekly