Sign-Up Flow Overhaul

Sign-Up Flow Overhaul

Sign-Up Flow Overhaul

Sign-Up Flow Overhaul

Timeline

Timeline

Jul 2022 - Oct 2022

Jul 2022 - Oct 2022

Responsibility

Responsibility

Responsibility

End-to-end design process

End-to-end design process

Company

Company

Company

Carousell

Carousell

Overview

Overview

Overview

Carousell is a C2C marketplace operating across Southeast Asia, Taiwan, and Hong Kong. By 2022, the product was mature, but the data told a different story at the top of the funnel.


Only 20% of new users were completing the sign-up flow. That meant 8 out of 10 people who tried to join never made it through. As the sole designer on this project, I led the end-to-end redesign of the sign-up experience, from research through to final delivery, with the goal of removing friction early enough to give users a reason to stay.

Given the resource constraints we were working with, we launched in phases, tackling the highest-impact changes first.

Impact

Impact

Impact

โ†—22% Increase completion of sign-up flow
โ†—13% Increase in the growth of new users

โ†—22% Increase completion of sign-up flow
โ†—13% Increase in the growth of new users

โ†—22% Increase completion of sign-up flow
โ†—13% Increase in the growth of new users

๐Ÿค”

We know there's a significant percentage of sign-up failures. And we want to understand more about where and why they fail...

๐Ÿค”

We know there's a significant percentage of sign-up failures. And we want to understand more about where and why they fail...

I started by pulling six months of funnel data to map where users were dropping off. The pattern was clear: the biggest drop-offs weren't on the account creation steps โ€” entering an email or setting a password. They were on the personalization steps: selecting interest categories, following recommended sellers, and setting up a feed before users had any context for what the app actually offered. We were asking users to make decisions about a product they hadn't experienced yet.

To understand the "why" behind the numbers, I conducted interviews with 8 users across three groups: people who had never used Carousell, casual users, and more active sellers. The sessions revealed a consistent pattern, users felt the app was pushing a seller identity on them before they'd decided how they wanted to use it. As one user put it: "It's a lot to do with selling phones, I'm getting a feeling I need to sell something โ€” feels like a seller-oriented app." Several others tried to skip through the personalization steps as fast as possible just to get to the product.

Competitive analysis

Competitive analysis

Before moving into design, I also ran a competitive analysis across similar marketplace apps to benchmark common onboarding patterns. The key takeaway: the best-performing flows shared one principle โ€” get users to their first valuable moment as fast as possible, and defer personalization until they have enough context to make meaningful choices.

Before diving into the design process, we conducted a competitive analysis. This allowed us to establish benchmarks that we could leverage throughout the design phase.

3 problems emerged from the research

3 problems emerged from the research

  • The flow asked too much, too soon. Users were required to select interests, follow sellers, and configure a feed before they'd seen what Carousell had to offer. The steps weren't wrong โ€” the placement was.

  • The onboarding created the wrong first impression. Seller-focused choices early in the flow made buyers feel the app wasn't built for them. A single undifferentiated flow was failing three distinct user types: buyers, casual sellers, and merchants.

  • Several screens lacked clarity. Outdated UI patterns and ambiguous instructions left users making decisions without enough context to make them confidently.

Design

Design

To move from problems to solutions, I ran a workshop with the PM and researcher. Working from the three personas, we framed the challenge as a single HMW:

๐Ÿ’ก
"How might we design a concise and quick sign-up flow that only asks necessary questions, allowing users to experience the product first."

The strongest idea to emerge was a personalized entry point โ€” letting users identify as a buyer, casual seller, or merchant at the start, then tailoring the flow to match. It directly addressed the wrong-first-impression problem and would have made the experience meaningfully different for each user type.

New flow: Personalized entry point

๐Ÿšจ
Then we looked at the timeline and realized we weren't going to make it.

๐Ÿšจ
Then we looked at the timeline and realized we weren't going to make it.

Rather than delay the entire release, I worked with the PM to phase the work. Phase 1 focused on the highest-impact, lowest-complexity changes: removing confusing screens, simplifying personalization, and updating UI components to the new design system.


The personalized entry point โ€” which required significant backend work โ€” moved to Phase 2.It wasn't the ideal solution. But a meaningfully better experience now was more valuable than a perfect one later.

Ideation

With the scope defined, I focused the final design on three changes that directly addressed the problems we'd identified. Simplified the flow from 6 steps to 3. The removed steps were the personalization-heavy ones โ€” selecting interest categories, following recommended sellers, and configuring a feed. These weren't deleted permanently; they moved to post-onboarding, where users would have enough context to make those choices meaningfully. What remained: account creation, minimal profile setup, and a direct path into the product.

Final design

Final design

We simplified personalization to just gender and age. Instead of asking users to manually curate their experience upfront, recommendations became automatically tailored based on basic inputs. Less friction, same personalization outcome.


Updated UI to the new design system. Outdated components were replaced, ambiguous instructions rewritten, and visual hierarchy clarified across every screen.

Web design

Web design

For the web version, I extended the same flow while adapting it for the platform's constraints. Unlike mobile, web doesn't have native components for things like date pickers, dropdowns, or permission prompts, each had to be rebuilt using web-native patterns while maintaining visual consistency with the app.

The goal was for a user moving between platforms to feel like they were in the same product, even if the underlying components were different.

Results

Results

Phase 1 shipped on schedule. The results were meaningful:

22%

22%

22%

Increase completion of sign-up flow

Increase completion of sign-up flow

Increase completion of sign-up flow

13%

13%

13%

Increase in the growth of new users

Increase in the growth of new users

Increase in the growth of new users

๐Ÿ”…
For a flow that 80% of users had previously abandoned, moving the needle this much with Phase 1 alone validated the core hypothesis: the drop-off wasn't about the product โ€” it was about asking too much before users had a reason to care.

๐Ÿ”…
For a flow that 80% of users had previously abandoned, moving the needle this much with Phase 1 alone validated the core hypothesis: the drop-off wasn't about the product โ€” it was about asking too much before users had a reason to care.

Reflection

Reflection

Two things I'd carry into the next project:

  1. Constraints are a design input, not just a limitation. The timeline pressure that forced us into phases ended up being clarifying, it made us ask which changes actually mattered most. The personalized entry point was the "right" solution, but Phase 1 proved we didn't need it to make a significant impact. Sometimes shipping the 80% solution teaches you more than waiting for the 100% one.

  2. Phased releases need a plan, not just a promise. We shipped Phase 1 with a clear intent to follow up, but "Phase 2" without a concrete timeline is just a good intention. Next time, I'd push for Phase 2 to be scoped and scheduled before Phase 1 ships, not after.

Next: Design System Revamp โ†’

Top โ†‘

Email

Copied!

ยฉ 2026 Ryan Chang

Email

Copied!

ยฉ 2026 Ryan Chang