Leaders often bring broad, emotional complaints to the Issues List right at meeting time, forcing the team to spend valuable IDS minutes untangling vague venting into a real problem. How can we use an asynchronous intake protocol or AI prompt before the meeting to force clear issue definition?

Question

Tyler Smith · Accepted Answer

When an issue is added to the list as an emotional fragment like Ops communication breakdown or Sales is dropping the ball, the team burns fifteen minutes of IDS® just figuring out what is actually broken. Identify should uncover the root cause, not decipher a vague complaint.

You can enforce pre-meeting clarity by requiring leaders to run their issues through a structured three-sentence framework before adding them to the agenda:
- Sentence one: The objective fact of what occurred.
- Sentence two: The specific operational or financial consequence to the business.
- Sentence three: The exact decision or support needed from the leadership team.

AI tools can automate and sharpen this discipline between weekly pulses. Create a dedicated team prompt or internal assistant where a leader can paste their raw, messy frustration. The AI is instructed to strip away emotional venting, identify missing factual data, and output a clean, single-sentence issue statement along with the relevant seat on the Accountability Chart.

If a leader cannot state what happened, the financial impact, and who owns the seat, the issue is not ready for the Level 10 Meeting™.

By using an asynchronous intake protocol supported by AI filtering, issues arrive at the meeting already distilled down to objective reality. The leadership team bypasses initial defensive confusion and moves directly into identifying root causes and locking down decisive To-Dos.