Home About Work Approach Impact Contact
← Back to Work
Project Management · Workfront

Product Launch Readiness

Leading an eLearning project end-to-end for a medical device product launch. From kickoff through LMS deployment, scope, schedule, and dependencies actively managed against a fixed go-live date.

Discover
Design
Build
Measure
4 Phases
Led End-to-End
100+ Learners
Trained
92.7%
Avg. Assessment Score
On Target
Delivered On Schedule 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 lead the eLearning workstream from kickoff through closeout, owning design, development, and delivery.

The complication: my schedule had a critical external dependency. The training content depended on technical documentation the engineering team was still writing, which meant my development milestones were tied to their delivery milestones. Managing that cross-team dependency without letting it slip the schedule 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
Project ownership, instructional design, LMS administration
The Work

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

A dedicated project plan with its own scope and schedule baseline

I built and owned a Workfront project plan to track every phase of the eLearning development independently from the broader product launch program. Four phases, 39 tasks, all dependencies mapped during planning. 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 to validate requirements. A shaver system has specific maintenance, troubleshooting, and escalation processes. Verifying each one with SMEs before storyboarding kept rework out of the build phase.

Holding the schedule against upstream dependencies

My development work depended on the engineering team finishing the product's direction-for-use guides and work instructions first. I tracked their progress against my milestones and proactively flagged risks when their timelines put mine at risk. Holding the schedule required consistent follow-up and early risk identification.

Performance targets defined before execution

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 targets shaped how I built the course and the performance metrics I tracked after launch.

Stakeholder Management
"Monthly status reviews from kickoff. Biweekly as the launch date approached. Stakeholders stayed aligned across the full project lifecycle."

From kickoff, I held monthly status meetings with the New Product Development (NPD) team and directors to review schedule performance, open items, completed milestones, and any risks to 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 subject matter experts for product knowledge. I worked directly with them to walk through every technical process and validate requirements 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 status reviews. Held approval authority on scope and delivery and stayed engaged across the full project lifecycle from kickoff through closeout.
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 schedule. 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 the project's success criteria: 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 before launch 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, with go-live close enough that the content stayed fresh.

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