K–12 EdTechB2C

Cutting support tickets by 90% for a mandatory account migration

Designing a flow educators could finish on their own, without calling support.

  • UX writing
  • Usability testing
  • Interaction design
K12JobSpot upgrade prompt: a free upgrade to Frontline Passport, the K12JobSpot and Frontline Passport logos joined by an arrow, three icon-led benefits, and an Upgrade to Frontline Passport button.

The 30-second version

Problem

A mandatory change, mid job search

K12JobSpot users had to move from legacy credentials to a new Frontline account. The migration would interrupt every user while they were looking for work.

What I did

Designed a flow that works at a glance

Logos and icons carried the message. I tested copy variants with users and designed the success screen to teach the new sign-in.

Outcome

<1% escalation at launch

90% fewer migration tickets than the 2016 rollout. The flow went on to migrate about 12 million accounts.

01

Context

K12JobSpot is a job-search platform educators use to find openings across the country. As part of Frontline’s platform modernization, every user had to move from their legacy K12JobSpot credentials to a new Frontline account before they could keep browsing jobs.

Frontline had tried to unify accounts once before, in 2016, by migrating users in the background. Cleaning up the data problems that caused took significant customer service resources and was one of the reasons that initiative failed. For the company, this was an infrastructure project. For a teacher looking for work, it was an interruption at the worst moment, and any confusion risked losing them.

Role
Product Designer
Team
1 product designer (me), 1 platform UX designer, 1 K12JobSpot PM, engineering team
Timeline
2 months, K12JobSpot phase
Research
10 moderated usability sessions
Scope
End-to-end flow design, UI design, UX writing, usability testing
02

Decisions that shaped the flow

Research showed that migrating accounts in the background would fail again: there were too many accounts, and user data was too inconsistent across products. The platform designer and I proposed self-migration instead, product by product as each moved onto the new identity system. It kept the data clean and matched the vision for the new accounts: they belonged to the person and would follow them to B2C products after they left a job. The tradeoff was that users would migrate mid-login with no onboarding, so the flow had to work without support.

In the first round of testing, people skimmed past explanatory copy and filled in credential fields before they understood what was happening. Based on those results, I proposed the K12JobSpot and Frontline logos joined by an arrow as the main message, so even someone skimming understood they were moving from one account to another. On the credential screen, I replaced paragraphs with a short list of icon-led reassurances about account continuity, security and data safety. The logo pattern was reused at key moments throughout the flow.

The upgrade prompt: K12JobSpot and Frontline Passport logos joined by an arrow, three icon-led reassurances, and an Upgrade to Frontline Passport button.
The logos and arrow carry the message; each reassurance is one icon and one line.

I tested the copy and advocated for the words users preferred. In moderated sessions, “Upgrade your account” tested better than “convert” or “update,” and “Continue for free” reduced anxiety compared with “Continue to job listings.” I brought the findings to the product team and argued for the user-preferred language, even where it was less technically precise.

Copy variants tested in moderated sessions

TestedConvert your account
User preferredUpgrade your account
TestedContinue to job listings
Reduced anxietyContinue for free

I designed the success screen to teach the next login. Legacy and new sign-in paths would coexist for a while, and users were likely to fall back on old habits. The success screen uses the same “Sign in with Frontline Passport” button users would see on the new sign-in page, so finishing the migration also showed them where to log in next time.

Upgrade success screen: confirmation that the K12JobSpot account is now a Frontline Passport, the new username with a Copy button, and a Sign in with Frontline Passport button.
The success screen. Sign in with Frontline Passport is the same button users see on the new sign-in page.
03

Results & learnings

At launch, under 1% of migrating users contacted support, 90% fewer migration tickets than the 2016 rollout. Counting the engineering work the new approach avoided, we estimated about $100K in savings. The flow became the pattern for the rest of the migration, which eventually moved about 12 million accounts. It also worked beyond consumer products: when the same flow launched for Ohio SIS, a B2B product, the first 2,000 users migrated with zero support calls.

The lesson I took is that a mandatory change succeeds when the screen works for someone on autopilot.

Next case study · 03 Redesigning a low-NPS product towards unanimous buy-in from users Read next