AI WORLD HQ
If your team can talk fluently about AI but freezes the moment someone says "build me a small workflow," you are not alone. The biggest barrier to using AI at work is rarely knowledge — it is the gap between reading about it and actually wiring it into your day. AWS published a playbook on closing that gap, and the lessons translate cleanly to any team willing to copy the structure.
Before you start: what you'll need
- A group of 4–12 learners. Smaller is easier to coach; larger works with breakouts.
- 90 minutes per week, for six weeks. Block this on everyone's calendar before week one. Make it a recurring meeting you don't cancel.
- A facilitator who has built something. Not a teacher — a coach. Someone who has shipped at least one small AI tool themselves.
- One AI tool everyone can access. A chat-based AI with a project workspace, or a no-code builder (a tool that lets you create apps without writing code, using a visual drag-and-drop interface), both work well for non-technical learners.
- A shared demo slot. A 20–30 minute weekly show-and-tell where two or three people show what they built.
Step 1 — Foundations week (what AI actually does)
Start with the smallest possible theory dose: what an LLM (large language model — the kind of AI engine behind tools like ChatGPT) actually does, what a prompt (the instruction you type to the AI) is, and what an API (a way for two programs to talk to each other — think of it as a phone line between your tool and the AI) is. Keep theory to 30 minutes, with plain-language examples.
Then immediately assign the first tiny build. Don't let theory linger.
💬 Try this prompt together: "Explain in three sentences what a large language model actually does, like I'm explaining it to a colleague who has never heard the term."
You'll know it worked when every learner can describe, in their own words, what happens when they type a prompt and hit enter — without using the words "magic" or "AI brain."
Step 2 — First build (something useful to the builder)
Each learner picks one small project that solves a problem in their own work. AWS's playbook, like most adult-learning frameworks, emphasizes that the project must matter personally to the builder — not be an abstract exercise. A FAQ assistant for one shared document. A draft-responder for the team's most common customer email. A meeting-summary helper.
💬 Starter prompt: "You are an assistant that answers questions using only the document I paste below. If the answer isn't in the document, say 'I don't know.' Here's the document: [paste text]."
You'll know it worked when the learner has a working demo they can show in under two minutes — even if it's rough.
Step 3 — Iteration week (prompting is editing)
Most beginners quit here because their first version isn't perfect. The lesson: prompting (the way you phrase instructions to the AI) is closer to editing a draft than typing a command. Tweak the wording. Add constraints. Show examples of good and bad answers.
The facilitator's job this week is to sit with each learner for 15 minutes and help them improve their original build — not start over.
💬 Iteration prompt: "Your previous answer was too long. Reply in three sentences max, then ask me one clarifying question."
You'll know it worked when the learner can name two specific changes they made to the prompt that made the output better.
Step 4 — Sharing week (demo to peers)
Each learner demos their tool to the group for five minutes, then takes 10 minutes of questions. Effective adult-learning programs treat this show-and-tell as the highest-value session of the program. Teaching forces clarity.
The facilitator should resist the urge to add new content. The demo IS the lesson.
💬 Demo script template: "I built this for [specific problem]. Here's what it does. Here's where it failed. Here's what I'd try next."
You'll know it worked when at least one other learner says "I want to try that for my project."
Step 5 — Real workflow problem
The build task now comes from the learner's actual day-to-day work — not the sandbox. AWS's playbook describes this shift as the moment training becomes useful, because the project has a real stakeholder (the person whose problem it solves).
Examples: a sales rep builds a follow-up email drafter that pulls from the team's top-performing templates. A support agent builds a triage helper for incoming tickets. A teacher builds a quiz generator for one specific unit.
💬 Real-work prompt: "You are helping me draft a follow-up email after a sales call. I'll paste the call notes below. Write the email in our team's standard format, then flag anything I should double-check before sending."
You'll know it worked when at least one teammate outside the cohort asks to use the tool.
Step 6 — Public showcase and next steps
Week six is a larger demo event — open to the wider organization. Each learner presents their final tool, what they learned, and what they want to build next. The point is to make the learning visible and to recruit the next round.
End the program with a clear path forward: an internal community (a chat channel, a monthly demo, a shared prompt library) where builders keep learning from each other.
💬 Closing prompt for the cohort: "Write a five-sentence summary of what you learned in this program, written for someone about to start. What's the one piece of advice you'd give them?"
You'll know it worked when at least one person outside the original cohort asks "when's the next round?"
Common mistakes
- Mistake: front-loading theory. Fix: cut theory to 30 minutes, then build. Learners remember what they made, not what they watched.
- Mistake: assigning abstract projects. Fix: require every project to solve a real problem the builder personally has. No exceptions.
- Mistake: skipping the demo week. Fix: the demo IS a deliverable. Treat absence from demo week like missing a deadline.
- Mistake: no follow-up community. Fix: end week six with a concrete ongoing space — a chat channel, a monthly demo, a shared doc of starter prompts. Without it, the skills fade in a month.
Wrap-up
The message from AWS's playbook is refreshingly plain: most people are closer to "AI builder" than they think, but the jump never happens through reading. It happens through shipping a small real thing, showing it to a peer, and shipping another one the next week. Pick your start date today, name your first tiny project, and block the calendar. That is the whole framework, and it works.