When employees worry about AI, a broad adoption statistic is unlikely to answer the question they are asking: what will change about my job, my work, and how decisions are made? Start with the actual proposed use and be clear about what has and has not been decided.
Name the Task Before Making a Promise
Drafting an internal checklist is different from sending customer messages automatically. Summarizing notes is different from evaluating staff. People need to know which task is under discussion before they can give useful feedback.
Do not promise that nothing could ever change if that is not something you can guarantee. Explain the limited use you are considering, who will review the result, and what would make you stop or change it.
Keep People in the Review
The employee who does the task may be best placed to spot an incorrect answer or an awkward extra step. Let that experience count. A draft that looks impressive to someone outside the job can still create more work for the person responsible for finishing it.
Agree on who can approve, send, publish, or change information. Make it clear when the AI is producing a suggestion and when a person is making the decision. Do not assume a tool’s default permissions match your expectations.
Check the Workload, Not Just the Demo
Try a limited, appropriate example and compare the whole task: preparing the information, checking the answer, correcting it, and using it. Faster first drafts do not automatically mean less total work.
Ask what became easier, what became harder, and whether anything important was missed. Those observations are more useful for this decision than a percentage from another group of businesses.
Give People Room to Learn
Someone may be comfortable with the job and unfamiliar with the interface. That is a training need, not proof they cannot learn. Use a familiar example, explain unfamiliar terms, and avoid making every advanced feature part of the first attempt.
Account permissions and business information need care too. Make sure the person responsible for those decisions approves any new connection or use of restricted material before it is enabled.
Personal Help Has a Defined Scope
An ai1on1 session can help you understand the software and work through a setup or problem. It does not determine staffing decisions or replace the conversations you need to have with your team. Use it for the part where personal technical guidance would help.
Questions Worth Asking
Can a survey prove AI will not affect any jobs here?
No. Your decisions and the particular work matter. Do not use a survey as a guarantee about your own business.
What is a reasonable first trial?
Choose a limited task with an output the person doing the work can review, and compare the entire effort, including corrections.
Does everyone need advanced features immediately?
No. Start with the relevant basics and add features only when there is a clear purpose.
Related reading: who should actually own this decision in a small business · what to do when even the people at the top disagree about it.
Want help understanding a feature before you explain it to your team? Jeremy can guide you through your chosen tool during paid message help. See paid message help at ai1on1.com — $150 for the first hour.