K–12 EdTechB2B/Enterprise SaaS

Redesigning a low-NPS product towards unanimous buy-in from users

Redesigning the lowest-rated product in Frontline’s suite around what 750,000 educators actually log in to do.

  • Information architecture
  • UX strategy
  • Visual hierarchy
  • Design systems
Redesigned Professional Growth Home: a To do list grouped by urgency, current activities with progress, meetings and requests.

The 30-second version

Problem

Lowest NPS of all seven Frontline products

Teachers dreaded logging PD. One missed a raise because their hours never got submitted.

What I did

Proposed the initiative, then found where to start

Analytics and ODI pointed to the landing page.

Outcome

Shipped to pilot; 6 of 6 participants positive

New patterns adopted as React components across Frontline.

Before: the original My Growth Journey dashboard, dense and unprioritized, with no clear next action. After: the redesigned Home dashboard, with to-dos grouped by urgency and meetings and requests surfaced.

Drag to compare the legacy dashboard with the redesign.

01

Context

Professional Growth is where teachers track and complete their professional development. It serves 750,000 educators across 1,500 districts. Its landing page, My Growth Journey, had already been redesigned once, and after launch the product had the lowest NPS of Frontline’s seven products. Teachers dreaded logging in. One missed a raise because their PD hours never got submitted.

I joined after that redesign as the only designer on the product.

Role
Senior Product Designer
Team
1 designer (me), 1 group PM, 2 PMs, 1 eng lead, 2 dev teams (one offshore, 12 hours ahead)
Timeline
9 months, Jan–Sep 2025
Scope
Research, strategy, end-to-end design, design system
Constraints
Legacy pages on an older stack; Angular homepage laying groundwork for React; Summer 2025 MVP target
02

Finding where to start

At a roadmap brainstorm, I proposed improving navigation. People had trouble finding anything, and the mix of legacy and redesigned pages made the product feel disconnected. To decide where to start, I reviewed page analytics alongside our ODI interviews. Every user landed on My Growth Journey, and almost none clicked any of its links. They went straight to My Learning Plan. That made the landing page the highest-impact place to begin. It needed to show teachers what needed attention and let them act on it.

The legacy My Growth Journey landing page: growth-journey tabs, activities in progress, attention required, requests and a column of recommendations.
My Growth JourneyWhere everyone landed.
The legacy My Learning Plan page: a dense My Requests table grouped by status, from drafts and approvals to final credit and completed activities.
My Learning PlanWhere they went instead.
03

Decisions that shaped the product

I renamed the categories to match how existing users thought about their work, since the growth-metaphor language didn’t resonate with them. I also cut a whole branch of the IA. Content discovery had a full top-level branch, and no participant used it. Rebuilding it depended on districts tagging content and users setting goals, and neither was in place. I removed it and left room to bring it back.

Annotated IA diagram of My Growth Journey
BeforePriority tasks buried two levels deep across three branches. Red: high-frequency tasks. Orange: valued but less frequent.
IA diagram of Home
AfterThree branches matching how users relate to their work. The dashed branch marks planned future investment.

I created a visual hierarchy for urgency without adding a component. The standard card gave every tile equal weight. Primary tiles kept the white card, and secondary tiles dropped the fill and sat back on the page. The Principal Designer flagged it as a pattern for other products.

Redesigned Professional Growth Home: To Do and Current Activities on white cards, with Requests and Meetings set back on the page surface.
White cards pull urgent content forward; secondary tiles sit back.

I argued to keep a page Product wanted to retire. Analytics showed My Learning Plan was where users actually managed their activities. I designed a modernized version to show a path forward, and it stayed until the new Home page had usage data.

Proposed Learning plan page: My requests with progress toward credit on the left, and the evaluation cycle with action required, scheduled, in progress and complete steps on the right.
My proposed Learning plan: requests and their progress toward credit beside the year’s evaluation cycle.
04

Results & learnings

All six validation participants responded positively and understood the to-do panel without explanation. The redesign shipped to pilot and reached general availability in 2026. The set-back tile and several new patterns were approved as React components across Frontline.

The lesson I took is to let the evidence decide where a broad problem starts. Navigation touched the whole product, and the landing page was where one change would reach every user.

Next case study · 01 Reducing risk during the highest-volume week in staff contracting Read next