Learning Tree Global LMS

A multi-country learning platform delivering localized, culturally-relevant education to 1,200+ children across Guatemala, Colombia, Ukraine, Poland, and Pakistan.

RoleBusiness Analyst / PM
CompanySave the Children International
Timeline2022 — 2023
Reach5 Countries · 1,200+ Children
DomainEdTech · Localization · Humanitarian
The Challenge

One platform, five countries, infinite complexity

Teachers and caregivers in Guatemala, Colombia, Ukraine, Poland, and Pakistan needed a unified yet locally adaptable learning platform. Language barriers, infrastructure differences, and varying educational standards made this a deeply complex product challenge.

Existing tools were built for a single context — they weren't designed to flex across cultural, linguistic, and technological divides simultaneously. Any solution needed to feel local to each country while being manageable from a single administrative layer.

Coordinating a team across 5 country offices, each with its own curriculum teams and technical constraints, meant the delivery challenge was as complex as the product itself.

My Approach

Localization-first, async-ready delivery

01

Led product development coordinating across 5 country teams with different languages, curricula, and technical infrastructure requirements

02

Adapted the platform to regional needs — localized content, offline-capable learning modules, and culturally relevant UX for each context

03

Implemented Agile ceremonies adapted for async, cross-timezone collaboration — keeping delivery on track across wildly different working hours

04

Built per-region analytics to measure engagement and iterate on content effectiveness — data-driven decisions at the country level

05

Designed a modular architecture that could accept country-specific content packs — future-proofing expansion to additional regions

The Thinking

How I decided what to build and what to skip

Five countries meant five different opinions on what the platform should be. The work was deciding which differences were real requirements and which would fracture the architecture.

How I found the real constraints

  • Interviewed country coordinators across all 5 deployment regions
  • Every team wanted something different: Guatemala wanted gamification, Ukraine needed offline-first due to power cuts, Pakistan needed content controls, Colombia wanted bilingual support
  • The question shifted from "what features to build" to "how much customization can one platform support before it splits into 5 separate codebases"

How I cut the feature list

  • Built a feature matrix scoring each request on 3 dimensions: how many countries need it, how easily it localizes without branching the code, and expected impact on learning outcomes
  • Offline module support scored highest. Every country needed it, it was architecturally clean, and coordinators ranked access reliability first
  • Gamification scored high on engagement but was hard to localize. Different cultures respond to competition differently. Moved to Phase 2
  • Parental controls were required in two markets, neutral in others. Added as a configurable option in Phase 1

The content governance tradeoff

  • Country teams wanted direct CMS access to manage their own content. A fair request as they knew local curricula better than anyone centrally
  • The risk: a content error in Pakistan could go live unreviewed and reach hundreds of children before anyone caught it
  • In a humanitarian context, that was not acceptable
  • Resolution: staged publishing. Country-level draft, central review, then publish. Teams pushed back on the added step. The tradeoff held

How engagement was tracked

  • Did not aggregate into a single global number. Each country had a different access model
  • Tracked module completion rate and session return rate per country cohort
  • Ukraine scored lower than others early on. Not because of content quality but because power cuts were interrupting sessions mid-module
  • Fix: auto-save every 2 minutes, resume from the exact point. Ukraine completion rate came in line with the other cohorts after that
Reflection

What I would do differently

  • Would invest more time upfront setting communication rhythms with the country teams
  • Each team had a different review cadence. We lost weeks waiting on feedback that clearer agreements would have surfaced faster
  • Defining turnaround windows, one channel per decision type, and a clear escalation path in week 1 would have been worth more than most scope decisions made later
Explore the Platform

See it live

Learning Tree is a live, multi-country platform. The web dashboard is accessible and gives a real sense of the localization, content architecture, and user experience across regions.

Learning Tree Web Platform
The live web dashboard — browse localized learning content, see how multi-country content architecture works, and explore the teacher and admin experience.
lt.scibd.info ↗

The admin content management system, per-region analytics, and full localization workflow can be walked through in detail upon request.

The Outcome

A global blueprint, locally delivered

The platform's modular architecture became the blueprint for subsequent Save the Children LMS projects worldwide — proving that a single product, thoughtfully designed, can serve radically different contexts.

1,200+
Children reached with localized, accessible learning content
5
Countries served — Guatemala, Colombia, Ukraine, Poland, Pakistan
30%
Increase in engagement during early adoption across country cohorts