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.

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.
Drag to compare the legacy dashboard with the redesign.
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
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.
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.
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.
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.
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.
