UX WORK › CASE STUDY
Closing the Door
Carefully.
UX WORK › CASE STUDY
Closing the Door
Carefully.
Deprecating phone-number-only accounts for 2M+ users without burning trust.
Role
Sole UX Designer
Timeline
July 2025 – January 2026
Scope
Migration UX, notification strategy, legal copy alignment, banner messaging
Team
1 Product, 3 Engineering, 1 Content, 1 Legal
TL;DR
The problem
2M+ legacy phone-number-only accounts were blocking a platform-wide messaging upgrade and costing $10K/month, but deleting them required reaching deeply disengaged users fairly and legally.
What I did
Led end-to-end migration UX, notification sequence design, in-product banner messaging, and iterative legal copy alignment; treating this as a human communication problem, not just an engineering cutover.
The key framing
The question wasn't "how do we tell users their account is being deleted." It was "how do we give genuinely disengaged users a fair chance to act?"
The result
Launched February 18, 2026, on schedule, with no escalations. $10K/month in costs eliminated. Platform-wide messaging upgrade unblocked. India platform rollout cleared to 100% completion.
OUTCOMES
↓$10K
monthly WhatsApp infrastructure costs eliminated
recurring savings
2M+
users migrated with legally compliant disclosure
primarily India
0
escalations on launch day
on schedule, Feb 18 2026
100%
India platform rollout
India program
THE PROBLEM
A feature that worked, until it didn't.
Phone-number-only accounts weren't a failed experiment. They were a deliberate inclusion bet, one that generated real early growth, then quietly became unsustainable.
Launched in late 2022, PNO accounts were designed to reach job seekers in India without email addresses, lowering the barrier to joining Indeed. The early signal was real: a 14% increase in account creation in India. The problem was what happened after sign-up.
Over time, the data told a different story. PNO users showed significantly lower long-term engagement and hire rates than standard accounts. Their Indeed profiles weren't searchable, the core way Indeed creates value for job seekers, which meant the accounts existed but couldn't fully participate in the platform. Account recovery had become non-functional following regulatory changes to phone recycling solutions. And the accounts required passwords, creating friction at odds with how Indeed was evolving its sign-in experience.
WHY DECOMMISSIONING BECAME NECESSARY
The path forward was clear. What wasn't clear was how to do it for millions of real users, many in India, many disengaged, without creating legal exposure or eroding trust with job seekers who might return someday.
MY ROLE
A communication problem, not just an ops problem.
Deprecation projects are often scoped down to "write the email." I owned the full communication experience and helped shape how the migration itself was sequenced.
I led UX for the end-to-end migration: banner messaging, WhatsApp and push notification UX, and the full copy and information architecture of the deprecation flow, including close collaboration with Legal on language that had to be accurate, enforceable, and still readable by someone who hadn't thought about their Indeed account in two years.
I also contributed to the PRD and evaluation documentation, helping shape how the migration was sequenced and what the decision criteria were for the account deletion phase.
DISCOVERY
Designing for disengagement, not against it.
These were users who hadn't logged in for two or more years. The design couldn't assume attention, it had to earn it.
A disengaged user reading a deprecation notice is in a different headspace than an active user responding to a product update. They're likely confused about why they're hearing from a platform they barely remember using. Dense, alarming, or unclear messages get ignored.
There was also a legal dimension shaping every decision. Notifications had to be legally defensible, not just clear, which meant UX work and legal review had to run in parallel, not sequentially.
THE DESIGN
A sequence, not a single blast.
NOTIFICATION SEQUENCE
Each touchpoint was calibrated to where users were in the timeline, what action was still available, and what urgency was appropriate.
KEY DESIGN DECISIONS
RESULTS
On schedule.
No escalations.
Platform unblocked.
The deprecation established a repeatable pattern for how Indeed handles legacy account migrations at scale with legal alignment, sequenced communication, and UX designed for disengagement.
Account deletion for non-migrated users was scheduled for May 19, following the full notification sequence. The migration affected sign-in flows for approximately 2 million users in India.
TAKEAWAY
The success was that nothing went wrong.
PNO deprecation is the kind of work that doesn't get celebrated. There's no launch moment, no new feature to point to.
But the design problem was real. PNO accounts were introduced to lower barriers for underserved users, and they worked, early on. Communicating their closure to those same users in a way that was both legally sound and genuinely fair to the people on the receiving end required the same rigor as any new product experience.
The costs are gone. The platform is unblocked. The work is done.