Case Study: Conference room reservation app for The Nerdery
Methods Used: competative audit // directed storytelling // feature cards // kano analysis
Tools Used: Pen and Paper // Sketch // Keynote // Google Forms
User:
The user is an internal employee of The Nerdery that is seeking a quick and simple way to find and reserve a meeting room for client and team meetings.
Challenge:
I was asked to design an application for the Nerdery that helps their employees find available conference rooms and reserve them. Employees would be able to find and schedule a conference room that they need "at the push of a button." The User asked that the app be "optimized for mobile." It will be an internally hosted app by the Nerdery.
Goal:
Design a meeting room reservation application that allows the user to quickly and easily find and reserve a meeting room from their phone.
Research:
I conducted a competitive audit of three scheduling sites to see what their features, UI elements and flows were. The most popular websites and apps were simple and and easy to navigate. They had straight forward e-mail login systems, double booking avoidance by integrating the businesses own calendar, mobile and desktop compatible, and had the ability to send notifications or alerts about reservations and events. There was also an admin account section for adding and editing rooms and users.
I then went to the Nerdery and met with the 3 users. I was able to ask effective questions during my contextual inquiry after learning what other websites and apps featured. It was very valuable to be able to sit in front of the users that will use this as well as the client. We asked them to walk us through the current process of booking rooms for meetings.
This was all great information and was very helpful in identifying the major pain points of their current system and allowed me to develop journey maps. Below are journey maps for their current booking process and a journey map for their ideal booking process.
The users chose the feature cards that best supported what the users wanted and I set up a quick survey of those cards to gain even more insight. We used the information we got and put that through a Kano Analysis to help prioritize the cards and tell us which cards and which features to focus in on when building our prototypes.
Final Deliverable: