Project Overview

Project Overview

Airbnb is a global platform that connects travelers with unique places to stay. It empowers hosts to monetize their spaces while giving guests a more personal, local alternative to traditional hotels.


During my design bootcamp, my partner and I were tasked to design a native payment split feature within Airbnb's existing platform (sneak peek below).

Typical party size breakdown

2-4 people: 59%

8-10 people: 27%

5-7 people: 14%

Typical party size breakdown

2-4 people: 59%

8-10 people: 27%

5-7 people: 14%

Market Sizing

Group trips are core to the Airbnb experience.

We surveyed frequent Airbnb users to better understand how they felt about and organized group trips. A majority of responders plan at least 1 group trip a year, and within that sample size, nearly half planned more than 1.


This underscored the importance of group travel to Airbnb's user base, and how improvements in this experience could lead to outsized impacts.

Typical party size breakdown

2-4 people: 59%

8-10 people: 27%

5-7 people: 14%

Market Sizing

Group trips are core to the Airbnb experience.

We surveyed frequent Airbnb users to better understand how they felt about and organized group trips. A majority of responders plan at least 1 group trip a year, and within that sample size, nearly half planned more than 1.


This underscored the importance of group travel to Airbnb's user base, and how improvements in this experience could lead to outsized impacts.

Typical party size breakdown

2-4 people: 59%

8-10 people: 27%

5-7 people: 14%

Market Sizing

Group trips are core to the Airbnb experience.

We surveyed frequent Airbnb users to better understand how they felt about and organized group trips. A majority of responders plan at least 1 group trip a year, and within that sample size, nearly half planned more than 1.


This underscored the importance of group travel to Airbnb's user base, and how improvements in this experience could lead to outsized impacts.

Typical party size breakdown

2-4 people: 59%

8-10 people: 27%

5-7 people: 14%

The Problem

The hidden cost of group travel.

Users reported that payment collection was the biggest headache of planning a group trip. Money is a sensitive topic, and chasing someone down to get their payment share is never fun.

The Problem

The hidden cost of group travel.

Users reported that payment collection was the biggest headache of planning a group trip. Money is a sensitive topic, and chasing someone down to get their payment share is never fun.

The Problem

The hidden cost of group travel.

Users reported that payment collection was the biggest headache of planning a group trip. Money is a sensitive topic, and chasing someone down to get their payment share is never fun.

54.5%

54.5%

Collecting timely payments from group

31.8%

31.8%

Coordinating payment methods

27.3%

27.3%

Deciding whose card to use for the booking

22.7%

22.7%

Lack of transparency around cost splitting and payment

Note: Surveyors were allowed to choose more than 1 answer.

How might we design a group payment feature that helps groups reduce payment stress?

How might we design a group payment feature that helps groups reduce payment stress?

How might we design a group payment feature that helps groups reduce payment stress?

User Context

For group trips, there's usually a group leader.

From research, we learned that groups naturally appoint a leader whose responsibilities can include managing timelines, reminders, sending restaurant and activity ideas, and at the very least, booking the Airbnb. Although some groups were more collaborative, we leaned into the idea that managing power should go to a single user.

User Context

For group trips, there's usually a group leader.

From research, we learned that groups naturally appoint a leader whose responsibilities can include managing timelines, reminders, sending restaurant and activity ideas, and at the very least, booking the Airbnb. Although some groups were more collaborative, we leaned into the idea that managing power should go to a single user.

User Context

For group trips, there's usually a group leader.

From research, we learned that groups naturally appoint a leader whose responsibilities can include managing timelines, reminders, sending restaurant and activity ideas, and at the very least, booking the Airbnb. Although some groups were more collaborative, we leaned into the idea that managing power should go to a single user.

Initial Idea Sketch

At first, we focused too much on efficiency & speed.

We initially thought to embed group payments directly within the checkout funnel as a seamless and efficient solution. However, early usability testing and edge-case analysis revealed that this design couldn't support asynchronous coordination and led to low trust in state persistence (users felt they would lose progress if they leaved the checkout flow despite having a save button).

Initial Idea Sketch

At first, we focused too much on efficiency & speed.

We initially thought to embed group payments directly within the checkout funnel as a seamless and efficient solution. However, early usability testing and edge-case analysis revealed that this design couldn't support asynchronous coordination and led to low trust in state persistence (users felt they would lose progress if they leaved the checkout flow despite having a save button).

Initial Idea Sketch

At first, we focused too much on efficiency & speed.

We initially thought to embed group payments directly within the checkout funnel as a seamless and efficient solution. However, early usability testing and edge-case analysis revealed that this design couldn't support asynchronous coordination and led to low trust in state persistence (users felt they would lose progress if they leaved the checkout flow despite having a save button).

Pivoting to dashboard

Users wanted a space where they could collect payments that was decoupled from checkout.

By shifting to a dashboard, group owners could more easily reference, track, and remind their group to achieve the group payment deadline. This ended up making users feel more comfortable vs feeling pressure in a checkout flow, and becomes a fun way for the group owner to stay updated on overall progress.

Pivoting to dashboard

Users wanted a space where they could collect payments that was decoupled from checkout.

By shifting to a dashboard, group owners could more easily reference, track, and remind their group to achieve the group payment deadline. This ended up making users feel more comfortable vs feeling pressure in a checkout flow, and becomes a fun way for the group owner to stay updated on overall progress.

Pivoting to dashboard

Users wanted a space where they could collect payments that was decoupled from checkout.

By shifting to a dashboard, group owners could more easily reference, track, and remind their group to achieve the group payment deadline. This ended up making users feel more comfortable vs feeling pressure in a checkout flow, and becomes a fun way for the group owner to stay updated on overall progress.

Positive

Positive

Feedback from friends and family testing

Feedback from friends and family testing

Reduced

Reduced

Payment reminder stress

Payment reminder stress

15

15

Redesigned screens.

Redesigned screens.

Final designs and results

Final designs and results

Final designs and results

Dashboard

Dashboard

Group payments sits in a separate dashboard

Group payments sits in a separate dashboard

Group payments sits in a separate dashboard

We internalized our initial user feedback and designed a dashboard page where users could manage their group payment. To begin a group payment, users can select the option nestled seamlessly withinAirbnb's existing checkout flow, which triggers a booking hold.

Ownership Dynamics

Ownership Dynamics

Designated group owner

Designated group owner

Designated group owner

The user who creates the booking becomes the designated "group owner" and has the exclusive ability to invite guests, edit splits, and contact the host. This prevents version control issues and mimics real-life group dynamics we observed through research.

Trips Tab Integration

Trips Tab Integration

Easily access your group booking

Easily access your group booking

Easily access your group booking

Pending group bookings will sit as the first item within the Trips tab, allowing for easy access for the group owner, as well as seamless integration with Airbnb's existing design architecture.

Payment Logic

Payment Logic

Group owner pays last

Group owner pays last

Group owner pays last

Studying other group features like Uber Eats, we adopted the logic that the group owner pays last in order to oversee the beginning-to-end booking.


We also placed other edge-case factors onto the group owner. For example, when editing a custom split, the group owner's amount is autofilled, and any remaining pennies after a non-even split goes to the group owner.

Reflections

Reflections

1

Broadening our user research audience

For this project, we conducted a survey with friends and family, and are cognizant that politeness bias and other factors could have skewed our findings. Although this sample reflected real Airbnb users, next time we would have selected a broader, and more randomized audience to get more accurate data.

Broadening our user research audience

For this project, we conducted a survey with friends and family, and are cognizant that politeness bias and other factors could have skewed our findings. Although this sample reflected real Airbnb users, next time we would have selected a broader, and more randomized audience to get more accurate data.

2

More open-ended survey questions

Our survey was multiple-choice heavy and looking back, we would have uncovered more useful information to prevent us from going down the wrong path, or bring us towards a new, better path. Ideally, our survey would have benefitted from 1-2 more open-ended questions focused on deeper patterns around group travel, payment splitting, and payback tendencies. However, since open-ended responses take more effort, we would definitely monitor user fatigue and include a completion incentive.

3

Continually improve communication and teamwork.

After competing this project, I learned that systems allow teams to move faster together. Despite having weekly check-ins to discuss design and strategy, we still had a lack of structure in terms of prioritization and a general buildout roadmap. Next time, I would explore implementing Agile methodologies, such as better defined checkpoints, frequent & shorter check-ins, or a dashboard to visualize progress and blockers.

Continually improve communication and teamwork.

After competing this project, I learned that systems allow teams to move faster together. Despite having weekly check-ins to discuss design and strategy, we still had a lack of structure in terms of prioritization and a general buildout roadmap. Next time, I would explore implementing Agile methodologies, such as better defined checkpoints, frequent & shorter check-ins, or a dashboard to visualize progress and blockers.

4

Improving balance between micro and macro focus.

I sometimes found myself engulfed in making pixel-perfect UI changes rather than moving onto the next screen. Although I pride myself on my attention to detail, in the future, I will try to be more mindful about zooming out from a micro UI change, to a more macro project-based view to ensure that I'm staying on track and using my time effectively.

Improving balance between micro and macro focus.

I sometimes found myself engulfed in making pixel-perfect UI changes rather than moving onto the next screen. Although I pride myself on my attention to detail, in the future, I will try to be more mindful about zooming out from a micro UI change, to a more macro project-based view to ensure that I'm staying on track and using my time effectively.

Next Project

Next Project

©2026 Arnold Wei

Let's chat! arnold.1.wei@gmail.com

©2026 Arnold Wei

Let's chat! arnold.1.wei@gmail.com

©2026 Arnold Wei

Let's chat! arnold.1.wei@gmail.com