Activity-upload enforcement is blocking real workouts while protecting the feed from abuse.
Athletes need completed activities to appear quickly, while trust and safety must keep suspicious uploads out of social surfaces.
Who you’d be doing this for
“My club asked why Sunday’s ride vanished, and all I have is a sync confirmation.”
Ai Suzuki · Recreational cyclist
She syncs rides from a connected watch and shares completed training activities with her club.
What is at stake
Legitimate watch workouts with unusual GPS traces are being held back from the feed. You must weigh faster publication against the risk of letting abusive uploads through.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- athlete publication speed vs. abuse exposure
- model recall vs. enforcement precision
- manual certainty vs. scalable decisions
- release urgency vs. verified evidence
Why Strava
Strava activity sharing depends on athletes trusting that recorded workouts will appear accurately and safely in the feed.
Written with these in mind
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.