Start here
In about thirty minutes, you will build a voice profile, test AI on work you already finished, watch it fail safely, and use it on one real task.
You have probably been told, in the same week, that AI will transform your job and that it's overhyped autocomplete. Both things are being said by people who want something from you, and neither is much help on a Tuesday when you have an outcomes report due.
This introduction gives you a more useful starting point: what AI does well, where it fails, and the workflow that keeps it useful.
What these things actually are
A large language model is trained on large amounts of text and other data, then generates tokens based on patterns in that training and the context you provide. It is a compact explanation, but it is enough to understand the central risk.
Because it learned from how people write, it's very good at shape. The structure of a document, the tone, the rhythm of a professional email, turning notes into prose. And because it's predicting plausible text rather than looking up verified facts, it can be unreliable with facts. It may produce a polished citation that does not exist, and present incorrect and correct claims in the same fluent style.
That's the whole idea. There isn't a deeper layer you're missing, and you don't need to know how it works inside any more than you need to know how a search index works to search well.
A common early pattern
Many people move through some version of this pattern. Recognizing it can help you treat a disappointing result as a workflow problem to diagnose, not a final verdict on the technology.
Week one feels uncanny. You ask it something and it answers fluently. It feels like a big deal. You tell a colleague.
Week two is a letdown. You give it real work and get back something generic, faintly corporate, and wrong in one important place. You decide it doesn't understand your field and quietly stop. This is the point where a better workflow matters.
Week four is useful, if you get that far. Not because the tool changed, but because you did. You stopped asking it to know things and started asking it to do things with material you supplied. That's the entire shift, and it's what this handbook is for.
Your first twenty minutes
Do these four in order, right now, in whichever tool you have. The third one is designed to fail on purpose.
Make it sound like you. 5 minutes.
Open your sent folder. Choose three ordinary emails with no sensitive content, then remove names, dates, project details, signatures, and contact information before using them:
Here are three emails I've written. Describe my writing voice back to me: how I open and sign off, sentence length, how direct I am, how formal I am, and what I never do. Then turn that into a short set of instructions you could follow to write in my voice. [paste three emails]
Save what it gives you. That's your voice profile, and it's the most reusable thing you'll make today. It goes at the top of every writing request from now on.
Give it something you already finished. 5 minutes.
Take a document you completed and were reasonably happy with. Ask:
Name the three weakest things about this document. Don't tell me what works. Assume a doubtful reviewer who thinks it overstates its case. What do they go after first? [paste your document]
You're not hoping it is right. You are testing whether any criticism helps you see the work differently. Keep what is specific and defensible; discard what is generic or unsupported.
Notice also that you had to ask for criticism. If you'd asked "is this good?", you'd have been told it was good. That pull toward agreement never goes away, and you have to work around it.
Watch it fail. 5 minutes.
This is the important one. Pick a topic you know well and ask:
Give me three peer-reviewed references on [a topic you know thoroughly], with authors, journal and year.
Now go and look for them. Depending on the tool and whether it searched the web, the references may be real, may not support the claim, or may not exist. The point is to practice verifying, not to guarantee a failure on demand.
Do this once, deliberately, while nothing is riding on it. It's the most valuable five minutes on this site because it makes the need for source verification concrete. That reflex can prevent a fabricated or misapplied reference from reaching learners.
Do one real thing. 5 minutes.
Go to the faculty email recipe and use it on an email you genuinely need to send today. Paste your voice profile from step one at the top.
Not a practice exercise. A real email, actually sent. The value shows up in your actual work or it doesn't show up at all.
The habit that makes AI useful
Stop treating it as a search engine that talks. Start bringing the material.
People ask it what the requirements are, what the evidence says, what the prevalence is, what their accreditor expects. And it answers, fluently and plausibly, sometimes right and sometimes not, with nothing to tell the two apart. Then they either get burned once and drop the whole thing, or, worse, they don't get burned for a while.
The habit that replaces it: bring the material. Your gap statement, your evaluation data, your last report, your notes, the guideline you already found. Then ask it to reorganize, summarize, critique, give you options, or write a first draft. That's what every recipe here does, and it's the difference between the tool being a liability and being the most useful thing in your week.
Three things to go and find out
One email to your privacy officer, compliance lead or IT contact settles hundreds of future decisions:
- Which AI tools has my organization licensed and approved for work?
- Is any of them cleared for confidential or regulated information, and which kinds?
- Who do I ask when I'm not sure?
Ask by email so you have the answer in writing, then send the reply to your team. You won't be the only person who wanted to know and didn't want to ask.
Where to go next
If you're a CME coordinator or planner: start with faculty email for the quick win, then evaluation comments for the big one.
If you write the accreditation reports: go straight to the outcomes report. It's the biggest single time saving on the site.
If you work in leadership development: rehearsing a hard conversation. It's the one that does something you couldn't do before at all, rather than doing something faster.
If you consult or manage cross-functional programs: start with turning needs into objectives, then use the house-style and number-audit templates to make the process repeatable across clients or teams.
If you'd rather understand it properly first: the four skill modules take about an hour, and then you can write your own recipe for whatever lands on your desk next.