← Back to Work
Project Management · Workfront

Product Launch Readiness

Managing an eLearning project end-to-end for a medical device product launch. From kickoff through LMS deployment, every phase tracked, every dependency managed, delivered on time.

Discover
Design
Build
Measure
4 Phases
Managed End-to-End
100+ Learners
Trained
92.7%
Avg. Assessment Score
On Target
Delivered to Launch Date
The Problem
A new product was launching. Over 100 customer-facing employees needed to be ready before the first support call came in.

When a medical device company launches a new product, the pressure lands on everyone who touches customer support. Service engineers, product managers, and the broader customer-facing workforce all need to be prepared before the product ships. I was brought in as a consultant to design, develop, and manage the eLearning component from start to finish.

The complication: my timeline was not entirely mine to control. The training content depended on technical documentation the engineering team was still writing. My development milestones were tied to their delivery milestones. Managing that dependency without letting it slow the project down was half the job. In a product launch environment, training readiness and launch readiness are the same thing. If customer-facing staff can't field a support call on day one, the product launch feels the impact.

Audience
Customer-facing support staff, remote and in-branch
Delivery
eLearning + facilitated Q&A sessions
Tools
Articulate Storyline · Adobe Workfront · LMS
Responsibilities
Instructional design, project management, LMS administration
The Work

End-to-end ownership, from kickoff to deployment.

A dedicated project plan, separate from the product launch

I built and owned a Workfront project to track every phase of the eLearning development independently from the broader product launch program. Four phases, 39 tasks, all dependencies mapped from day one. Keeping the training project visible on its own meant stakeholders could see exactly where things stood without digging through a larger program board.

Process walk-throughs before the storyboard

Before writing a single slide, I walked through every workflow with the service engineers and product managers step by step. A shaver system has specific maintenance, troubleshooting, and escalation processes. Verifying each one before storyboarding meant the content was accurate from the start, not corrected after the fact during SME review.

Staying on schedule with upstream dependencies

My development work depended on the engineering team finishing the product's direction-for-use guides and work instructions first. Rather than waiting, I tracked their progress against my milestones and reached out proactively when timelines were at risk. Staying on schedule required consistent follow-up.

Measurement built into the project plan

Before development began, I defined what success looked like. Every assigned learner needed to complete the course, score above the passing threshold, and walk into the Q&A session without critical knowledge gaps. Those criteria shaped how I built the course and what I tracked after it launched.

Stakeholder Management
"Monthly check-ins from the start. Biweekly as the launch date approached. Everyone stayed aligned from kickoff to launch."

From kickoff, I held monthly status meetings with the New Product Development (NPD) team and directors to review timeline status, open items, completed milestones, and anything that could affect scope or delivery. As the launch date got closer, those meetings shifted to biweekly. In a product launch environment, the training project is one piece of a much larger program. Keeping my work visible and connected to the broader timeline meant stakeholders were never caught off guard.

Service Engineers
Primary source for product knowledge. I worked directly with them to walk through every technical process before storyboarding, confirming accuracy before development began.
Product Managers
Provided SME review during development and co-facilitated the Q&A sessions after training launched. Their sign-off was a required step before the course was finalized.
NPD Team & Directors
Key stakeholders in monthly and biweekly project meetings. Held approval authority and stayed engaged across the full project lifecycle, not just at launch.
Project Artifact

The project plan.

Workfront Gantt chart showing four project phases at 100% complete.
Assessment 21 days · 12 tasks
Design 50 days · 8 tasks
Development 59 days · 13 tasks
Implementation 14 days · 6 tasks
21 Days · Assessment
50 Days · Design
59 Days · Development
14 Days · Implementation

Adobe Workfront project plan. 4 phases, 39 tasks, delivered on target. Project Owner: Emberleigh Oracion. Planned completion: Oct 28, 2025. Status: Complete.

Results

The product launched. The team was ready.

Before the course launched, I defined what success looked like: every learner completing, scoring above the passing threshold, and no critical gaps surfacing in the Q&A. The eLearning was uploaded to the LMS and assigned on October 7th. The product launched October 31st. Three weeks of runway, no last-minute scramble, and a team that was ready when the first support call came in.

92.7%
Average Assessment Score
80% passing threshold required by the LMS. Learners retook the assessment until passing. Average reflects all completions across the full audience.
100%
Completion Rate
Competency-required training assigned in the LMS to all customer-facing staff. Every assigned learner completed before the product launch date.
3 Weeks
Ahead of Launch
Training was live and assigned 24 days before the product launched. Enough lead time for learners to complete and retain, not so far out that knowledge faded by go-live.

Full outcome data available on the Impact page. View Impact →