Product design

Strava: see where your effort differs on the same stretch of road

Strava helps runners and cyclists record activities and review their performance. Segment comparisons focus on the same stretch of a route, making it possible to revisit personal efforts with an explicit baseline.

Form your own approach first, then explore the reasoning to check trade-offs and validation you may have missed. There is no single right answer.

01
DESIGN QUESTION

Explain “faster by how much, compared with what?”

A running app’s card only says “12 seconds faster.” Users do not know whether that means faster than last week or their best effort. You can change the card’s layout and wording. Available data includes the segment name, both activity dates and times, and which effort is the baseline.

  1. Task: Design a results card that identifies both efforts and the baseline. Use “October 20: 5:12; October 27: 5:00” as an example, and explain which information must change when the baseline changes.
  2. Deliver and check: Submit a sketch and explanation. Ask a reader to identify the two records and explain which one the faster/slower result is relative to. Do not add training advice or heart-rate data that was not provided.
Explore the reasoning
  1. Identify the context needed to understand the difference, then decide what must remain beside the most prominent number.

  2. Swap the baseline between the two records and check that the difference can still be explained correctly.

  3. Ask someone to interpret the card alone. Notice whether they miss a date, direction or comparison subject, then adjust the hierarchy.