Making event setup easier for Director of Ticket Operations

The Problem

The current Event Setup is not only out of date, but requires a manual to get through all the steps in the correct order to actually set up an event. There are required steps, that are in different menus, and if not done fully, will not actually set up the event.

Plan of Attack

Talk to users & SMEs

Better understand what the current pain points are, and what process the user actually go throughs currently to set up an event.

User Flows

Based on the user insights, put together flows of how the user actually go about setting up an event.

Initial Mockups

Create initial mockups based on user insights, keeping the pain points in mind as well as exploring other ways to help user set up an event..

User Test & Iterate

Run the mockups by users to get feedback to make sure that everything they need is included, as well as making the process more streamlined for them.

User Flows

Insights Discovered During Flows

While doing the user flows, we realized that some of the current flows were actually backwards to how the user users actually set up their events.

For example: in the current setup, the user has to set up all the events first, then set up a season and put events in it. This is backward to how the user wants to set up a season. They want to be able to set up a season that they can then put events into.

Initial Mockups

List Pages

The list pages contain the configurations for the various flows.

Added functions (not in current setup):

• Search functionality: can search facility, season or event to more easily find the list item they are looking for.

• Clone: Users would also be able to clone a season or event.

• See status: Users would be able to quickly see the status of an event from the list.

Creating/Editing Events

Initial mockup for Creating/Editing an Event.

During user testing, some items came up that weren’t included in this initial round, that needed to be.

Also, there was a lot of pressure from the CTO to do a Wizard like event setup, but during research we learned that users will set up events over time, over multiple sessions which wouldn’t lend itself very well to a wizard. An example of what user might do: they go in and create all the events in a season, with just the name of the opponent and arena with nothing else and then return at a later date when they had more detail to add to the event.

Another item we had to keep in mind, with the tech stack available, pricing would need to remain separate from the event set up.

Final Mockups

List Pages

We did a visual update as well as adding a highlight section where onsales (specific term to the user) would live.

We also made a few updates to the list showing some data analytics and adding the ability to bulk upload (to better align with those who want to continue doing things the “old school” way).

Creating/Editing Events

We added in all the data points that were needed to create an event.

A user made the comment that they would like to have a checklist in the current setup to ensure they put in everything. We thought that was a good idea to add here as well so it is more obvious where they were in the process of creating an event.