The Comparison Problem: Why Strava Can Make You Slower
Public training logs turn easy days into moderate days and rest days into guilt. How social visibility distorts training decisions, what selection bias does to your sense of normal, and how to keep the useful parts.
- The main cost is that easy days stop being easy when someone can see them.
- Your feed is a selection of other people's best days, not their training.
- Nobody posts the rest day, so rest looks rarer than it is.
- The accountability benefit is real — the fix is adjustment, not deletion.
- Hide the paces on easy runs and the problem largely disappears.
There is a version of this article that tells you to delete the app and train by feel. That version is wrong, because the accountability is genuinely valuable and most people who quit simply train less.
The useful version identifies exactly what the problem is, because it turns out to be narrower and more fixable than "social media is bad".
The main cost: your easy days stop being easy
This is the specific, measurable harm and it is worth understanding precisely.
Endurance training works largely because most of it is easy. The physiological case is well established — a large volume of genuinely low-intensity work drives aerobic adaptation with a fatigue cost low enough to allow the hard sessions to be hard. The argument runs through why Kenyan runners jog so slowly and the Norwegian method.
The benefit of an easy run depends entirely on it being easy.
Now add visibility. You are on an easy run. Your pace is going to appear in a feed. And 5:45/km looks better than 6:20/km.
So the pace drifts. Not consciously, and not by much — 20 or 30 seconds a kilometre. But 30 seconds a kilometre is frequently the difference between comfortably aerobic and mildly uncomfortable, and it converts a recovery session into a moderate one.
Do that four times a week and you have arrived in the well-documented failure mode: all your running is moderately hard. Too hard to recover from, too easy to drive adaptation. You are tired all the time, your hard sessions are worse than they should be, and your training log looks excellent.
This is the single largest cost of public training, and it is invisible from inside. Nobody decides to run their easy days faster. The pace just settles slightly higher when someone is watching.
The second cost: a distorted sense of normal
Your feed is not a representative sample of how people train.
Posting is selective. Good sessions get posted. Abandoned ones frequently do not. The 5 km someone cut short because they felt awful either does not appear or appears without much detail.
Fast runners post more. People pleased with their training engage more with a platform that displays it.
The platform surfaces the impressive. By design.
Nobody posts the rest day. This is the most distorting omission of all. An athlete taking two rest days a week is invisible on those days, so your feed contains only the people who trained. Rest appears rare when it is universal.
The result is a sense of normal that is calibrated against a filtered sample of other people's best days, compared against your own complete and unfiltered record.
The third cost: rest feels like failure
Follow enough people and someone is always training. There is no hour of the day when the feed is empty.
Which converts a rest day — a training component with a specific physiological purpose — into an absence. Something you are not doing, while everyone else is.
The consequence is people training on days they should not, accumulating fatigue, and getting injured. And the mechanism is not competitiveness so much as the simple discomfort of visible inactivity.
The fourth cost: segment hunting
Small and worth naming.
Segments turn an easy run into a race, in 90-second bursts, at unplanned times. A single hard effort in the middle of a recovery run is not catastrophic, and doing it habitually removes the recovery function of the session entirely.
What is genuinely good about it
The reason not to just delete it.
Accountability works. The evidence on social accountability and exercise adherence is reasonably supportive. People who log publicly train more consistently, and consistency is the variable that matters most over years.
The training log is valuable. Being able to look back at what you did before a good race, or to see that a bad patch coincided with a large volume increase, is genuinely useful — this is how you catch the load jumps that cause the injuries described in tendons adapt slower than muscle.
Community matters, particularly for people who train alone. Someone noticing a return from injury has real value.
Comparison is not always corrosive. Seeing what a training block actually looks like can be instructive, especially when starting out.
The fixes
Structural, not willpower-based, because willpower loses this fight reliably.
1. Hide the pace on easy runs. The single highest-value change. Most platforms let you hide pace and heart rate per activity. You keep the log, the accountability and the community, and you remove the incentive that was pushing the pace. If your easy runs are the problem, this alone fixes it.
2. Run easy days without looking. Watch on the wrist, screen not on pace, or simply do not check it. Run by effort and look afterwards. This also builds the perceptual calibration discussed in heart rate vs pace vs power.
3. Unfollow generously. Anyone whose training reliably makes you feel behind. This is not petty; it is removing a stimulus that degrades your decisions.
4. Post the rest days. Or at least stop treating their absence as meaningful. Someone in your feed needs to see that a serious athlete takes days off.
5. Compare against yourself, a year ago. The only comparison with any information in it. Other people's current fitness tells you nothing about your trajectory.
6. Turn off segments if you find yourself chasing them mid-run.
7. Remember the context you cannot see. Training age, available hours, injury history, genetics, job, sleep, whether they have children, whether they are 25 or 45. A feed shows you an output with none of the inputs.
The deeper version
Underneath the practical fixes there is a question worth sitting with: who is your training for?
If it is for you — health, capability, the satisfaction of doing hard things — then the pace of an easy run is a private technical detail with no audience. Nobody is grading it. It is not a performance.
If it has quietly become a performance for an audience, then the audience's preferences start to determine your training, and the audience prefers fast easy runs and no rest days. Which is precisely the training that makes you slower.
The most consistent athletes tend to have quiet training and loud results. Their easy runs are unremarkable, most of their weeks look identical to the last one, and none of it photographs well.
The summary
The problem is not the platform. It is that visibility applies pressure to exactly the thing that most needs to be free of pressure — the pace of your easy running.
Hide the pace on easy days. Take the rest days without apologising for them. Compare with your own log from last year. Keep the accountability, which is real and useful.
Your easy runs are supposed to look slow. That is not a flaw in the session to be hidden — it is the session working.
Questions people ask
Does Strava make you train harder than you should?
For many people, yes, and the mechanism is specific. Knowing that an easy run will be visible nudges the pace upward, which converts genuinely easy running into moderate running. Since the benefit of easy running depends on it actually being easy, that drift removes most of the value of the session while adding fatigue.
Why does everyone on Strava seem faster than me?
Because you are seeing a filtered sample. People post good sessions more than bad ones, faster runners post more consistently, and the platform surfaces impressive activity by design. Your feed is a compilation of other people's best days set against your complete record, including the bad ones.
Should I make my training private?
Making easy runs private, or simply hiding the pace and heart rate data on them, addresses most of the problem while keeping the parts that help. Full deletion works too, but it discards a genuinely useful accountability and record-keeping tool for a problem that has a narrower fix.
Is social fitness tracking bad for you?
It is a trade. The accountability, the training log and the community are real benefits that keep people consistent. The costs are pace drift on easy days, guilt about rest, and a distorted sense of what normal training looks like. Whether it is net positive depends on how susceptible you are to those, which is worth assessing honestly.
How do you stop comparing yourself to other runners?
Structurally rather than through willpower. Hide pace data on easy runs, unfollow accounts that reliably make you feel behind, compare against your own log from a year ago instead of other people's current week, and remember that you cannot see anyone's context — their training age, available hours, injury history or life circumstances.
Keep reading
What the Data Says About Who Actually Sticks With Training
Motivation is not the variable. Across the adherence research, the traits that separate people still training in month six from those who stopped in week three are unglamorous, specific, and almost entirely about friction.
The Two-Week Rule: Why Most People Quit in Week 3
Week one is novelty. Week two is discipline. Week three is when the results have not arrived, the soreness has, and the decision actually gets made. What is happening physiologically, and the change that gets people through it.
Training Around a Full-Time Job: How Athletes Actually Do It
Nobody with a job trains like a professional, and the plans written by professionals assume you do. The scheduling patterns that survive real work weeks, ranked by how well they hold up when the week goes wrong.