How should leadership teams use AI as a tool during the IDS portion of their weekly Level 10 Meeting without slowing down the decision-making process?

Question

Tyler Smith · Accepted Answer

The IDS (Identify, Discuss, Solve) portion of your Level 10 Meeting is designed to resolve issues quickly and decisively. The key is to prevent AI from becoming a distraction or a reason to delay decisions. If your team uses AI to research every minor detail during the meeting, you will inevitably lose momentum and fail to solve your issues.

Strategic AI Use in IDS

Instead, use AI selectively as a fast information synthesizer when your team encounters a roadblock. Here's a structured approach:

• Identify a knowledge gap: If you are debating an issue and truly lack crucial context, such as historical data, industry benchmarks, or a summary of best practices, consider a quick AI query.
• Designate a query person: Have one team member responsible for quickly querying an AI tool. This prevents multiple people from getting sidetracked.
• Time-box the query: This lookup should take no more than sixty seconds. The goal is to gain just enough information to make an informed decision, not to achieve absolute perfection.
• Focus on 'good enough' data: This approach aligns with a middle Fact Finder conative style, where you gather sufficient data to act without falling into analysis paralysis. For more on how conative profiles can impact decision-making, see [how AI can analyze team conative profiles](/qa/analyze-kolbe-indexes-with-ai-project-teams).

Complex Issues and Follow-Up

If an issue proves too complex for a quick lookup:

• Assign as a To-Do: Instead of getting bogged down, assign it as a To-Do for a specific team member.
• Research outside the meeting: This individual can then use AI tools to research the issue thoroughly outside of the Level 10 Meeting.
• Bring recommendations back: They should bring their findings and recommendations back to the team for discussion at the next meeting.

The primary focus of your Level 10 Meeting should always remain on healthy discussion and decisive action, rather than exhaustive research. For example, ensuring your [Scorecard metrics are reviewed efficiently](/qa/how-to-review-scorecard-under-five-minutes) can also help maintain meeting momentum. If your team struggles with defensive behaviors when discussing metrics, consider [how to use the Accountability Chart to stop the blame game](/qa/using-accountability-chart-to-stop-blame-in-ids).

Related questions

• [How do we review our weekly scorecard in under five minutes?](/qa/how-to-review-scorecard-under-five-minutes)
• [How can we analyze our team conative profiles or Kolbe Indexes using AI to build a more effective project team for a major operational shift?](/qa/analyze-kolbe-indexes-with-ai-project-teams)
• [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)
• [How does AI assist in identifying and mitigating risks for businesses undergoing exit planning?](/qa/how-does-ai-assist-in-identifying-and-mitigating-risks-for-businesses-undergoing-exit-planning)
• [I have a visionary leader who wants to automate everything with AI tomorrow, but my Integrator is a high Fact Finder who is stalling the roll-out. How do we use conative profiles to get our AI strategy back on track?](/qa/kolbe-profiles-ai-visionary-integrator)