IDS Process
IDS (Identify, Discuss, Solve) is the EOS problem-solving framework. It is simple, disciplined, and effective. Used during the L10 Meeting, IDS transforms a team's ability to tackle issues from chaotic debate into focused resolution.
Why IDS Exists
Most teams struggle with problem-solving because they:
- Jump to solutions before understanding the problem
- Discuss symptoms instead of root causes
- Rehash the same issues week after week without resolution
- Allow dominant personalities to dictate solutions
- End discussions without clear action items
IDS solves all of these by imposing structure on the conversation.
The Three Steps
Step 1: Identify
Name the real issue.
This is the most important and most overlooked step. Teams often discuss surface-level symptoms rather than the underlying problem.
Example: Symptom vs. Root Cause
- Symptom: "We're losing deals in the final stage."
- Root Cause: "Our pricing process takes too long -- prospects go cold."
If you solve for "losing deals," you might invest in more sales training. If you solve for "slow pricing process," you fix the actual bottleneck.
During the Identify step:
- The person who raised the issue states it clearly in one or two sentences.
- The team asks clarifying questions (but does not discuss solutions yet).
- The issue is restated if needed to reflect the root cause.
Key question to ask: "What is the real issue here?"
Step 2: Discuss
Have an open, honest conversation about the root cause.
Once the real issue is identified, the team discusses it openly. Everyone contributes -- not just the loudest voices.
Ground rules for the Discuss phase:
- One person talks at a time. No cross-talk.
- Say it once. If you have made your point, do not repeat it. Repetition signals that you do not feel heard, so the facilitator should explicitly acknowledge contributions.
- Stay on topic. If a new issue arises, drop it to the Issues list and return to the current discussion.
- Be direct. EOS requires radical candor. Say what needs to be said, respectfully but honestly.
- No tangents. The facilitator keeps the discussion focused on the identified root cause.
WARNING
The Discuss phase is where most teams lose time. The facilitator must be willing to cut off tangents and keep the team focused. If a discussion exceeds 10-15 minutes without convergence, consider whether the issue needs to be broken into smaller pieces.
Step 3: Solve
Agree on a solution and assign action items.
The Solve step produces one of three outcomes:
- A To-Do -- A specific action item assigned to one person, due in 7 days.
- A Rock -- If the solution is too large for a To-Do, it becomes a Rock for the quarter.
- A decision -- Sometimes the solution is simply agreeing on a policy or direction.
The solution must be:
- Clear -- Everyone understands what was decided.
- Actionable -- Someone owns the next step.
- Measurable -- You can tell if it was done or not.
IDS in the L10 Meeting
The IDS segment occupies 60 of the 90 minutes in the L10 Meeting. Here is how it flows:
1. Prioritize
The team looks at the full Issues list and votes on the top three issues to discuss. Start with the most important one.
2. Work Through Each Issue
For each issue:
- Identify -- Clarify the root cause (1-2 minutes).
- Discuss -- Open conversation (5-15 minutes).
- Solve -- Agree on action, create To-Do or Rock (1-2 minutes).
3. Move to the Next Issue
Once an issue is solved, move it to the Solved list and start the next one. Continue until time runs out.
4. Carry Forward
Issues that were not reached remain on the list for next week. They are reprioritized at the next meeting.
TIP
Aim to solve 3-5 issues per meeting. If you are consistently solving fewer, your discussions may be running too long. If you are solving more, you are building great IDS muscle.
Common IDS Mistakes
| Mistake | Fix |
|---|---|
| Skipping Identify, jumping straight to Solve | Force the team to state the root cause before discussing |
| One person dominates the discussion | Facilitator calls on quieter members directly |
| Solving the symptom, not the cause | Ask "What is the real issue?" until you get to the root |
| No clear action item after solving | Every solved issue must produce a To-Do, Rock, or explicit decision |
| Carrying the same issue for weeks | If an issue keeps coming back, it has not been truly solved -- dig deeper |
| Trying to solve everything in one meeting | Focus on the top 3. Quality over quantity. |
The Issues List
The Issues list is a living document. Issues come from:
- Off-track Scorecard numbers
- Off-track Rocks
- Headlines that need discussion
- Items raised by team members between meetings
There are actually two types of issues lists in EOS:
- Short-term Issues -- Discussed weekly in the L10 Meeting. These are tactical.
- Long-term Issues -- Stored in the V/TO. These are strategic and addressed during quarterly or annual planning.
How EOS Hub Helps
EOS Hub's Issues feature supports the full IDS workflow:
- Issues list with priority levels (High, Medium, Low)
- Status progression: Open, Solving, Solved
- Direct creation of To-Dos from issue resolution
- Integration with the L10 Meeting IDS segment
- Creation of issues from off-track Scorecard numbers and Rocks
Related Pages
- Issues Feature -- Using IDS in EOS Hub
- Level 10 Meeting -- IDS is segment 6 of the L10 Meeting
- To-Dos Feature -- Where IDS solutions are tracked
- Six Key Components -- IDS is the tool for the Issues component