Pick the row that best describes you and follow the link.
| Your audience | Recommended starting point |
|---|---|
| A customer who's new to AI | Track 0 L100 → Track 1 L100. 2 hours total. |
| A customer evaluating Copilot for production | Track 1 L200 + Track 3 L200. |
| A customer building agents | Track 2 L100 → L200. Pair with Track 5 L100 for the "why does my agent forget?" conversation. |
| A customer at "we use Copilot, now what?" stage | Track 6 — Topic 4 (ROI) + Topic 2 (Workflow Design). |
| An internal team or community pod | adaptations/for-internal-teams.md. |
| Partner train-the-trainer | adaptations/for-partner-enablement.md. |
| A workshop / executive briefing for one customer | adaptations/for-customer-workshops.md. |
You're brand new to AI in your work: Track 0 L100 → Track 1 L100 → Track 3 L100. ~3 hours of self-paced Microsoft Learn modules. Free.
You use Copilot daily but want to go deeper: Track 3 L200 + Track 5 L100. This is the highest ROI per learning hour for working professionals.
You're an engineer building AI features: Track 2 L300 + Track 5 L300. Production-grade agent and context-management depth.
You lead a team and need to drive adoption: Track 6 — all four topics, L100 first. Decision intelligence, workflow design, change management, ROI.
Track 6 — Topic 2: Human–AI Collaboration Workflow Design (L100). Link
It's the session that most consistently moves audiences from "AI is a tool I have to learn" to "AI is a teammate I have to design around." That mental shift unlocks everything else.
Quick self-test:
| If you can… | You're at |
|---|---|
| …open Copilot Chat and ask it to draft an email | L100 |
| …write a multi-step prompt with examples and structured output | L200 |
| …design a RAG pipeline with vector indexing and human approval gates | L300 |
Don't overthink it. Start at L100, finish in 30 minutes if it's too easy, jump to L200.
- Skipping Track 0. "We'll do Responsible AI later" is how you end up with the incident that becomes your case study. Start there.
- Starting at L300 because the audience is "technical." Technical audiences still appreciate the L100/L200 framing for shared vocabulary; just move through them faster.
- Trying to run all six tracks in one event. Don't. Pick two. Run them well. Add more next quarter.
- No real scenarios. Generic examples kill engagement. Bring one real workflow from the audience's own work — even if it takes a 15-minute prep call to surface.
Once you've picked a track and level, open the track file and skim the "Hands-on focus" column. That tells you what the live session needs to cover. Then read FACILITATOR-GUIDE.md for session format and timing.