Photo by appshunter.io on Unsplash
You open Strava after a run, see three kudos and a comment from someone you vaguely know from parkrun, and feel a small hit of something. Then you close the app and forget most of what the run actually told you. That’s the honest state of Strava for most runners: a social feed dressed up as a training tool, used mostly for validation rather than improvement.
That’s not a criticism — it’s just how the app is designed. The kudos button, the segment leaderboards, the year-in-review graphics: all of it is built to keep you opening the app, not necessarily to make you a better runner. But underneath the social layer, Strava holds genuinely useful data. Pace trends, heart rate over time, weekly mileage, elevation gain, how your easy runs compare to three months ago. Most runners never look at any of it.
This isn’t about becoming a data nerd or turning your hobby into a spreadsheet. It’s about using the free information you’re already generating to train a bit smarter — without needing a coach, a premium subscription, or hours of analysis.
Stop chasing kudos, start checking trends
The single biggest shift is moving from “how did this run look to other people” to “how does this run compare to my last ten.” Strava’s Training Log (under “You” > “Training Log” on the app, or the Progress page on desktop) shows your weekly distance, time, and elevation over rolling weeks. That’s the view worth checking, not your feed.
Look for two things specifically:
- Sudden jumps in weekly mileage. If you’ve gone from 20km a week to 35km in a fortnight, that’s the kind of spike associated with injury, not the actual mileage number itself. Most experienced coaches still lean on the old “no more than 10% increase per week” guideline — it’s not gospel, but it’s a sane guardrail if you have no other signal to work from.
- Flatlining pace on easy runs over months. If your easy pace hasn’t nudged down at all in 12 weeks despite consistent training, something in your training mix probably needs to change — more easy volume, better sleep, or a look at whether your “easy” runs are actually easy.
Use Relative Effort instead of obsessing over pace
Strava’s Relative Effort score (visible on individual activities, calculated from heart rate if you wear a strap or compatible watch) is more useful than pace for most everyday runners, because pace is affected by heat, wind, hills, and how much sleep you got — effort isn’t, or at least not as much.
If you don’t have a heart rate monitor, Strava still estimates Relative Effort from pace and grade, which is rougher but not useless. The practical use: if two runs cover the same distance but one has a Relative Effort of 140 and the other 85, treat them differently the next day. High effort yesterday generally means an easy or rest day today — not because Strava says so, but because that’s just sound recovery logic. If you’re unsure what “easy” should actually feel like on those lower-effort days, it’s worth reading up on the difference between an easy run and a recovery run, because most runners run both too hard.
Segments: useful for motivation, dangerous for pacing
Segments are Strava’s most addictive feature and its most misused one. A segment is a fixed stretch of route where everyone who’s ever run it gets ranked. They’re genuinely good for one thing: giving you a repeatable, local benchmark to test fitness against, without needing a race.
Pick one or two segments near your usual routes — a flat 1km stretch, or a specific hill — and check your time on them every few weeks. That’s a legitimate, free fitness test.
What segments are bad for is real-time pacing decisions. Chasing a Personal Record on a segment mid-long-run because you suddenly see you’re 8 seconds off your best time is how easy runs turn into unplanned tempo efforts and how niggles turn into injuries. If you want structured speed work, plan it — don’t let a segment notification dictate it. Hill segments in particular are worth using intentionally rather than accidentally; if you’re building a hill session, it’s worth reading about specific hill training sessions that work rather than just hammering the local hill Strava has flagged for you.
Set up your training zones properly — don’t trust the defaults
Strava will auto-calculate heart rate zones based on age (220 minus your age, roughly), which is a decades-old formula that’s wrong for a meaningful chunk of runners — sometimes by 10-15 beats. If your zones are off, every “you spent 80% of this run in Zone 2” summary is misleading you.
The fix takes ten minutes: go to Settings > My Performance > Heart Rate Zones and enter your actual max heart rate if you know it (from a recent hard effort, not a guess), or better, set zones based on a recent lactate threshold estimate if your watch provides one. If you’re not sure what any of this means practically, it’s worth reading a proper breakdown of running heart rate zones before you trust the app’s colour-coded pie chart.
| Strava feature | What it’s actually good for | What to ignore |
|---|---|---|
| Training Log / Progress | Spotting mileage spikes or plateaus | The “you’re on track” badges |
| Relative Effort | Deciding if tomorrow should be easy or hard | Comparing your effort score to a friend’s |
| Segments | Repeatable local fitness tests, hill benchmarking | Real-time PR chasing mid-run |
| Heart rate zones | Structuring easy vs hard days correctly | Default age-based zone calculation |
| Kudos/feed | A bit of social motivation, nothing more | Any actual training decision |
| Year in Pixels / Annual Review | Fun to look at once a year | Basis for setting next year’s goals |
Build a simple weekly review habit
You don’t need to analyse every run. Once a week — Sunday evening works for most people — spend five minutes looking at:
- Total distance and how it compares to the previous week
- Whether your easy runs actually stayed easy (check average heart rate or how they felt against effort)
- Whether you hit the one or two key sessions you planned (a long run, a tempo, whatever your week called for)
That’s it. This is far more useful than daily scrolling, and it fits into an actual life with a job and a commute and other things going on. If you’re newer to running altogether and still working out which apps are worth your time beyond Strava, it’s worth a look at the best running apps for beginners in the UK — Strava doesn’t need to do everything.
Know what Strava can’t tell you
Strava is very good at describing what happened. It’s much worse at telling you why, or what to do next. It won’t tell you that your calf tightness is because you haven’t done strength work in six weeks, or that your flat week was because you slept four hours a night with a newborn. It has no idea you’re base-building for a spring marathon or recovering from a niggle.
That context is yours to hold, not the app’s. If you’re in a genuine base-building phase, for instance, low relative effort and unremarkable pace data is exactly what success looks like — worth knowing before you panic-compare your numbers to a training peak months away. It’s worth reading about what base building for runners actually involves so you’re not misreading quiet weeks as failure.
Similarly, if Strava shows you running fewer days than planned, don’t assume that’s automatically a problem before checking in on how many rest days you actually need — sometimes the data is telling you the plan was wrong, not you.
The Honest Takeaway
- Check your Training Log weekly, not your feed daily — trends over four to six weeks tell you far more than any single run.
- Set your heart rate zones manually using a real max HR or threshold estimate, not Strava’s age-based default.
- Use one or two local segments as repeatable fitness tests, but never let a segment notification talk you into an unplanned hard effort.
- Relative Effort is a better daily decision-making tool than pace — high effort yesterday generally means easy or rest today.
- Remember Strava describes what happened; it doesn’t know your sleep, your stress, or your training phase. You still have to think.
Next read: Understanding your training zones properly