EOS IDS Framework: How to Solve Problems Faster in Team Meetings

Executive overview

Most leadership teams believe they are already identifying, discussing, and solving issues — but in practice they conflate all three steps and stall on the wrong problems. The IDS framework (Identify, Discuss, Solve) from EOS forces a clean separation between those phases, with the hardest and most neglected work sitting in the Identify step. Clearing 8–12 issues per weekly L10 meeting is the benchmark for a team doing IDS well. Three predictable failure modes block teams from reaching that throughput, and each one has a direct fix.

The single most important IDS habit: force every issue into one sentence before moving to discussion.

The three IDS steps and how to run them

• Identify: Ask "What is the problem we are trying to solve in a sentence?" — write it visibly so the group can see it.
• Visible writing (screen or whiteboard) causes people to stop talking in paragraphs and compress to a sentence.
• When one issue turns out to be several, list them all, then ask which to tackle first.
• Get explicit group agreement on the sentence before moving forward.
• Discuss: Ask "Does everybody understand the problem?" — allow free-for-all context sharing, but lean forward to create urgency and limit time.
• Skipping straight to Solve often triggers discussion organically; use that as a deliberate technique.
• Solve: List options visibly (Solve 1, Solve 2, Solve 3); writing them shifts the group into decision mode.
• Assign a named owner and a due date; track it the following week.

Why IDS gets stuck: the three root causes

Root cause 1 — Strategic issues in a tactical meeting

• Weekly L10s are for tactical execution: scorecard, rocks, short-term issues only.
• Benefits overhauls, pay structure changes, new facility processes — these are rocks, not weekly issues.
• When a strategic topic surfaces, label it immediately and move it to the long-term issues list.
• Revisit it at the quarterly session where hours are available for deeper IDS.
• Tool tip: in the 90.io platform, drag it to the Long Term tab instantly.

Root cause 2 — Bowl of spaghetti: multiple issues disguised as one

• Example: a single "issue" about Meg's maternity leave contained five distinct problems (maternity policy, account risk, untrained employee, client relationship, coverage plan).
• When everyone hears a different sub-problem, they talk past each other and nothing resolves.
• Fix: force the sentence question. The speaker must choose which single problem to solve right now.
• Remaining sub-issues go on the issues list for future meetings or get delegated to the relevant department.

Root cause 3 — Chasing consensus too long

• Leaders naturally want buy-in, but prolonged consensus-seeking is where IDS time leaks.
• On lower-stakes issues especially, reasonable people disagree and waiting for unanimity is wasteful.
• The "fearless leader" role requires courage: decide, declare it, move on.
• Not everyone has to agree — they have to commit to the decision.

Weekly L10 vs. quarterly IDS: key differences

• L10 (weekly): target 8–12 issues cleared; 3–5 minutes per issue; strictly tactical.
• Quarterly: strategic issues only; 15–20 minutes per issue is acceptable; expect multi-part problems.
• Quarterly sessions are the right venue for complex, multi-sentence problems that genuinely need extended discussion.
• Even in quarterly IDS, break the big topic into sub-sentences and solve each one sequentially.

Practical facilitation techniques

• Project the issue sentence and the solve options on a shared screen or whiteboard throughout the meeting.
• Seeing their words typed back at them causes presenters to self-edit and compress in real time.
• Lean slightly forward and create mild urgency during Discuss — passivity invites hour-long tangents.
• In Solve mode, number each option as it is offered; the visual list naturally moves the group toward a decision.
• Aim for momentum: clearing one issue cleanly builds rhythm for the next.