Education Cannot Wait LMS

Built a learning management system that works where traditional schooling cannot reach. An offline-first platform designed for crisis-affected students in Cox's Bazar – Chattogram, Bangladesh, bringing structured education to 2,000+ learners despite intermittent connectivity and resource constraints.

RoleBusiness Analyst / PM
CompanySave the Children International
Timeline2022 - 2025
Team15 People (Cross-functional)
DomainEdTech, Global Impact, Humanitarian
Type0-to-1: Built from scratch
The Problem
Crisis-affected students in Cox's Bazar had no structured learning pathways. Existing platforms assumed reliable connectivity and ignored real classroom constraints on the ground.
The Solution
An offline-first LMS that works without internet, syncs when connectivity returns, and was shaped by direct feedback from teachers in the field, not from stakeholders in offices.
My Role
BA/PM on a 15-person cross-functional team, responsible for offline architecture decisions, in-country user research, and translating field constraints into product requirements.
The Impact
2,000+ students reached with structured education, 35% engagement lift, and the platform became the reference model for Save the Children's subsequent LMS projects.
The Challenge

Education in fragmented systems

Crisis-affected students in Cox's Bazar lacked structured learning pathways. Existing tools treated connectivity as a given and were disconnected from actual classroom needs on the ground.

01

Connectivity was assumed, not accommodated. The prior platform required reliable internet. In deployment zones with intermittent or no connectivity, it became unusable half the time. Students simply stopped trying.

02

Content was one-size-fits-all. A single English-language platform served a population with distinct languages, curricula, and cultural contexts. Teachers were forced to constantly adapt material that didn't fit their students' needs.

03

Requirements came from stakeholders, not users. Education specialists, IT teams, donors, and field staff had competing priorities. Teachers and students in crisis zones weren't asked what would actually work. UAT caught problems that cost a full sprint to fix.

The Approach

Rebuild for real constraints

The solution required rethinking what a learning platform meant in crisis contexts. Offline-first architecture, so learning never stops when connectivity fails. A single platform with per-country content and language layers, reducing maintenance burden while preserving local autonomy. And most importantly, continuous feedback from teachers in deployment zones, not just donors in offices.

Five core features emerged from this thinking, each addressing a specific bottleneck in how students actually learn.

5 core features redesigned for offline-first, inclusive learning
Platform Health

How the platform evolved across six dimensions

These six areas represent the full scope of what needed to change. Scores are rough estimates out of 10, based on capability and coverage before and after the work.

At launch (2022) Connectivity-dependent, single language, fragmented reporting, minimal field feedback loops.
Today (2025) Offline-capable, multi-language, unified reporting, continuous teacher feedback, interactive radio content.
Connectivity Resilience
Before: 2After: 9
Content Accessibility
Before: 3After: 8
Localization Coverage
Before: 2After: 9
Stakeholder Alignment
Before: 4After: 8
Engagement Quality
Before: 3After: 8
Reporting Clarity
Before: 2After: 9
Core Features

Five changes that matter in crisis education

Each feature below is paired with the problem it solved, the decision made, and the result. Numbers reflect actual usage patterns tracked across the Cox's Bazar deployment.

Shipped Feature 01

Offline-First Architecture — learning continues without connectivity

Before
Platform required active internet. Students in zones with intermittent connectivity saw loading spinners more than content. No learning happened offline.
→
After
Full offline capability. Text, audio, and interactive radio all work without connection. Content syncs when online, learning never stops.
100% of modules function offline
CONNECTIVITY STATUS
Online Mode
Offline Mode
Shipped Feature 02

Multi-Country Localization — one platform, five local contexts

Before
A single English-language platform forced teachers to adapt content to local contexts. What worked in one country's curriculum made no sense in another.
→
After
One platform with a localization layer. Each country has its own language, curriculum, and content—no separate codebases to maintain.
5 countries, one codebase, no duplication
DEPLOYMENT REGIONS
Syria
Sudan
Afghanistan
Ukraine
Yemen
Shipped Feature 03

Interactive Radio Content — learning that doesn't require reading

Before
Content was text-heavy. Many students had interrupted schooling and struggled with reading. Text-only modules created barriers to entry.
→
After
Built radio-style audio modules. Students listen, respond, and progress without reading. Works fully offline. Teachers found engagement tripled.
35% engagement increase after audio rollout
CONTENT TYPES
Text Modules
Audio Lessons
Interactive Radio
Quizzes (Offline)
Shipped Feature 04

Continuous Field Feedback — built with teachers, not for them

Before
Requirements came from stakeholders and donors. Teachers weren't consulted until UAT. Problems surfaced late, requiring full sprint rewrites.
→
After
Monthly field sessions with teachers in each country. Changes are driven by actual usage patterns, not assumptions. Issues caught at wireframe stage, not launch.
Monthly feedback cycles with in-country teachers
FEEDBACK CYCLE
Deploy
Collect
Diagnose
Fix
Shipped Feature 05

Unified Donor Reporting — consolidated impact data in one place

Before
Each country had its own tool. Producing consolidated impact reports for ECW donors required manual aggregation across 5 systems. Reports took days.
→
After
Single platform, unified reporting layer. All data feeds into one dashboard. Donor reports auto-generate from standardized metrics.
8 hours saved per reporting cycle (from 2 days to 2 hours)
REPORTING EVOLUTION
+ Country A report
+ Country B report
+ Country C report
+ Manual merge
→
Unified dashboard
Auto-aggregated
Instant exports
The Thinking

How I decided what to build and what to skip

The technical problem was solvable. The hard part was deciding which constraints were real and which were assumptions masquerading as requirements.

Finding the root problems

  • Ran structured interviews with education coordinators in each deployment region
  • Asked where the previous LMS had failed, not what new features sounded good
  • Two root causes appeared in every conversation: connectivity assumptions and content language rigidity
  • Everything else complained about was a symptom of those two

Why offline came first

  • Offline capability was non-negotiable. Without it, the platform cannot function in most deployment contexts
  • Phase 1 scoped to three content types that work offline: text, audio, and interactive radio
  • Video and live sessions moved to Phase 2
  • Some stakeholders pushed for richer media in Phase 1. The response: a video-enabled platform nobody can access is not better than a reliable one that works

One platform vs. five separate systems

  • The choice was a single platform with a localization layer versus separate per-country deployments
  • Per-country would have been faster for each team and allowed more customization
  • But it would have created 5 separate maintenance burdens and made consolidated donor reporting impossible. ECW required unified impact data
  • Chose the single platform, accepting higher upfront complexity for long-term sustainability

How engagement was measured

  • Login frequency was the wrong metric. Students used shared devices in scheduled lab sessions, not on demand
  • Tracked module completion rate (did students finish what they started?) and 30-day return rate (did they come back?)
  • Both tracked per country, not aggregated, so issues in one region could be diagnosed independently

What I would do differently

  • Involved in-country teachers earlier, before requirements were locked
  • Teacher feedback during UAT surfaced UX issues that cost a full sprint to fix
  • Those same issues would have taken an hour to catch at the wireframe stage
Explore the Platform

See it live

The ECW LMS is a live, actively used platform. Public-facing learning content and resources are accessible after account creation. The full platform experience including interactive radio modules can be explored there.

ECW LMS Platform
The live learning platform with accessible content, learning modules, and interactive radio features. Available after account creation and admin approval.
ecwlms.scibd.info ↗

The admin dashboard, content management system, and full analytics layer are not publicly accessible. A guided walkthrough including the interactive radio feature and multi-country localization can be arranged upon request.

The Outcome

Education delivered at scale in crisis contexts

The platform became the reference implementation for future Save the Children education initiatives. It proved that careful product thinking can extend educational access even in the hardest environments.

2,000+
Crisis-affected students gained access to structured learning modules
35%
Increase in engagement after feedback-loop driven iterations
Reference
Platform became the blueprint for all future Save the Children LMS projects