Personal project / case study
About the Project
As an avid tennis player for the past decade, there has never really been a great solution to being able to see all courts in a city or even more so the availability of them. What started out as a figma challenge during my time in the google design certificate, has now turned into a full case study.
Users want an "all in one" tennis court locator solution to be able to see real time availability of a court on a detailed map, reserve said courts, and rate courts based off user experience.
TENNISGO allows users to locate and schedule tennis courts and helps users stay connected to the tennis community.
Final Design Preview
I gave myself a general understanding of certain user pain points, motivations, and use cases while interacting with the site. Prior to the two round of usability studies, I wanted to see the general consensus of having an app like this in the first place.
10 user interviews
Young adults that play tennis casually
Young adults that play tennis competively
Young adults that used to play tennis in any capacity
John is a 25 year old who is very active, partaking in multiple recreational sports such as rock climbing, ultimate frisbee, and tennis. In his current endeavors John is always looking for new tennis courts to play on available to him in his area. Unfortunately his only method of culminating a list is through an online search and a mapping tool.
1. Play more tennis
2. Find local courts with ease
3. Be able to book those courts
1. Can't find most courts in the area
2. Most tennis centers make you call them
3. Courts are usually full when I show up
No universal booking system in place
Users struggled with finding all purpose system to book a local tennis court, and each tennis center had their own complex methods.
Players would like to see court details
With online searches as the only resource as a visual and informational aid to tennis players, tennis courts are vaguely described with the number of courts, restrooms, and other amenities.
From the sitemap, I noticed that there was no way to display sub menus for the profile tab. To address this issue of navigation, I added this feature into the second iteration of design. also in my very first iteration of the design, the confirmation and modification pages were too synonomous and confusing so that was also changed with keeping the userflow in mind.
During my time in the Google UX design certificate program, I started on TENNIS as a small project that had its first iteration of design giving a rough estimate on what I actually wanted to create post certificate.
The v0 wireframe was one of my first mockups for this project, turning into the v1 wireframe getting more familiar with Figma and working with auto layouts, components and basic aspects of information architecture
Two iterations of unmoderated usability studies were conducted for the low and high fidelity designs.
The following charts are from the first iteration to discern certain design changes for the second iteration.
After these findings, the main design change I wanted to implement was completely redesigning the bookings tab. From the file format I opted for an accordion style menu because it would add motion to the design and also retain the simple nature of the entire design.
Opting for a neutral color palette, I decided on these primary colors as they closely resembled the nature of the sport. With nothing too harsh on the eyes, but also readable enough for accessibility sake.
This is my first case study outside of my certificate and I definitely learned a lot for future projects and what I personally enjoyed working on and getting into that designer mindset.
Things I Learned
Streamline Future Research Plans
As there are preferred methods in conducting any type of research, I want to definitely perfect my personal way of getting quality research and feedback from users. Getting into that user first mindset is definitely something I want to work on and hoping to gain more knowledge from their point of views.
Add More Features In Designs
Prefacing my final point, I wanted to add more features in my design. But in this particular case, I believe that quality of my main user flow was the most important and wanted to focus on minor features later on in future revisions.
Iterate Iterate Iterate
I did have an initial iteration of my design, and brought it to life in a more formal setting, but in the future I'd like to better document even my sketches and create multiple iterations to better align with user needs/wants/etc.