During IDS, our team habitually jumps straight into proposing solutions within thirty seconds of an issue being read, which leads to implementing band-aids that fail and reappear on the Issues List three weeks later. How does the facilitator strictly separate the Identify step from the Solve step?
Most leadership teams suffer from premature resolution. They spend five seconds identifying an issue, five minutes discussing symptoms, and fifty minutes debating competing tactical fixes for the wrong problem. When an issue resurfaces week after week, you did not solve it; you merely agreed on a temporary patch.
The facilitator must treat the Identify (I) phase as an absolute gate. No one is permitted to discuss solutions until the root cause is stated in one clear, concise sentence agreed upon by the entire room.
When someone puts an issue like Customer onboarding is too slow on the board, do not ask how to speed it up. Dig into the root cause by asking why three to five times. Is onboarding slow because the software is broken? Because sales overpromises features? Or because the customer success manager lacks clear standard operating procedures?
If someone offers a solution during this phase, the facilitator must call it out: That is a Solve. We are still in Identify. Hold your solution.
Once the true root cause is identified, the discussion (D) phase should be brief and focused entirely on options to eliminate that cause. The solve (S) phase is simply agreeing on who owns the specific one-week To-Do to fix it. True IDS requires discipline. Spend seventy percent of your time identifying, twenty percent discussing, and ten percent solving.
Category: Level 10 Meetings