I redesigned Donut's onboarding flow to make it more flexible and intuitive, helping increase product installs by 30% and trial-to-paid conversion by 10%.

Donut's previous onboarding design was made for a single product install. But as the offerings grew into a suite of products (Intros, Watercooler, Celebrations, and Onboarding), the way first time users learned about Donut needed a radical change.

CHALLENGE

Redesign an onboarding flow to help expand Donut's growing suite of tools, without losing the magic of its simplicity and remaining true to its established design language

ROLE

I partnered closely with data scientists, PMs, and engineers to identify business critical metrics, conduct user research, and design iteratively to address important KPIs

TEAM

Myself (UX and UI Design)

1 Product Manager

2 Developers

TIMELINE

2 Months

I redesigned Donut's onboarding flow to make it more flexible and intuitive, helping increase product installs by 30% and trial-to-paid conversion by 10%.

Donut's previous onboarding design was made for a single product install. But as the offerings grew into a suite of products (Intros, Watercooler, Celebrations, and Onboarding), the way first time users learned about Donut needed a radical change.

CHALLENGE

Redesign an onboarding flow to help expand Donut's growing suite of tools, without losing the magic of its simplicity while remaining true to its established design language

ROLE

I partnered closely with data scientists, PMs, and engineers to identify business critical metrics, conduct user research, and design iteratively to address important KPIs

TEAM

Myself (UX and UI Design)

1 Product Manager

2 Developers

TIMELINE

2 Months

Celebrate your teammates birthdays and anniversaries!

Celebrate your teammates birthdays and anniversaries!

Celebrate your teammates birthdays and anniversaries!

Recreate Watercooler conversations, virtually!

Recreate Watercooler conversations, virtually!

Recreate Watercooler conversations, virtually!

Introduce colleagues

from different departments for a quick chat!

Introduce colleagues

from different departments for a quick chat!

Introduce colleagues

from different departments for a quick chat!

👋 Welcome to Donut!

👋 Welcome to Donut!

👋 Welcome to Donut!

Get Started

Get Started

Get Started

donut

donut

donut

Donut helps your organization build collaboration, community, and camarederie, without leaving Slack!

Donut helps your organization build collaboration, community, and camarederie, without leaving Slack!

Donut helps your organization build collaboration, community, and camarederie, without leaving Slack!

Here’s your Topics Queue

Here’s your Topics Queue

Here’s your Topics Queue

You can configure this queue at a later step.

You can configure this queue at a later step.

You can configure this queue at a later step.

Set up Intros

Set up Intros

Set up Intros

Step 1

Step 1

Step 1

Add Members

Add Members

Add Members

Step 3

Step 3

Step 3

Set up Watercooler

Set up Watercooler

Set up Watercooler

Step 2

Step 2

Step 2

Watercooler Presets:

Watercooler Presets:

Watercooler Presets:

Channel

Channel

Channel

i

i

i

Select a channel

Select a channel

Select a channel

or create a new channel

or create a new channel

or create a new channel

Scheduling

Scheduling

Scheduling

i

i

i

Every Monday at 10AM EST

Every Monday at 10AM EST

Every Monday at 10AM EST

Topic Header

Topic Header

Topic Header

i

i

i

Time for a Watercooler topic

Time for a Watercooler topic

Time for a Watercooler topic

Finish Watercooler Setup

Finish Watercooler Setup

Finish Watercooler Setup

Skip Watercooler Setup

Skip Watercooler Setup

Skip Watercooler Setup

Back to Intros Setup

Back to Intros Setup

Back to Intros Setup

Mon, Feb 1

Mon, Feb 1

Mon, Feb 1

What’s your favorite type of potato?

What’s your favorite type of potato?

What’s your favorite type of potato?

Preview

Preview

Preview

Mon, Feb 7

Mon, Feb 7

Mon, Feb 7

What’s your favorite type of ice cream?

What’s your favorite type of ice cream?

What’s your favorite type of ice cream?

Preview

Preview

Preview

Mon, Feb 14

Mon, Feb 14

Mon, Feb 14

Share a photo of your home office setup

Share a photo of your home office setup

Share a photo of your home office setup

Preview

Preview

Preview

Mon, Feb 21

Mon, Feb 21

Mon, Feb 21

What’s your favorite type of pasta?

What’s your favorite type of pasta?

What’s your favorite type of pasta?

Preview

Preview

Preview

Mon, Feb 28

Mon, Feb 28

Mon, Feb 28

What’s your favorite vacation spot?

What’s your favorite vacation spot?

What’s your favorite vacation spot?

Preview

Preview

Preview

Mon, Mar 5

Mon, Mar 5

Mon, Mar 5

Share a photo of the most beautiful place you’ve been.

Share a photo of the most beautiful place you’ve been.

Share a photo of the most beautiful place you’ve been.

Preview

Preview

Preview

Impact

+10%

TRIAL TO PAID CONVERSION

+33%

MULTIPLE PRODUCT INSTALLS

+10%

INCREASE IN TRIAL STARTS

Impact

+10%

TRIAL TO PAID CONVERSION

+33%

MULTIPLE PRODUCT INSTALLS

+10%

INCREASE IN TRIAL STARTS

Problem
Problem
Problem

Analysis of usage and business data revealed a key insight: 80% of teams using Donut were not paying customers.

Working with our data scientist, we discovered that paying teams consistently used more than one Donut product. This raised two critical questions:

  1. How does multi-product usage impact conversion?

  2. What’s preventing the majority of teams from adopting more than one product?

User Research Methods
User Research Methods
User Research Methods

To explore these questions, our team aligned on a dual approach: conducting qualitative interviews alongside usability tests. The map below outlines the strategy we used to guide this research.

Identifying Who to Interview
Identifying Who to Interview
Identifying Who to Interview

Finding the right people to talk to was critical for us. Who do we recruit and how do we find them? We were looking for 3 specific types:


Group 1: Teams who installed Donut and became paying customers, to understand what drove conversion.


Group 2: Teams using only one Donut product, to explore barriers to multi-product adoption.


Group 3: New users preparing to install Donut for the first time, to gather fresh feedback on the current onboarding experience.

Finding the right people to interview was a huge challenge. Who do we recruit and how do we find them? We were looking for 3 specific types:


Group 1: Teams who installed Donut and became paying customers, to understand what drove conversion.


Group 2: Teams using only one Donut product, to explore barriers to multi-product adoption.


Group 3: New users preparing to install Donut for the first time, to gather fresh feedback on the current onboarding experience.

Finding the right people to interview was a huge challenge. Who do we recruit and how do we find them? We were looking for 3 specific types:

Group 1: Teams who installed Donut and became paying customers, to understand what drove conversion.

Group 2: Teams using only one Donut product, to explore barriers to multi-product adoption.

Group 3: New users preparing to install Donut for the first time, to gather fresh feedback on the current onboarding experience.

Recruiting Interviewees
Recruiting Interviewees
Recruiting Interviewees

Observing fresh users was critical for understanding why some teams only installed one product. We used Intercom to identify new visitors who had just initiated the installation flow. We intercepted them through Intercom’s chat, inviting them to join a usability study in exchange for a reward.

This tactic worked surprisingly well. By catching users at the exact point of entry, we were able to recruit high-quality participants who gave us rich insights into their first impressions and decision-making process.

Observing fresh users was critical for understanding why some teams only installed one product. We used Intercom to identify new visitors who had just initiated the installation flow. We intercepted them through Intercom’s chat, inviting them to join a usability study in exchange for a reward.

This tactic worked surprisingly well. By catching users at the exact point of entry, we were able to recruit high-quality participants who gave us rich insights into their first impressions and decision-making process.

Finding the right participants required a bit of ingenuity. We started by emailing current Donut admins a screener survey, filtering for those who had personally installed Donut in their Slack workspace. Qualified respondents were offered financial incentives to join our research sessions.

But the real breakthrough came from targeting first-time users in real time. Since observing fresh users was critical for understanding why some teams only installed one product, we used Intercom to identify new visitors who had just initiated the installation flow. Then, right in the moment, we intercepted them through Intercom’s chat and invited them to join a usability study in exchange for a reward.

This tactic worked surprisingly well. By catching users at the exact point of entry, we were able to recruit high-quality participants who gave us rich insights into their first impressions and decision-making process.

Discovery + Deeper Insights
Discovery + Deeper Insights
Discovery + Deeper Insights

After 20 interviews and 15 usability tests, we began to uncover a clear relationship between multi-product usage and customer conversion.

After 20 interviews and 15 usability tests, we began to uncover a clear relationship between multi-product usage and customer conversion.


Different people connect in different ways


Teams often found that not every Donut product fit their culture, but having options mattered. For example, extroverted teams gravitated toward Intros (video-based), while more introverted teams preferred Watercooler (chat-based). This flexibility made it more likely that multiple products would get adopted within a single workspace.

10% of teams trying a paid product eventually convert


This stat reframed our goal: instead of pushing conversion directly, we needed to increase meaningful exposure to more products during onboarding and early use.

More products = more billable users


Because Donut’s pricing is per user, the more teammates engaging with different products, the more likely a team is to exceed the free tier and convert to paid. Multi-product use effectively increased the "surface area" for monetization.

?

?

?

Most users weren't aware of Donut's full suite of products


A surprising number of participants were only aware of one Donut product. When shown a page listing all available products, many said it was their first time seeing it. This likely contributed to low conversion rates; people simply didn’t know what else they could use.

"I didn't even realize Donut had all these features. I was the one who installed it in our workspace but this is the first time I'm learning about all these!"

"I didn't even realize Donut had all these features. I was the one who installed it in our workspace but this is the first time I'm learning about all these!"

Usability Study Findings from Old Design
Usability Study Findings from Old Design
Usability Study Findings from Old Design

Our second research goal was to understand why 80% of users only engaged with one Donut product.

I initially audited our onboarding flow and encountered a likely cause: the product didn’t clearly communicate the full suite of features. I hypothesized this lack of visibility was limiting multi-product adoption.

To test this, I ran a usability study with first-time installers. Watching how they navigated the flow helped us spot friction points and missed opportunities to highlight value early on. Below are several usability issues that likely contributed to drop-off and limited product adoption:

The second objective of our research was to uncover why 80% of users were only engaging with a single Donut product.

An audit of the existing onboarding flow revealed a potential culprit: the experience lacked clarity and visibility around Donut’s full range of offerings. I hypothesized that this gap in communication was limiting multi-product adoption.

To explore this, I conducted a usability study with first-time users actively looking to install Donut. By observing how they navigated the onboarding experience, we were able to identify friction points and missed opportunities to surface value early.

Below are several usability issues that likely contributed to drop-off and limited product adoption:

Donut’s install page forced an installer down only one product path, missing an opportunity to highlight its other strengths.

⚠️ One way in, no way out

⚠️ One way in, no way out

Donut’s install page forced an installer down only one product path, missing an opportunity to highlight its other strengths

⚠️ Lengthy onboarding

Donut's sign up flow has about 18 steps split into 6 tabs. Analytics showed that about 50% of installers drop off by the 2nd tab, missing out on customizing Donut for their team to have the best experience.

⚠️ Lengthy onboarding

Donut's sign up flow has about 18 steps split into 6 tabs. Analytics showed that about 50% of installers drop off by the 2nd tab, missing out on customizing Donut for their team to have the best experience.

⚠️ Disjointed flow and steps that got ignored

Donut DMs installers 24 hours after installation to promote other products like Watercooler and Celebrations or to add members to the newly created channels. Our qualitative interviews that these DMs are often missed, leaving these crucial onboarding steps abandoned and forgotten.

Donut DMs installers 24 hours after installation to promote other products like Watercooler and Celebrations or to add members to the newly created channels. We found out through our qualitative interviews that these DMs are often missed, leaving these crucial steps abandoned and forgotten.

⚠️ Disjointed flow and steps
that got ignored

Donut DMs installers 24 hours after installation to promote other products like Watercooler and Celebrations or to add members to the newly created channels.

We found out through our qualitative interviews that these DMs are often missed, leaving crucial onboarding steps abandoned and forgotten.

"I ignore the updates from Slack. That's probably how I missed this message."

"I ignore the updates from Slack. That's probably how I missed this message."

Hypothesis
Hypothesis
Hypothesis

If users are introduced to all of Donut’s core products during the installation flow through a clear, streamlined, intuitive experience, then the rate of multi-product adoption per team will increase, and in turn, raise Donut's bottom line.

We now have 2 new guiding insights:

1. Different people prefer different modes of connecting with people within company, and this increases the monetization surface area

2. First time installers aren’t fully aware of Donut’s full suite of offerings, leading to missed opportunities for proving Donut's value, which could lead to conversion

Leading Ideation Workshops
Leading Ideation Workshops
Leading Ideation Workshops

With a refined hypothesis, I partnered with PMs to run a cross-functional workshop with the goal of redesigning Donut's onboarding. I brought in stakeholders from engineering, product, customer success, and marketing to gather diverse perspectives and create alignment early.

To spark ideas, participants shared favorite onboarding experiences from other apps, revealing patterns in what made them intuitive and memorable. I framed our challenge as: “How might we encourage teams to install multiple Donut products during onboarding?”

Through rapid sketching, critique, and dot voting, we surfaced concepts that sparked alignment and excitement. The session not only generated strong ideas, but also built shared ownership, eliminated blind spots, and gave the team a clear direction forward.

Design Imperatives
Design Imperatives
Design Imperatives

Building on what we learned from usability testing and user interviews, I defined a set of design imperatives to guide the new onboarding experience. These were aimed at addressing friction in the current flow, while testing our hypothesis: That teams who adopt multiple Donut products are significantly more likely to convert to paying customers.

Scroll

Scroll

Show value early


Surface Donut’s benefits within the first few steps to create momentum and buy-in.

Show value early


Surface Donut’s benefits within the first few steps to create momentum and buy-in.

Show value early


Surface Donut’s benefits within the first few steps to create momentum and buy-in.

Scroll

Scroll

Sign Up Flow Redesign
Sign Up Flow Redesign

2

3

1

Next

->

Back

<-

Donut’s old install page forced an installer down only one product path. The tabs made it harder for users to understand what each product did.

2

3

1

Donut’s old install page forced an installer down only one product path. The tabs made it harder for users to understand what each product did.

Next

->

Back

<-

2

3

1

Next

->

Back

<-

Donut’s old install page forced an installer down only one product path. The tabs made it harder for users to understand what each product did.

The old flow took 6 tabs to complete. This lengthy process hurt Donut's onboarding completion rate, as 50% of users drop off by the 2nd tab.

2

3

1

Next

->

Back

<-

The old flow took 6 tabs to complete. This lengthy process hurt Donut's onboarding completion rate, as 50% of users drop off by the 2nd tab.

2

3

1

Next

->

Back

<-

2

3

1

Next

->

Back

<-

The old flow took 6 tabs to complete. This lengthy process hurt Donut's onboarding completion rate, as 50% of users drop off by the 2nd tab.

The old design relied on Slack messages to prompt users to install other Donut products, which felt disjointed.

Next

->

Back

<-

The old design relied on Slack messages to prompt users to install other Donut products, which felt disjointed.

Next

->

Back

<-

Next

->

Back

<-

The old design relied on Slack messages to prompt users to install other Donut products, which felt disjointed.

Alternative Directions
Alternative Directions
Alternative Directions

Next

->

Back

<-

Here are a couple other design directions that were considered.

Here are a couple other design directions that were considered.

Next

->

Back

<-

Here are a couple other design directions that were considered.

Next

->

Back

<-

Implementation and Early Results
Implementation and Early Results

Our team understood that implementing a radical redesign project like this can be risky, despite a high level of confidence in the new design due to good usability test results and support from the rest of the company.

To mitigate risk, we decided to conduct an A/B test to compare the new design’s efficacy against the current one’s, tracking key metrics like:

• Number of products installed per session (+33%)
• Trial starts (+10%)
• Conversion to being paid customers (+10%)

Based on these KPIs (taken 6 months after initial implementation), there was some truth to our hypothesis. Increased product exposure and education in the onboarding phase ultimately led to a 10% increase in customer conversion. And though, that is not a small feat, we were expecting that number to be higher. This experiment certainly answered some questions around product exposure and how it affects conversion, but introduced a few more that could be further explored down the line, such as clarity around product value and getting to product "aha moments" faster, not only through onboarding exposure and education but through experiencing the product.

Learnings
Learnings

Design Starts with Listening, Not Solving

One of the biggest lessons from this project was the value of slowing down to deeply understand the problem before rushing into solutions. It was tempting to act quickly on early insights, but it was only through sustained user interviews, usability testing, and talking to other company members that the real patterns and opportunities began to emerge. The time we invested upfront made the eventual design process easier, because it was far more grounded.

Design is a Team Sport

By treating partners in data science and customer success as co-designers, we were able to challenge assumptions, uncover blind spots, and enrich our understanding of the problem space. Their input brought context and nuance we couldn’t have seen alone, and that ultimately shaped a stronger, more effective solution.

Design Starts with Listening, Not Solving
One of the biggest lessons from this project was the value of slowing down to deeply understand the problem before rushing into solutions. It was tempting to act quickly on early insights, but it was only through sustained user interviews and usability testing that the real patterns and opportunities began to emerge. The time we invested upfront made the eventual design process easier, because it was far more grounded.

Design is a Team Sport
By treating partners in data science and customer success as co-designers, we were able to challenge assumptions, uncover blind spots, and enrich our understanding of the problem space. Their input brought context and nuance we couldn’t have seen alone, and that ultimately shaped a stronger, more effective solution.

Other Projects
Other Projects
Other Projects

GRAFITI

Building and growing a data visualization search tool to 30K MAU

30,000

MAU

-31%

BOUNCE RATE

+50%

REPEAT USERS

TRIP TIP

Making sharing travel tips among friends easier (0-1)

DONUT FOR FIGJAM

Designing a creative warmup widget to improve collaboration (0-1)

43,000

TOTAL DOWNLOADS