splash-screen.png

Case Study: Hiker

Hiker Case Study

Project Overview

The Challenge

Problem Space

More travellers then ever are beginning to hike when they travel, and for those who only have a couple days to explore trails, they want to be able to get the most out of these trips. They’re not sure which trails would best suit their hiking ability and trail preferences, while maximizing the time that they have.

Enabling travellers hiking in different countries to find trails they would enjoy the most by encouraging hikers to share trail insights and favourite experiences from their travels. 

 

Project Logistics

Timeline: 8 weeks / Role: UX & UI Designer and Researcher

 

 

Design Solution

 
 

Through Hiker, travellers are able to plan for hiking experiences when on vacation, discover the trail that’s right for them, and access practical tips from other hikers to inform their hiking experience.

To view a key flow of the app, please feel free to view the InVision prototype.

 
Hiker-Titled-Screens.png
 
 

App Functionality 

While Hiker provides travellers with full support from planning, finding, navigating to, and recommending a hike, it has three key features that sets it apart from other hiking apps:

 
 
hike-overlay copy.png
 
 

Tips & info from other hikers

Users are not only able to look at how other hikers have rated the trail (on a 4-star system), but they can also read helpful tips that others have left behind, discover images of the trail, as well as trail traffic averages per month (i.e., is the trail usually busy in June).

 
 
 
filter-overlay-test.png
 
 

Filtering by trail feature

While users can search and filter for trails based on length and difficulty, a key part of finding the right trail for their hike also rests on the type of features or terrain that the trail has to offer. Hiker allows users to filter for trails that include features such as waterfalls, lookout points, mountains, rivers etc.

 
 
 
explore-overlay.png
 

Recommending and sharing hikes

For many hikers a recommendation from someone they know plays a large role in making a decision on a trail. Through Hiker, you can recommend and share trails, and by connecting with friends and other hikers, users can see where these people have hiked and browse a selection of trails that users have dubbed “hidden gems” or “must-hike trails.

 
 
 

Research 

Methods:

 
interviews.png
 

Five in-depth interviews were conducted with people, who hiked while they were on holiday. These interviews were limited to those who were beginner-intermediate hikers, as defined by those who rarely (or ever) did multi-day hikes

 
 
secondary-research.png

Secondary research was also conducted through travel/hiking industry reports and academic studies of trail usage.

 
 

Interview Insights

 

  1. People care about the length and difficulty of a trail, but after that, they just want to hike the “prettiest one.

  2. Even a great hike can be ruined by factors like too many people on the trail or not being well equipped.

  3. Travellers trust friends, locals, hosts and hotel/hostel staff for hiking suggestions over online recommendations.

 
Whatever one looks the prettiest! Biggest return on your investment.
— Interview Participant
Rowdy people around you is less nice. People suck.
— Interview Participant
 
 

Secondary Research

 

While some research spoke directly to the hiking experience, other research suggested insights from millennials’ travel experiences and planning.

 
 
 
1-1m.png
 
one.png
 
70-percent.png
 
 

trips were made overseas by Canadians in April 2017 to countries other than the US.
(Statistics Canada)

of the fastest growing sectors in the travel industry is adventure tourism.
(Lonely Planet)

of people look at up to 20 hotel reviews before booking. (Worms University)

 
 
 

Developing the Persona: Jennifer Keel

 

Using the interviews that I conducted, I created a persona as a representation of the data, with the pain points and travelling goals draw directly from the interviews. Using the persona, Jennifer Keel, I was able to put a human face on the problem as I began to map the user journey and create the wireframes.

 
 
 
hikingblogs1.jpg
I don’t mind winding in and out in the forest, but it would be really nice to see a lake or the ocean.
— Jennifer

Biography

At 27 years old, Jennifer works as a nurse and lives in downtown Toronto with her partner of five years.

They love to travel once or twice a year in another country, usually reserving a day or two for hiking. She enjoys straying off the beaten path for local food, culture, and hiking, but also makes sure to see the major sites. And though she’s not an expert hiker, she does enjoy a hike every month or two close to home during the summer. Her ideal trail includes waterfalls, scenic lookout points and mountain views.

Travelling Goals

  • Disconnecting in nature and quality time with her partner.

  • Going on one to two stunning hikes while on vacation.

  • Finding the hike that will give the most enjoyment.

Pain Points

  • Too many people on the trail while she is hiking.

  • Hiking to a lookout point only to find the view disappointing.

  • Getting lost or getting eaten by bugs on the trail.

 
 

Early Challenges

 

During the early stages of sketching and creating early wireframes, I encountered several challenges that helped me pivot and brought me to an overall learning outcome: the need to experiment broadly and determine when to make drastic versus incremental changes.

 
 
 

“What am I looking at?”

I attempted to solve the pain points identified in interviews, such as too many people on the trail, by having hikers update the info on the app. However, in the first few iterations, none of my testers were able to interpret the data.

I had to take a step back, figure out the most useful info to be collecting from other hikers and other ways to represent it. After several tries, I realized that instead of making incremental changes, I had to look at more inspiration and experiment more widely.

Challenge-trail-info Copy.png
 
challenge-search-details copy.png

“And how is this sorted?”

When users first looked at the explore screen, they didn’t understand how the hikes were sorted–why certain entries were appearing above others. While I subsequently revised it several times, it was a slow process. User feedback at each stage still came back to the question “how is this sorted?”

I needed to address the issue more holistically, instead of making a series of small changes.

 
 

Developing the Wireframes

 

After a series of sketches and wireframes, I identified a key task flow and primary screens that would act as main entry points for anyone using the app, including: Explore screen, filter screen and hike details screen.

 
Artboard 2.png

01 Explore

Images give an immediate idea of what the trail looks like, together with important planning info: location, length and difficulty.

Artboard 2 Copy.png

02 Filter

After length and difficulty level, trail features were an important aspect of trip-selection for travellers, so these are prominently featured.

Artboard 2 Copy 2.png

03 Hike

In addition to overall trail description and details, hiker-inputted info such as trail traffic was included, along with trail reviews.

 

Task Flow

 

A task flow was generated of a primary task that users were looking to participate in: searching for a hike and saving it to go back to when needed.

 
Task Flow.png
 

UI Library

 

After establishing the visual identity and building out the UI Components, I created a UI library to ensure consistency across the app. The below is a condensed version of the full UI library.

 
Colours.png
Typography.png
Grids.png
Buttons_1.png
Icons.png
Buttons_2.png
 
 

User-Testing

User-testing took place throughout the creation process, from early wireframe iterations to high-fidelity prototypes, informing and pivoting the design as needed. The last round of user testing was at the high-fidelity stage. Below are some of the significant changes that were made.

 
 
x- mark-v3.png
 

Before: Explore Screen

In user testing of the Explore/Search page, I found users were confused by the “Friends’ Recent Hike category, the rating system and their location on the page.

 
 
check-mark-v3.png

After: Explore Screen

To solve the confusion in the Search/Explore page, I added clarity around the category (through use of friends’ profiles) and rating, and added colour to signify section location.

 
 
User-Tested Version

User-Tested Version

Revised Version

Revised Version

 
x- mark-v3.png
 

Before: Hike Screen

From missing information to usability issues, there were several instances where users ran into issues.

 
check-mark-v3.png
 

After: Hike Screen

Added in relevant information (such as map location, and introduced a new format for some sections.

 
User-Tested Version

User-Tested Version

Revised Version

Revised Version

To see the final version of the prototype, access the InVision link.

 
 

 Learning Outcomes

The project helped strengthen my ability to translate user interviews and user testing insights into an interface that would help users achieve their goals and reduce pain points. It also gave me an awareness of the importance of generating multiple ideas and experimenting with alternative interfaces from which to choose the best one for the user. 

 
 

Next Steps

 

I recently pitched Hiker to a small group of people interested in working on a side start-up together, and whether or not that possibility will come to fruition, I’d like to continue to design the My Hikes and Profile sections, and then conduct another round of usability tests. In tandem, I’d like to gather insights from talking to hikers and observing a few hiking trips, to make sure we are building out the most functional features first.