← Back to Microsoft 365 Prototypes

Case study · Software adoption

Getting Started with Microsoft Teams

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 Getting Started with Microsoft Teams prototype: a course menu listing ten lessons and a wrap-up, a progress bar, the lesson title Why We Use Teams with its objective, and a banner of coworkers collaborating

Lesson 1 of the rapid prototype, built with Claude Code and styled to look like Rise.

10
Lessons of 5–10 minutes, plus a wrap-up and final assessment
12
Knowledge checks, each with feedback that explains the reasoning
4
Branching workplace scenarios with Maria
80%
Passing score on the final assessment

The ask vs. the real goal

The ask

Turn the SME outline into a Rise 360 course on Teams for every employee, from first login to managing notifications.

The real goal

Change a habit: make Teams the primary place for conversations, files, and decisions, while email keeps its place for formal notices and outside contacts.

People centered

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

A habit change, not a feature tour.

  • Five messages carried through every lesson
  • A steady rhythm keeps cognitive load low
  • Prototype before building, so the client decides early
Impact focused

Practice that carries onto the job.

  • A “Try it this week” task in every lesson
  • A personal commitment list in the wrap-up
  • A final assessment with an 80% passing score

Storyboard, then prototype

Building directly in Rise would have meant hours of block-by-block work before the client saw anything she could click.

  1. Hear the ask The client wanted a Rise 360 course built from the SME's outline.
  2. Reframe the goal Named the real outcome: Teams first, email second, in every lesson, not just the introduction.
  3. Set the design parameters Gave Claude the outline with guardrails: linear Rise microlearning, Knowles' adult learning principles, low cognitive load, and WCAG accessibility.
  4. Storyboard every lesson Mapped all 10 lessons to objectives and Rise blocks, with a course map, design notes, and a build list.
  5. Build a rapid prototype Used Claude Code to turn the storyboard into a clickable, Rise-style prototype with menus, progress, scenarios, and scored checks.
  6. Review with the client She clicked through real interactions, not a document, and confirmed the direction.
  7. Develop in Rise Built the final course in Rise 360 from the approved direction.

Step 5 is the turning point.

Typical path
  • Build every lesson in Rise first
  • Client reviews late in the process
  • Changes mean reworking finished blocks
This project
  • Storyboard sets structure and blocks
  • Client clicks through a Rise-style prototype early
  • Rise build starts from an approved direction

The client clicked through the course before a single Rise block was built.

The idea behind the prototype

Learners make decisions, not just read about them

Lesson 1 opens with Maria, whose project update spiraled into 35 emails. Every interaction explains its reasoning, including for wrong answers.

Maria's email challenge, In email tab: an inbox with 35 messages for one project update, including an old file version, a duplicate thread, teammates left off, and an unanswered question
In email: 35 messages, conflicting files, and teammates left out.
Maria's email challenge, In Teams tab: a project Updates channel with a pinned shared file, Maria's update, and the decision recorded in the same thread
In Teams: one channel, one shared file, and the decision in the thread.
Scenario: Maria asks what to use for a quick question that may take a few messages. Start a Teams chat is marked as the best choice, and Maria cheers with feedback explaining why
Scenarios: Maria reacts to each choice and explains the reasoning.
Labeled graphic of the Teams interface with six numbered markers for Search, Activity, Chat, filters, Calendar, and OneDrive, with the Activity description shown below and an option to show all labels as a list
Labeled graphic: learners explore the Teams screen one area at a time.

Accessibility, built in from the first draft

Knowledge check 1 of 3 asking where you see your @mentions and replies, with Activity selected and feedback explaining it is the best answer
Knowledge checks explain the right answer in plain language.
Skip to lesson content Keyboard navigation Screen reader announcements Text list for every labeled graphic Video transcripts and captions Reduced-motion support Short paragraphs and bullets

Who did what

I set the direction and made the design calls. The client and SME supplied the needs and content, and Claude built what I directed.

Jacqueline Davis

Learning strategy & design

  • Reframed the request as a habit change
  • Set the instructional parameters and guardrails
  • Designed the lessons, scenarios, and assessment
  • Reviewed every lesson and led the client review

Client & SME

Organization rolling out Teams

  • Provided the outline of what employees needed to know
  • Set the requirement for a Rise 360 course
  • Clicked through the prototype and confirmed the direction

Claude & Claude Code

Anthropic · build partner at my direction

  • Drafted the storyboard from the SME outline
  • Built the clickable, Rise-style prototype

Seven decisions and why

Show all 7 decisions
#DecisionWhy
1Treat it as a habit change, not a software tourTeams first, email second had to run through every lesson
2Prototype before building in RiseThe client reacts to something real early, when changes are cheap
3Start with “why,” not featuresAdults commit when they see the problem it solves in their own work
4Carry five messages through every lessonRepeating the behavior change in context keeps it from becoming a feature tour
5Use a steady lesson rhythmA predictable structure keeps cognitive load low
6End lessons with “Try it this week”Applying a skill right away turns training into a habit
7Require accessibility from the first draftAccessibility 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.

Directed by a person, built with AI

Human authorship

The goal, design parameters, lesson design, scenarios, assessment, review, and client sign-off.

AI generation

A storyboard draft from the SME outline and a clickable prototype, built by Claude and Claude Code at my direction.

Open by design

The client saw and reacted to the course in days. Disclosing how is part of the work. How I use AI

Click through the prototype Try Maria's scenarios, explore the Teams screen, and take a knowledge check.

Need a course your team can see before it's built?

I'd love to hear what you're rolling out and how we could turn it into learning people actually use.

Let's talk