Team cslowly DP1 Report
====

Experience
----
__Redesign the Path Finding Experience__

In this project, our team decided to redesign the path finding experience. With this topic, our target user can be anyone, especially people who mainly use public transportation, or people who travel to far distance.

Interview
----
### Interviewee
We recruited 4 people with different background.
There are three university student, and one high school student.
The detailed participants information displayed on below table.

|Number|Properties|Interviewer|
|---|---|---|
|1|High School Student, Do not have experience of solely long-distance path finding, Get pocket money from parents.|Junu Kim
|2|University Student, Use Naver Map frequently, Irrelevant with CS/ID|Sanghyeok Nam
|3|CS student without HCI-related knowledge, Lots of long-distance path finding experience.|Dang Minh Hoang
|4|CS student with HCI-related knowledge|Thi Nguyen

We judged that the first participant is extreme case. The reason is that the participant has different financial condition compare with other participants(university students).

### Methods
Because the outdoor activites are restricted by COVID-19, all of the interviews are performed on online.
Considering our topic that related with outdoor activity, we have to replace the observation to remote interview.
We asked to user about their personal experience about path finding.

### Questions
It performed with the form of open-interview basically, but we asked some questions to observe overlapped needs between users.
- Q1. If there are multiple paths in suggestion, how would you choose the best path?
- Q2. Rate the importance ratio between cost, comfort, and time.
- Q3. Is there any inconvenience in previous path finding experience?
- Q4. Is there any suggestion to improve the path finding experience?

### Results
#### Participant 1
Participant 1 has relatively less experience of path finding compare with other participants. The participant mainly used Naver Map application for path finding.
- A1. Considering time consumption and <u>number of transfers</u>.
- A2. Time > Comfort = Cost (6 : 2 : 2)
- A3. There are some inconveniences such as:
- The application finishes the guide near the destination, so it is easy to wander the path.
- A4. There are some suggestions such as:
- Continue guiding until arrive to exact destination.
Fig 1. Guiding finished before arrival
#### Participant 2
Participant 2 is KAIST student who has experience of path finding from KAIST to Daejeon Station or Daejeon Complex Bus Terminal. He mainly uses Naver Map and Google Map. Furthermore, he is irrelevant to CS/ID so that he was interviewed from the perspective of the public.
- A1. Usually sort the recommended paths by <u>time</u> and <u>number of transfers</u>, then choose the first option.
- A2. Time > Comfort > Cost.
- Also, he thought time and cost are inversely related to each other.
- A3. There are some inconveniences such as:
- In naver maps, real-time traffic information is often wrong.
- Lack of transfer information (ex. After riding a train, what should I ride: bus, metro, or taxi?)
- If I go outside of the path, it doesn’t give us feedback or alternative paths.
- A4. There are some suggestions such as:
- What if the apps let us to set weights of time / comfort / cost when they make path recommendations?
- What if we can see other people’s paths that toward to the same direction?
Fig 2. No feedback when user go out form path

#### Participant 3
Participant 3 is an international student which is not really fluent in Korean.
- A1. To choose route amoung many difference choices recommended by an app, interviewee choose to sort by cost and number of transfer. He/she mainly uses KaKao Map and Google Map
- A2. Cost > time > comfort. When the difference in time isn’t significant,he/she sorts by cost).
- A3. Since he/she is not really fluent in Korean, it is hard to use local map application that only support Korean (this applies to KakaoMap)
- A4. There are some suggestions such as:
- In case of Google map, when finding direction by GPS locating, Google should make the displayed direction consist with the direction of the phone
- Need suggestion for the surrounding sight-seeing places around destination.
Fig 3. Insufficient language support

#### Participant 4
Participant 4 is an Computer Science with prior knowledge of HCI. Participants 4 is not familiar with the nearby area so he/she uses navigation application a lot. Good at direction and love explore the app interface user.
- A1. To choose the route, tt depends on which context, which situations or who he/she goes with. He/she mainly uses KaKao Map and Google Map
- A2. There is no fixed answer for all cases for this interviewee. It is 100% for each depends on situation:
- If rush or business work: choose time
- If go with others (for example: go on a date): choose comfortable
- If just go hang out and want to have a lot of time, cheapest is the chosen
- A3: Google Map did not show the high or stairs but just show that is the distance is close. He/she not able to know that beforehand and at the end had to carry heavy carriers up to the hill and stairs.
- A4: He/she recommend something that is not for interviewee-self, but observe his/her friends need:
- How high/ stairs/ how comfy the route by gradient map/coloring so it is more visible to users
- Direction keep changing when moving make people who do not know the map find it hard to locate where he/she is.
Fig 4. No consideration of obstacles

Needs
----
In the interviews, we could find some interesting moments and identify their needs.
- N1. Want to spend less time
- N2. Want recommendation based on time / cost / # of transfer / comfort balanced for most user
- N3. Want apps to guide them to exact destination, not near it
- N4. Want to know surrounding landmarks around destination
- N5. Want to choose transportations to ride
- N6. Want to minimize walking time
- N7. Want correct real-time traffic information (ex. bus arrival time)
- N8. Want full support for English (ex. searching function)
- N9. Want to refer to other people’s path
- N10. Want to spontaneous feedback when they go outside the path
- N11. Want to know if the high stairs including in the path
- N12. Want to fixed the direction to easy to locate his/herself

Insights
----
Beyond the identified needs, we could find insights what can help users overcome the needs.
- I1. User interface that provides easy ratio setting among time, comfort, cost, and number of transfers(N1, N2)
- I2. User interface that provides easy transportation setting among bus, metro, taxi, and so on(N5, N6)
- I3. User Interface that makes users easily recognize and set direction of the display(N12)
- I4. System that reduces the difference between suggested estimation and the reality(N7)
- I5. User interface that keeps users from going out of the path(N10)
- I6. User interface that provide appropriate feedback to users who went out of the recommended path(N10)
- I7. User interface that provides path to the exact destination(N3, N4)
- I8. User interface that gives landmarks information around the destination(N3, N4)
- I9. User interface with perfect language supports(N8)
- I10. User interface that provides geometricity and obstacles of the path that users can easily recognize(N11)

Studio Reflections
----
During studio sessions, a lot of classamtes gave us various helpful feedback. There were feedback about specification, presentation, needs, and insights. Furthermore, there were some other suggestions.

### Specification
The most common feedback was that the range of target user was too broad. We can consider narrow down the range of target user in ideation stage if we find more sufficient proofs. Or for another possibility, we can consider "special users" for example: mobility handicaped, people with luggage, etc. Since not many application currently supports this, we can make an unique user interface during this project.

### Presentation
As follow to the feedback about insufficient participant info, we reinforced the explaination: many specific characteristics of interviewee that suitable with purpose of the projects. We are also indicated about using of highlighting and images.

### Needs and Insights
There were some feedbacks that our insights are close to solutions, not close to problems. So, we thought about problems that cause the user needs, and tried to identify the insights after the studio sessions.

### Other Suggestions
Some students gave some suggestions about the direction of our project and the hardness of the project. People suggest that we can try with user who are mountain traveler, flight pilot, etc. We perceive that it is a nice idea. However, since these sets of users are unique, it is quite hard to us to integrate in this project.
Moreover, many people claims that they are already satisfied with current application like Kakao Map and Naver Map, it is hard for our team to somewhat do better interface. How to test our work later on is also a question/ suggestions that worth to focus on.