An extension of Circle Media’s, Inside College Athletics’ digital publications, Inside Sports Travel was a solution to help get fans more involved with their team. Inside Sports Travel (IST) allows universities and fans to organize and plan trips around their team and events.
The idea behind the Inside Sports Travel app, is supplying the fan with all the tools they need to stay in touch with their team and get the most out of a sporting event. Whether they are attending an event at home or traveling to another state, users can access anything they might need with this pocket concierge; including game day tickets, flights, hotel accommodations, calendar reminders, news and more.
Fortunately, there was already an existing market for IST, it was only a matter of being able to meet their demand.
Using the subscribers of Inside College Athletics as our test group, we sent out questionnaires to users, asking what we could include in future updates or apps to improve their experience. We also asked users what they wish they could access or get out of a sports app.
What we discovered is, collegiate sports fans have on average 2-5 different applications on their smart device for connecting with their team. They may have one app dedicated to their team and recent news, one to check live scores, and another for general information regarding the schools standing in their division.
Unfortunately, I left the project before it could be completed. However, prior to my departure from the project, I was able to create a working and sensible information architecture, wireframes, and several hi-fidelity wireframes that the following team would be able to build off of.
The most challenging part of building Inside Sports Travel was the organization of information and data. Between the asks of users as well as stakeholders, the app quickly became cluttered with features, making the app distracting and difficult to navigate.
There were a few things that I learned from working on what became such a complex product. The biggest lesson taught was that UX is not linear. There were many times I had to go back and revisit different sections of my process and research because users were getting confused. This was mainly because features were constantly being added to IST and were rushed to meet stakeholder meetings. I learned how to compromise with my stakeholders and users, and sit down and figure out which features were absolutely critical to user goals, and which others could be held back for post launch.