Our editorial perspective: Define the task that should change
We would start a technology trial with one specific task. Take an incoming enquiry: drafting a reply, deciding whether to make an exception and sending a binding commitment are different activities. A useful trial should name each one separately.
Describe which activity the tool will support and which decisions remain with a responsible person. Add who can correct an inaccurate result. That gives the team a concrete proposal to discuss before anything changes in the workflow.
Keep the first trial manageable
Our suggestion is a bounded trial with a named owner and an outcome you can check. Agree in advance which information may be used, when somebody must ask for help and what would cause the trial to stop.
Record more than the successful results. Include corrections, unclear answers and additional questions in the review. Ask the people doing the work to describe which tasks disappeared and which new tasks arose. Give them a straightforward way to report a problem while the trial is running.
Review how the team works together
For the next decision, we would bring together the person doing the task, the person accountable for it and the recipient of the result. Are responsibilities clear? Can the steps be followed afterwards? What needs to change before a wider rollout?
These are our editorial suggestions, not recommendations attributed to Alex. The interview belongs to its publication date; current product capabilities should be checked against current product information.