Your Watch Says You Had a Bad Run. Did You?

You finish your run, stop your watch, and look down.

Your pace was slower than you expected.

Maybe your heart rate was higher than normal. Maybe your watch tells you that your training was “unproductive,” your recovery time suddenly jumped, or your performance score wasn't what you wanted to see.

Five minutes ago, you were just happy you got the run done.

Now?

It feels like you had a bad run.

I've caught myself doing this more times than I probably realize. We have access to so much information about our running now that sometimes it's hard not to let the numbers decide how we feel.

Pace. Heart rate. Cadence. VO₂ max. Training status. Recovery time.

The list goes on.

And don't get me wrong, I love having the data. Being able to look back at my runs and see how my training is progressing is incredibly useful.

But I think there's a point where the data can stop helping us understand our running and start telling us how we're supposed to feel about it.

When Did a Run Become a Score?

Think about the last time you went for a run without looking at your watch.

For a lot of us, that's probably harder to remember than it should be.

You might head out planning an easy five miles. You feel pretty good, the weather is nice, and you're enjoying yourself.

Then you look down.

Your pace is 30 seconds slower than what you normally run.

Suddenly you're wondering what's wrong.

Am I losing fitness?

Why am I so slow today?

Shouldn't this pace feel easier by now?

Nothing actually changed between the moment before you checked your watch and the moment after.

You were still running the same pace. Your body still felt the same.

The only thing that changed was that now you knew the number.

That's kind of crazy when you think about it.

A Slow Run Isn't Automatically a Bad Run

This is something I've had to learn with my own running: not every run is going to look impressive on paper.

Some days you're tired.

Some days it's hot.

Some days your legs just don't have it.

And sometimes there's no obvious reason at all.

That's running.

If you're training consistently, you're going to have days where a pace that normally feels comfortable suddenly feels way harder than it should. You're also going to have days where you unexpectedly feel amazing.

One run doesn't define your fitness.

But when we have a watch collecting every second of every mile, it's really easy to treat each run like a test.

Did I pass today?

Did I run fast enough?

Was my heart rate low enough?

Did my fitness score go up?

Running doesn't always work like that.

Your Body Knows Things Your Watch Doesn't

Your watch knows a lot about your run.

But it doesn't know everything.

It doesn't know that you had a stressful day.

It doesn't know that you didn't sleep very well.

It doesn't know how motivated you were to get out the door in the first place.

It doesn't know that maybe today's biggest accomplishment wasn't running an 8:00 mile instead of an 8:30 mile.

Maybe it was simply showing up.

That's why I think learning how a run felt is just as important as knowing what the numbers say.

If you finished an easy run feeling relaxed, comfortable, and like you could have kept going, does it really matter if your pace was slower than last week?

I'd argue that it doesn't.

In fact, that might have been exactly the run you needed.

The Watch Isn't the Problem

I'm definitely not saying we should throw our running watches away.

I know I'm not going to.

The data can be extremely helpful. It can show trends in our training, help us control our pace during workouts, track mileage, and give us another way to measure progress.

The problem starts when we give the watch the final say.

Your watch should be a tool.

It shouldn't be the judge.

There's a big difference between looking at your pace and thinking, Interesting, I was a little slower today, and looking at it and thinking, I'm getting worse at running.

One is information.

The other is a conclusion.

And one run usually isn't enough information to make that conclusion.

Maybe the “Bad” Run Was Actually a Good One

Maybe you ran slower because your body needed recovery.

Maybe you ignored the pace and finally ran an easy run truly easy.

Maybe you were tired but still got yourself out the door.

Maybe you stopped halfway through because something didn't feel right instead of forcing yourself to finish.

Maybe you didn't hit the workout you wanted, but you learned something that will help with the next one.

Those things don't always show up in your stats.

They're still part of becoming a better runner.

I think that's something we can lose sight of when we're constantly chasing better numbers.

Progress isn't going to show up on your watch every single day.

Sometimes progress looks like a personal record.

Sometimes it looks like knowing when to slow down.

Look at the Watch, Then Look at the Bigger Picture

The next time you finish a run and your watch gives you a number you don't like, don't immediately label the run as bad.

Ask yourself a few other questions.

How did I actually feel?

What was the purpose of today's run?

Did I accomplish that purpose?

What else could have affected my performance today?

And most importantly:

Would I have thought this was a bad run if I hadn't looked at my watch?

You might be surprised by the answer.

Because your watch can tell you how fast you ran.

It can tell you how far you went.

It can estimate your fitness, recovery, and dozens of other things.

But it doesn't get to decide whether your run mattered.

You do.

Run your pace. Reach your reality.