Role playbooks overview
**Role playbooks** translate AI literacy into workflows for founders, marketers, support, ops, developers, designers, students, and teachers/parents.
What it is
Role playbooks translate AI literacy into workflows for founders, marketers, support, ops, developers, designers, students, and teachers/parents.
Why it matters
The same model is a different tool in each job. Playbooks keep ANN Learn practical without pretending one prompt fits all.
How it works (plain)
Each playbook will cover: goals, allowed uses, verification habits, escalation rules, and a short technical stack note. This overview explains the pattern.
Everyday example
A marketer’s “draft → human edit → brand check” differs from a developer’s “spec → tests → code assist.”
Try it
Pick your role. Write 3 tasks AI may draft and 3 tasks that stay human-owned.
Myths
- ⚠️ Myth: Role playbooks replace learning the fundamentals.
- ✓ Reality: They sit on Courses 01–21; shortcuts without verification fail.
- ⚠️ Myth: Your industry is too special for shared patterns.
- ✓ Reality: Verification, permissions, and evaluation transfer—even when jargon differs.
Sources
- Course 08 prompting; Course 20 work; Course 26 HAI
- NIST AI RMF: https://www.nist.gov/itl/ai-risk-management-framework ↗
