Strava segments are the most useful free benchmarking tool in cycling — and simultaneously the single biggest threat to your easy days. The same feature that lets you track fitness gains over a season also turns a Tuesday recovery spin into an unplanned threshold effort because you spotted a segment notification and couldn't resist.
I've watched this pattern play out hundreds of times. A rider builds a solid training plan, sticks to it for three weeks, then blows it all because a Strava segment popped up on their Garmin and they chased a local leaderboard time on what was supposed to be a Zone 2 ride. Two hours later they're cooked. Two days later they can't hit their intervals. And they cannot understand why their training isn't working.
Here's the thing nobody tells you: the problem isn't segments themselves. It's how you use them. Get this right and segments become a legitimate training tool. Get it wrong and they'll quietly undermine every structured programme you try to follow.
When Segments Actually Help
Informal Time Trials
This is where segments earn their keep. Pick two or three local segments — ideally one flat section and one climb — and ride them as controlled maximal efforts every four to six weeks. Same warm-up, similar conditions, solo, full gas.
You now have a real-world performance test that complements whatever you're doing indoors. Your FTP test tells you one thing. Your segment times tell you something else: how that fitness translates to actual road performance, with hills, wind, corners, and all the variables that a turbo trainer removes.
The key word is controlled. You choose when to test. You control the effort. You're not reacting to a notification — you're executing a plan.
I use two climbs and a flat 5km stretch near my house. Every month or so, I'll ride them properly — full effort, recorded conditions, noted wind direction. Over a season, that trend line is properly informative. More informative, honestly, than most indoor tests, because it tells me how I'm performing in the environment I actually race in.
Route Discovery
Strava's segment explorer is one of the best route planning tools nobody talks about. Filter by popularity, look at where the local riders are going, and you'll find roads you've never ridden. The most popular segments in an area often correlate with the best roads — good surface, scenic, interesting terrain.
I've found some of my favourite training loops this way. When I'm riding somewhere new, I'll look at the segment map before I go. If a climb has 10,000 attempts on it, there's usually a good reason. It's either a beautiful road, a proper test, or both.
Tracking Fitness Over Time
Here's where it gets really interesting. When you ride the same segments regularly — not chasing times, just riding them as part of your normal routes — you build a longitudinal dataset that's hard to get any other way.
Your time up the local climb in January versus April versus August tells a story. If you're training well, you'll see it. If you're overtrained, you'll see that too. A segment time that's consistently 15 seconds slower than your best, ride after ride, is a signal worth paying attention to.
The mistake is treating each individual time as meaningful. It's the trend that matters. One slow time means nothing — you might have had a headwind, been tired from yesterday's intervals, or eaten badly. Ten slow times in a row means something.
When Segments Wreck Your Training
The Unplanned Effort
This is the big one. You're riding easy — properly easy, Zone 2, nose-breathing, recovery ride. Your head unit pings: segment ahead. You see the leaderboard. You see your PR. You see that one local rider who's 30 seconds ahead of you.
And suddenly you're at threshold. For three minutes, maybe five, you're absolutely buried. It feels great in the moment. You might even set a PR. But here's what you've actually done: you've turned your easy day into a moderate day, you've accumulated fatigue you didn't plan for, and you've compromised your ability to go hard tomorrow when you're supposed to.
Dr Stephen Seiler's research on training intensity distribution — the work that gave us the 80/20 model — is clear on this. The easy days need to be properly easy. Not "mostly easy with one hard effort in the middle." Easy. The riders who improve fastest are the ones who polarise hardest: very easy on easy days, very hard on hard days. Segment hunting on recovery rides puts you in the grey zone that Seiler has repeatedly shown produces the worst outcomes.
One unplanned segment effort doesn't ruin a training block. But if you're doing it twice a week on your "easy" rides, you're systematically undermining the polarisation that makes structured training work.
Ego-Driven Riding
Let me break this down. You've just been passed by someone on a climb. You know there's a Strava segment on this road. You also know that today is supposed to be easy. But the idea of that rider beating your time on a public leaderboard is too much.
So you chase. Not because it's in your training plan. Not because it serves any physiological purpose. Because your ego can't handle seeing someone else's name above yours on a local climb.
This is human nature. I'm not immune to it. Nobody is. But recognising it for what it is — an emotional reaction masquerading as a training decision — is the first step to not letting it control your riding.
The fix isn't willpower. Willpower is a finite resource and you'll burn through it by Tuesday. The fix is structural: remove the trigger. Hide the leaderboard. Turn off segment notifications on easy days. Make it harder to make the bad decision.
Segment Hunting Replacing Structured Work
I've spoken to riders who've essentially abandoned structured training in favour of "riding segments." They go out, hit every segment on the route as hard as they can, ride easy between them, and call it interval training.
It's not interval training. The effort durations are random. The recovery periods are uncontrolled. The intensity is determined by segment length rather than by the physiological adaptation you're targeting. A 45-second segment and a 6-minute segment demand completely different energy systems, and smashing both at maximum effort in the same ride with no structure isn't training — it's just riding hard.
Proper intervals target specific adaptations. Three-minute efforts at 120% of FTP stress your VO2max. Twenty-minute efforts at threshold build your sustainable power. Segment hunting does a bit of everything and not enough of anything.
The Comparison Trap
Your local leaderboard shows times. It doesn't show bodyweight, wind conditions, group size, rest status, or whether someone was on an e-bike. And yet we treat these numbers as though they exist on a level playing field.
The rider who set the KOM on your local climb might weigh 58kg. You weigh 82kg. On a 7% gradient, that weight difference is worth roughly 30-40 watts of advantage at the same power-to-weight ratio — or minutes on a longer climb. You will never beat that time. Not because you're less fit, but because physics doesn't care about your feelings.
Similarly, a segment time set in a group of six riders drafting each other on a flat road is meaningless for comparison to your solo effort. Drafting saves 20-30% of your power output. So the KOM holder might have been producing 250 watts in a group while you're producing 300 watts solo — and they'll still have a faster time.
Wind is the other invisible variable. A 15kph tailwind on a flat segment is worth an enormous amount of time. Someone's "incredible" segment PR might simply mean they rode it on a day when the wind was behind them. Strava doesn't record wind.
KOM and QOM Psychology
There's something deeply addictive about the KOM/QOM system. It taps into the same competitive circuits that make racing compelling — public ranking, measurable performance, social comparison. The difference is that racing happens on a defined day with controlled conditions and agreed rules. Segment hunting happens every day, on every ride, with no controls and no rules.
The riders who hold the most KOMs in your area are almost certainly not the best riders. They're the riders who've done the most rides, in the most varied conditions, and got lucky with tailwinds often enough. Or they're the riders who specifically target segments — riding them repeatedly, checking wind forecasts, picking the perfect day.
Neither of those things is a measure of fitness. They're a measure of dedication to Strava, which is a very different quality.
The good news is that once you understand this, the KOM leaderboard loses most of its power. You stop comparing yourself to names on a screen and start comparing yourself to your own previous performances — which is the only comparison that actually tells you anything useful.
Local Leaderboard Dynamics
Here's where segments do something properly valuable for the cycling community. Local leaderboards create shared reference points. When you and your mates all ride the same roads, segment times become a common language.
"How did you go on the Vico Road climb?" is a conversation that only exists because Strava tracks it. That friendly rivalry — the nudging, the trash talk, the "I'll get you next time" — is part of what makes cycling social. It gives people something to talk about beyond kit and equipment.
The problems start when friendly rivalry becomes obsessive comparison. When you're checking the leaderboard daily. When you change your route specifically to target a segment someone beat you on. When you start timing your rides around weather forecasts to get optimal conditions for a segment attempt.
The line between healthy competition and unhealthy obsession is different for everyone, but a good test is this: does it bring you joy, or does it cause you stress? If seeing someone beat your time ruins your evening, you've crossed the line.
How to Use Segments as Informal TTs
If you want to use segments properly as training tools, here's a framework that works.
Pick your segments wisely. Choose two or three that you ride regularly. One should be a climb (2-5 minutes is ideal), one should be a longer effort (8-15 minutes), and one can be a flat power test. Avoid segments through junctions, roundabouts, or busy intersections — you don't want traffic lights determining your time.
Schedule your tests. Don't ride segments hard on random days. Put them in your calendar. Every four to six weeks, do a proper test ride: warm up for 20 minutes, ride the segment at maximum sustainable effort, record everything.
Control the variables. Ride solo. Note the wind direction and strength. Ride at a similar time of day. Don't test when you're fatigued from a hard training block — test when you're fresh, ideally after a rest day.
Track the trend, not the time. A single segment time is a data point. A season of segment times is a trend. The trend is what matters. If your 4-minute climb time goes from 4:30 in February to 4:15 in June to 4:05 in September, your training is working. If it flatlines or gets worse, something needs to change.
Compare only to yourself. The leaderboard is irrelevant for training purposes. Your position 47th versus 43rd tells you nothing about your fitness. Your time versus your own time six weeks ago tells you everything.
When to Hide the Leaderboard
This is practical advice, not philosophical. Most modern head units — Garmin, Wahoo, Hammerhead — let you configure segment display settings. Use them.
Hide segments on easy days. Create a separate activity profile for your recovery and endurance rides. In that profile, turn off segment notifications entirely. No pop-ups, no leaderboard, no temptation. You can still see the data after the ride on Strava — you just can't see it in real time when your legs are feeling good and your ego is feeling competitive.
Show segments on hard days. When you're doing intervals or a test effort, segments can actually help with pacing. Seeing your time relative to your PR gives you a target to work with. This is a legitimate use of the feature.
The on/off switch is the whole strategy. You're not abandoning segments. You're choosing when to engage with them. That distinction — between reactive and intentional use — is the difference between segments helping and segments hurting.
Strava Live Segments: Useful or Distracting?
Strava's Live Segments feature pushes real-time segment data to compatible head units. As you ride through a segment, you see your current time versus your PR or the KOM, with a progress bar showing whether you're ahead or behind.
On interval days and test efforts, this is a real asset. It's like having a virtual training partner. You can pace yourself against your best effort, see where you're gaining or losing time, and push harder in the sections where you know you can improve. For a structured segment test, Live Segments adds real value.
On easy days, it's a disaster. The real-time comparison is the most powerful trigger for unplanned efforts. Even riders with excellent discipline find it hard to watch themselves falling behind their PR and not respond. The visual cue is too immediate, too compelling.
The solution, again, is configuration. Set up Live Segments on your race or interval activity profile. Remove it from your endurance profile. This takes five minutes on your head unit and saves you from yourself for the rest of the season.
The Drafting and Wind Problem
Here's the fundamental issue with Strava segment comparisons that most people don't think about carefully enough.
Drafting: Riding in a group reduces your aerodynamic drag by 20-30% depending on your position. On a flat segment, this translates to a massive time advantage. Two riders producing identical power will have wildly different segment times if one was solo and the other was sitting third wheel in a group of eight. Strava can't tell the difference.
Wind: A 15kph headwind versus a 15kph tailwind on a 5km flat segment can mean a difference of two to three minutes. That's not a fitness difference. That's a weather difference. And yet both times sit on the same leaderboard as though they represent comparable efforts.
Weight: On a climb, lighter riders have an inherent advantage that no amount of fitness can overcome beyond a certain point. A 60kg rider and an 80kg rider both producing 4 watts per kilogram are producing 240 watts and 320 watts respectively. The heavier rider is producing 80 more watts — and still climbing slower. Strava doesn't have weight classes.
GPS accuracy: Segment start and end points are determined by GPS, and GPS accuracy varies between devices, between days, and even between firmware versions. A segment time can vary by several seconds based purely on when your device thinks you crossed the start line. On short segments, this error can be larger than the actual fitness difference between riders.
All of which means the leaderboard is, at best, a rough guide. Treating it as a precise ranking of ability is a mistake that will either demoralise you unnecessarily or inflate your ego unreasonably — neither of which helps your training.
Making Segments Work for You
The riders who get the most from Strava segments are the ones who treat them as a tool rather than a scorecard. They use segments to benchmark their own fitness, to discover new roads, and to add a bit of spice to their riding. They don't use segments to validate their self-worth or to measure themselves against strangers whose circumstances they know nothing about.
If you take one thing from this, make it this: the relationship between you and Strava segments should be intentional, not reactive. You decide when to engage. You decide when to chase. You decide when to ignore. The notification on your screen is not an instruction — it's information, and you get to choose what to do with it.
Turn off the leaderboard on easy days. Use segments as structured tests when you want real-world performance data. Track the trend over months, not the time on a single ride. And remember that the rider sitting at the top of your local leaderboard probably just had a really good tailwind.
Your training plan is smarter than your ego. Trust it.
If you want to talk training, segments, and how to stop sabotaging your easy days, the Roadman Cycling community on Skool is where the conversation happens. Riders sharing data, asking questions, and keeping each other honest. Come say hello.