LMS Administration
Owning the platform that owns the learning. Configuration, governance, user lifecycle, and the migration that nobody else wanted.
- Role
- Sole administrator
- Scope
- Platform, content, governance
- Stakeholders
- CS, Sales, Product, HR
- Status
- Migration in progress
The situation I inherited
[Iliana — fill in: What did the LMS look like when responsibility landed on you? Was it being used? Was it the wrong platform? Was governance ad-hoc? 2-3 paragraphs.]
When I took ownership of the LMS, the platform had been adopted but not operated. Courses existed, but ownership was diffuse — anyone could publish, no one was accountable for accuracy, and retirement of stale content had never been formalized. The system was technically running. It was not technically working.
What I own, end to end
- Platform configuration — User roles, permissions, integrations, branding, and SSO.
- Content governance — Authoring standards, review cycles, retirement criteria.
- User lifecycle — Provisioning, deprovisioning, role changes, audit trails.
- Reporting — Engagement, completion, capability progression by team.
- Migration — Currently leading a full platform migration originally scoped to a now-departed HR role.
What I built
[Iliana — pick 2-3 specific things you built and describe each in a paragraph. Examples: a content governance model, a learning path structure, an onboarding curriculum, the migration plan itself, a reporting dashboard. Be concrete about what existed before and what exists now.]
What changed
[Iliana — fill in measurable outcomes. Even rough numbers work: "completion rates moved from X% to Y%", "course count grew from N to M with the same headcount", "ramp time reduced by Z weeks". If you don't have hard numbers, qualitative outcomes from stakeholders count too.]
What I'd do differently
[Iliana — this section is gold for hiring managers. It shows self-awareness. Pick one decision you'd make differently with hindsight, or one constraint you'd push back on harder next time.]