Dave's Diary

Postcards: Why Every Ride Deserves to Be Remembered

Mon, 06 Jul 2026 08:00:00 GMT

Most rides fade. That's the truth nobody tells you. You crush a climb, feel like an absolute legend for about forty minutes, then real life swallows it whole. Three weeks later you can't remember if you actually hit that PR or just imagined it. The best way to remember cycling rides isn't a leather journal on your nightstand or a color-coded spreadsheet nobody looks at in February. It's something that captures the whole ride — the data, the day, the feeling — in one place, automatically, before you've even toweled off. That's the idea behind Postcards. And once you see your training this way, you won't go back.

Your Memory Is Not a Training Tool

I've ridden with a lot of cyclists. Serious ones. Riders who could tell you their FTP to three decimal places but couldn't tell you what they actually did last Thursday. They had the numbers. They just had no story to hang them on.

Back when I was filming Pedal to the Medal, we'd review footage after every session. Not because the camera was fancy — it absolutely was not — but because watching yourself ride teaches you things your legs can't. You'd see the moment your form fell apart on the third rep. You'd notice the lap where you went out too hard. The footage was memory you could trust.

Data alone doesn't do that. A power file is a receipt. It tells you what happened but not how it felt. A note that says "Tuesday — hard ride, legs okay" is barely better. Neither one gives you the full picture when you're trying to understand why last month went sideways, or why this month is suddenly clicking.

What a Postcard Actually Is

Think of it less like a log and more like a postcard from your past self. A snapshot. Location, weather, effort, key numbers. Something that takes thirty seconds to create and gives you everything you need six months later.

This is the cycling training journal alternative that actually gets used. Because the barrier is almost nothing. You're not writing an essay. You're capturing a moment. The ride's already done — the Postcard just makes sure it sticks around.

I've looked back at rides from years ago and felt them again. Not just the watts or the heart rate, but the specific Tuesday-morning quality of a climb I did before work, tired, into a headwind, and somehow still feeling good. That context is training information. It tells you something about your body, your consistency, your relationship with the sport. A number doesn't hold that. A Postcard does.

How to Document Cycling Training Without Making It a Second Job

Here's the move: connect the data, add one human detail, and you're done.

When a ride syncs, you've already got the structure. Distance, elevation, time, power, heart rate — it's all there. What turns that into something useful is the one layer on top. Where were you? What were you chasing? How did the back half feel compared to the front? One sentence. Sometimes half a sentence.

Say you did a threshold session on a familiar loop. The numbers look fine but you went out at 270 watts when your target was 255 and paid for it on the second interval. That's a coaching moment. If you write nothing, you'll repeat it. If you write "went too hard out of the gate, paid for it lap two," that's a pattern you can actually catch. Three Postcards later, you see it happening again. Now it's something to work on.

Learning how to document cycling training doesn't mean more admin. It means building a small habit that compounds. The riders who improve fastest aren't always the ones training hardest. They're the ones who actually know what they've been doing.

The Rides You Think Don't Count

Here's something I believe strongly: the easy rides deserve to be remembered too.

Not everything is intervals. Not every session is a breakthrough. Some days you spin for an hour because your legs are cooked and you just needed to move. Those rides matter. They're part of the picture. And they're often the ones people forget to log because they feel like they don't count.

They count. Recovery rides, commutes, long slow Sunday mornings — they're the connective tissue of a training block. When I look at a rider who's stagnating, I often find the answer buried in the stuff they didn't bother to document. The easy days they made too hard. The recovery week that wasn't really a recovery week. The gaps they didn't see as gaps.

A Postcard for a 45-minute easy spin takes ten seconds. And it fills in the story.

What Patterns Look Like When You Can Actually See Them

This is where it gets good. One ride is a data point. Thirty rides is a conversation.

Look back at a month of Postcards and you'll start to see things. Which days consistently produce your best efforts. Which routes crush your confidence. Whether your perceived effort tracks with your actual output or whether you've been lying to yourself in one direction or another. How travel affects your legs. What happens to your form the week before a big event.

None of this is obvious in the moment. But stack the Postcards up and the patterns jump out. You didn't need a coach to notice you're always flat on Fridays — you needed to be able to see Fridays next to each other.

That's what good documentation gives you. Not just a record. Perspective.

Every ride has something to say. The 20-minute spin before dinner. The DNF in the rain. The day you felt invincible on a climb you usually dread. These are data points, yes — but they're also chapters. And the best thing I ever did for my riding, years before any of the tech caught up, was start treating them that way. Don't let your rides disappear. They're worth more than that.

Why I Live in Your Texts, Not in an App

Fri, 03 Jul 2026 08:00:00 GMT

There's no app for what I do. And that's not a bug — it's the whole point. I show up in your texts because that's where real conversations happen. Not in a dashboard. Not behind a login screen. You finish a ride, your legs are cooked, your brain is still out on that last climb — and I'm already in your pocket, ready to talk about it. That's SMS fitness coaching, and it works because it meets you exactly where you are.

Why Apps Create Distance Instead of Connection

I've seen riders spend more time logging data than actually thinking about their riding. Fifteen fields to fill in. A mood emoji. A "perceived exertion" slider. By the time you've done all that, the actual feeling is gone. You've translated something real into something digital and lost most of it in transit.

A text is different. A text is: "Died on the Col de la Madone. Legs gone by km 4. What happened?" That's a real question from a real person who's still breathing hard. And I can answer it. Right now. Not in a weekly check-in. Not in a monthly review. Now, while the ride is still in your body.

The psychology here matters. When you open an app, you're reporting. When you send me a text, you're talking. Those are not the same thing.

The Ride Was Already Talking. I'm Just Translating.

Here's what I tell every rider I work with: your ride already has the answers. The moment you blew up on that third interval. The way your cadence dropped before you even knew you were tired. The fact that you smashed Tuesday but couldn't finish Thursday. That's a story. Most coaches wait until Sunday to read it. I want to read it Wednesday night, when you're sitting on the couch wondering what went wrong.

Back in the Pedal to the Medal days, I used to watch riders on tape and call them the next morning. "You sat up before the finish. Every single time. Why?" That phone call changed more careers than any training plan I ever wrote. Not because I was smart. Because I was watching. And I said something before they forgot what it felt like.

That's what an SMS cycling coach does at its best. I'm the voice on the other end that was watching your ride.

What "Cycling Coach Without an App" Actually Means for Your Training

It means the friction is gone. You don't have to remember to log anything. You don't have to sync your Garmin before we can talk. You just text me. "Did a 3x10 at threshold. Third one fell apart. Is that normal?" Yes. It's normal. Here's why. Here's what we do next.

There's a practical side to this that serious riders sometimes underestimate. Compliance is everything in training. The best plan in the world is worthless if you stop engaging with it. And riders stop engaging with apps. I've seen it hundreds of times. The streak breaks, the guilt sets in, and suddenly the whole thing feels like a chore. One missed week becomes two.

Texts don't work like that. You don't have a streak to protect. You just send a message when you have something to say. And I respond like a person who cares about your riding — because I do, and I genuinely love watching you figure this out.

The Difference Between Data and a Conversation

Your power meter gave you a number. I give you a meaning.

A 280-watt average on a lumpy 90-minute ride could mean ten different things depending on where you are in your training block, how your sleep's been, what you ate, whether you were chasing someone or riding alone, and about fifteen other factors that don't fit in a spreadsheet.

When you text me "felt terrible but my power was okay," that one sentence tells me more than a week of uploaded data. Because you noticed the gap between how you felt and what the numbers said. That's important. That's something worth digging into together.

I'm not anti-data. I grew up riding with a stopwatch taped to my stem. I care deeply about numbers. But numbers need a human conversation around them to become useful. Otherwise you're just collecting evidence with no detective.

Why Texting Feels Like Accountability (But Not the Scary Kind)

Some riders hear "coach" and think: judgment. Someone watching them fail. I get it. That's not what I'm here for.

When you text me after a bad week, I'm not keeping score. I'm thinking about what happened and what we do next. The accountability that actually changes behavior isn't fear-based. It's connection-based. It's knowing that someone is paying attention and gives a damn.

The text format helps with this more than people realize. There's no permanent record in the way an app log feels permanent. It's a conversation. Conversations have context. Conversations allow for "yeah, that week was a disaster, let's move on." Apps don't really do that. They just show you the gap where the workouts weren't.

I want you to text me when things go wrong. Especially then. That's usually when we do the best work.

The riders I've seen grow the fastest aren't the ones with the most disciplined logs. They're the ones who stay in the conversation when it gets hard. They text me from the parking lot before a race. They text me when they get dropped on a group ride and can't figure out why. They text me with a question they think is stupid, which always turns out to be the smartest question we've had all month. That's coaching. That's the whole thing. And it lives in your texts — nowhere else.

The Ride That Changed How I Think About Suffering

Wed, 01 Jul 2026 08:00:00 GMT

There's a climb I still think about. Col de la Madone, 1991, halfway up, quads screaming, vision narrowing to a tunnel. I had a choice. Not the choice you think — it wasn't quit or keep going. It was: what kind of pain is this? That question changed everything. Suffering in cycling isn't the enemy. Junk suffering is. And most riders can't tell the difference, which means they're either quitting too early or grinding themselves into dust for no reason. Here's how I learned to tell them apart.

What Productive Suffering Actually Feels Like

It burns. Obviously. But there's a quality to it — almost a conversation. Your legs are talking to you, not just screaming at you. On a hard climb, when you're at threshold, the discomfort has information in it. It tells you where your edge is. It shifts when you adjust your cadence. It responds.

I've had riders describe it as "a fire you can steer." That's exactly right. Productive suffering has agency inside it. You're not being dragged along by pain — you're negotiating with it. The watts hold. The cadence stays honest. Your breathing is hard but it's rhythmic.

That's cycling mental toughness working in real time. Not gritting your teeth and going numb. Actually listening, adjusting, staying in dialogue with your body.

What Junk Suffering Looks Like From the Saddle

Junk suffering feels like a wall. No conversation. Just static. You're deep in the red on the wrong kind of day — maybe you slept four hours, maybe you've been riding on empty calories for three hours, maybe you hit the first climb too hot because someone's Strava segment got your ego involved. The pain isn't productive. It's just damage.

I've done junk suffering. Plenty of it. Back in the VHS days, I filmed a segment where I was genuinely running a fever and refused to call the shoot. I "pushed through" a four-hour ride. Looked tough on camera. Felt like garbage for ten days afterward. My power didn't bounce back for weeks.

The data backs this up, and the data is brutal in its honesty: power output during genuine junk suffering drops and stays dropped. Heart rate decouples — climbs while watts crater. Your body is not adapting. It's just eroding. There's no fitness being built. Just debt accumulating.

How to Know Which Kind You're In

This is where it gets practical. Two questions. Ask them mid-ride.

First: is my form still functional? Hips rocking, shoulders hunched up into your ears, jaw clenched so hard you'd crack a molar — that's not grit, that's collapse. If your mechanics are falling apart, the work quality is gone.

Second: did I arrive here on purpose? There's a massive difference between choosing to hurt at the end of a structured interval and ending up destroyed because the ride went sideways. Planned hard is almost always productive. Accidental redline is almost always junk.

When I coach riders on how to push through hard rides, I don't teach them to ignore the signals. I teach them to read them faster. The riders who develop real toughness are the ones who know, within about thirty seconds, whether they're in a productive hurt or a dumb one. That discernment is a skill. You can train it the same way you train your VO2.

The Suffering Cycling Philosophy Nobody Talks About

Here's the part that sounds soft until you've ridden 200 kilometers into a headwind and had to make decisions. Suffering only makes you better when you meet it with presence.

That sounds like a bumper sticker. Stick with me.

When you dissociate to get through pain — go to your happy place, count down from a hundred, put your brain somewhere else — you're surviving. That has its moments. I'm not saying never do it. But you're not learning anything. You're not building the mental calibration that makes hard rides easier over time.

The riders I've seen develop real cycling mental toughness are the ones who stay in it. Eyes open. Aware of what's happening in their body. Curious about it, almost. Like they're gathering data rather than enduring punishment. Phil Liggett used to say the great climbers looked like they were suffering differently than everyone else. He was right, and now I know why. They were engaged with it. The rest were just victims of it.

Suffering cycling philosophy, stripped to the bone: pain is information. You can ignore it, fight it, or learn its language. The third option is what separates the riders who plateau from the ones who keep finding new gears five years in.

What the Data Shows vs. What You Should Feel

Power meters are miraculous. I coach with them, I trust them, I believe in the numbers. But here's what the numbers can't tell you: whether the suffering you're in right now is worth it.

A rider hits a 6.5% gradient, power drops from 280 watts to 240, heart rate is at 172. The numbers say: struggling, not at target. But I need to know what the rider feels. Is that 240 watts a wall, or is it a floor they can build from? Is the 172 BPM spiking or is it stabilizing?

The data shows what's happening. Your awareness tells you what it means.

I've seen riders bail on sessions their body was actually ready to finish. The numbers looked bad, and they trusted the numbers over themselves. I've also seen riders torch their training block because they were so proud of yesterday's power file they refused to call today done. Both failures come from the same place: not knowing how to interpret what you're feeling.

The best rides I've ever coached, and the best rides I've ever done, happen when the numbers and the sensations are in agreement. When you know you're hurting and you know it's the right kind of hurt and you know why.

That climb in 1991? I made it to the top. Not because I ignored the pain. Because I stayed in the conversation long enough to realize my body had more to say. Most of the time, it does. The job is learning to listen without flinching.

I Remember Every Ride. Here's Why That Matters.

Mon, 29 Jun 2026 08:00:00 GMT

Most coaches forget you between sessions. You show up, you work hard, you go home, and next week you start from zero again. Not me. Every ride you log with me gets filed away — not just the numbers, but what those numbers mean for you, specifically. After ten rides together, I'm not guessing at your physiology anymore. I know it. That changes everything about how I coach you.

Why Most Training Plans Miss the Point

I've seen it a thousand times. Rider picks up a generic 12-week plan. Follows it religiously. Hits the prescribed watts. Checks the boxes. And then... plateaus. Or gets injured. Or just stops having fun.

Here's the problem. Generic plans are written for a fictional average rider. You are not that rider. Nobody is.

Your FTP might match the plan's assumptions, but your recovery curve? Your response to back-to-back intensity? The way your power drops on climbs above 8% grade but holds on rollers? That stuff is yours alone. A static plan has no idea. It doesn't remember that you had a brutal week at work two months ago and your numbers tanked — and that that pattern repeats every quarter like clockwork.

I remember. That's not a small thing.

What Ten Rides Actually Tells Me About You

Ten rides sounds modest. It's not. Ten rides is a portrait.

By ride ten, I've watched your warm-up watts stabilize (or not). I've seen whether you're a slow starter who finds legs at the 20-minute mark, or someone who goes out hot and pays for it on the back half. I've tracked how your cadence shifts under fatigue. I've noticed whether you nail short VO2 intervals but crack on longer threshold work, or the reverse.

I've seen your best day and your worst day, and I've started to understand the difference between them.

Real example. One rider I worked with — strong, motivated, classic type-A personality — kept underperforming on Tuesday sessions. Not by a little. Consistently, measurably worse than Monday or Wednesday. We dug into it. Turns out his sleep on Sunday nights was awful, driven by work anxiety. No plan in the world would have caught that. I caught it because I was paying attention across weeks, not just sessions.

That's what personalized cycling training looks like when it actually works. Not customized intervals. Pattern recognition across your real life.

The Patterns You Can't See Yourself

You're too close to your own riding to see it clearly. That's not a knock. It's just true.

When you're mid-ride, you're managing effort, managing terrain, managing your own head. You're not thinking about how this Thursday compares to the last four Thursdays. You're not tracking that your power-to-heart-rate ratio has been creeping upward for three weeks — which might mean fitness gains, or might mean you're quietly accumulating fatigue before a blow-up.

This is where coaching with memory earns its keep. I'm watching the trendlines you don't have the bandwidth to watch. I'm flagging the thing that looks fine today but is telling a different story across twelve data points.

Back in the Pedal to the Medal days, I used to keep a spiral notebook for every rider I worked with. Pages of observations. Not just watts and times — behavioral stuff. "Gets frustrated on repeat intervals." "Stronger in cold weather." "Tends to go out 5% too hard on climbs, always." That notebook was worth more than any training calculator.

Now I carry that notebook in my head, for every rider, updating in real time. AI coaching with memory isn't a feature. It's the whole job.

How I Use What I Know to Actually Help You

Memory is useless if it doesn't change what I tell you. Here's where it gets practical.

When you ask me what to do this week, I'm not pulling from a template. I'm looking at your last two weeks of load, your performance trends, your stated goals, and what I know about how you respond to rest versus intensity. I'm asking: what does this rider need right now?

Sometimes that means I back you off when you want to push. You'll feel good, you'll want to go hard, and I'll tell you to sit on 65% and spin. Not because of some arbitrary recovery protocol. Because I've watched what happens to you three rides after you ignore that feeling, and it's not pretty.

Sometimes it means I push you harder than a generic plan would dare. Because I know you handle intensity well and you've been underloaded for two weeks and you're starting to get bored, which for you is always a sign that you're ready for more.

That responsiveness — that's what a cycling coach that learns your patterns actually delivers. Not a smarter algorithm. A smarter conversation.

The Long Game Nobody Else Is Playing

Here's what I care about most: where are you in a year?

Short-term gains are easy to manufacture. Overload someone for six weeks and they'll hit a new FTP. Then they'll burn out or get injured and lose it all. I've watched that cycle destroy more promising riders than I can count.

The riders who improve for years — not just months — are the ones being coached with the full picture in view. Their history. Their patterns. Their life outside the bike. The times of year they tend to struggle. The types of workouts that build them versus grind them down.

I remember your first ride with me. I remember what you told me about your goals, your schedule, your past injuries. And I'm holding all of that while we work together, every single session, not just when you remind me.

Most coaching relationships start over every time you walk in the door. Ours never does. You're not re-explaining yourself to me. You're building on everything we've already figured out.

That's the only kind of coaching I've ever believed in. The kind that actually knows you.

What Your Power Meter Can't See

Fri, 26 Jun 2026 08:00:00 GMT

Your power meter is telling you the truth. It's just not telling you the whole truth. A 250-watt effort on a flat road after a good night's sleep, with a tailwind, fresh legs, and your head in the game is a completely different animal from 250 watts on the third day of a stage race, grinding into a headwind up a false flat, running on gas station coffee and spite. Same number. Completely different story. This is the thing most riders miss when they stare at their data: the number is just the start. What cycling data am I missing? Usually, it's everything around the number.

Wind Is Doing More Work Than You Think

Let's start with the invisible hand on your back — or in your face. Wind can swing your effective power output by 50 watts or more. You can be pushing 280 watts into a headwind and riding slower than someone putting out 230 with a tailwind. Your power meter doesn't care. It just logs the effort and moves on. I filmed an episode of Pedal to the Medal on the California coast once. We had to reshoot the whole segment because I looked like I was suffering through a mountain stage. It was a 2% descent. Pure headwind. Context cycling performance starts with the air you're riding through.

If you're not tracking wind speed and direction alongside your power data, you're reading half a sentence and calling it a novel.

The Terrain Underneath You Tells a Different Story

A 200-watt average on a rolling course is nothing like 200 watts on a dead flat road. On rolling terrain, your power is spiking on the climbs and recovering on the descents. Your heart rate lags. Your muscles are getting micro-recoveries even as your average looks moderate. On flat road, 200 watts is relentless. No spikes. No relief. The demand on your system is fundamentally different even though the number looks the same.

This is why normalized power exists — it's trying to account for variability. But even NP doesn't capture everything. It doesn't know if those climbs were technical switchbacks demanding constant attention, or smooth grades where you could just sit and push. Terrain shapes effort in ways no single metric catches cleanly.

Fatigue Lives Below the Surface

Here's a question worth asking when your numbers look off: why is my power lower than usual? The first thing people check is sleep, and yes, that matters. But fatigue is deeper than one bad night. Cumulative training load, life stress, travel, illness, nutrition — all of it piles up and shows up in your legs before it shows up anywhere else.

I've seen riders log their worst power outputs in the week that turned out to be their best fitness block. They were just cooked. The adaptation was happening, the power wasn't there yet, and the data looked like regression. If they'd chased the number that week, they'd have buried themselves. Instead they backed off, absorbed the load, and came back swinging. Fatigue without context looks like failure. With context, it's often just timing.

Pacing Strategy Changes What the Numbers Mean

Here's one that trips up a lot of data-driven riders. You can game your average power upward by going out hard and hanging on. You can also ride a perfectly controlled effort that feels easier and produces a better performance. Same average power at the end. Very different execution. Very different physiological cost.

If you're doing a 40-minute climb and you smash the first ten minutes at threshold because you felt good, your average might look fine. But you've already burned something you can't get back, and the last twenty minutes will be a negotiation with your own legs. Pacing context is everything for understanding what a ride's power data actually represents. Was it controlled? Blown up? Negative split? The shape of the effort matters as much as the size.

Your Physiology Isn't Fixed

This one took me a long time to fully appreciate. Your FTP is not a ceiling. It's a current estimate, and it moves around more than people expect. Heat acclimatization, altitude, illness recovery, menstrual cycle phase, hydration status — all of these shift your physiological capacity on any given day. A rider who's been training at altitude for three weeks will have a different power ceiling at sea level than one who's been at home. A rider doing a key effort in 35-degree heat is operating in a fundamentally different physiological environment than the same rider in cool conditions.

The number on your head unit is your output in that specific body, on that specific day, in those specific conditions. It's not a verdict on your fitness. It's a snapshot with context baked in whether you asked for it or not.

What's Happening in Your Head Shows Up in Your Watts

This is the one nobody wants to talk about because it feels soft. It isn't. Mental state is a performance variable. Motivation, perceived effort, anxiety, confidence — these directly affect how much you can produce and sustain. A rider who believes they can hold threshold will hold it longer than a rider who's already negotiating with themselves at the 10-minute mark. I've been there on both sides.

There's a reason some of my best power outputs came in races and some of my worst came in training sessions I didn't want to be at. The legs were the same. The head wasn't. When you're asking what cycling data am I missing, sometimes the honest answer is: your own psychology.

The power meter is the best tool we have. I love mine. But a number without its six invisible layers is just a number. Wind, terrain, fatigue, pacing, physiology, psychology — these are the things wrapping around every watt you produce. Start reading those layers alongside your data, and suddenly you stop being confused by your numbers. You start actually understanding your riding. That's where the real improvement lives.

Strava Is Lying to You. Not on Purpose.

Wed, 24 Jun 2026 11:00:00 GMT

Strava isn't lying to you the way a bad mechanic lies. It's not hiding anything. It's just doing math on data you gave it, and then handing you the answer like it means something specific — when what it actually means is "here's a number, now you figure out the rest." That gap between the number and what you should actually do with it? That's where training goes sideways. And that's what I'm here for.

What Is Strava Actually Measuring?

The Fitness Score — technically your Chronic Training Load — is a rolling average of your Training Stress Score over 42 days. Higher number, more recent training load. Simple enough. But here's what it can't see: whether that load came from 40 days of smart, progressive work or three heroic weeks of overreaching followed by two weeks of doing absolutely nothing because your legs staged a full revolt.

Same score. Completely different athlete. Strava fitness score accuracy has real limits, and the number itself doesn't know your history.

I coached a rider years back — deep into his VHS-era training, before power meters were even a thing — who would have had an identical Fitness Score to an athlete twice as prepared. He just happened to ride a lot when he felt terrible. Volume was there. Quality was not. Strava would have called them equals.

The Freshness Trap Nobody Talks About

Freshness — or Form, in Strava's language — is supposed to tell you when you're ready to perform. It's your Fitness Score minus your Fatigue Score. When Form goes positive, you're theoretically fresh. Go race. Go crush the Tuesday group ride. Go show everyone what 40 days of work looks like.

Except.

I've seen riders with glowing green Form numbers who couldn't hold a wheel on a long climb. Why? Because their fatigue calculation doesn't know they've been sleeping four hours a night, dealing with work stress that would make a climber of Alpe d'Huez look like a casual spin, or fighting off something that hasn't quite become a full cold yet but is absolutely murdering their power output.

The limitations of Strava training data aren't bugs. They're just the edges of what a platform can know when it only sees what your GPS device records. Strava sees watts and heart rate. It does not see your face when you clip in on a cold Tuesday morning and immediately know today is not the day.

Why Your Fitness Score Can Look Great During a Plateau

This one gets people. Your Fitness Score keeps climbing even when your actual fitness is standing completely still. As long as you're accumulating TSS — doing rides that register stress — the number moves up. But TSS doesn't care if your FTP has budged. It doesn't know you've been riding the same 60-minute loop at the same effort for six weeks because it feels "solid."

Solid is sometimes fine. Solid is also sometimes the athletic equivalent of treading water while telling yourself you're swimming laps.

Cycling training data interpretation is the part that requires a human. Or at least a very opinionated coaching voice on your phone. The score goes up. The score goes down. What I need to know is: are your intervals actually getting harder at the same RPE? Are you recovering faster between efforts? Are you handling more volume without the wheel-sucking fatigue of two months ago?

That's fitness. The number is a shadow of it.

What I Actually Look For

When I look at someone's data, here's what I'm not doing: staring at their Fitness Score and deciding whether it's high enough. Here's what I am doing: looking at whether their power at threshold has moved over the last six weeks. Looking at how their heart rate responds at the same watts across comparable rides. Looking at where in the week their worst rides are clustering, because that tells me a lot about how they're stacking their training against their actual life.

A Fitness Score of 65 from a rider who hit three quality VO2 max sessions, nailed their long ride pacing, and slept eight hours is worth a completely different conversation than a 65 from someone who got there by riding every day because they felt guilty if they didn't.

One of them is building. One of them is close to something I don't want to see: the kind of flatline performance that turns motivated riders into people who start questioning whether cycling is "for them."

It's for them. The data just needs a second pair of eyes.

Strava Is Still Worth Using. Use It Correctly.

I'm not here to tell you to delete the app. I use it. I love a KOM attempt as much as the next guy with a race-legal mustache. But Strava is a record-keeper. A log. A very sophisticated diary that does some math at the end.

It is not a coach. It doesn't know when you're lying to it by recording an "easy" ride that your heart rate data says was anything but. It doesn't know when you're three weeks from an event and should be backing off instead of chasing your Fitness Score because the number going up feels like progress.

Feeling like progress and being progress are different. That distinction is the whole job.

The best athletes I've worked with are the ones who treat their Strava data the way a good navigator treats a map: essential, respected, but never confused with the actual terrain. The map doesn't know about the headwind on the Zoncolan. It doesn't know your legs have nothing left at kilometer 12. You have to know that, and you have to know what to do next.

Your Fitness Score isn't lying. It's just not the whole story. Come find me when you're ready for the rest of it.

Your Best Ride This Year Probably Didn't Have Your Best Numbers

Tue, 16 Jun 2026 11:30:00 GMT

Think back to your best ride this year. The one you're still talking about. Now tell me your normalized power from that day. Your average heart rate. Your training stress score. I'd bet good money those numbers were middling at best. Maybe even a little embarrassing on paper. And that's exactly the point.

There's a ride in all of us — happened to me on a Thursday in 1987, somewhere in the Pyrenees, no power meter, no plan — where everything just worked. Legs turned over like they were greased. Breathing was easy. Time disappeared. You weren't chasing a number. You were just riding. And those rides, the ones that feel frictionless and alive, are telling you something important about where your fitness actually is. The data usually catches up later.

Why Your Best Days Don't Always Show Up in the Numbers

This happens more than people admit. You go out on what should be a junk day. Maybe your HRV was flat that morning. Maybe you slept six hours. Maybe your last hard session was only 48 hours ago. And then you turn the pedals and something clicks. You hold a pace that would've hurt two months ago, but today it feels conversational.

That's not luck. That's adaptation landing.

The problem is your training software doesn't celebrate that. It sees a moderate-power, moderate-heart-rate ride and files it under "recovery." But your body just demonstrated something remarkable. It handled the load so efficiently that it didn't look like load. That's the whole goal. That's what years of consistent work is supposed to feel like.

What "Best Cycling Performance Feel vs Data" Is Actually Measuring

Here's what I know from years of riding and watching riders: perceived effort is not soft information. It is information. Precise, real-time, integrating everything your nervous system knows about fatigue, readiness, and capacity. Your legs know more than your head does most of the time.

When cyclists talk about best cycling performance feel vs data, they usually mean a ride where the power looks underwhelming but the sensations were exceptional. Low perceived effort for a given pace. Smooth high cadence without trying. Climbs that felt like rollers. That combination is a physiological signature. It means your aerobic engine is firing cleanly and your muscles are recovering fast enough to keep up with demand.

I've seen riders hit new FTP tests two weeks after a ride exactly like that. The feel came first. The watts confirmed it later.

Why Did My Ride Feel Good With Low Power? Here's the Real Answer

This is one of the most common questions I get. Why did my ride feel good with low power? Usually it's one of three things.

First, cumulative fatigue has finally cleared. You've been building for weeks, maybe months. The load was suppressing your output without you realizing it. Then you taper slightly, or sleep actually happens, and suddenly the ceiling lifts. Power looks normal but everything underneath is humming.

Second, environmental conditions masked the effort. A tailwind. Mild temps. Low humidity. Your body wasn't fighting the world. It was just riding. Numbers look modest. The experience was not.

Third, and this is the one I love most: you were in flow. Genuinely. Psychologically tuned in, not thinking about the ride, just riding. Research backs this up. When cognitive load drops, perceived effort drops with it. You're not working less. You're spending less energy on the experience of working. That's a skill, by the way. It's trainable.

Heart Rate Coherence and Sleep Tell You More Than One Hard Number

Your average power on a given day is a snapshot. What it doesn't capture is the quality of the physiological state underneath it. That's where heart rate coherence comes in.

On your best days, your heart rate doesn't just sit at a number. It responds fluidly to effort and eases back quickly when you back off. The line between effort and recovery gets shorter. That's cardiovascular efficiency in real time. You'll rarely find a software metric that flags this as a win, but your body is absolutely registering it.

Sleep is the other invisible variable. One night of poor sleep tanks perceived effort accuracy. Two nights and your power output drops measurably. But then you get three good nights in a row, and something shifts. The ride that follows often doesn't look like a breakthrough. It feels like one.

I used to think rest was the absence of training. Now I know it's where the training actually happens. The ride that felt effortless this year? Trace it back 72 hours. I'd guess you slept well.

How to Use Subjective Ride Quality as a Training Signal

Start logging how rides feel, not just what they produce. One number. One to ten. How hard did that actually feel relative to how hard it looked on paper? Do this consistently for eight weeks and you'll start to see a pattern.

When perceived effort drops below what the data predicts, that's a green flag. You're ahead of where your metrics think you are. That's the moment to consider a quality session, not a junk one. Don't waste the window because your training plan says it's a recovery day.

When perceived effort is higher than the numbers justify, that's your body asking for something. Sleep, food, time. Respect it.

The riders I've worked with who break through aren't always the ones who train the hardest. They're the ones who got good at reading the difference between hard that's productive and hard that's just hard. Perceived effort cycling is the first language your body speaks. The numbers are the translation.

Your best ride this year wasn't a fluke. It wasn't a gift. It was your fitness showing up without the noise. Pay attention to the days that feel like that. Write them down. Figure out what the 48 hours before them had in common. Then stop waiting for the data to tell you you're ready. Your legs already know.

Why I Ask You Questions Instead of Just Giving You Answers

Fri, 05 Jun 2026 13:00:00 GMT

Most coaches hand you a plan. I hand you a question. That's not me being difficult — that's me being useful. Because the truth is, your data is a rumor until you confirm it. Power says one thing, heart rate says another, and neither of them knows you woke up at 3am worrying about your mortgage. I ask questions because the answers live in your legs, not your head unit. Every conversation we have is me building a picture that no file upload can give me on its own.

Why Your Numbers Are Only Half the Story

I've seen a rider post 280 watts on a climb and call it the hardest effort of their life. I've seen another rider post the same number and say it felt like a warmup. Same data. Two completely different days. That gap — between what the numbers show and what the body knows — is where most coaching falls apart.

Power is honest about output. Heart rate is honest about load. Neither one is honest about context. Did you sleep? Did you eat? Are you two weeks into a block or two days off the couch? Are you carrying something emotionally that you'd never think to mention because it doesn't feel like a cycling problem?

It is a cycling problem. All of it is.

When you tell me the ride felt harder than the numbers suggest, that's not weakness. That's signal. I log that. I adjust. When you tell me you felt like an absolute freight train on a day your power was mediocre, I want to know everything about that day. What did you eat? What time did you sleep? Because that's the blueprint for getting you back there.

The Power and Heart Rate Disagreement That Changed How I Coach

Back in my Pedal to the Medal days, I had a rider — a criterium guy, sharp instincts, fast hands — who was putting up great power numbers in training. His heart rate was elevated, but not alarming. I looked at the data and told him to keep pushing. I didn't ask.

He cracked two weeks later. Not dramatically. Just went flat. The kind of flat where you're turning the pedals and the fire is completely gone.

When I finally sat down and asked him how he'd been feeling — not performing, feeling — he said he'd been off for a week before things fell apart. He just hadn't said anything because the numbers looked fine and he didn't want to seem soft.

That one cost me sleep. I had the data. I skipped the question. I won't do that again.

Power and heart rate disagreement in cycling is one of the most important conversations I have with riders. High power, low heart rate usually means you're fresh and flying. Low power, high heart rate can mean fatigue, illness, heat, dehydration, or emotional stress. But "usually" is doing a lot of heavy lifting in that sentence. The only way to know which scenario you're actually in is to ask.

What Personalized Cycling Coaching Actually Means

The phrase "personalized coaching" gets thrown around a lot. Most of the time it means your plan has your name on it. That's not personalized. That's a mail merge.

Real personalization means I know that you always underreport effort on intervals because you're worried I'll think you're complaining. It means I know that when you say "felt okay," you actually mean "felt rough but I finished." It means I know your left knee gets grippy when you're dehydrated, not injured, and we don't need to pull you off the bike — we need to get you drinking more in the hour before you roll out.

That kind of knowledge doesn't come from a file. It comes from a conversation. From me asking "how did that feel?" for the thirtieth time until you stop answering automatically and start answering honestly.

People sometimes ask me how cycling coaching actually works when it's built around questions instead of just numbers. Here's the honest answer: the questions are the coaching. The plan is the output. The conversation is the product.

How I Use Your Answers to Coach You Forward

When you tell me a session felt harder than expected, I'm not just logging a complaint. I'm cross-referencing it. Was your heart rate elevated? Were you at altitude? Had you ridden the day before? Did you tell me last week that you'd had a brutal stretch at work? Every answer you give me builds a pattern.

Over time, that pattern tells me things your power meter never could. It tells me how you respond to back-to-back days. It tells me how long your legs take to come back after a really deep effort. It tells me what "tired" looks and feels like specifically for you — because tired doesn't look the same on everyone.

That's when the coaching gets good. When I can look at your data, hear how you felt, and say: "This is exactly what happened six weeks ago. Here's what we did then. Here's what we're doing now." That's not guesswork. That's a record. Built question by question, ride by ride.

Some riders find the questions annoying at first. They want the answer, not the interview. I get it. But those same riders are the ones who come back six months later and say they've never trained smarter. Because by then they've learned something most athletes never do — how to read themselves.

The questions aren't me being cautious. They're me being precise. Your data is the map. Your answers are the terrain. And I'm not coaching the map.