This document discusses Eventbrite's efforts to design a simple seat mapping tool for organizers of reserved seating events. It provides background on Eventbrite as an online ticketing marketplace and outlines the benefits of reserved seating events. The document then discusses principles of simplicity in design and how Eventbrite applied these principles to create an intuitive seat mapping tool that reduces complexity and supports users throughout the process.
DevEX - reference for building teams, processes, and platforms
Simple Seat Map Design for All
1. Finding Simple,
Seat Map Design for Everyone
Jason Bayly
Senior UX Architect, Eventbrite
The Davenport Theatre, New York NY
Image courtesy of davenporttheatre.com
#uxaustralia @jasb
4. Eventbrite is an online marketplace
for live experiences.
• Website localized in 14
countries, events listed in 187
countries
• $1B in gross ticket sales
annually, 1M tickets sold each
week
• Founded in 2006, late stage
start-up
• 450 employees worldwide,
offices in 5 countries
5.
6. What is reserved seating?
Reserved seating is a type of an
event where each attendee is
guaranteed a specific seat.
Up until recently Eventbrite only
catered to general admission events.
14. Benefits of reserved seating
Attendees
Can choose
where they sit,
feel in control
Less stress on the
day, no lining up,
a seat is
guaranteed
Organizers
Greater flexibility
Smoother entry
management
Increased
revenue through
tiered pricing
Eventbrite
Little self service
competition
Larger capacities,
sell more tickets
Extend our reach
and relevancy
15. What is simplicity?
Simplicity is when something is
neither hard to understand or to do.
16. As UX designers we struggle to find
the delicate balance between the
simplicity of use and the complexity of
usefulness.
17.
18. Design should be collaborative
A problem shared and ideated on is a problem solved.
19.
20.
21.
22.
23.
24.
25.
26. Principles to guide your way
Restricted complication – Try to avoid
complication at all costs
Progressive complexity - When we hit
complexity, reveal it progressively
Easy error recovery and system
forgiveability – What ever happens its
never the end of the world
Guide me to completion - Support and nurture
me, the system is my Sherpa
Communal creation & sharing – Share the love
that is reusable templates, assets & stencils
Seat map creation is a last resort – templates
are the key to greater simplicity
Aid spatial comprehension of the venue - the
seat map is my guide
Content over chrome (UI) – Don’t let the UI get
in the way of my ticket/seat needs
The design and UI should BE Eventbrite - Light,
bright & airy – always on brand
Find ways to minimize input (with template seat
maps, smart defaults & intuitive tools)
Delight is in the details - The experience is the
sum of all the moving parts
Error prevention and affordance before
messaging - Errors should be preventable
Afford greater task focus through the use of
contextual controls and feedback
27. Designing seat maps can be
simple
Methods and techniques used along the way.
53. The 10 laws of simplicity…
1. Reduce
2. Organise
3. Time
4. Learn
5. Difference
6. Context
7. Emotion
8. Trust
9. Failure
10. The one
Dr John Maeda
@johnmaeda
lawsofsimplicity.com
54. Thanks for listening!
Finding simple, seat map design for everyone
UX Australia Conference
2014
Jason Bayly
Senior UX Architect
jbayly@eventbrite.com.au
@jasb
eventbrite.com.au/reservedseating
vimeo.com/87748221
Editor's Notes
Church gatherings
New Hope Oahu
Art auction in an old torpedo factory
Spin classes
Outdoor philharmonic orchestra dinner event
Discuss what self service means, platform (SAAS model), mass adoption
Game changer
Importance of design
Less urgency getting through the door, a seat is guaranteed
Organizers can visually define their seat maps, flexible spaces
Organizers can optimize revenue with tiered pricing
Very little competition in the self service space
Reserved events are generally larger and in bigger venues
Some organizers mature into hosting reserved events
Expand our reach, relevancy and income potential
Life reboot == simpler beginnings
If the UI is pretty people will want to touch it
If something looks pleasing and appears simple users are more inclined to start the process
People are more willing to trust something that is professionally crafted and executed
Establish a style guide and pattern library and stick to it
Organize features and tasks into chunks that drive towards a visible end goal
Always start shallow and then go deep, the deep end of the pool can be scary at first
Tasks within tasks are ok as long as the flow makes sense
Feedback is critical to success, way finding keeps things moving
Reward the user regularly