Global Learning at Scale
ENTERPRISE LMS ARCHITECTURE AND UX
Designing a seamless, multilingual learning experience for a global audience from end-to-end
TAKE A TOUR
How I built this
UX Action Mapping | A design activity that maps the end user's journey.
​
Four-Column Video Script | A production blueprint that aligns visuals, narration, on-screen text, and notes in a single document.
Course Outline Template | Developed to standardize translation process and ensures consistency across all language versions.
AT A GLANCE
210,000
END USERS
200+
COUNTRIES & TERRITORIES
9
LANGUAGES
THE CHALLENGE
An international membership organization with over a century of history needed to rethink how it delivered learning to its members. The existing LMS was unstable, unable to support the organization's scale, and creating a fragmented experience that didn't reflect the standard of excellence the brand was known for.
​
The scope was significant: 80,000 active end users across more than 200 countries and territories, community leaders and business professionals who expected a high-quality, polished experience - and who would notice when it fell short.
​
The goal wasn't just to replace a broken system. It was to build a future-ready learning infrastructure that could grow with the organization and serve its members wherever they were, in whatever role they held, and in the language they actually learned in.
.png)
MY ROLE
I served as enterprise project visionary - the person responsible for keeping the organization's future in view while the day-to-day complexity of implementation unfolded around us. That meant championing learning best practices, facilitating alignment across a highly diverse cross-functional team, and being the connective tissue between business needs and technical decisions.
My involvement was truly end-to-end: requirements gathering, RFP development, vendor evaluation, implementation leadership, and measurement design. I didn't hand things off - I stayed in it.
​
Our core team included an HR Manager, Project Manager, IT Director, and Systems Architect. We brought different disciplines, different cultural backgrounds, and different ways of working and diversity made every decision sharper.
THE COMPLEXITY WE WERE SOLVING FOR
A database that didn't play well with others. The organization's member database was a custom-built, legacy system with over 100 years of institutional history behind it. It didn't integrate with commercial SaaS solutions out of the box. Our SSO solution required a CRM token-based approach - carefully designed so that members could move seamlessly between the public website and the LMS without ever experiencing a login barrier.
​
Nine languages. No shortcuts. Not a single LMS on the market had all nine required languages natively built in. Many vendors relied on auto-translation engines - and the results were unreliable, often inaccurate, and inconsistent with the organization's voice. We specifically sought a platform with a customizable localization editor that could be used by human translators, not algorithms. Every language string was reviewed and corrected by people who actually spoke the language.
​
Two audiences. One platform. Beyond the member-facing experience, we also needed to build out a second domain within the same LMS instance to support employee learning and development across seven international offices. This required clear governance, thoughtful architecture, and a system structure that kept both audiences' experiences distinct and purpose-built.
​
Governance at scale. With courses available in nine languages and a team where no single person spoke all nine, file organization and LMS governance became mission-critical. We invested heavily in process documentation - folder structures, naming conventions, workflow standards - so that any team member could confidently work within the system and maintain quality without ambiguity.
​
Ongoing stewardship. Every platform update required coordination with our interpretation team. A SaaS solution doesn't run itself - especially not at this level of localization complexity. We built a roadmap and a maintenance vision from day one, because we knew that sustaining quality over time required as much intentionality as launching did.
MEASURE WHAT MATTERS
+80
Average Course NPS
+18
Additional LMS Languages
+0.9
Net Sentiment Score
.png)
What I learned
Governance is part of design | The folder structures, naming conventions, and workflow documentation turned out to be some of the most important work we did. It isn't about red tape- it's about sustainability and quality.
​
Translation isn't localization | Auto-translation failed every evaluation. Multilingual organizations need to design frictionless collaborative workflows to maintain their instance.
​
The team was the achievement | Every technical outcome was the product of something less visible: a team that genuinely trusted each other. That's not a footnote - that's the whole story.