LinkedIn · Sales Solutions Learning Center
Six weeks to launch.
Scope was the decision.
I led a 10-person squad across UX, Engineering and Customer Success through the Skilljar MVP launch and migration.
Make the launch boundary clear
Keep what each user needs.
Leave irrelevant content behind.
The hardest choice was what belonged in the six-week launch.
| Scope | Decision |
|---|---|
| Two role-based user flows | Preserved for launch |
| Irrelevant legacy content | Excluded from migration |
Lead the work across teams
A shared deadline.
Different dependencies.
I owned the roadmap, implementation and migration, connecting stakeholders, Product, the delivery squad and Skilljar. I made decisions about the desktop and mobile experience, adjusted scope around stakeholder priorities and sought additional people where needed.
Work through an integration failure
An authentication integration built by Engineering was failing to collect the expected data. I coordinated its resolution with internal and vendor engineers.
The squad launched the MVP and completed the migration in six weeks.
03 · Own the work after launch
Give people the means
to run what we launched.
I continued to own the platform roadmap and operations. I added advanced search and filtering, role-based learning paths and localization into seven languages.
Administrator self-service, documentation and training gave content managers more control over routine work. I documented uploads, tagging, user activation and permissions so nontechnical administrators could maintain content and presentation.
I also managed integrations and upgrades and established incident-response and release playbooks, helping sustain 99.9% uptime.
- Addressable audience
- 70K+
- Less content-management effort
- about 40%