AI training or setup help: which does your team need first?

Choose help for the obstacle you have

Start with training when staff have the information and tools but do not know how to ask for a useful draft or check it. Consider setup help when each task needs the same instructions, approved material or template prepared again. Consider a connected workflow when the difficulty is moving work between people and systems. These are practical starting points, not a requirement to buy all three.

Try one small practice task

Imagine preparing a short customer update from approved job notes. Use harmless sample notes in a tool your business permits. Ask for three sentences, name the intended reader and say which facts may be used. Microsoft describes a Copilot prompt through its goal, context, source and expectations. For this proposed exercise, a job aid might say: draft a friendly update from these notes; do not add dates, prices or promises that are absent. The output is a draft for staff review, not a sent email.

Prompt components checked October 10, 2026. The job-update exercise and buying comparison are proposed examples, not client results. Microsoft: getting started with Copilot prompts

Notice where the task breaks down

Have a colleague repeat the exercise with a complete example, an example missing a completion date and one containing conflicting notes. If they need coaching to give instructions or check unsupported statements, training addresses that gap. If they cannot find the approved notes or keep rebuilding the same template, investigate setup. If the reviewed update then gets lost between the office and the job record, investigate that handoff separately. An AI lesson cannot fix unclear source records.

Ask for something staff can use afterwards

A focused training scope could include guided practice, a one-page job aid and a follow-up check using a new example. A setup scope could include reusable instructions, an agreed source location, a draft template and a named reviewer. Ask the provider to explain which of these you receive and what staff still do manually. Keep the first version to one task; a general demonstration does not establish that your team can repeat it independently.

Confirm the tool and the checking step

Check the exact account, available features and permitted information before choosing a course or setup. Microsoft says Copilot sources can depend on the account and advises checking responses; repeated prompts can produce different answers. Do not assume a practice exercise grants access to work files or installs an integration. For the sample update, staff compare the draft with the approved notes and decide whether it is ready to send. Keep a manual route for work that does not fit.

Supports account-dependent sources, checking responses and variation between repeated prompts. Your actual setup and access still need confirmation. Microsoft: account-dependent sources and response review

Measure whether the help is useful

Suppose four updates take twelve minutes each to prepare and check: forty-eight minutes a week. After a pilot, assume seven minutes each plus six minutes maintaining the job aid: thirty-four minutes, releasing fourteen minutes of staff capacity. Count an initial ninety-minute training session separately, along with setup fees and any subscriptions. These are illustrative assumptions, not measured savings. Track corrections and whether staff actually use the job aid before paying to expand the project.

Want help putting this to work?

This guide applies across Canada. We provide remote AI consulting for businesses in Ottawa; it does not describe a local client or a staffed office.

AI help in Ottawa · See how we can help · View pricing and scope