ONEBOOK
OVERVIEW
OneBook is a web portal that allows the guest to view and book a room, services, and amenities offered by the property and make a single payment for all their purchases.
ROLE
UX Manager
User Research, User Flow, Interaction design, Visual Design, Prototyping & Design Reviews
PLATFORM
DURATION
Responsive
February 2024 - JULY 2024
TEAM
4 (1 Manager, 1 Lead Designer and 2 Junior Designer)
PROBLEM STATEMENT
Guests who want to have comfortable vacation face problems in deciding the rooms/services offered by the property because of the lack of information provided. Also, they are frustrated by the current payment flow after their bulk purchases.
DESIGN GOALS
-
Users should have an option to see all services offered by the property
-
Users should avail a facility to make a payment for all the services they chosen at one instance
-
Users should also be able to avail the add-on services
RESEARCH
User Interview​
​
We have conducted user interviews to understand the pain points faced by the users in the present system.
Questionnaires that were prepared to understand the below data points:
-
Type of Travelers?
-
Pain points they face while booking?
-
How do they view the availability of Rooms/Services?
-
What data helps them to finalize the decisions on rooms/services?
-
What type of devices do they use for booking?
-
What type of data they are looking for?
-
Improvement areas in the existing application?
Research Findings​
​​
Lack of information
​Decision-making information like amenities, data-wise pricing, offers are not provided upfront to the user.
​
Payment Process
Guest cannot make a single payment for all services chosen.
​
Repetitions:
Guest cannot choose all the needed services as a one-time activity
​
No Summary
Guest have no clue whether the booking is made after payment until the confirmation mail is received.
​
Search
Category selection is difficult and search results are not informative.
KEY BOOKING REASONS
ANALYSIS
User Persona​
​
User Groups
-
Business Travelers
-
Leisure Travelers
-
Long-term Travelers
​
Based on the research data the user group was categorized into multiple groups like business travelers, leisure travelers, and long-term travelers. These are groups that would like to do their booking from hotels directly instead of going through third-party websites.
​
Task flow - ​
DESIGN
Paper Sketches
FINAL PROPOSED DESIGNS (Limited screens attached due to policy)
Paper sketches will always give enough freedom to come up with multiple variations
-
Based on the data we collected during the research we placed the items that the users are looking for and with this, we went to get the feedback
-
With each variations, we got some positives and negatives
-
Finally, the image attach left side was drafted out based on the feedback we received and we decided to proceed with the wireframes and visual designs based on this layout.
Services View Screen (Card View & List View)​
-
Users can filter/search the any of the services and add them to the cart.
-
Navigation between multiple services and making a booking is made easy now.
-
Any services-related information like room details like amenities details, breakup pricing all can be viewed from the home screen and proceed to book. This reduces the lack of information and provides clear information to make a decision.
-
Add to cart is a function proposed to ease the booking flow of the user.
-
Cart is persistently available for the guest to see the added items and also gives more flexibility to remove or make any modifications.
RESULTS & OUTCOME
-
User research will reveal more data not only restricted to the current system pain points it also gives more insights on how the data to present, what users expect to see at each stage.
-
Always test the complex flow in the application which will help to address all the real-time scenarios including the exceptions.
-
Good knowledge of the integrated products and their functionality will help in making the right design decisions.