Helping Your Team Work Better With AI
Updated
An AI rollout changes people’s work. Employees deserve a clear explanation of what is changing, who makes the decisions, and how their feedback will shape the result.
The useful starting point is a task your team wants help with. Ask the person who handles the inbox or prepares the weekly report where the repetition is, what goes wrong, and what they would rather spend that time doing.
Give people a concrete starting point
“Use AI to be more productive” is not much of a brief. “Prepare a first draft of this routine reply using our approved service information” is something a person can try and evaluate.
Choose an ordinary task with a visible result. Let staff compare the draft with their existing method and explain what they changed. Keep examples of good work so the team has a shared standard.
Make the source easy to inspect
An answer about a policy is more useful when an employee can see the policy it came from. Keep documents current, name the owner, and separate internal information from material customers are allowed to see.
For a reporting workflow, preserve links to the underlying figures. Ask the assistant to distinguish a recorded fact from a possible explanation. A plausible story about a sales dip should not become a management decision without checking the data.
Design review as real work
Give reviewers enough time and authority to reject output. A queue that rewards approving everything quickly is a weak control, even if it technically includes a person.
Our recommendation is to define a short checklist for each task. For a customer reply, that might be the correct recipient, accurate price, relevant policy, and clear next step. For a report, it might be the date range, source totals, and missing records.
Use a separate route for sensitive complaints, personnel matters, and decisions outside the assistant’s scope. Staff should know who owns each exception.
Measure workload as well as output
Track editing time, rejected drafts, escalations, and customer corrections. Ask whether the tool makes the job easier or simply shifts effort from writing to checking.
Do not use the number of prompts someone sends as a measure of their contribution. People have different tasks, and a sensible decision not to use AI can be valuable. A short pilot with candid feedback is more informative than a company-wide usage target.
Keep learning after launch
Vendor features and models change. Save a small set of representative examples and recheck the workflow when its tools, instructions, or source documents change. Anthropic’s guidance on effective agents supports simple designs and increasing complexity only where it helps.
Selser Media’s implementation service includes documentation and training so staff understand the workflow and its limits. Request a free consultation and bring the person who does the work into the conversation.