01Foundations Days 1–10

You'll write prompts that work like a clear brief, and reuse the good ones.

Team session guide →

  1. 01Brief it like a colleague. Not a search box.A prompt is a brief.
  2. 02If it's not in the prompt, it's a guess.It reads everything. Literally.
  3. 03If a colleague would be confused, so is the model.Plain words. Better output.
  4. 04Tell it what a new hire would need to know.Context in. Quality out.
  5. 05Task first. Add parts until it's unambiguous.Five parts. One prompt.
  6. 06Define done before you hit enter.Vague in. Vague out.
  7. 07Give feedback like an editor, not a judge.The first answer is a draft.
  8. 08Use it where you can check it and share it.Sometimes the best prompt is none.
  9. 09Before you blame the model, reread your prompt.Six ways to get bad answers.
  10. 10Five good prompts beat fifty saved ones.Write it once. Reuse it forever.

02Frameworks Days 11–20

You'll pick a simple prompting framework to fit the job and make it your own.

Team session guide →

  1. 11Who, what, what shape. Most prompts need no more.Role. Task. Format.
  2. 12One good example beats ten adjectives.Six letters for creative work.
  3. 13Say who's listening and how it should feel.Built for words people read.
  4. 14Spell out the steps when the order matters.For work with steps.
  5. 15Frameworks give shape. Patterns give leverage.Small moves. Big difference.
  6. 16Match the framework to the job.Pick by the job, not the acronym.
  7. 17Your words. Your work. Your framework.Make it yours.
  8. 18The tool builds the structure. You bring the facts.From rough idea to real prompt.
  9. 19Better brief. Better answer. Every time.Same ask. Better brief.
  10. 20Forget the letters. Remember the questions.The whole module on one page.

03Core techniques Days 21–30

You'll use examples, steps and checks to get better answers first time.

Team session guide →

  1. 21Show it good. Say what to copy.Show, don't tell.
  2. 22Hard problem: let it think. Easy task: just ask.Let it think.
  3. 23Set the limits. Rank them if they clash.Limits make it better.
  4. 24Decide where it's going. Then pick the shape.Ask for the shape you need.
  5. 25Instructions here. Material there. No mix-ups.Label the parts.
  6. 26Smaller steps. Checkpoints between. Better finish.Big job? Make it a chain.
  7. 27Not sure what to say? Let it ask.Let it interview you.
  8. 28Don't ask if it's good. Ask what's weak.Make it check its own work.
  9. 29Name the criteria. Score each one. Quote the proof.Define good before you ask.
  10. 30Point it where to go. Save “never” for red lines.Say what to do.

04Documents & data Days 31–40

You'll summarise, extract and compare documents and data without losing the facts.

Team session guide →

  1. 31Ask what it left out, not just what it kept.Shorter, not different.
  2. 32Missing is an answer. Make it say so.Pull out exactly what you need.
  3. 33Point it to the pages. Ask for the quotes.Big doc? Give it a map.
  4. 34Old vs new. Clause by clause. Then legal.What changed?
  5. 35Define the terms. Get the formula. Check the total.Numbers need rules.
  6. 36No source, no claim. Then open the source.Where did that come from?
  7. 37Question, sources, weighing. Then the write-up.Research is a process, not a prompt.
  8. 38Decisions. Owners. Dates. Nothing else matters.From talk to actions.
  9. 39Ask for the recipe. Cook it yourself.Messy data? Clean it first.
  10. 40Numbers, names, dates. Check them every time.Trust, but check.

05Writing with AI Days 41–50

You'll write with AI in your own voice, from emails to proposals.

Team session guide →

  1. 41Show it your writing. Name what you're not.Make it sound like you.
  2. 42One ask. Up front. With a date.Emails that get replies.
  3. 43Your thinking. Its polish.You write. It edits.
  4. 44Their problem. Their words. Your solution.Proposals that win.
  5. 45Answer first. Evidence after. Detail last.Lead with the answer.
  6. 46AI drafts the words. You bring the story.Posts people stop for.
  7. 47Describe the style you want. Then edit like a human.Spot the robot.
  8. 48One page. Loaded every time.Write the rules once.
  9. 49AI drafts it. A fluent speaker signs it off.Translate the meaning.
  10. 50Be open about the help. Own every word.Say when AI helped.

06Thinking with AI Days 51–60

You'll use AI to think harder, and keep the final decision yourself.

Team session guide →

  1. 51The good ideas are past the obvious ones.Go past the obvious.
  2. 52Find the holes before your customers do.Argue with me.
  3. 53You set the criteria. You own the call.It advises. You decide.
  4. 54Start from what you know. Ask where the analogy breaks.Explain it like I'm new.
  5. 55Answers solve today. Learning solves next time.Don't tell me. Teach me.
  6. 56Plan backwards. Start Monday. Check with the team.From goal to Monday.
  7. 57Question the question first.Solve the right problem.
  8. 58Agree the triggers before you need them.Plan for more than one future.
  9. 59Ask neutral questions. Get honest answers.It wants to agree with you.
  10. 60Think first. Then ask. Then decide.Keep your brain switched on.

07Safety & privacy Days 61–70

You'll keep personal and confidential data out, and check answers before you use them.

Team session guide →

  1. 61Wouldn't email it to a stranger? Don't paste it.Some things never go in the box.
  2. 62Keep what the task needs. Strip the rest.Strip it before you send it.
  3. 63Same law. New tool. Write it down.POPIA doesn't pause for AI.
  4. 64Give it an out. Give it the source.Confidently wrong.
  5. 65The higher the stakes, the harder you check.Check before you trust.
  6. 66Anything it reads can talk back. Limit what it can do.When content gives orders.
  7. 67Check who it assumes. Check who it leaves out.Fair isn't automatic.
  8. 68Tools catch the slips. Habits prevent them.A safety net before you send.
  9. 69Work data. Work tools. Check the terms.Same model. Different rules.
  10. 70Short enough to use. Every time.Five seconds before you send.

08Reusable prompts Days 71–80

You'll build a small library of tested prompts your team can share.

Team session guide →

  1. 71Proven prompt. Fixed rules. Clear blanks.Build it once.
  2. 72Clear names. Sensible defaults. Five max.Name the blanks.
  3. 73Who you are, how you like it. Once.Tell it once, not every time.
  4. 74One project per job. Keep the files fresh.Give each job a home.
  5. 75Package a job people do every week.Package the expertise.
  6. 76Curated, owned, easy to find.Best prompts, one place.
  7. 77Number it. Log it. Keep the last one.Know which version works.
  8. 78Five real cases. One hard one. Then share.Test it before you trust it.
  9. 79Prompt, purpose, example, limits.Share the why, not just the words.
  10. 80Review quarterly. Retire freely. Retest after updates.Prompts age.

09Prompting by role Days 81–90

You'll have prompts that fit your role, from sales to support to engineering.

Team session guide →

  1. 81Filter the noise. Test the message. Keep the call.Less reading. Better decisions.
  2. 82Prep deeper. Practise harder. Follow up faster.More selling, less admin.
  3. 83AI drafts. Agents care. Customers notice.Faster replies. Same care.
  4. 84AI for the paperwork. People for the people.People work needs people.
  5. 85AI writes the story. You own the numbers.Explain the numbers.
  6. 86AI multiplies content. You protect the truth.More ideas. One voice.
  7. 87Triage with AI. Decide with a lawyer.First draft. Never final word.
  8. 88Write it down once. Fix it faster next time.Runbooks. Rosters. Root causes.
  9. 89AI drafts the story. The team has the conversation.From idea to backlog.
  10. 90If you can't explain it, don't merge it.Pair with it. Review it.

10Advanced Days 91–100

You'll move from chat to tools, agents and tests, like an engineer would.

Team session guide →

  1. 91Set the rules up front. Enforce the big ones in code.The rules behind the chat.
  2. 92Crop it, point at it, then ask.Show it, don't describe it.
  3. 93Subject, style, framing, details.Describe the picture.
  4. 94Brief it like a contractor. Approve before it acts.From answers to actions.
  5. 95Right tool for the job. Least access to do it.Give it the right tools.
  6. 96No test set, no rollout.Test like an engineer.
  7. 97Match the model to the job. Test before switching.Not all models are equal.
  8. 98Curate what it sees. Start fresh when it drifts.What it sees decides what it does.
  9. 99Plan it. Chunk it. Log it. Review it.Big jobs need milestones.
  10. 100Practise daily. Review quarterly. Stay curious.Day 100 is day one.