← Strava
Something new at Strava

Prove athletes act on an insight when it cites their own workouts

You’re the ai / ml engineer. Your team is in the room. Printed Oct 13, 2026.

Personal training context must be useful without overstating what activity data proves.

Athletes want a clear explanation of change, while the insight must stay grounded in recorded activity evidence.

Who you’d be doing this for

“My coach asked why my long runs dropped off, and I spent ten minutes digging through old activities.”

Hassan Rostami · Recreational runner

She logs runs consistently and uses recent activity history to decide whether to increase training for a spring race.

What is at stake

Athletes can record months of workouts yet still have to reconstruct why their training changed. You have to weigh useful personalization against evidence that the model can genuinely support.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • athlete usefulness vs. unsupported inference
  • broad personalization vs. sensitive-data boundaries
  • fast learning vs. evaluation confidence
  • shared platform leverage vs. focused product proof

Why Strava

Activity history and athlete context make personalized training interpretation a natural extension of the consumer experience.

Written with these in mind

product-minded ML engineerresponsible AI practitionerpersonalization systems builder

Not your kind of problem? 6 more at Strava, or browse every organization.

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.