The Boston Red Sox team is looking to modernize their existing internal ticketing application by making it responsive, cleaner, and automating processes where possible.
In addition, in this iteration, we were focused on the baseball ticketing process and how it can be made into a multi-tenant solution for other sports franchises if they wanted to use the same design.
We began the process by looking at the existing functionality of Red Sox Central through the lens of the developer and from there we were able to interview users throughout the business to get a better understanding of pain points and opportunities to improve the application.
Highlighting the request from the business, audit findings relevant to this flow, results of the interviews, and ways we want to solve these pain points.
User personas.
The existing application for Red Sox Central is 15+ years old (see below).
Wireframes that show the flow for an employee to request a combination of comped tickets and paid tickets without having to leave the application to enter credit card data.
Wireframe flow shows how an employee would handle a combination flow for comped tickets and paid tickets where another user is paying. Requires two different transactions and would send a link to the payee to enter their credit card information.
Multi-tenant design. Simple, clean, and easy for other organizations to adopt without too many complicated design elements.
An example of configurable components and how it could potentially look for the A's to change the styling to match their color scheme.
