New to AI? Begin with three steps.
No coding. No big course. A little learning each week adds up. Take these in order, and give each one a week.
Learn to ask well
Most “bad” AI answers come from a vague request. The fix is a better ask. A simple way to remember what to include is CRAFT:
- CContext · the situation, in a sentence or two
- RRole · who the AI should act as
- AAsk · the exact task
- FFormat · length and layout
- TTone · how it should sound
Compare these two requests.
This week: take one request you would normally type in a few words, and rewrite it using the five parts.
Pick one task a week
Do not try to learn everything. Choose one task you repeat often, such as replying to a long email, tidying meeting notes or summarising a report, and let AI help with that one task all week.
- Ask for a draft. Use CRAFT and paste in the facts.
- Read it like an editor. Check names, numbers and dates. AI can sound sure and be wrong.
- Make it yours. Change what does not sound like you, then send it under your name.
- Save the ask. Keep the prompt that worked, so next week takes half the time.
AI is a thinking partner, not a shortcut. You stay responsible for the final work.
Know what stays out
Before you paste anything into an AI tool, stop and check. These should not go into a public AI tool:
- Sensitive personal data: health, religion, race or ethnic origin, political views, union membership, biometric data.
- Staff and customer records: names linked to pay, appraisals, disciplinary cases, ID, bank or phone details.
- Confidential business information: anything under an NDA, unpublished financials, passwords and access codes.
- Information about children.
When in doubt, anonymise first: replace names with roles, remove ID numbers, phone numbers and exact figures, and type a short description instead of uploading the original file.
Want help doing this with your team?
We teach it. We build it. We stay.