How to solve business issues effectively using EOS

Executive overview

Most teams struggle to resolve issues because they mis-label them, delay them, or address symptoms rather than root causes. The EOS IDS (Identify, Discuss, Solve) framework creates a structured, psychologically safe space to surface and resolve issues at the right level.

Without a clear process, issues leak into ad hoc Slack messages or emails, losing context and accountability. IDS fixes this by parking issues on a list until a protected meeting time, then solving them using the right tools and the right people.

The single most important habit is practice — teams that IDS well have simply done it hundreds of times.

What makes issues hard to solve

• People confuse issues with agenda items — renaming them "issues" signals they require a solution, not just a discussion
• Teams often address branches (symptoms) rather than digging to the root cause
• Issues lists grow unwieldy when each entry is a paragraph; this prevents prioritisation
• The most uncomfortable issues get subconsciously delayed — teams start with quick items, wasting time on the wrong things
• If the accountable person isn't in the room, the issue cannot be solved

Two traps that block resolution

• Heart trap — keeping someone because they're a strong cultural fit despite bad behaviour
• Performance trap — excusing bad behaviour because the person delivers strong results
• Neither is a valid reason to retain the wrong person; both core values fit and job performance are required

The people analyser for people issues

• People issues are the most emotionally charged — different leaders have different exposure to the same person
• The people analyser neutralises emotion by rating each team member against each core value (plus/minus/plus-minus)
• Adding GWC (Get it, Want it, Capacity) assesses whether the person is in the right seat
• Running the tool turns subjective opinions into an aggregated, structured assessment
• When applied consistently it becomes the default tool for any people challenge

Capturing issues on the list

• Capture every issue in three to five words — if you can't, you don't yet understand it
• Think of it as the "sexy movie title": a hook, no plot spoilers until IDS begins
• Overly long entries slow meetings and tempt teams to dive into solutions before prioritising
• An issues list full of paragraphs is itself an issue

Running effective issue-solving meetings

• Read the full issues list aloud at the start of each meeting and reprioritise — skipping this step buries older items permanently
• Prioritise in order: people issues, scorecard numbers, rocks — then everything else
• With practice, routine issues take two to three minutes; without process they consume ten to fifteen
• Some issues legitimately need the full session — protect that time rather than rushing
• Ask issue owners to arrive with a possible solution, not just a complaint
• Delegate issues to the right level; leadership teams should not solve operational issues that belong elsewhere

Creating a psychologically safe space

• Psychological safety — feeling safe enough to give and receive open, honest feedback — is a prerequisite for IDS to work
• Core values framed around openness make psychological safety an explicit cultural accountability
• Protected meeting time (vs. ad hoc messages) gives people confidence the conversation will happen properly
• The IDS framework itself reduces emotional charge by giving everyone the same structured process

Solving the right issue at the right time

• Excitement about the future can cause teams to skip foundational issues blocking near-term progress
• Analogy: fix the foundations before building the bridge; tie your shoelaces before the race
• When an issue is really a theme containing multiple sub-issues, create a mini issues list for it and find the root
• The right issue, solved by the right people, at the right time, using the right tools — that is the standard