EOS IDS in practice: teams solve 3 of 8 L10 issues
We followed 2,266 issues through the IDS segment of 300 real L10 meetings to see which ones teams solved and where the time went.
Independent research by TenTenor. Not affiliated with or endorsed by EOS Worldwide.
IDS fills most of an L10: the team identifies an issue, discusses it and solves it. Our study of 1,000 L10 meetings measured how much time teams give it. This study looks at what they get out of that time.
TenTenor’s analysis records how long a team spent on each issue in IDS and how the issue ended. We took a random sample of 300 L10 meetings held in September 2026 and followed their 2,266 issues. We count an issue as solved when the team made a decision that resolves it and named an owner. Sending someone off to look into it counts as discussed.
The typical meeting raised eight issues and solved three.
- 3 of 8issues solved in a typical L10
- 1 in 5minutes of the L10 attributed to unresolved discussions
- 3×the solve rate when the team named the root cause
Unresolved issues took as long as solved ones
We could attribute about a fifth of total meeting time to issues that remained unresolved. These discussions typically lasted as long as those that ended in a resolution.
Share of all meeting time, by how each issue ended. The rest of the meeting covers the other agenda sections and any IDS time not counted on a timed issue, such as issues without a recorded time. Passed on means routed to the right owner or escalated to a leadership meeting.
Show the numbers
| Meeting | Issues solved | Discussed, unresolved | Tabled, passed on or only raised | Rest of the meeting |
|---|---|---|---|---|
| 90-minute L10s | 28% | 25% | 7% | 40% |
| 60-minute L10s | 26% | 17% | 6% | 51% |
Tabling an issue or routing it to the right owner took less than half as long as discussing an issue that remained unresolved.
Critical issues got the most time and the fewest decisions
The analysis rated each issue’s impact on the business. Teams spent a median two minutes on a low-impact issue and solved half of them. A critical issue took a median 12 minutes, and teams solved one in five.
A team that can’t solve a critical issue in one sitting can still decide the first step and who takes it.
Share of issues solved by the impact the analysis assigned. Median discussion minutes per issue in brackets.
Show the numbers
| Impact (median minutes) | Issues solved |
|---|---|
| Low (2 min) | 51% |
| Medium (4 min) | 43% |
| High (7 min) | 42% |
| Critical (12 min) | 21% |
Teams solved three times as often when they named the root cause
Share of issues solved, by whether the team identified the root cause.
Show the numbers
| Root cause | Issues solved |
|---|---|
| Named | 58% |
| Not named | 18% |
Naming the root cause was associated with a higher solve rate. This doesn’t establish cause and effect: the same analysis assessed both.
Three things to try in your next IDS
- Give each issue a time box. When the time runs out and no decision is in sight, table the issue or give someone a To-Do to bring back a proposal.
- Name the root cause first. Ask what the real issue is before anyone proposes a fix. If the team can’t agree on the cause, make finding it the To-Do.
- Close each issue out loud. Say whether it is solved, tabled or passed on, and who owns it. Share plain updates in headlines and keep IDS for issues that need a decision.
TenTenor tracks how each IDS issue ends for your team, so you can see which ones keep coming back.