Built for how adults learn new tools.
- Every lesson starts with why, not features
- Relevant to every role: clinical, administrative, and support
- Accessibility required from the first storyboard draft
← Back to Microsoft 365 Prototypes
From SME outline to a prototype the client could click.
A client asked for an Articulate Rise 360 course to move employees from email to Teams. Before building in Rise, I storyboarded the course and used Claude and Claude Code to build a rapid prototype styled like Rise. The client clicked through every lesson and confirmed the direction before we developed the final course.
Lesson 1 of the rapid prototype, built with Claude Code and styled to look like Rise.
Turn the SME outline into a Rise 360 course on Teams for every employee, from first login to managing notifications.
Change a habit: make Teams the primary place for conversations, files, and decisions, while email keeps its place for formal notices and outside contacts.
Building directly in Rise would have meant hours of block-by-block work before the client saw anything she could click.
Step 5 is the turning point.
The client clicked through the course before a single Rise block was built.
The idea behind the prototype
Lesson 1 opens with Maria, whose project update spiraled into 35 emails. Every interaction explains its reasoning, including for wrong answers.
I set the direction and made the design calls. The client and SME supplied the needs and content, and Claude built what I directed.
Learning strategy & design
Organization rolling out Teams
Anthropic · build partner at my direction
| # | Decision | Why |
|---|---|---|
| 1 | Treat it as a habit change, not a software tour | Teams first, email second had to run through every lesson |
| 2 | Prototype before building in Rise | The client reacts to something real early, when changes are cheap |
| 3 | Start with “why,” not features | Adults commit when they see the problem it solves in their own work |
| 4 | Carry five messages through every lesson | Repeating the behavior change in context keeps it from becoming a feature tour |
| 5 | Use a steady lesson rhythm | A predictable structure keeps cognitive load low |
| 6 | End lessons with “Try it this week” | Applying a skill right away turns training into a habit |
| 7 | Require accessibility from the first draft | Accessibility is designed in, not checked at the end |
The final course was developed in Articulate Rise 360. Placeholders in the prototype marked what the Rise build still needed: a leader welcome video, a meeting join demo, and screenshots of the client's own Teams environment.
The goal, design parameters, lesson design, scenarios, assessment, review, and client sign-off.
A storyboard draft from the SME outline and a clickable prototype, built by Claude and Claude Code at my direction.
The client saw and reacted to the course in days. Disclosing how is part of the work. How I use AI
I'd love to hear what you're rolling out and how we could turn it into learning people actually use.
Let's talk