01
Test in Market
In fast-moving markets, testing solutions in-market can be advantageous if you have development capacity to iterate quickly.
Product Design · Fintech · Lead Designer
Fidelity lost its loan verification partner, so I reframed enrollment as a read-back: show us your loan, we read it back instantly. The result: 67% of loans auto-verified, up from 0, and no 5-day wait for most participants.
Jump to the design
Fidelity lost its automated loan verification partner. Failed documents went to a 5-day manual review, and enrollees dropped off.
Reframed enrollment as a read-back: you show us your loan, we read it back instantly.
More loans verified automatically, more people finishing enrollment, and the 5-day manual review gone for most.
01 · CONTEXT
Fidelity lost its automated loan verification partner due to legislative changes, disrupting the student debt benefit enrollment process. When uploaded documents failed verification, they were sent to a manual review team with a 5-day response time via chat.
As the market leader in student debt workplace benefits, Fidelity faced mounting pressure as enrollment rates dropped and operational costs threatened profitability. The business model — priced per enrolled participant — made every abandonment costly.
Every document that fails auto-verification goes to a manual review, and that cost grows as the product gains users, so the goal is an estimated 85% auto-verification rate once all proposed solutions are live.
The original enrollment flow, before the redesign · select a screen to preview it
02 · HOW I FRAMED IT
Participants treated enrollment like mailing paperwork: upload something, then wait days to learn if it worked. That model hid every mistake until it was too late to fix. I reframed it as a conversation: you show us your loan, we read it back to you instantly, and you fix anything that's off before you leave. Guidance, servicer selection, and PDF extraction all serve that one idea. We ruled out adding more instructions up front, because users skipped text they couldn't act on yet.
I aligned partners on three goals (raise auto-verification, lift completion, cut drop-off) and a phased plan that shipped value every few weeks: guidance first, then servicer selection, then the feedback loop.
Pain points
Opportunities and insights
Pain points
Opportunities and insights
Pain points
Opportunities and insights
03 · KEY SOLUTIONS
Each moment shows what broke, what I tried, and what it changed. You can choose the happy path or the feedback loop path.
Dynamic benefit guidance up front
What was wrong
Our previous guidance page had large text blocks users likely skipped.
What shipped
Working with our enterprise patterns team, we designed an interactive component to encourage engagement with key information: benefit fit and document requirements.
In-market learning
Users dropped off when we linked out to plan details mid-enrollment. We moved the link to the guidance page, where people learn about the benefit, so enrolling never takes them out of the flow.
What I triedFrom where we started to what shipped · select one to preview it
Quick select loan servicer tiles
What was wrong
People typed their loan servicer’s name, so typos and inconsistent names made documents fail verification.
What shipped
A tile selector standardized the top five lenders, which cover 90% of loans.
What I triedFrom where we started to what shipped · select one to preview it
Fixing document issues in real time
What was wrong
Failed documents went to a manual review with a 5-day wait. People treated enrollment like mailing paperwork: submit, then wait. Many never came back.
What shipped
We read the PDF in real time, show what we found, and flag what’s missing while people are still in the flow. They choose to upload a better document or enter the detail.
What I tried5 directions before this shipped · select one to preview it
You’re enrolled, see what’s next
What was wrong
Next steps were unclear. People didn’t know whether they could start participating in the benefit, or what to do next.
What shipped
A clear confirmation of how to participate in the benefit. It makes it obvious the participant is enrolled and can start adding payments.
What I triedFrom where we started to what shipped · select one to preview it
NEGOTIATION OF THE SCOPE
With a vision that covered every use case, I led the negotiation across engineering, product and business partners to decide what could go into the first release. Engineering weighed in on what was feasible, product set its requirements, and I worked to find a middle ground that still balanced what users needed.

Not a PDF or unreadable
Return to upload with a message, or send the document for manual review.
First release
Servicer not found
Return to upload with a message, or continue with the servicer they selected and the account number we read.
First release
Account number missing
Return to upload with a message, or enter just the account number.
First release
Balance missing
Return to upload with a message, or enter just the balance.
First release
Participant name missing
Return to upload with a message, or review the extracted data.
First release
Servicer doesn’t match
Update the servicer to match the document, or upload a different one.
To be incrementally released
Loan paid off
Upload another document, or add a different loan with a balance.
To be incrementally released
More than one issue
Upload another document, or add the missing balance and account number.
To be incrementally releasedWHAT WE LEARNED AFTER LAUNCH
A participant’s name on their document didn’t match the one we had in our system, and our feedback page was generic in that case. So we used in-market data to choose the next release: a feedback page built for name mismatch, which helps people either correct the name or confirm the name on the document is theirs.
We expect this page to raise the auto-verification rate by about 10 points, to 77%.

Last name mismatch
New: confirm the loan is yours, or send it for review.
Next release
All other name mismatches
The existing page, which stays as is.
Unchanged04 · OUTCOMES
Each release raised auto-verification on its own. Together they got 30% more people through enrollment and removed the 5-day manual review for most of them.
A PATTERN THAT CARRIES INTO PAYMENTS
After enrollment, participants upload payment documents to get credit for the benefit, the same way they upload loan documents.
05 · KEY LEARNINGS
01
In fast-moving markets, testing solutions in-market can be advantageous if you have development capacity to iterate quickly.
02
Ground work in specific goals over lengthy requirement documents. For every decision, ask if it will move the needle to meet your goal.
03
Starting a project with technical restraints, even in a time crunch, can be limiting. Start with the best solution for the user, then scale back to what is achievable now.
Next project
Task Usage Predictor