Created for: Contract Work
Paper/Pencil, Illustrator, InVision
I began this project by conceptualizing the pathways through the full website for HotelRate. There is a public facing side and a secure side to the site. The public-facing side is to capture a new user base (secondary audience) and to support the existing user. As in the project statement, the primary user – a hotel owner or hotel manager or similar – seeks to find out (1) how good or bad their hotel is rated and (2) how to prepare for the next review.
The secure site will give the primary user access to review their current review(s) and past reviews if they exist. It was assumed that primary users would (1) already have an account and be provided a username and password to log in to the secure side of the website, and (2) primary users would receive an email notification that a review had been made with a direct link to log in from that email. Within the secure side of the site, primary users will be able to navigate to the public-facing content, but remain logged in to their active session to get back to the review data without having to log back in.
As noted in the project description, the data has potential to be massive for these 5 diamond infraction reviews. The table system for the data will be built in to be displayed by infraction order by default. The user can then click on the header name of the table to view results:
• Order by Severity (highest to lowest, or lowest to highest)
• Order by Room (room number ascending or descending)
• Order by Rule (rule number ascending or descending)
• Order by Location (location in a room alphabetical or reverse)
• Order by Category (rule category alphabetical or reverse)
Users will also have the ability to determine how many results the user can view on a page at a time (10, 25, 50, 100, ####).
The filtering system will allow users to drill down into multiple options to refine the results. This option will give the user the ability to see all of the 1 level severity items to try to work on those before the next review, or see where Cleanliness is an issue and ratify those issues, or limit to Rooms where the infractions took place to review staff who are in charge of those rooms. The Version 1 prototype does not reflect this, but multiple filters will be able to be used at once to drill down into the most refined output.
The final product will want to avoid a zero-output option, meaning that, if a user drills down so far into the data that there are no results, the system will not allow for a zero result. Options to avoid this would be to start to limit (gray-out) filters when fewer topics become available, or when a zero-point has been reached, the system can suggest different options (e.g. “Would you prefer to remove XXX?”).
My first step in this process was to take pencil to paper to create a rough flow chart of the site so I could visualize the entirety of this project. This allowed me to envision the front end (aesthetics and layout) and back end (database) needs. From the sketch, I created a refined Version 2 of the IA.
This revision allowed me to further refine the outcome of the design. From the Information Architecture V2, I began pencil sketches of the site (visuals) and interactions. My sketches informed the wireframe layout, created in Illustrator.
From the initial wireframes, I created an InVision prototype to simulate the user experience/interaction for the HotelRate website. This interaction caused further refinement of the wireframes and brought to my attention some of the overlooked necessary interactions.
InVision allowed me to quickly mock up an interactive piece to show the intended flow through this project.