Free Bookkeeping Evaluation. Free Classes Every Friday. Free Compliance Checks. Free SEO Audits
All Ops Tools
EOS Tool

IDS

Also known as: Identify · Discuss · Solve

The three-step issue resolution method that turns the L10 Issues List into actually-solved problems. The hour in your week where real work happens.

What It Is

IDS is what happens during the 60-minute IDS block in the L10. It's the EOS method for working through the Issues List:

Identify: Get clear on the REAL issue, not the symptom that landed on the list. Often this is the longest of the three steps.

Discuss: Everyone weighs in once. Honest disagreement is welcomed. Then you stop, with no looping back to the same point twice.

Solve: Pick a concrete next action, name a single owner, and set a deadline. Drop it to the To-Do list or assign a Rock if it's bigger.

When To Use It

Every L10. The Issues List should never be empty going into IDS; if it is, something's wrong with the surface-and-name step earlier in the meeting.

Use IDS outside the L10 when an ad-hoc decision needs structure, particularly when you can feel a meeting starting to circle. Naming the steps out loud ("OK, are we still on Identify, or are we discussing?") usually unstucks the room.

How Launch Uses It

For new EOS adopters, we facilitate IDS for the first several weeks because the discipline of "no looping" is genuinely hard to learn. Most leadership teams have years of habit running in the other direction.

We coach explicit "park it" language: when a non-issue masquerades as the issue, name it ("Sounds like the real issue is X, not Y") and move the surface-level item back to the list. We also coach on root-cause work: the issue you Identify is usually not the issue someone wrote on the list.

Tips

  • Hardest issues first. The ones the team most wants to avoid are the ones IDS most needs to work on.
  • Time-box Discuss. If a single issue has been discussed for 12 minutes without resolution, park it and move on.
  • Every Solve has an OWNER and a DUE DATE. 'The team will look at this' is not a Solve.
  • If an issue keeps coming back, the Solve was wrong, not the issue. Re-IDS the same issue.

Pitfalls To Avoid

  • Trying to fix the symptom instead of the issue. Spend extra time on Identify before moving on.
  • Letting one person dominate Discuss. The facilitator's job is to make sure everyone weighs in once.
  • Compromise solutions designed to make everyone slightly unhappy. Pick the best answer, not the diplomatic one.
  • Solving without naming an owner. Issues without owners come back next week unchanged.

Template

IDS: Worksheet

Date

 

Facilitator

 

Attendees

 

Issue #1

Symptom (as written on the Issues List)

 

I: Identify (the real issue)

 

D: Discuss (perspectives, data, options)

 

S: Solve (concrete action)

 

Owner

 

Due

 

Issue #2

Symptom (as written on the Issues List)

 

I: Identify (the real issue)

 

D: Discuss (perspectives, data, options)

 

S: Solve (concrete action)

 

Owner

 

Due

 

Issue #3

Symptom (as written on the Issues List)

 

I: Identify (the real issue)

 

D: Discuss (perspectives, data, options)

 

S: Solve (concrete action)

 

Owner

 

Due

 

Issue #4

Symptom (as written on the Issues List)

 

I: Identify (the real issue)

 

D: Discuss (perspectives, data, options)

 

S: Solve (concrete action)

 

Owner

 

Due

 

Need help running this with your team?

Operations consulting from Launch Industries can lead, facilitate, or co-pilot any of these tools alongside your team.

Book a call