Completed onboarding
A healthy completion rate was masking what happened afterward.
Case study · Carrot Fertility
I led a five-week redesign of Sprints onboarding and Day 0, using an unexpected research signal to reframe a journey expansion into a broader retention opportunity.

In one minute
Improve early retention by simplifying onboarding and redesigning the Day 0 experience across the native iOS and Android apps.
Onboarding looked healthy at 90% completion, but that metric was not telling the whole story. 39.2% never returned, 29% did not log in once during the first seven days, and members who finished the long intake still waited up to 24 hours for access to their real program.
Product context
A fertility and family-building benefit offered by employers, supporting paths like egg freezing, IVF, IUI, adoption, surrogacy, and more.
Carrot’s metabolic health app, designed to help members build habits that support fertility and reproductive health. I was the Lead and only Product Designer on Sprints, responsible for all product design and UX research.
Starting point
A healthy completion rate was masking what happened afterward.
Members were willing to finish onboarding, but many did not come back.
Nearly a third did not log in once during their first seven days.
The work began as research for a Men’s Health expansion.
We wanted to understand what copy and messaging needed to change to make men feel welcome. Instead, onboarding became the bigger issue. 6 of 8 participants said it felt too long or were unsure how long it would take, revealing a problem we needed to fix before launch.
6 of 8 participants flagged onboarding as too long or unclear. That shifted the work from adapting one journey to improving the first seven days for everyone.

I reduced the mandatory questions in Onboarding and moved the rest into moments where they had context and purpose.
Day 0 was redesigned around three behavioral principles: the Goal Gradient Effect to make progress visible, the Endowment Effect to build investment through participation, and Progressive Disclosure to introduce questions when their purpose was clear. Members added one goal at a time, and each goal unlocked personalized suggestions so the value of setup was immediately clear.

After a long onboarding flow, members still had to wait 24 hours for their first recommendations while human moderators reviewed the AI output. That meant no immediate payoff after setup.
I challenged the delay with data: only 0.11% of recommendations were ever rejected by moderators. I brought that evidence to Product and Engineering and helped push toward a faster experience without losing the safeguard.
Skip human moderation for the first round of suggestions so members could begin immediately, then bring moderators back from Day 1 onward.

User research
The first study confirmed that the new onboarding was easier to complete, but only half of participants understood how their goals shaped personalized suggestions. I refined the copy, hierarchy, and goal-setting experience, then tested again.
By the second round, comprehension had improved and the shorter flow held up, giving the team confidence to move forward.
The shorter flow was easy to finish.
Clarity improved after refining goals, copy, and hierarchy.
Research moved the experience from shorter to clearer.
Development
The research gave us confidence in the core flow, so development shifted to turning those decisions into a complete product system across onboarding and Day 0. That meant defining how goals, personalized suggestions, empty states, and progress behaviors worked together in the shipped experience.

Measurement plan
The research validated that members could understand and complete the redesigned experience. After launch, the real measure of success will be whether that clarity translates into stronger retention and healthier engagement over time.
Goal: Increase
Goal: Improve
Goal: Maintain or improve
Goal: Improve
Looking back
This project reminded me that the best design work often starts by listening closely to users, recognizing when the problem is bigger than expected, and having the confidence to change direction.