amansultan
scaling lesson production through modular architecture
Amansultan is a primary-school lesson platform used by teachers to assemble and deliver interactive lessons. As the library scaled (~700 lessons), production stalled.
I led the redesign of the lesson production system, addressing bottlenecks in workflow and architecture that created rework across roles — reducing lesson assembly from days to hours and enabling scalable curriculum production.
Amansultan · EdTech · Internal tools
operational bottleneck
The workflow worked at low volume but broke under continuous production.
Lesson assembly required coordination across 4-5 roles, and the monolithic editor amplified coupling — small edits cascaded across stages and triggered rework. A single lesson took 3-5 days, limiting throughput and delaying delivery.
Production couldn’t scale under growing curriculum demand.
architectural constraint
Both legacy editors were monolithic. Mechanics shared a single core and configuration layer, creating tight coupling.
Adding or modifying one mechanic required changes in the shared core — increasing complexity, slowing releases, and amplifying maintenance risk.
structural decision
I led the shift from a shared-core model to a modular, template-based editor architecture.
Each mechanic operates within a bounded context, isolating configuration and enabling independent evolution — enabling parallel production and reducing coordination overhead.
production model redesign
The new architecture enabled a structural shift in production. Editors worked within bounded mechanic templates instead of a shared configuration layer — removing cross-role dependencies and stabilizing the assembly flow at scale.
Lesson assembly moved from multi-day cycles (3-5 days per lesson) to same-day publication — enabling throughput of 10-30 lessons per week.
trade-offs
We constrained flexibility to enable scale.
Mechanic variety was intentionally limited to reduce coupling and engineering overhead — trading short-term breadth for long-term production stability.
impact & structural shift
The modular editor replaced fragmented workflows with a unified production foundation.
• lesson assembly reduced from 3-5 days to hours
• throughput increased to 10-30 lessons/week
• handoffs reduced from 4-5 roles to 2-3
• mechanic delivery cycles shortened from 4 weeks to 1-2 weeks
The editor became the primary production tool immediately after release — shifting the focus from building mechanics to scaling curriculum.
reflection
Scalable growth required structural clarity before flexibility. This shift reframed lesson production from manual coordination to a scalable system.