Amplify Math Suite Experience

Unifying three products into one cohesive curriculum experience.

  • Amplify Math was evolving from a single core curriculum product into a full suite — Amplify Desmos Math (core), mCLASS Math, and Boost Math — sold in multiple combinations depending on what a district purchased.

    This created a hard content architecture problem. The platform's authoring system treated everything as "editions" — a parent/child structure where child content could only add or subtract from a single parent, never reorganize independently. That meant:

    • Content had to be authored once, with every product variation inheriting from the same source

    • No duplicating or restructuring content differently across editions

    • Three previously separate products now had to feel and function as one cohesive experience, regardless of which combination a district licensed

    The result needed to make sense visually and structurally whether a teacher had just core curriculum, or the full suite, or any combination in between — all from the same underlying content.

  • This case study spans two connected efforts:

    Design System — Directed across my team I owned the suite-wide style guide and UI kit, directing a team of designers, illustrators, and production designers to translate the content architecture into a consistent visual and interaction language across all three products.

    End-to-End User Journey — Led personally I led the initial build and gap analysis myself — mapping where the suite's user experience broke down across different licensing combinations. I then orchestrated workshops with product leadership to walk through those gaps, which directly informed the product requirements for new features. Suite design directors took that foundation and built out solo work from there.

    • Mapped the full content hierarchy across all editions to understand where the parent/child authoring constraint would create visual or structural conflicts

    • Built a visual diagram of the content architecture to align engineering, product, and design on the same mental model

    • Identified gaps in the existing user journey through this lens — where would a teacher's experience break or feel disjointed depending on their licensing combination?

    • Ran cross-functional workshops with product leadership using that gap analysis, translating findings into concrete product requirements

    • Directed the design team in building the style guide and UI kit that would hold up across every possible product combination

  • The Math Suite launched successfully as a unified, sellable commercial product — proving that three previously separate products could be authored once and presented coherently across every licensing combination a district might choose.

 
 
Back to Work