Built for staff on the move.
- Clinical, administrative, and support staff between units, rounds, and offices
- Off-shift time protected by design
- WCAG 2.2 AA and Universal Design for Learning
← Back to Microsoft 365 Prototypes
Strategy first: every mobile skill paired with a boundary.
A healthcare organization needed staff reachable away from their desks without work following them home. I built the learning strategy and outline first, then a draft prototype of a 6-lesson course in which every skill is paired with a boundary. The client approved it right away and built the final course themselves.
The action map: every lesson practices one on-the-job behavior.
Staff reachable away from a desk, work conversations kept in an approved app, and alerts that respect shift boundaries.
Connected, not tethered. Every capability taught (chat, calls, meetings) is paired with a boundary (quiet hours, status messages, approved apps).
The most important call was the design thesis: teach every capability with its boundary.
Step 2 is the turning point.
Connected, not tethered.
The design thesis behind every lesson
Activate, demonstrate, apply with feedback, then act on the job.
Practice: reply to a coworker between rounds. On the job: move one work text into Teams.
Practice: labeled phone tour, then a status check. On the job: install and sign in.
Practice: help Maria join a meeting away from her desk, then on weak data. On the job: join one meeting from your phone.
Practice: fix the echo from a second device. On the job: test audio with earbuds.
Practice: what happens to an 8 PM message? On the job: set quiet hours and a status message.
Practice: the 9 PM question. On the job: update the app.
A 10-question final assessment (80% to pass) and a “This week, I will…” action plan.
The prototype targets WCAG 2.2 AA and follows Universal Design for Learning (UDL): the same idea comes as text, a drawing, and a list, and learners choose their own path through the menu.
I was asked for the outline and a draft prototype. The client reviewed in short cycles, approved it right away, and built their own final course. Claude built the prototype I designed.
Learning strategy & design
Healthcare organization
Anthropic · build partner at my direction
| # | Decision | Why |
|---|---|---|
| 1 | Pair every capability with a boundary | Staff need to be reachable without work following them home |
| 2 | Let Action Mapping decide the content | Content that doesn't support a behavior stays out, so the course stays short |
| 3 | Let SAM decide the process | The client reacts to something real early, when changes are cheap |
| 4 | Let Bloom's taxonomy decide the difficulty | Learners build confidence before they're asked to judge situations |
| 5 | Give every lesson the same arc | Activate, demonstrate, apply, act keeps practice at the center |
| 6 | Make each theory visible in a feature | A reviewer can point to where the learning science shows up |
| 7 | Target WCAG 2.2 AA and UDL | Every learner can use it, on any device |
| 8 | Recommend Kirkpatrick measures at all four levels | So the client could decide behavior and results measures up front, not guess afterward |
What I suggested to the client. Levels 1 and 2 fit inside the course; Levels 3 and 4 were for the client to choose, since they built the final product.
Recommended next: spaced reinforcement nudges at 2 and 7 days, a one-page job aid, managers modeling quiet hours, and a pilot with 5 to 8 staff before launch.
The strategy, design thesis, action map, outline, lesson design, evaluation recommendations, and review.
A clickable, Rise-style prototype for client review, built by Claude Code at my direction.
Disclosing AI use builds trust, and directing AI well is a skill in its own right. How I use AI
I'd love to hear what you're rolling out and the behavior you need to change.
Let's talk