Teaching & Workshop Design

Module 16.3: Teaching & Workshop Design

Estimated time: ~35 minutes

Prerequisite: All previous modules

Outcome: After this module, you will know how to design and deliver Claude Code training for teams.

---

1. WHY — Why This Matters

You’ve mastered Claude Code. But your impact is limited if you’re the only one who knows it.

Teaching multiplies your value: your team becomes more productive, you solidify your own knowledge, you become the go-to expert, and organizational benefits compound. This module equips you to share what you’ve learned — from quick tips to full workshops.

---

2. CONCEPT — Core Ideas

Teaching Formats

Format	Duration	Best For
Tips Session	15-30 min	Quick wins, demos
Lunch & Learn	45-60 min	Single topic deep-dive
Half-day Workshop	3-4 hours	Hands-on practice
Full-day Training	6-8 hours	Comprehensive coverage

Workshop Design Principles

1. Show, Don’t Tell — Live demos over slides
2. Hands-On Practice — 50% lecture, 50% practice
3. Progressive Complexity — Quick wins before advanced
4. Relevance — Use their codebase, solve their problems
5. Takeaways — Cheat sheets and templates

Workshop Structure

Hook (10%) → Foundation (20%) → Main (50%) → Advanced (20%) → Wrap (10%)

---

3. DEMO — Step by Step

Example: 2-Hour “Claude Code Kickstart” Workshop

Audience: Development team new to Claude Code Goal: Basic proficiency, immediate productivity

Schedule:

0:00-0:15 — HOOK

• Live demo: Build a feature in 5 minutes
• “By the end, you’ll do this too”

0:15-0:35 — FOUNDATION

• What is Claude Code? (5 min)
• Installation check (5 min)
• First command together (10 min)

0:35-1:05 — CORE TECHNIQUES

• CLAUDE.md introduction (10 min)
• Hands-on: Write CLAUDE.md (15 min)
• Share and compare (5 min)

1:05-1:15 — BREAK

1:15-1:45 — PRACTICAL WORKFLOW

• Live demo: Reading + writing code (20 min)
• Hands-on: Complete a task (10 min)

1:45-2:00 — WRAP-UP

• Recap 3 key techniques
• Distribute cheat sheets + templates
• Q&A

Demo Script Template

# Demo: [Name]
Duration: [X] minutes

## Setup (before workshop)
- [ ] Project cloned
- [ ] CLAUDE.md prepared
- [ ] Commands tested

## Script
1. "Let me show you [capability]"
2. Type: `claude "[command]"`
3. Explain output
4. "Now you try..."

## Backup
If demo fails: [alternative approach]

---

4. PRACTICE — Try It Yourself

Exercise 1: Design a 30-Minute Session

Goal: Create a mini-workshop for one technique.

Instructions:

1. Pick one technique from the course
2. Design: hook (5 min), demo (10 min), hands-on (10 min), takeaway (5 min)
3. Write the demo script
4. Test on a colleague

💡 Hint

Start with CLAUDE.md or Think mode — they're easy to demo and have immediate impact.

✅ Solution

30-min session: “CLAUDE.md Power”

• Hook (5 min): Show project with vs without CLAUDE.md
• Demo (10 min): Create CLAUDE.md live
• Hands-on (10 min): Everyone writes their own
• Takeaway (5 min): Template + cheat sheet

Demo script:

1. “Watch Claude without CLAUDE.md” — generic response
2. “Now with CLAUDE.md” — project-aware response
3. “Let’s create one together”
4. “Your turn — use this template”

---

5. CHEAT SHEET

Workshop Structure

Phase	Time	Focus
Hook	10%	Impressive demo
Foundation	20%	Core concepts
Main	50%	Key techniques + practice
Advanced	20%	Complex scenarios
Wrap	10%	Recap + resources

Time Allocation

• 50% Hands-on practice
• 30% Live demos
• 20% Lecture

Materials Checklist

• Demo scripts (tested!)
• Practice exercises
• Cheat sheets
• CLAUDE.md templates
• Follow-up resources

Golden Rules

• Show, don’t tell
• Everyone practices
• Use their code
• Quick wins first

---

6. PITFALLS — Common Mistakes

❌ Mistake	✅ Correct Approach
All slides, no demos	Live coding is more engaging
Watching without doing	Everyone must practice
Generic examples	Use their actual codebase
Too advanced too fast	Start with quick wins
No takeaways	Provide cheat sheets and templates
Untested demos	Run through everything before

---

7. REAL CASE — Production Story

Scenario: Vietnamese tech company rolling out Claude Code to 50 developers across 5 teams.

Teaching Strategy:

• Week 1: Train-the-Trainer — 4 senior devs became team champions
• Week 2-3: Each champion ran 4-hour workshop for their team
• Week 4: Office hours, Slack channel, monthly advanced sessions

Materials Created:

• 2-hour kickstart workshop (reusable)
• Team-specific CLAUDE.md templates
• Laminated cheat sheets on every desk

Results (2 months):

• 50/50 developers actively using Claude Code
• 3 champions became internal experts
• New hire onboarding includes workshop
• Productivity: +30% team average

Quote: “We didn’t just teach a tool. We created internal experts who keep teaching others.”

---

🎓 CONGRATULATIONS!

You’ve completed Claude Code Mastery — 16 phases, 55 modules, 200+ techniques.

You’re now equipped to:

• Master Claude Code for your own work
• Customize workflows for your role
• Lead Claude Code adoption in your team
• Design and deliver training for others

Your journey continues. Ship great software. Teach what you learn.

— Ethan, Claude Code Mastery Author