Corporate Learning
This case study demonstrates how I designed a performance-based learning solution to support Microsoft Teams adoption across a federal enterprise environment. The solution combined instructor-led practice, cohort sandbox environments, job aids, asynchronous learning, and post-training support to address both skill gaps and resistance rooted in prior experience.
Project Snapshot
-
Environment: Federal enterprise IT
-
Audience: 800+ employees across multiple departments
-
Business need: Transition from Webex to Microsoft Teams
-
Performance challenge: Low confidence and resistance based on earlier Teams experiences
-
Solution: Hands-on ILT, cohort sandbox Teams, scenario-based practice, job aids, and asynchronous reinforcement
-
Impact: 97% satisfaction, 89% increased confidence, and approximately 35% fewer related support requests.
At a Glance
Microsoft Teams Adoption & Collaboration Training
Enterprise system transition in a hybrid work environment
Explore the Design Process
The Challenge
The organization was transitioning from Webex to Microsoft Teams.
Many employees preferred Webex and viewed Teams as unreliable or inefficient.
What the Analysis Revealed
The resistance was not simply caused by unfamiliarity.
Many employees had used early versions of Teams and formed lasting negative perceptions.
The learning solution therefore needed to do more than explain features—it had to rebuild confidence, demonstrate the platform’s evolution, and help employees experience successful collaboration firsthand.
Learning Objectives
By the end of the learning experience, participants could:
-
Navigate Teams, channels, posts, chats, and mentions to locate information and complete common collaboration tasks.
-
Create, share, co-edit, organize, and retrieve files across Teams, SharePoint, and OneDrive using appropriate file-management practices.
-
Select and use the appropriate communication or collaboration method for common workplace scenarios.
-
Manage file sharing, version history, access, and permissions in common internal and external collaboration scenarios.
Learning Strategy
This slide reframed the transition from Webex to Microsoft Teams by acknowledging prior experience and focusing on hands-on practice to rebuild confidence and support adoption.
Learning Strategy
Before training
Participants joined a dedicated cohort Team and became familiar with the training environment.
During training
Facilitator-led instruction was paired with immediate practice using realistic files, posts, channels, permissions, and collaboration scenarios.
After training
The cohort Team remained available as a practice space and resource center containing job aids, examples, session materials, and reinforcement resources.
This approach treated training as an extended adoption experience rather than a single event.
Solution Design
Live, facilitated practice
Participants brought their laptops and completed tasks as they were introduced.
Cohort sandbox environment
Each cohort used a dedicated Microsoft Team where learners could safely experiment without affecting production work.
Scenario-based workflow practice
Activities focused on realistic tasks such as posting, sharing files, co-editing documents, organizing content, and managing access.
Embedded performance support
Job aids and reference materials remained inside the Team so employees could access support in the same environment where they worked.
Solution Design
Selected Deliverables
Task-Based Job Aid: Microsoft Teams File Sharing
Selected excerpts from a job aid designed to clarify file sharing behaviors in chats versus channels and reinforce where files are stored in OneDrive and SharePoint. The resource was embedded directly into the training Team and knowledge base to support continued use after training.
Managing Channels & File Sharing Concepts
This slide was used to clarify where work happens in Teams—distinguishing between posts, notes, chats, and files—and to explain how content is stored across SharePoint and OneDrive. Visuals and concise explanations helped correct common misconceptions that previously caused frustration and mistrust of the platform.
By connecting collaboration behaviors to storage locations, learners gained confidence in finding, sharing, and managing documents correctly.
Training Activities (Scenario-Based Practice)
This slide illustrates how learning was structured around hands-on and scenario-based activities, not passive instruction. Learners practiced sharing files, collaborating on documents, creating private channels, and managing permissions using real-world scenarios aligned to their daily work.
The focus was on application during training, so learners left the session already having completed key tasks successfully.
Asynchronous eLearning (Adobe Captivate)
To extend the solution for employees unable to attend live sessions, and to demonstrate how the ILT experience could be translated into self-paced learning, I developed a companion Adobe Captivate course.
Format: Self-paced Adobe Captivate course
Purpose: Reinforcement and alternate access
Design: Modular, scenario-based, workflow focused
Interactions: Simulations, decisions, knowledge checks, and applied practice
Transfer: Tasks mirror common workplace collaboration activities
Course Structure (eLearning)
Course Structure
-
Microsoft Teams Today
-
Teams and Channels
-
Communication in Teams
-
File Collaboration
-
Organizing and Managing Work
-
Sharing, Permissions, and Security
-
Practice and Knowledge Check
Each module combines concise instruction with applied scenarios, interactions, and knowledge checks.
Learner Outcomes
-
Increased confidence using Teams
-
Improved understanding of file storage and sharing
-
Greater ability to complete collaboration workflows
-
Reduced confusion about Teams, SharePoint, and OneDrive
Organizational Impact
-
stronger adoption of Microsoft Teams
-
reduced reliance on email and legacy tools
-
fewer support requests
-
reusable solution for onboarding and future transitions
800+ Employees Supported
97% Learner Satisfaction
89% Reported Increased confidence
35% Reduction in Related Support Tickets