During the IDS portion of our Level 10 Meeting, our leadership team frequently gets stuck in analysis paralysis, agreeing on the root cause of an issue but refusing to solve it because they want to collect more data first. How do we push past this stalling tactic?

Question

Tyler Smith · Accepted Answer

Analysis paralysis during the IDS® (Identify, Discuss, Solve) portion of your [Level 10 Meeting™](/qa/rein-in-level-10-meeting-segue) is a significant source of meeting waste. Teams often use the desire for more data as a shield to avoid making difficult decisions or confronting conflict. This delay stalls traction and slows down your entire organization.

Overcoming Analysis Paralysis

To break this stalling tactic, the facilitator must enforce a bias for action. While some complex issues genuinely require additional information, eighty percent of the issues on your list can and should be resolved in the room using the collective intelligence of the team. This is crucial for maintaining momentum and achieving the ultimate goal of [solving issues permanently](/qa/using-accountability-chart-to-stop-blame-in-ids).

Techniques to Force Resolution

When your team begins to loop on an issue, use these techniques to force a resolution:

• Define success: Ask the owner of the issue to clearly define what a successful outcome looks like in one concise sentence. This helps narrow the focus and clarifies the objective.
• Prioritize good over perfect: Remind the team that a good decision made today is far better than a perfect decision made next month. Excessive waiting for perfect data often leads to missed opportunities.
• Assign data collection: If data is truly missing, create a weekly To-Do for one specific leader to gather that exact data point and bring it to the next meeting. This moves the issue off the table immediately and ensures focused action. Avoid broad requests for "more research."
• Empower accountable leaders: Use the leader-leader model to empower the accountable department head to make the call right then, rather than seeking unanimous consensus from the entire group. This leverages the [Accountability Chart](/qa/resolving-accountability-chart-seat-overlaps) and promotes quicker decision-making.

By refusing to let the team hide behind requests for more research, you foster a culture of decisive leadership. Speed of resolution is key to maintaining momentum in your [Level 10 Meetings](/qa/should-integrator-facilitate-level-10-meetings) and throughout your business.

Related questions

• [How do we review our weekly scorecard in under five minutes?](/qa/how-to-review-scorecard-under-five-minutes)
• [When an issue is dropped to IDS, my leadership team immediately starts pointing fingers at other departments rather than taking ownership. How do we use the Accountability Chart to stop the blame game during meetings?](/qa/using-accountability-chart-to-stop-blame-in-ids)
• [Our Integrator acts as the Level 10 Meeting facilitator but struggles to participate objectively because they are busy managing the timer and the agenda. Should we rotate the facilitator role or hire an outside moderator?](/qa/should-integrator-facilitate-level-10-meetings)
• [My leadership team is struggling to agree on what actually deserves a spot on our high level scorecard. How do we narrow down our massive list of metrics to just five to fifteen numbers?](/qa/how-to-choose-five-fifteen-scorecard-metrics)
• [Our weekly segue during the Level 10 Meeting consistently runs fifteen minutes late because my leadership team uses it to share long-winded personal life updates. How do I rein in the segue without killing team culture?](/qa/rein-in-level-10-meeting-segue)