When we run our weekly Level 10 Meeting and dive into the IDS process to solve our biggest operational issues, we are tempted to feed our issues list into an AI to generate solutions. What parts of resolving these issues must stay strictly human to avoid eroding trust?

Question

Tyler Smith · Accepted Answer

Feeding an issues list into an AI can generate a list of generic solutions, but it completely bypasses the real work of IDS. The Identify, Discuss, and Solve process is not a search for theoretical answers. It is about alignment, healthy conflict, and shared commitment among human leaders.

AI cannot feel the tension in the room. It does not understand the unwritten dynamics, the history between two team members, or the subtle fear that keeps someone from speaking up. When you outsource the Discuss phase to a machine, you rob your team of the opportunity to build trust through healthy conflict. You end up with a list of textbook solutions that nobody actually owns or believes in.

Keep AI completely out of the IDS process itself. You can use AI before the meeting to gather clean data, analyze financial patterns, or organize customer feedback. But when the leadership team sits down to solve the issues, the work must be entirely human. The solutions must come from the heads and hearts of the people who are accountable for executing them. True operational health is built on vulnerable conversations, not clever prompts. If your team cannot openly discuss the root cause of an issue, no technology on earth will save your culture.