Train around roles and tasks
A finance manager, customer-service adviser and operations lead have different needs. A generic demonstration may introduce the possibilities, but it rarely shows exactly how each person should change their work. Begin with tasks that staff already perform. For example, practise structuring a management summary, preparing a response from approved information or turning meeting notes into a draft action plan. Use suitable sample information for training.
Teach judgement as well as prompting
The useful skill is knowing what to ask, what context to supply and how to evaluate the answer. Staff should learn to recognise unsupported statements, check source material and decide when a task needs a different approach. A fluent output can still contain errors. Make verification part of the exercise: participants should explain how they would assess the result before using it.
Set clear boundaries
Teams need practical rules about approved tools, confidential information, customer data and external communications. Explain who can approve a new use case and who handles uncertainty. Avoid relying on a long policy document that nobody connects to daily work. Give staff realistic examples of what they may use, what needs permission and what should be escalated. Align those examples with the organisation’s actual tools and controls.
Give leaders a different conversation
Leaders need clarity on priorities, investment, risk and accountability. Their training should help them ask useful questions about proposed projects and recognise the difference between a demonstration and operational evidence. They should understand what users need from them: time to practise, clear ownership and support for changing processes. Leadership engagement is most useful when it creates those conditions, rather than simply endorsing a new tool.
Support practice after the workshop
Create a small set of reusable task examples and provide a place to ask questions. Identify colleagues who can share useful workflows and feedback, while keeping IT and security responsibilities with the appropriate owners. Microsoft’s Copilot Skilling Center separates resources for leadership, users, technical roles and adoption champions. That role-based structure is a useful reference, even when your business uses other platforms.
Measure useful adoption
Attendance and logins tell you that people participated, not that the work improved. Revisit a few selected tasks after training. Are outputs more useful? Are staff checking them appropriately? Does the process take less time overall, including review? Where use is low, ask whether the task, access or guidance is wrong before assuming people are resistant. Use the feedback to adjust the programme.
How AiQ helps
AiQ’s training and enablement work combines leadership briefings with practical, role-based workshops. We help teams explore tools such as Copilot, ChatGPT, Gemini and Claude in the context of their work, with safe-use guidance and adoption priorities. The goal is confident, considered use that supports your business, rather than a collection of impressive prompts. Begin with the roles and recurring tasks you want to improve.