Experience Finding App.

To discover life in other people's shoes

Overview

The Challenge

Find new user needs regarding travel & leisure

Time Frame

5 weeks

Team: 4 people

My Role: 

- Prepare and Facilitate group meeting discussions. 

- Facilitate conversations on contrasting ideas.  

- Flow charts2nd stage Wireframes

- Assign & organize jobs

- ensure feedback is given for each

- notify group members of each other's current state in the process & the group's overall process. 

- 1st stage wreframe and Prototype assigned frames. 

NeedsResearch

Findings

Following Others

Most people find experiences by looking at what others have done, this includes:

Personal

Users want more customization in all aspects

- Recommendation results

- Filters choices

Users want the system to remember who they are with customizations so that they don't have to start fresh each time

Unified Experience

Users desire to have the experience of finding events and route-finding to be unified in one place.

Users think that would result in a quicker and more convenient experience

Local

Users want more local experiences that are not always organized by the city. 

e.g. Drag show at a bar, Parties...

Features

search up "Attractions" on Google Maps to find experiences.

A potential solution for having a "unified experience for planning & action"

Users

The desire of customed features is repeating theme

Based on these feedbacks, the idea of a platform that shows users similar people's travel plans started to emerge.

Business Case Studies

2015:

53%  Leisure Travel

27% Friend & Relative Visits, Religious, Health

Unexpected Validation of an Early Concept

The idea of a platform where users post and find travel plans for people of similar interests applies to both the Leisure user group and the religious & Friends user group. (visits often involve group activities e.g. dinner & night out)

Learning from Existing Products

Market Validation

Reviews

It is easier to gather review if the related "transaction" happens on the same platform. 

Relationship to users through user habits

Users feel more engaged when the output is relevant to the users' habits

Learning from Failed Travel Startups

1/4

Why Startups Failed:

Market Knowledge

Travel data is complex, it's hard to keep the User experience simple.

Adapt to Changing Landscape

Consumers have high expectations.

Information is constantly changing

Vulnerable Business Model

When are returns going to be generated?

Volatile Customer Memory

Users don't travel all the time. How to ensure return .

MarketResearch

TargetGoals

&Users

Targets

Connective - real people, and real experiences

Unified - planning + doing

Personal - Customizable & tailored experiences

Local & within the nation - Discover life right around you

Focused User Segments:

Local explorer

Young single user 

Young small group users

Travelers (city to city)

UserFlow

RoughIdeas

Discussion

& Decisions

Example of Feature Decisions:

On-Boarding Questions & System Memory

- a short questionnaire to understand users' lifestyles and interests. 

- continuously updates the user's interest profile according to recent activities.

Suggested Routes & Experiences on map

- visually connected to the map, easy access

- are the main components and would be on the home page.

FlowChart

Wireframes

UserTest Feedbacks & Changes

Users love Friends' activity feature & seeing others' routes

" I want to be able to see what people I know are doing and maybe join them if I don't know what to do on a Friday afternoon."

" I would go on here just to stalk on what other people are doing."

Users confused about whom the routes on the map belong to and when they were made.

Overall Users feel that there are too many frames

Search location suggestions are too short, and the “refine your search” section is too long

Tackled in 2nd stage Wireframe 

Simplifying the Design

  suggestion tab  & suggested routes serve the same function

-> got rid of the suggestion tab, which gives us space for filters on the first page. This allows filters to be put on the current location immediately and bring more spontaneous results.

List View Button

  clearer visualization of information 

Search Bar

  Neglected to be intentional about the search bar

  Discussions of the filter options location unresolved - > re-examine the problem -> realized the problem may lie in another feature

  Search bars = defined locations 

 

  Our feature = experience finding app = abstract

  Features not utilized by the users because the changes were too small to satisfy the action, users are impatient

Change on Design: 

  Delete & combine actions that show small results

Screens combined

Combined as tabs on one main page. Now users can quickly switch between these pages to add experiences to a trip they are planning.

FinalPrototype

Keyword Filters

& Listview

• Tailored recommendations
- Recommend
 routes based on personal interest profiles (number of routes that shows are controlled within a max number)

- control results by choosing filters or input concise keywords

- Listview provides information & rating based presentation of routes

- User-generated

- Presents who is currently on this trip and the option to request to join the trip

- Option to save to "Saved Trips" or "Saved Experiences"

- Users could click on the individual experiences and choose to use that alone

- Navigation powered by Google map

Route & Experience

Overview

Trip Planning & Saved Trips

- Users could create a new trip or drag "saved trips" or individual "saved experiences" into the "current" creating page and edit them.

- Users could choose to make their trips private

- shows pronouns

- badge levels encourage user participation

- Follow the user to see their route in recommended trips

Profile

Message

- Users can request to join a trip

- Users can create group chats for group trips

Screen Designs

MovingForward

• Style Guide & Prototype User test

Follow other route creators & friends

Group Trip feature? Can users request to join others' trips?

Global trips expansion. Should we? How do the features change when moving to a bigger scale?

Thank you!