Our team wants to use AI meeting bots to transcribe our Level 10 Meetings and automatically generate action items, but it seems to make people self-conscious during IDS and creates massive unvetted task lists. What is the operational rule for using AI tools inside the weekly pulse?

Question

Tyler Smith · Accepted Answer

Bringing automated AI transcription bots into an executive Level 10 Meeting usually does more harm than good. While AI is transformative for automating operational workflows and drafting documentation, dropping a recording bot into an executive problem-solving session destroys the psychological safety required for radical candor.

When leaders know every tentative idea, blunt critique, or tense disagreement is being captured verbatim in a searchable corporate transcript, they self-censor. Candor vanishes. Instead of digging into the root causes of business breakdowns during IDS, executives choose diplomatic language to protect themselves. Furthermore, AI transcription bots routinely flag every casual conversational remark as an action item, producing a bloated list of twenty low-value tasks that destroys the discipline of 7-day To-Dos.

The operational rule is clear: keep recording bots out of the leadership team Level 10 Meeting. The weekly pulse requires absolute presence, confidentiality, and active listening. Documentation should remain manual and lean, captured by a designated scribe who logs only three things: off-track Scorecard metrics, off-track Rocks, and clear, binary To-Dos agreed upon during IDS.

Use AI outside the meeting to help team members execute their individual To-Dos or build out systems. Keep the 90-minute weekly pulse human, confidential, and focused entirely on solving problems.