< Back to projects

The Run App

Roles

  • Lead Product Designer
  • UX Researcher

Project Type

  • Team-based
  • Product Design
  • UX Research

Duration

  • 12 weeks

Tools Used

  • Figma
  • Qualtrics
  • Teams
  • Excel

Background

Runners have several motives and varied needs for running, outside of the obvious motive to be physically healthy. However, the majority of smartwatch running apps and sports watches in today’s market use the one-size-fits-all principle and take little or no account of a runner’s individual characteristics. Standard running apps have features that allow users to select a run type, select a run goal, start tracking a run, pause (manual or auto) tracking a run, and stop tracking a run. There is generally very little room for customization in the current market of smartwatch running apps.

Challenge

Current market smartwatch running applications are a one-size-fits-all interfaces that do not allow many opportunities to customize the experience for users. The client asked for a smartwatch application interface that allows the user to customize the metrics tracked during their run.

Process

Data Collection:

Three methods were applied to the data collection process.

The primary research method was user interviews. Users were selected to participate in a structured, individual interview that comprised mainly of seventeen open-ended questions. Users of the “Design Squad: UX Community” Discord server and a private, unnamed Discord server volunteered themselves to participate. Each interview lasted approximately 30 minutes. Two users were interviewed on Discord, and the remaining was interviewed on the phone. The users were required to meet a minimum threshold of two requirements to participate in the interview. The first requirement was that the person must have had experience running before. The second requirement was that the person must have used running-related technology before.

The secondary data collection method was to evaluate published scholarly articles that relate to running-related technologies and their users. Articles published from an educational or governmental institution have been accepted as a valid form of secondary research for this study.

The third data collection method was a competitive audit consisting of the top three running-related applications used on smartwatches was conducted to understand the current state of running-related applications. The three applications that were chosen to be audited are Strava, Apple Workouts, and Nike Run Club.

Data Interpretation:

Two methods were used to interpret the data and consolidate results.

The interpretation team consisted of three members. Team member one reviewed the interview transcripts and secondary research data with members two and three. Members two and three asked the reviewer additional questions to draw out more details such as interviewees’ tones, attitudes, possible motives, and environment during the interview.  Members two and three also asked questions about the secondary data to measure against their initial assumptions made about the target user groups. Team member two reviewed the competitive audit. The other two members asked questions regarding whether the insights gathered during the interviews and secondary research data were in line with the competitive audit.

The interpretation team captured user insights as affinity diagram session notes using FigJam. Notes were captured at random by all three members of the interpretation team. After insights were considered complete, the team unanimously removed notes considered similar in nature (i.e., “User aspires to be active” and “Wants to be active” would be considered similar). Insights were then sorted into clusters without speaking. Once the clustering was complete, each cluster was discussed, and the label for each cluster was determined. Although there were parallels among each runner classification, there were discernable differences between their motivations.

Data Representation: Personas and HTA

Two methods were chosen to represent the data. The first data representation was user personas. These user persona types were identified in the labeled clusters during the affinity diagram process. Each attribute of the user persona is based on the interpretation team’s insights on the data collected in the primary user interviews and secondary data research. The second data representation was a hierarchical task analysis. This task analysis is a generalization of the insights found during the competitive audit and secondary research. It is based on how users currently use running-related smartwatch applications.

Personas

Hierarchical task analysis

Target User Groups

Novice Runner
Demographic: High School through Retirement Age
Motivations: Running is a supplemental activity used to support another recreational sport • Socializing with running community
Constraints: New to pure form running and needs heavy guidance • Has no goal to improve on pure form running
Frequency: Runs less than three times per week

Hobby Runner
Demographic: High School through elderly population
Motivations: Running community events • Stay active and healthy
Constraints: Does not have a strong desire for running improvements • Not data-focused  
Frequency: Runs less than three times per week

Lifestyle Runner
Demographic: College age through elderly population
Motivations: Running community events • Stay active and healthy
Constraints: Does not have a strong desire for running improvements • Not data-focused  
Frequency: Runs less than three times per week

Research Insights

One insight from this study, gained through the user interview process, is the strong social connection within the running community. Although running is generally considered a health activity, it is not often considered social or community-driven. One interviewee mentioned that road running and hiking were encouraged by the community in which the user lives. Based on this and other comments, it was determined that there is a sense of pride, belonging, and locality that was referenced regarding participation in 5K and 10K events. As a result of this study, the target user groups for this project were redefined. Initially, target users were thought to be “running experts,” “running novices,” and “running returnees.” However, runner traits were segmented differently than what was initially assumed. Through the affinity diagram generation, the target users and target users’ issues were better identified.  

Paper Prototype

Storyboard

User Evaluation Results and Redesign

We used Nielsen and Molich's Nine Heuristics to gauge the effectiveness of the product during initial concept testing with users. The users were asked to customize data fields and start a run.

Solution

UI Analysis

Demonstration