LessonLoop v3 Product Overhaul

Turning a founder’s vision into a product teachers describe as easy to use

Visuals in this case study are limited due to NDAs and proprietary information.

The LessonLoop cycle: Plan, Teach, Assess, Grow
The LessonLoop cycle: Plan, Teach, Assess, Grow

Timeline

Mar 2026 – present (v3: May–Aug 2026)

My Role

Fractional Product & UX Lead

Skills Used

Product Design Strategy

Prioritization

UX Strategy

Task-based Design

UX Design

UI Design

User Need Advocacy

Cognitive Load Theory

Design Systems & Libraries

Front-end (HTML, React, Angular, Vue)

Goal

Turn the founder’s vision for LessonLoop into a usable product for teachers by completely redesigning and rebuilding v2 into a v3 that makes the core teaching workflows clear and easy to use.

Constraints

  • Non-profit startup with a very limited budget

  • Existing codebase from 2020 that was partway through a migration from Bootstrap to PrimeVue

  • One person covering product management, UX/UI design and development

  • Four months to redesign and rebuild the core experience

  • Balancing the founder’s vision with teacher needs and startup resources

Summary

As the fractional product and UX lead, I own product management, UX/UI design and development of both the Vue front end and the APIs behind it. Using my UX, classroom and EdTech expertise, I translated the founder’s broad concepts into concrete workflows, information architecture and UI, and then led a complete redesign and rebuild of the product from v2 to v3 in four months. Teachers described the new v3 as “night and day easier to use” than v2.

4 Months

Time to complete the v2 to v3 redesign and rebuild (May-August 2026)

“Night and Day”

How teachers described v3’s ease of use compared to v2

3 Roles

Product management, UX/UI design and full-stack development owned end to end

Process

From Founder Vision to Teacher Workflows

LessonLoop began as a strong vision from its founder: a loop that teachers move through to plan, teach, assess and grow. The challenge was turning that vision into a product that a teacher could open and immediately understand what to do next.

I used my experience as a classroom teacher and EdTech designer to translate the founder’s broad concepts into concrete teacher workflows, information architecture and UI. I also owned the product strategy, roadmap and prioritization, balancing what the founder wanted to build with teacher needs and what a small startup could realistically deliver.

From founder vision to teacher workflows

LessonLoop began as a strong vision from its founder: a loop that teachers move through to plan, teach, assess and grow. The challenge was turning that vision into a product that a teacher could open and immediately understand what to do next.

I used my experience as a classroom teacher and EdTech designer to translate the founder’s broad concepts into concrete teacher workflows, information architecture and UI. I also owned the product strategy, roadmap and prioritization, balancing what the founder wanted to build with teacher needs and what a small startup could realistically deliver.

From founder vision to teacher workflows

Decision

Treat the LessonLoop loop as a cycle rather than a linear sequence. Teachers can start at either Plan or Assess, so the guided flows allow teachers to begin where they are and resume where they left off instead of forcing every teacher to start at step one.

Decision

Treat the LessonLoop loop as a cycle rather than a linear sequence. Teachers can start at either Plan or Assess, so the guided flows allow teachers to begin where they are and resume where they left off instead of forcing every teacher to start at step one.

The v3 Overhaul

Problem

The existing codebase dated back to 2020 and was partway through a migration from Bootstrap to PrimeVue, resulting in a mix of legacy and new UI patterns across the product.

Solution

I moved the Educator Portal - Class Hub, surveys, loops and the lesson planner - onto PrimeVue and a coded, token-based LessonLoop theme, so new and existing work share one design system.

Years of feature additions had left pages and components that were no longer used or were duplicated.

I inventoried every page and component in the product (233 files) and removed the dead and duplicate pieces along the way.

With a very small team, a separate handoff from design to development would have slowed the overhaul down.

I designed the new experience and built it myself in Nuxt and Vue over four months (May-August 2026), removing the design-to-development handoff entirely. Onboarding, the guided stepper flows and the teacher profile were all rebuilt as part of the overhaul.

Before and after: how every screen is styled

Problem

The existing codebase dated back to 2020 and was partway through a migration from Bootstrap to PrimeVue, resulting in a mix of legacy and new UI patterns across the product.

Solution

I moved the Educator Portal - Class Hub, surveys, loops and the lesson planner - onto PrimeVue and a coded, token-based LessonLoop theme, so new and existing work share one design system.

Years of feature additions had left pages and components that were no longer used or were duplicated.

I inventoried every page and component in the product (233 files) and removed the dead and duplicate pieces along the way.

With a very small team, a separate handoff from design to development would have slowed the overhaul down.

I designed the new experience and built it myself in Nuxt and Vue over four months (May-August 2026), removing the design-to-development handoff entirely. Onboarding, the guided stepper flows and the teacher profile were all rebuilt as part of the overhaul.

Before and after: how every screen is styled

Impact

Teachers described v3 as “night and day easier to use” than v2.

Impact

Teachers described v3 as “night and day easier to use” than v2.

AI Lesson Planning

I designed a unified lesson planner that handles four different starting scenarios within one experience, with AI responses streaming in as they are generated and the teacher’s own uploaded materials used to inform the plan. I built both the planner UI and the API endpoints behind it on a serverless back end (AWS Lambda, DynamoDB and Bedrock).

Four starting scenarios feeding one unified lesson planner

I designed a unified lesson planner that handles four different starting scenarios within one experience, with AI responses streaming in as they are generated and the teacher’s own uploaded materials used to inform the plan. I built both the planner UI and the API endpoints behind it on a serverless back end (AWS Lambda, DynamoDB and Bedrock).

Four starting scenarios feeding one unified lesson planner

Guiding Principle

AI planning tools should start from the teacher’s own materials and classroom context rather than a blank prompt, reducing the cognitive load of figuring out what information the AI needs in order to be helpful.

Guiding Principle

AI planning tools should start from the teacher’s own materials and classroom context rather than a blank prompt, reducing the cognitive load of figuring out what information the AI needs in order to be helpful.

Making Student Voice Data Usable

LessonLoop’s surveys capture how students and educators are doing. I redesigned how those results are shown to teachers and leaders, including class profiles and trends over time, question-level results grouped by what each measure is about, reflection logs, and CSV exports for teachers and admins who want to work with the raw data.

For district and school leaders, I designed and built a new admin portal for managing districts, schools, users and accommodations, replacing the legacy admin pages that were spread across the product.

Survey data turned into teacher views and an admin portal

LessonLoop’s surveys capture how students and educators are doing. I redesigned how those results are shown to teachers and leaders, including class profiles and trends over time, question-level results grouped by what each measure is about, reflection logs, and CSV exports for teachers and admins who want to work with the raw data.

For district and school leaders, I designed and built a new admin portal for managing districts, schools, users and accommodations, replacing the legacy admin pages that were spread across the product.

Survey data turned into teacher views and an admin portal

Takeaway

Results are organized around what each measure tells a teacher about their class, including a “How to Read this Room” card.

Takeaway

Results are organized around what each measure tells a teacher about their class, including a “How to Read this Room” card.

What’s Next: A Teacher Home Page

With v3 launched, I’m now designing a teacher Home page - a cross-class landing page shown on login that is separate from the single-class Class Hub. After reviewing options with stakeholders, we’re moving forward with a hero-led direction that shows returning teachers where they left off, and gives new teachers minimal text and two clear places to start: Plan or Assess.

Teacher Home page directions for returning and new teachers

With v3 launched, I’m now designing a teacher Home page - a cross-class landing page shown on login that is separate from the single-class Class Hub. After reviewing options with stakeholders, we’re moving forward with a hero-led direction that shows returning teachers where they left off, and gives new teachers minimal text and two clear places to start: Plan or Assess.

Teacher Home page directions for returning and new teachers

Get in Touch

Get in Touch

Get in Touch

Subscribe to EdTech Insights