Every time I start working with a new client, the same conversation comes up. They want to get faster, go farther, do more right from the start. And the first thing we have to talk about is that there’s going to be times to slow down.

Not metaphorically. Literally. Slow down to improve.

New runners who go out fast all the time blow up pretty often. They hit a wall halfway through a longer run that should have been manageable, walk parts of it in frustration, and then go home convinced they're just not a runner - that their body isn't cut out for this, that everyone else finds it easier than them. The pace that felt right in the first five minutes wasn't right for the long haul - it was adrenaline and optimism, and the body hasn't been trained to sustain it yet.

At every race I've done, I see a similar pattern play out. You can feel it before the gun even goes off - the crowd energy does something to your sense of pace that training runs never prepare you for. Then the gun goes off, the crowd surges forward, and within the first quarter mile, half the field is running faster than they should be.

The pace feels easy at the start, and everyone around you is moving with excitement and speed. So you move with them, faster than you trained for.

While doing my Ironman build over this summer, a heat wave settled in and didn't ease up for weeks. Temperatures were high enough to make afternoon rides a genuine struggle. I came back from my morning runs dehydrated, even though I'd done everything to prepare. And there were days when I had a workout on the calendar, but my body and motivation made it clear it wasn't happening.

I modified those days because the conditions made it dangerous or counterproductive to follow the plan as written. That's training in the real world.

At group runs, the conversation almost always ends up on the same topic. Someone mentions an ache or tightness mid-run, and then others start mentioning their aches or pains as well. I’ll ask how long it's been going on, but I know the typical answer is almost always longer than it should be.

A few weeks. Sometimes a couple of months. Sometimes longer.

They weren't ignoring it, exactly. Usually they just didn't know what to do with it, so they kept going, and the pain kept coming, until it got loud enough to stop them.

At my run club this past weekend, fall races were on everyone's mind. Half marathons, marathons, a few trail runs and triathlons - and the inevitable conversation about training came up. Several runners were mapping out their plans, talking through how much they could add each week to get ready in time.

Most of them were planning increases that felt responsible because they were structured around the 10% rule 

The 10% rule is one of those pieces of running advice that gets passed around so confidently it sounds like established science. Add no more than 10% to your weekly mileage, and you'll stay injury-free. It's simple, it's memorable, and almost every runner has heard it at some point.

At my run club this weekend, someone asked me how long they need to train before they're ready for a half marathon.

Knowing that they regularly run four to five miles already, my honest answer was: you could do one this weekend if you don't mind walking some of it.

It's not a precise answer, but it's a real one, and it reveals something about the question itself. The question sounds like it's about training timelines, but it's really asking for permission. Somewhere in their head, there's a standard they're measuring themselves against - a threshold of fitness, experience, or speed they believe they have to hit before they're allowed to attempt something like a half marathon. And until they hit it, the goal isn’t theirs to chase.

A friend of mine has been struggling financially for the better part of a year. He's not lazy - he works constantly.

But every time a small income opportunity shows up, he takes it. A one-off job here, a favor that pays a little there, a side thing that fills a weekend. He's busy every week. But he's no more ahead than he was a few months ago.

Two weeks ago, the heat shifted where I live, and last weekend it caught up with me on a long ride. I ran out of water about two-thirds of the way through, and the last stretch made that impact very clear. I cut the ride short by eleven miles because I hadn't managed the heat correctly, and my body made the decision for me. 

This is the version of a bad hot weather workout that most runners never get a clear explanation for. They try to drink more water, they slow down, and they blame the heat or decide they're just not built for running in it, and they never isolate the variables that keep working against them.

Last week was one of those weeks where the same idea kept showing up in different places.

I was working through my own race calendar for the rest of the year - mapping out which races between now and Ironman Cozumel in November are doing real work in my build. Having that date locked for months has made every training decision cleaner. What to prioritize, what to skip, which races to add and which ones to pass on. When you have a clear endpoint, the decisions in between stop being guesses.

There's a conversation I have at club runs more often than I'd like. Usually after we stop, when people are cooling down and relaxed enough to mention what's bothering them.

Last week it was a runner I know who is getting ready for her first marathon. She was clearly in pain, and she let me know her hip had been hurting for several weeks. Bad enough that she almost went to urgent care the week before. But there she was, pushing through the run, telling me about it like it was a minor inconvenience she just had to work around. 

At this point, I'm not surprised by these conversations, because I've been that person. For longer than I should have been.

I was on a run with one of my clubs last week when one of the regulars asked me what she should eat before a run.

She's a retired nurse with decades of experience in healthcare. She understands how the body works at a level most people don't. And she was genuinely uncertain about whether fruit was okay before a workout, whether she needed protein beforehand, and whether her muscles would break down if she got it wrong.

When I sat down to write this piece, I noticed the date this article was going out. Last day of June.

I just came off my fourth half Ironman a few weeks ago, and I've been in that strange in-between space since. Recovered enough to think clearly again about what’s next, not yet deep into the next build. It's the kind of week when you can reflect on the calendar rather than just react to it.

Half the year is gone. The other half is still sitting there, unclaimed.

Over the last few weeks, I've been asking people at the run clubs the same question: why do you come to the runs? 

The answers usually start the same way. They came for something practical - they wanted to get into fitness, they were looking for something social, they needed a reason to show up consistently. The club gave them that.

Last week, someone asked me how they should be breathing while they run.

It's a reasonable question. People ask questions like this all the time. What's the right cadence? What's the best stretch before a run? Should I be landing on my heel or my forefoot?

Underneath all of these is the same real question: how do I run faster?

There's a week somewhere in every training block where nothing feels right.

Your easy runs feel hard. Your legs are extra heavy on days they shouldn't be. You're doing everything the plan says. Sleeping enough, eating enough, showing up. And somehow the strength you felt last month seems to have packed up and left. 

Most people assume something has gone wrong.

The registration email lands in your inbox at 11:47 pm on a Tuesday.

You know how this goes. You've been here before with the cursor hovering, the small hesitation, then the click.

You've done the long runs before. You've stood at a starting line with cold legs and a stomach that won't settle. You know the wall that comes in the later miles, and you know the miles after the wall. You know exactly what you just signed up for.

He'd been struggling for months.

Every run felt like a fight he couldn't win. His pace would spike, and his heart rate would follow.

No matter what he adjusted, the effort never evened out. He was working hard, but most of his miles were being done at a walk, and it was starting to show in how he talked about his running. 

But he kept going. Consistent days, easy effort, same plan.

The late-ride fade used to be a given.

I'd be an hour and a half into a long bike session, fueling the way I'd always fueled with a gel every thirty minutes, roughly fifty grams of carbohydrate per hour, and somewhere around mile forty, the effort would start to feel really heavy. My energy would drop. Focus would narrow to just getting to the end. I'd finish the session, but I'd finish it feeling empty.

I assumed it was a fitness problem. I needed more base. More training sessions. More time in the saddle. More weeks of work before the long rides would stop feeling that hard at the end.

I got an interesting text from a client about a month before her recent race.

It had nothing to do with the race, really. She'd already done three long races, including a full marathon, in the time we'd worked together - she knew how to get to a start line. Her text was about what came after.

She was planning to climb Mt. Whitney a few months out and wanted to know if it would mess with her training, and whether she needed to think about it differently for the new challenge she was taking on.

A runner I know took three weeks off training because he was feeling exhausted, lacking motivation, and his legs felt heavy every time he went out.

He'd been training consistently for months and couldn't understand why his body wasn't responding the way it used to. The effort and miles were basically the same. But something had shifted, and he couldn't put his finger on what.

He'd read about overtraining syndrome, and the symptoms looked familiar. So he backed off.