Our 2 designers led a series of iterations on the design with me directing evaluation between each iteration, providing actionable insights. I was responsible for creating all the testing scripts and organizing the team to conduct them as well as assisting with designs.
We started the design process with 3 initial big ideas (shown below) and then brainstormed as a team through a crazy 8 activities to explore more possibilities. We developed the generated ideas into storyboards to help us 1) validate the needs and 2) narrow down on path forward through an evaluation method called speed dating. These concepts were tested with both prospective guests and NWR staff.
Work of Xiangzhu Chen.
Speed-dating recruitment planSpeed-dating script - GuestSpeed-dating script - staffIt became obvious after speed-dating our initial concept storyboards with users that the solution we provide need to support the entire guests reservation journey, from the moment they start learning about the resort options, to looking into the specific hotel and dinning options, to finally complete the payment.
To understand the different pieces of information that are critical to the decision making process that users go through while planning for their trip, I led my team to conduct card sorting with 5 potential guests, asking them to categorize the information they’d like to see based on the stage they are in. Here are the results.
We started the design with exploring how to increase reservations during the hotel booking process. We wanted to make the reservation process as smooth as possible but also deliver the tailored experience that prospective guests look for. To accomplish the goal, we wanted to build in an survey process during booking for us to
- Make better recommendations to guests
- Collect data to train recommendation algorithm
We decided to go with a mobile-first approach when designing because during our contextual inquiry, most participants reported that they do their research and planning using their phones.
Group effort between Gillis Bernard, Xiangzhu Chen, and Melissa Shi.
Group effort between Gillis Bernard, Xiangzhu Chen, and Melissa Shi.
With initial round of testing, my goal was to understand which of the two or parts of the workflows better matches with users expectation and habit. Additionally, I also wanted to confirm our decision with a mobile first approach with design by better understand the devices used for trip planning. To accomplish these goals and work around our limitations around participant recruiting, my test plan consisted of 3 parts: guerilla research at Wholefoods, 1 in-person test, and 3 virtual tests.
Through testing, we were able to receive some feedback on the two work flows.
- Users desire more flexibility during the trip planning process and better affordance
- Users want to see more detailed information regarding the options NWR offers up front
- Users wish to know which days are the recommended options good for
Based on the feedback received, I was able to recommend the team to move forward with Flow 1.
Iteration 1 User testing planWith the second iteration, we improved on the design per feedback we received. In this design, we 1) integrated more details regarding the stay and experiences specialties, 2) allow users to manage itinerary easier, and 3) display itinerary based on day.
With this round of testing, I also decided to both guerilla and formal testing with guerilla research at the local farmers market and formal in-person testing. Additionally, we went through critique with our advising faculty members. During testing, we found out that we were lacking in the following area:
- Not setting up proper expectations on what the tool is for before prospective guests start using it.
- Not providing enough sense of urgency to promote reservation.
- Not enough details were provided on NWR offers to demonstrate their unique values.
- Need a way to come back to recommendations that guests are interested in.
Iteration 2 User testing planGuerilla paper prototype test at local farmers’ market.
From Iteration2 testing, it became clear that there is a lack of guidance for users to navigate from one step to the next, which prevents them from converting their trip interests to actual booking. In the new iteration, I helped built a better navigation for the planner.
Due to the limitation around recruiting testing participant from our targeted demographic, I decided to conduct round 3 of testing through two channels: guerilla research at local farmers market and virtual testing through usertesting.com. With the testing, I aimed to answer these questions:
- If user understood what the tool was for
- Did the overall process matches users’ expectations
- Users’ confidence in the recommendations provided
- Were there enough feedforward o guide users through the process
Iteration 3 virtual testing planIteration 3 Guerilla Testing PlanThrough testing, we were able to confirm that users are able to navigate the entire workflow presented smoothly with a clear understanding on what to expect from the tool. However, during this round of testing, we realized that there were other use cases that we haven’t consider yet. These use cases includes:
- What happens if users want to come back to their itinerary later?
- What happens if there are availability conflicts?
- What happens if user only book room and not activities?
Aside from the above use cases, we were also debating whether we should implement an auto generate itinerary feature to boost the likelihood of guests making activity and dinning reservations. It was critical to better understand the sentiment towards auto-populate user trip itinerary.
With this iteration, we were focused on refining the entire workflow and all the secondary use cases that we discovered during Iteration 3 testing. We built in the option to auto-populate itinerary based on users stared recommendations to assess users’ acceptance towards the idea. Additionally, we conducted a UI Exploration exercise to unleash our creativity on branding and uplift the over web app visual styles where we generated 63 different visual design layouts and asked peers to choose from based our intended branding image.
With this last round of testing, aside from evaluating whether we fulfilled the missing use cases discovered during iteration 3 we also wanted to assess users interest in having auto populated itinerary items and lastly understand users’ impression of the booking process and NWR.
When asked about their impression of the NWR trip-planning process, they reported that it was:
Professional
Modern
Efficient
Organized
Helpful
Clean
Inviting
Easy
We also looked into users sentiment towards the 2 ways of generating itinerary: auto-populate vs manual, and we found out that users do not have a strong preference toward auto-populate or manual itinerary creation.
Iteration 4 User testing planSince the goal is to design a smart trip planning tool that encourages higher conversion through custom recommendations based on user motivations and perceived values, we wanted to categorize all 70+ activities that NWR offers into various trip style. To help us categorize, I asked my team to conduct card sorting with the rest of the cohort, asking the participants to group the activities based whether they are cultural, relaxing, romantic, family friendly or active/wellness.
- Relaxation and Romance have a lot of cross-over. Depending on who you are travelling with, it could go either way.
- Active and Adventure seem to have overlaps as well.
- In general, more slow pace activity has the potential to be romantic.
- Animal Care Center, Cigar & Bar, and Metabolism Testing seem out of place.
- Adventure seems to be activities that requires to go offsite.