top of page

EVENTBRITE EVENT GROUPS

When Eventbrite first launched they targeted and catered to a pretty simple type of event. These events were usually general admission and one-off occurrences. As the company grew so did the types of events using the platform, this simple event model needed to evolve to cater to a larger variety of events and user needs.

 

One of the first things to be added to the core functionality was the ability for an organizer to schedule multiple instances of the same event. These repeating events enabled us to serve all manner of new customers, for example classes, workshops, tours and performances. They were still general admission events where the main differences being the date and/or time and potentially ticket prices. This allowed organizers to setup an event once and run it numerous times with little additional effort, it proved to be a huge revenue win for the company.

 

Fast forward to 2017 and after the success of our reserved seating product we started to see a need for more complex repeating seated events. These types of events took the form of multi day music festivals or conferences, a series of theatre performances or music concerts through to sporting seasons in seated stadiums. Our business development team saw this as a huge opportunity to capture these more complex grouped events and continue to move us up market into larger venues with an on average higher priced ticket.

 

So my team was tasked to partner with a Bay Area college football team to try and understand this type of event better and develop a solution that would enable us to service sporting seasons.

 

My Role & Team


My role of Senior UX architect and system designer was to investigate how these events operate, build user empathy and identify core needs for the V1 sporting seasons product. The work encompassed mixed methods of research across different key categories to determine a common set of features ensuring any solution would scale. At the heart of all these types of events is a fairly consistent event grouping model, it is a repeating instance of the same event with a variety of differences across each vertical. The biggest difference was the ability to sell tickets to more than a single event, this generally manifested as season tickets, multi game packages and/or annual renewable memberships. A massive change to our existing event and ticket data models, add to that seat assignment across multiple days and things got complex pretty quickly.


It was a small cross functional team, comprising myself and another product designer, six engineers a product manager and executive sponsor. We worked closely with our business development partner and sales team, product marketing and customer service representatives.
 

Research Goals


Perform primary research analyzing existing product solutions in market and interview representatives from key categories being;

  • Sporting teams running seasons

  • Performing arts series or programs

  • Multi-day music and film festivals

  • Multi-session conferences and classes


Seek to understand the context around each grouping model

  • Noting features and aspects of content presentation and display strategies

  • Determine methods and best practice around selling multi event tickets

  • Determine the role reserved seating functionality plays in grouped events

  • Uncover unmet needs, identify complexities and opportunities to innovate in this space.

 

Use these insights to inform product requirements and future design work.

 

Research Methodology

  • Survey of 4,000 existing Eventbrite organizers who identify as operating multiple instance events. Goal being to understand existing organizers better who are most likely to use new group based features.

  • Review 15 comparable websites across target categories

  • Interview 15 users responsible for managing events across target categories

 

Deliverables

  • A research deck and presentation with leadership and stakeholders to cover findings and key insights.

  • A revised event listing design specifically targeting sporting seasons and multi instance ticket types.

  • Concept designs for a new content management solution and update to our existing event creation product.

Examples from Research
Design Requirements


There were two major aspects requiring product design on this project, the first being the event listing itself and the larger piece of work was the content management system.

 

Goals for the event listing included:

  • Ability for the attendee to visually (and emotionally) connect with the sporting team.

  • Ability to view the game schedule to determine, opponent, date and ticket purchase options.

  • Ability to purchase single game tickets, multi game packages and season membership.

  • Returning season members also needed to be able to renew their membership.

  • Ability to choose seats from a seat map (when able to do so). A huge opportunity flagged in research was a great pick a seat experience for multi-game events. Seat assignment across multiple games is challenging due to the volatile nature of seat inventory. Best available seat assignment was the fall back in situations where pick a seat was not available.

  • Experience goals were to be able to purchase with confidence and be able to access their tickets (and assigned seats) at the end of flow.

The main goals for the create and manage product included:

  • Ability for the event organizer to setup their event and manage all aspects of its online presence. This included the content on the listing itself and all aspects of ticket sales.

  • Ability to create venue seat maps as needed. Most teams only ticket games to their home stadium or venue.

  • Ability to create 3 types of tickets, single game, multi-game packages and season membership tickets.

  • Ability to manage season ticket allocation, enabling renewals and new season ticket sales during the pre season. Season ticket holders usually have the same seats from year to year. 

  • Ability to stagger ticket sales to drive demand to season tickets and multi-game packages. Single game tickets usually go on sale later in the sales cycle. 

  • Ability to create a schedule of games and assign a seat maps, ticket types and holds for each.

  • Part of creating the event is completing all the necessary steps to enable the system to successfully go on sale.

Experience goals:

  • Make creating and publishing an event as simple and efficient as possible.

  • Ability to create templates and reuse them as needed. Templates contain the essential ingredients for each occurrence of an event. Some teams have between 6 -72 games per season - so some level of automation was desirable.

  • Ability to override or modify an instance of a game when needed. These types of events can be complex with a large range of venue capacities, from hundreds to thousands. A measure of control and visibility around the system rules is needed to ensure a successful management experience.

  • High visibility into event status, top level sales as well as inventory availability metrics. Displaying the appropriate data at the correct time to enable recognition and awareness as well as take action when needed.

UX/UI Examples
Invision Prototype
 

Wireframes were created to review with users and stakeholders. Use the Right Arrow on the keyboard to progress through the screens.

Results

  • Project was well received and team was tasked to start planning the work.

  • New event listing format and solution to handle the variable ticket types excited our external partner.

  • In partnership with my PM we created V1 product requirements and a roadmap for future releases.

  • Weekly cross functional design review meetings, to enable engineering peers to start planning core services and data models.

 

All in all we spent about 4 months in research and design of both the front end event listing and designs for the back end content management systems. Unfortunately the company went through a reorganization half way through the project, resources were reallocated to other initiatives and the work was paused. A team will be continuing the work in 2019/20, which makes me happy.

© 2019 Jason Bayly, San Francisco CA

bottom of page