Check the answer.Keep privatethings private.
Four weeks for anyone who has started using AI at work, or is about to. What it is good at, how to catch it when it is wrong, what never goes in the box, and how to point it at the inbox they already live in.
What is in it.
Getting a useful answer
What it is good at, and what it is not
Checking it before you send it
Catching a confident wrong answer
What never goes in the box
Names, records, payroll, contracts
Connecting it to your inbox
Claude or Copilot, Gmail or Outlook
Claude or Copilot,Gmail or Outlook.
Whichever your company already licenses. The habits are the same either way, and your team learns them on their own account.
A confident answeris not a correct one.
Three questions, in this order. Any no and you ask again with the file attached — which is the move most people never learn.
Describe it.Don’t paste it.
Names, records, payroll and signed contracts stay out. Nearly everything else is fine, and the swap costs a second.
The test, at the moment you are about to paste
Fine
- A public spec sheet
- Your own draft, before it goes out
- A policy anyone in the building can read
- Numbers with the names taken out
Never
- A customer's name, address or file number
- A payroll line
- A contract you were not cleared to share
- Anything out of a health or HR record
The swap
When the answer is never
Describe it, don’t paste it. “A customer in Ontario, two invoices overdue” does the same work as their name.
Ten hours,and a page they keep.
Short modules watched when it suits, one live hour on your own tools, and a page your team writes at the end.
Asked beforeevery cohort.
No. Week one starts from what it is and what it is not. If half the room already uses it daily they still get the checks, which is the part almost nobody has.
Book a call.
Start with the map of your organization, or with the one job that hurts. Measured in hours and money, and everything we build stays yours.