← Back to Microsoft 365 Prototypes

Case study · Learning strategy

Teams Mobile: Connected, Not Tethered

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.

Action map linking the course goal to five on-the-job behaviors, practice activities, and lessons

The action map: every lesson practices one on-the-job behavior.

6 + 1
Lessons plus a wrap-up, designed for Articulate Rise
~45 min
Total seat time, in 5- to 8-minute lessons
5
On-the-job behaviors on the action map
Approved
Outline and draft prototype, on first review

The business need and the design thesis

The business need

Staff reachable away from a desk, work conversations kept in an approved app, and alerts that respect shift boundaries.

The design thesis

Connected, not tethered. Every capability taught (chat, calls, meetings) is paired with a boundary (quiet hours, status messages, approved apps).

People centered

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
Strategy driven

Three models, each with one job.

  • Action Mapping decides the content
  • SAM decides the process
  • Bloom's taxonomy decides the difficulty
Impact focused

Measured on the job, not just in the course.

  • A “This week, I will…” action plan
  • A Kirkpatrick evaluation approach recommended to the client
  • Reinforcement and a pilot recommended

The strategy before the course

The most important call was the design thesis: teach every capability with its boundary.

  1. Start from the business need Reachable away from a desk, in an approved app, without carrying alerts into off-shift time.
  2. Name the thesis Connected, not tethered: pair every capability with a boundary.
  3. Map the behaviors Used Action Mapping to name five on-the-job behaviors.
  4. Design the practice Created a practice activity for each behavior, then added only the information that practice needs.
  5. Set the difficulty Leveled the lessons with Bloom's taxonomy, from understand to apply to evaluate.
  6. Prototype and review in cycles Ran short SAM cycles: outline, clickable prototype, and client review rounds, with immediate approval.
  7. Recommend the evaluation Suggested Kirkpatrick measures at all four levels; the client created their own final course.

Step 2 is the turning point.

Connected, not tethered.

The design thesis behind every lesson

Every lesson follows the same arc

Activate, demonstrate, apply with feedback, then act on the job.

Understand

1. Why Teams Mobile Matters · 5 min

Practice: reply to a coworker between rounds. On the job: move one work text into Teams.

Understand, apply

2. Understand the Mobile App · 6 min

Practice: labeled phone tour, then a status check. On the job: install and sign in.

Apply

3. Use Teams on Your Phone · 8 min

Practice: help Maria join a meeting away from her desk, then on weak data. On the job: join one meeting from your phone.

Apply, analyze

4. Stay Effective in Mobile Meetings · 6 min

Practice: fix the echo from a second device. On the job: test audio with earbuds.

Apply

5. Manage Notifications and Off-Shift Time · 7 min

Practice: what happens to an 8 PM message? On the job: set quiet hours and a status message.

Evaluate

6. Teams Mobile Best Practices · 5 min

Practice: the 9 PM question. On the job: update the app.

Remember, evaluate

Wrap-Up · 6 min

A 10-question final assessment (80% to pass) and a “This week, I will…” action plan.

Learning science, made visible

Knowles' andragogyLesson 1 opens with the why, and every lesson centers on a real job task.
Merrill's First PrinciplesOpener tabs activate, phone tours demonstrate, scenarios apply, and “Try it this week” integrates.
Cognitive load & Mayer5- to 8-minute lessons, one step at a time, labels on the drawings, and no decorative images.
Scenario-based learningMaria's situations build judgment, and every wrong choice explains its consequence.
Retrieval practiceA knowledge check in every lesson with unlimited retries, plus a 10-question final.
Fogg & implementation intentionsThe why builds motivation, small steps build ability, and “This week, I will…” is the prompt.

Accessibility & inclusion

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.

4.5:1 text contrast Full keyboard support Feedback in words, not color alone Text list for every phone drawing 44–48 px touch targets Reflows at phone width Reduced-motion support

Who did what

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.

Jacqueline Davis

Learning strategy & design

  • Set the strategy and the design thesis
  • Built the action map and learning architecture
  • Wrote the course outline and designed every lesson
  • Recommended an evaluation approach

Client

Healthcare organization

  • Defined the business need
  • Reviewed the outline and prototype in SAM cycles
  • Approved the design immediately
  • Created their own final course

Claude & Claude Code

Anthropic · build partner at my direction

  • Turned the storyboard into a clickable, Rise-style prototype for client review

Eight decisions and why

Show all 8 decisions
#DecisionWhy
1Pair every capability with a boundaryStaff need to be reachable without work following them home
2Let Action Mapping decide the contentContent that doesn't support a behavior stays out, so the course stays short
3Let SAM decide the processThe client reacts to something real early, when changes are cheap
4Let Bloom's taxonomy decide the difficultyLearners build confidence before they're asked to judge situations
5Give every lesson the same arcActivate, demonstrate, apply, act keeps practice at the center
6Make each theory visible in a featureA reviewer can point to where the learning science shows up
7Target WCAG 2.2 AA and UDLEvery learner can use it, on any device
8Recommend Kirkpatrick measures at all four levelsSo the client could decide behavior and results measures up front, not guess afterward

Kirkpatrick's four levels, as recommended

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.

1. ReactionThree-question survey: relevant, clear, will use.
2. Learning80% on the final, plus first-try rates on each check to find weak spots.
3. Behavior · 30 daysTeams mobile sign-ins from IT reports, plus a self-report on quiet hours and work texts moved.
4. Results · 60–90 daysA client-chosen outcome, such as fewer missed messages or less after-hours messaging.

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.

Directed by a person, built with AI

Human authorship

The strategy, design thesis, action map, outline, lesson design, evaluation recommendations, and review.

AI generation

A clickable, Rise-style prototype for client review, built by Claude Code at my direction.

Open by design

Disclosing AI use builds trust, and directing AI well is a skill in its own right. How I use AI

Click through the prototype A rapid prototype styled like Rise, using a fictional organization name. Try Maria's scenarios and the labeled phone tours.

Want training built on a strategy, not a slide count?

I'd love to hear what you're rolling out and the behavior you need to change.

Let's talk