Summer 2023, Product Design Internship

Universe: Improving the Add-On Checkout Experience

Overview

As the sole designer on this project, I designed a solution the checkout experience’s user interface inconsistencies, created a solution for add-on variation display and an add-on gallery view.

About Universe

Universe is an event management and ticketing platform that provides event organizers a place to create, list and manage their events, and for attendees to purchase tickets for them.

Roles

  • Research

  • Ideation


  • Hi-Fidelity Design

  • Prototyping

  • Presentation

Tools

  • Figma

  • Jira

Team

  • Nikki Policarpio (Product Designer)

  • Wasiq Wadud (Product Manager)

Problem Statement

There were recurring issues being brought up within the Universe team regarding the add-on checkout experience and requests from clients regarding possible new features.
How can we design solutions to these user interface inconsistencies and opportunities?

Background

As a ticketing platform, it’s extremely important for the Universe’s checkout flow to be usable, both functionally and intuitively.

Admission is the main transaction of this flow, but add-ons are also important within the checkout experience; they promote customer loyalty, customize a customer’s experience within the event they purchased, and is an extra point of revenue.

However...

We learned that the add-on purchasing process of the flow had a UI inconsistency that resulted in revenue losses, and the current design could be visually confusing for users and clients alike.

Additionally, there were requests from clients for new features that would aid event organizing.

Solution Overview

1

Automatic Add-to-Cart Functionality

I removed the Add button previously located under each listing, making the add-on purchase flow the same as the ticket purchase flow.

2

Add-On Variations

Variations live within a nested dropdown, below the originating item. Users who want to view the variations can press Show Options.

3

Gallery View and Description Support

When an add-on image is clicked, a gallery view appears. Users can view multiple, zoomed-in photos with descriptions.

Stakeholder Interviews

Starting the process through understanding the landscape

Being at Universe for a summer on the Product team exposed the Product Manager Intern and I to a lot of behind-the-scenes work and ongoing projects at Universe, but we needed to have a well-rounded grasp of the checkout process.

We organized interviews with the different teams at Universe for their feedback on the current checkout process: their pain points, client needs and opportunities, and in relation to add-ons, specifically.

What we learned:

1

The checkout process has UI inconsistencies

The classic "Add to Cart" function had different behaviours between the ticket purchase stage and the add-on purchase stage, which caused confusion and occasionally a loss in add-on revenue.

2

The team had ideas for additional add-on features based on client feedback

The teams that interface with Universe's clients learned of cases where three specific features would be useful: 1) being able to purchase add-ons after ticket purchase confirmation, 2) the ability to buy add-ons without a ticket and 3) the ability to have multiple photos for one add-on

3

The add-on stage lacks organization, in the case of add-on variations

Add-on listings could be confusing for customers, especially when it comes to variations (different designs of one product, for example: different colours of one mug) because there was no visual hierarchy or delineation in these instances.

4

There's currently another larger project regarding add-on improvements already in the works by the Product Team

The product designer and product manager were working on the host-side of the add-on checkout experience. They had conducted interviews and created preliminary designs.

We concluded that by improving the UI inconsistencies, we could increase conversion rate and cause less dissatisfaction, and by adding additional features, we could increase its value for both clients and users.

Competitor Analysis

How do other ticketing platforms tackle the add-on phase in checkout?  How do we measure up?

Ticketing platforms follow an identical flow for the purchase of admission; it allows users to follow a recognized (and therefore, intuitive) pattern across all platforms. Conversely, add-ons take on a different visual/technical approach depending on the platform. We needed to understand where Universe existed in the market.

Within the industry, there were consistent design elements present.

Similar Checkout Flow

All competitors followed a checkout flow: add-ons being a step after ticket choice, and a step before checkout

Automatic Add-to-Cart

All competitors had the same button function; users click the "add" button and it automatically adds to the total

Host-Side Customization

Event organizers are given some liberties in the design of their event's checkout, like visual design and user experience

Personas

Empathizing with our users

Technicalities considered, we also needed to consider how our users respond to the current add-on checkout process. We needed to centre our work on users (event-goers and hosts). I sought to paint a picture of each persona's frustrations of the current flow.

Bringing the research together

From the research, we understood that two improvements were of high-priority, and justified deep exploration:

1

Improving the UI to be consistent with the ticket purchase flow

2

Refining how add-on variations are displayed at the add-on purchase stage

Based on our communications with other Universe teams and gaps in the market, we also believed these features would hold value for users and hosts:

3

Purchasing add-ons without tickets

4

Purchasing add-ons in the post-purchase experience

5

Providing a gallery view for add-on photos/allowing multiple photos per add-on

After consulting with the Product team, we decided to prioritize three features that were regarded to have the highest value — 1. Improving the UI to be consistent with the ticket purchase flow, 2. Refining how add-on variations are displayed, and 3. Gallery view.

User Flows

How would users navigate through these features?

We needed to visualize how our users were ideally meant to go through these features, and see the gaps or potential causes of confusion throughout.

Design Iterations

Iterating on designs

During the iterative design process, I focused on finding a solution to display variations, especially in tandem with the add-to-cart functionality, because both had to work smoothly with one another for this stage to function properly.

The gallery feature already existed on other areas of the platform, but a description did not; I wanted to show its value here.

Iteration 1

Iteration 2

In summary, the key design choices made in this project are:

Automatic Add-to-Cart Functionality

To reduce mental load for users, I designed the add-to-cart functionality on the checkout process side to be the same as the admissions checkout

Add-On Variations

This UI change organizes variations into their own box, instead of having them displayed as unique add-on listings, which lowers cognitive overload, and supports the automatic add-to-cart functionality

Photo & Description Support

Provides additional information for event-goers, so they can make informed decisions!

Reflection

Looking back on a great summer!

Summer 2024 marked a time of deep learning and growth for me; I was exposed to new processes, added new skills to my design toolbox, and connected with wonderful people.  Some key takeaways:

Consider everything

While designing for this project, I learned that it's vital to consider the product in all its possible iterations: common usages, long descriptions, lack of photos, edge cases.

Collaboration and communication

I collaborated with the Product Management Intern throughout this project, communicated with different teams during the research period and received guidance from the product team; it drilled in me the importance of consistent, detailed and honest correspondence!

Mobile versus desktop-first approaches

I began my design work from a desktop-first approach, which, in hindsight, was the wrong way to go about this project. Users check out on Universe through their mobile devices 80% of the time, so I should have considered mobile earlier in the design process and worked with both the desktop and mobile versions side-by-side.