Everyone learns the same core. What changes is the work you point it at.
A finance manager, a facilitator, and an operations lead do not need three different AI trainings. They need the same footing — how to instruct it, how to check it, how to keep data safe — and then a thin layer of their own real work laid on top. Roughly seventy percent is the shared core; the last thirty percent is where AI meets the job in front of you.
This is what keeps a rollout coherent. When the foundation is common, people can help each other, share what works, and grow along one ladder instead of scattering into private habits no one can see or reuse.
Fast, tireless, widely read, and eager. It will draft in seconds what would take you an afternoon. It will also, now and then, state something wrong with perfect confidence. So you treat it exactly as you would a gifted new hire: give it clear instructions, and check its work every time. The speed is real. The judgment is still yours.
Always check. AI can be confidently wrong — inventing a figure, a citation, or a policy that sounds right. Read every output before you rely on it, and never let it be the last set of eyes on anything that matters.
Give clear instructions. Vague in, vague out. The more you tell it about the situation, the task, and the shape you want back, the better the result. Instruction quality is the single biggest lever you control.
Keep it confidential. Company data belongs in the company's sanctioned AI workspace — never in a personal account or a random consumer app. Where the data lives decides which tool you are allowed to use.
Almost every good prompt has three parts. Context — who you are, what the situation is, what the AI needs to know. Task — the one thing you want it to do. Format — the shape you want back. Miss one and the output drifts; supply all three and it lands close on the first try.
Worked example: “I manage the front desk at a serviced-apartment building and a guest has emailed to complain that their aircon was noisy for two nights (context). Draft a warm, apologetic reply that offers a partial credit and a follow-up call (task). Keep it under 120 words, friendly but professional, and give me two subject-line options (format).” — then read it, correct the details only you know, and send it yourself.
Notice the last move: you still read and correct before it goes out. The formula gets you a strong draft, not a finished decision.
AI is only as safe as the boundary you keep around it. The rule is simple: ordinary working material inside a sanctioned company workspace is fine; anything that identifies a person financially or personally does not go in at all.
When in doubt, leave it out — or summarise it so the sensitive specifics never reach the tool. And always use the company AI for company data, never a personal account.
The safe workflow is always the same three beats: AI drafts, you read and correct, then you send. The AI never presses send, and its draft is never the final word. This one habit prevents almost every embarrassing mistake.
Two more habits that compound quickly. Summarise instead of forwarding. Rather than forwarding a screenshot or a long thread, ask AI for a tight summary of what it says and what it asks for — turn images and clutter into a typed answer. And translate on demand — a Thai email you need in English, or an English document a colleague needs in Thai, is now a few seconds of work, not a bottleneck.
Gemini Gems, Claude Projects, or a custom GPT — same idea by different names. You save the setup once so you never re-type it: a fixed role, the context it always needs, the task it usually does, the format you want back, its limits, and a self-check rule. A good helper always ends by flagging what it was unsure about — and you still check. It is the difference between briefing a new intern every morning and having one who already knows the drill.
Most of the value AI creates is invisible: a draft that saved an hour, a summary that avoided a meeting, a translation that unblocked a decision. None of it shows up anywhere. The weekly report is how you make it show.
It starts almost trivially small — three questions, answered once a week:
1. What did AI help me with this week?
2. Did it actually work?
3. What will I try next?
That is the whole thing, at first. Then it grows. Week by week it accumulates — which prompts worked, which helper you built, where AI saved real time — until it is no longer a training exercise but a running record tied to your actual job. The report is the spine the entire curriculum hangs on: it turns scattered experiments into visible, reusable, reportable progress.
Progress with AI is not pass/fail. It is a climb from “never touched it” to “my whole team reuses what I built.” The ladder names where someone is today so the next rung is obvious — and so a rollout can see itself moving.
Not yet using AI in any visible way.
Understands what AI is and why it matters for the work.
Has applied it to actual work, not just a demo.
Can show what was asked and what came back — and treats it as a draft.
Reads, corrects, and owns the result before it goes anywhere.
Saves the setup so a recurring job runs the same way every time.
Maintains a running record of what AI is doing across their real work.
Turns personal practice into something the whole team can reuse.
The foundation is taught as a progression — each step small enough to do this week, each one building on the last. It always ends in the same place: AI carrying real weight on your actual work, with a record to prove it.
The one non-negotiable across every step: it must touch your actual job. A neat summary about AI is not the goal — a draft you actually sent, a helper you actually reuse, a report tied to work you actually own. If it never touches real work, it never happened.
A coaching foundation your whole team can climb — the same core, applied to each role.
Start a Conversation