Skip to content
Menu
Plan a session

After training

Making it stick: adoption and prompt habits

A good session produces a burst of enthusiasm. What turns that into normal practice is boring and simple: someone to ask, a place for prompts that work, and a manager who asks about it.

The first month

  1. W1

    Use it on the two tasks

    Each person uses Copilot on the two tasks they chose in the session, every time those tasks come up, and notes where it helped and where it did not.

  2. W2

    Share what worked

    Good prompts go into a shared list: a OneNote page, a Teams post or a Word document. Include who wrote it and what to check.

  3. W3

    Fix the blockers

    Usually one or two things: a feature that needs a setting, a permission that blocks a useful file, or confusion about what may be sent to clients.

  4. W4

    Check in

    A short follow-up session to answer questions, look at the shared list and decide who else should get a licence or a session.

Champions, not police

A champion is someone in each team who uses Copilot a lot and is happy to be asked. They are not there to measure usage or tell people off. In a small business the champion might be the owner; in a larger one, pick someone in each team rather than one person for the whole organisation. Give them a little time each week to answer questions and tidy the shared prompt list.

How to tell whether it is working

Usage reports exist, and an admin can see them, but the useful measures are closer to the work. Ask each team two questions a month after the session: which tasks are now faster, and which outputs did you have to correct? If the first list is growing and the second is shrinking, it is working. If nobody can name a task, the session did not connect with real work, and another short session on specific tasks is a better fix than more licences.

Be wary of reporting time saved as a precise number. People are poor at estimating it and the figure tends to grow with each retelling. A plain description (“meeting notes go out the same day instead of the next week”) is more honest and more persuasive.

Prompt habits, by role

These are illustrative prompts written for common roles. They are starting points; the version that works best is the one a person has edited for their own work.

Example prompts by role and what to check
RoleExample promptAlways check
Office managerUsing the attached supplier invoices, list each supplier, invoice number, amount and due date in a table, and flag any due in the next seven days.Totals and due dates against the invoices.
Sales or account managerSummarise everything this client has asked for in the last month across email and meetings, and list what we still owe them.Anything promised that is not on the list.
Team leaderFrom this week’s meeting recaps, list the actions assigned to my team, who owns each and the due date.Owners, because recaps can misattribute.
Practice or operations leadRewrite this procedure for a new starter on their first day, in numbered steps, under 300 words. Keep every safety step.That no step has been dropped or reordered.
Bookkeeper or financeExplain what the formulas in column F are doing, in plain English, and suggest a simpler version if there is one.The new formula against several rows by hand.

Habits that separate regular users from occasional ones

They keep prompts

A prompt that worked once goes somewhere it can be found again. Re-typing from memory produces a worse version each time.

They argue with it

“That’s not right, the date is the 14th” or “too formal”. Correcting a draft is faster than writing a better prompt from scratch.

They know when to stop

If three rounds of correction have not produced something usable, they write it themselves. Some tasks are faster by hand, and that is fine.

They say where it came from

When a summary or draft is shared internally, they mention it was Copilot-assisted and checked. That keeps the team’s trust calibrated.

They keep client data in the work account

No pasting client details into a personal chatbot because it is quicker. That is the rule people break most, and the one that matters most.

They tell someone when it fails

A wrong answer reported to the champion becomes a lesson for the whole team. A wrong answer quietly fixed teaches nobody.

When to add more training

Three signals: new staff who missed the first session, a new capability that changes a common task (Microsoft releases features often), or a team that never really started. A shorter session focused on one app or one team’s tasks usually does more than repeating the full half-day.