People issues stall in IDS because the Discuss step runs on opinion, not evidence. When you can see a person’s actual capacity behavior — initiative, follow-through, learnability — Identify gets specific, Discuss gets shorter, and Solve actually sticks.
The issue lands as a personality problem — who annoys whom — instead of a capacity gap you can actually name and close.
“I think Sarah’s stretched too thin.” “No, she’s fine.” With no data, the loudest voice wins and nothing is settled.
The team agrees to a vague commitment nobody can check next week — so the same issue is back on the list.
IDS — Identify, Discuss, Solve — is the right tool. It just struggles on people issues when every step runs on how the room feels rather than what a person is actually doing. Here is what behavioral capacity data adds to each step.
Name the specific capacity gap — initiative, follow-through, or learnability — not “attitude.” Behavioral data makes the problem concrete instead of a label.
Compare observed behavior over weeks, not competing anecdotes. Evidence shortens the argument because there is less to argue about.
Set a measurable behavioral change with one owner, and actually re-check it at the next Level 10 instead of re-litigating the whole thing.
This is the same distinction the Capacity letter in GWC runs into: the moment the read stops being a hunch and starts being behavior over time, the argument gets a lot shorter.
A people issue is solved when it stays off the Issues List, not when the room stops talking about it. Work it as a checklist:
In EOS, a people issue is any Issues List item about a person rather than a process or a number — the wrong person in a seat, someone who isn't Getting it, Wanting it, or has the Capacity for the role, or a recurring performance or behavior gap. It gets worked in the Level 10 meeting with IDS: Identify, Discuss, Solve.
Because the Discuss step runs on opinion, not evidence. The team argues who thinks what about a person, no one can settle it, and the Solve ends up being a vague commitment nobody can verify. Next week the issue is back on the Issues List because it was never actually solved — only re-described.
IDS stands for Identify, Discuss, Solve. Identify names the real problem, Discuss surfaces everything relevant, and Solve sets the action. For people issues, each step gets sharper with behavioral data: Identify names a specific capacity gap instead of “attitude,” Discuss compares observed behavior instead of anecdotes, and Solve sets a measurable behavioral change you can check.
Separate a capacity gap from a values or fit problem, state the issue as an observable behavior rather than a label, bring data instead of the loudest anecdote, assign one owner and a measurable follow-through, and re-check it at the next Level 10 rather than re-litigating it. A solve that can't be verified next week isn't a solve.
Yes. A Prove cycle scores Initiative, Applied Grit, and Learnability from roughly six weeks of real behavior, so the capacity question in a people issue becomes evidence instead of a hunch. That gives your Level 10 a shared read of what a person is actually doing over time — which is exactly what a circular Discuss is missing.
Want the mechanics? See how to measure capacity in EOS, or start from the For EOS hub to see where Prove fits alongside your toolset.
Prove works alongside EOS® and is independent of, and not affiliated with or endorsed by, EOS Worldwide. EOS®, Level 10™, IDS™, GWC™ and People Analyzer™ are trademarks of their respective owners. Prove complements the EOS toolset — it does not replace it.
Book a call to see how Prove gives your Level 10 the capacity evidence a real Solve needs.