"Listen to Your Body" Is Good Advice Nobody Knows How to Follow

Most runners were never taught what their body is actually saying

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.

"Listen to your body" is the advice coaches, training plans, and running forums default to when something feels off. It's also one of the most misunderstood pieces of advice, because it tells you to pay attention without telling you what you're paying attention for, or what to do when you notice something. Most runners fill that gap by acknowledging their pain while still pushing through until something gives, because the alternative is to stop at every ache and never build anything. 

Both responses come from the same problem: nobody explained what the message means.

Your Body Has a Communication System

The signals your body sends aren't always just random discomfort. They come from a specific set of structures doing specific jobs.

Muscle spindles detect how much and how fast a muscle is being stretched. When the stretch magnitude or rate exceeds what the system considers safe, it signals the nervous system. Golgi tendon organs sit at the junction between muscle and tendon and monitor tension. When the load at that junction becomes dangerous, they trigger inhibition to prevent tendon damage. Joint receptors detect pressure and compression at the joint capsule and communicate mechanical stress at the joint level. Inflamed tendons and bursae send their own signals through nociceptors - pain receptors that activate when tissue is under stress beyond what it can handle, communicating that the load being placed on that structure needs to change.

These structures are sending information continuously during every run. The problem is that most runners collapse it all into one category: something hurts.

My knee hurts. My hip is tight. Something feels off in my foot. The pain signal gets labeled and filed away rather than examined. Getting curious about what's actually happening - where exactly, when during the run, what makes it better or worse - is the difference between hearing the signal and listening to what your body is saying. 

When You Ignore the Pain Long Enough, the Stop Is No Longer Yours to Choose

The runners I see at group runs who mention something that's been going on for months aren't outliers. They're a regular pattern I see among runners as a whole. And the cost of running past the pain long enough is more than a longer recovery - it's that the injury eventually forces the decision to take a break for you.

A two-week rest or easing back on intensity and volume when the pain signal first shows up is a choice. A twelve-week forced stop, six months later, when something becomes seriously injured, isn’t. The training block you were protecting is lost either way - but with the longer downtime, now you're rebuilding from a hole instead of a manageable setback.

The longer you ignore what your body is telling you, the more likely your body will decide for you when you have to stop.

Soreness and Pain Are Two Different Signals With Two Different Answers

Running is supposed to feel like something. Effort is uncomfortable, especially on extended runs. Hard workouts are meant to be hard to push growth. Some runs are just going to feel rough, and that's part of the process. The question isn't whether something hurts - it's what kind of signal you're getting and whether it's part of the work or a sign the work is too much for your body. 

Some soreness after a hard effort is adaptive as your muscles rebuild slightly stronger than before. That's expected and not the concern here.

Discomfort that shows up mid-run and goes away afterward is worth paying attention to, but not necessarily worth stopping for. The question is whether it's a one-off or a pattern. A single run where your knee feels a bit off after a long descent is information. That same feeling on every run, in the same spot, at the same point in the effort, is a different consideration.

Recurring, localized pain is the signal most runners underestimate. A specific point you can put a finger on. Pain that shows up during every run. Pain that sharpens as the effort continues. Pain that comes back in the same place every time. These go beyond adaptation signals. They're load signals - receptors telling you that something is being asked of the tissue that the tissue can't currently give.

If the discomfort you're experiencing during a run isn't a normal byproduct of the workout, and it keeps showing up, that's the message to stop and get it looked at.

Four Reasons Runners Keep Running Through Pain 

The runners I talk to at group runs who've been dealing with something for months almost always say the same thing: it's manageable, so they keep going.

There are a few reasons this happens, and most of them are perception problems. 

The first is a physiological gap that creates a false sense of readiness. Aerobic fitness develops faster than musculoskeletal tissue - your cardiovascular system can handle more volume before your tendons, bones, and connective tissue have adapted to that same demand. The run feels fine aerobically because breathing is controlled and energy is there. But fine aerobically isn't the same as fine structurally, and the structural stress accumulates quietly in tissue that's been asked for more than it's ready to give, and shows up weeks later as something that "just started bothering me."

The second reason is normalization. A pain signal that shows up every run and never becomes catastrophic gets reclassified. It stops being a warning and starts being just part of running. The runner isn't ignoring it - they've decided it's background noise because nothing broke the last fifty times they ran on it.

The third reason is identity. Runners who are deeply invested in their training conflate stopping with failing. Acknowledging the signal means acknowledging they might need to pull back - and pulling back feels like losing everything they've built or are building towards. The training. The race goal. The version of themselves that shows up no matter what. So they minimize it, keep moving, hoping it just goes away on its own.

The fourth is culture. "No pain no gain." "Pain is weakness leaving the body." Running culture has a long history of treating discomfort as a character test, and many runners have internalized it. Stopping feels like admitting weakness - not just to themselves, but to coaches, training partners, and anyone watching. I've had athletes tell me after the fact that they didn't want to disappoint me by admitting things hurt. That conversation is always the same: my job is to push them, not break them. They're in charge of what their body is telling them. No external voice - including mine - can feel what they feel. The only person who can listen to their body is them.  

What the Signal Is Asking You to Do

Listening to your body means the response needs to match the signal.

Widespread soreness across a muscle group after a hard effort is asking for recovery - sleep, food, easy movement, and enough time before repeating hard work on the same muscle group. Rushing that window interrupts the healing and growth process.

Discomfort that shows up mid-run and fades is asking for attention. Note where it is, when it shows up, what makes it better or worse. That information is what turns a vague ache into something you can actually act on with changes to your training.

Recurring, localized pain or sharp pains during a run that aren't a normal byproduct of the effort are asking you to stop. Get it assessed. The current evidence-based framework for what comes next is PEACE & LOVE - the replacement for the outdated RICE protocol - to give your body the space to heal.

The most relevant principle for runners: let pain guide your gradual return to activity. Not a predetermined timeline, not a fixed number of days off. The signal tells you when the load is appropriate, and the load can increase as the signal quiets.

One thing worth naming directly: NSAIDs mute the signal, not the problem. Training on anti-inflammatory medication reduces the feedback mechanism - you can push past what the tissue can handle because you've turned down the communication channel. Research shows NSAIDs slow healing in muscles, bones, and tendons. They're not a management strategy, just a band-aid.

The runners in my group runs who mention things that have been bothering them for weeks aren't ignoring their bodies. They just never had a way to make sense of what they were hearing.

What has your body been telling you that you've been waiting to go away on its own?