We have implemented an AI transcription tool for our client meetings, but now our team is raising issues about data accuracy and client pushback during our weekly Level 10 Meetings. How do we use the IDS process to solve these operational friction points?

Question

Tyler Smith · Accepted Answer

When operational friction points arise around new technology, you must handle them with the same discipline you use for any other business issue. Do not let team frustration turn into a general rejection of the AI tool.

During your weekly Level 10 Meeting, place these complaints on the Issues List. When you get to the IDS portion of the meeting, start by identifying the root cause. Ask tough, incisive questions to determine if the issue is a software limitation, a training gap, or a lack of clear client communication.

For the client pushback issue, the root cause is usually a lack of transparency. Solve this by establishing a standard, upfront script for your team. Have them explain to the client that the tool is being used to capture exact details so the team can focus entirely on the conversation rather than taking notes.

For the data accuracy issue, the root cause is often a lack of human oversight. Solve this by clarifying the role on your Accountability Chart. Reiterate that the human is always the final editor. The AI output must be treated as a draft that requires verification before any action is taken. Once you agree on these solutions, assign clear to-dos to your team members and review their completion next week to ensure the issue is solved permanently.