Before changing the workflow, make the unknowns discussable.
A practical way to discuss a proposed AI-assisted task without assuming how people feel or promising what the change will deliver.
Original workplace discussion material. No employee survey, personal experience or measured outcome is represented.
Give the discussion
something concrete.
A draft from approved notes
A summary could help the next coordinator see the current task and unresolved decisions.
A person reviews the handoff
The coordinator still checks the sources and decides what can become an action.
Where does review time come from?
Agree who checks the draft and how that work fits into the shift before trying the new process.
An example to discuss, not an account of a real team. Keep the existing handoff process available during an exercise.
Describe the task change in ordinary language
A broad announcement about adopting AI can leave people guessing about the work they will actually do. Start with a narrow description: which task would change, what information the proposed method would use and which decisions would remain with a person. A concrete example gives colleagues something they can question without having to accept or reject an entire technology category.
Imagine a fictional team considering draft summaries for shift handoffs. The proposal is to prepare a draft from approved notes, then have the next coordinator check unresolved decisions. That description still leaves questions about review time, source access and responsibility for corrections. Naming those questions is more useful than treating a polished demonstration as a complete working arrangement.
Distinguish an open question from a promise
Keep a short record of what is known, what is proposed and what has not been decided. If the team has not agreed who checks the summary, do not describe review as a solved part of the process. If no comparison has been made, do not promise that the new approach saves time. A discussion becomes harder when uncertain assumptions are presented as settled facts.
People may have different questions about the same proposed change. One person may ask whether the source notes are suitable to use; another may ask how checking a draft fits into an already busy handoff. Invite task-specific questions without asking colleagues to disclose private feelings or make public declarations of enthusiasm. The discussion aid here does not collect responses or infer anything about a person.
Agree how the team would learn and stop
Define a small, reversible exercise before making the proposed method part of ordinary work. Keep the existing handoff process available, state what would count as an unacceptable draft and name the decision that follows the exercise. A practical stopping condition might be that unresolved source conflicts are repeatedly hidden in the summary. That is a question about the work, not a judgement about the people reviewing it.
After the exercise, discuss the observed task, including any work moved to other people. Record unresolved questions and the next decision instead of forcing a single positive conclusion. This page supplies an illustrative conversation structure only. It cannot establish what a team needs, replace a workplace agreement or show that a particular change will be useful.