Does Soreness Mean Muscle Growth? What DOMS Actually Tells You

No, soreness does not mean muscle growth. Delayed-onset muscle soreness (DOMS) tells you a muscle did something unfamiliar — usually a novel or heavy eccentric load — not that it grew, and not that you trained it hard enough to grow. You can build muscle with almost no soreness, and you can be crippled for three days from a workout that produced nothing. Soreness is a signal about novelty, not a scorecard for stimulus.

I've watched this myth wreck more programs than almost any other. A lifter changes one exercise, gets demolished by soreness for two days, and concludes that movement is "better for growth." Then their tried-and-true bench press — the one actually adding muscle every month — stops making them sore, and they assume it's gone stale. Both conclusions are backwards. Let me walk through what the research actually says, why chasing the burn is a trap, and what to track instead.

Does soreness mean muscle growth?

It does not. Soreness and hypertrophy are only loosely related, and the things that reliably drive growth — mechanical tension and training close to failure — can happen with little or no DOMS at all.

The cleanest way to see this is to look at what happens over a training block. Beginners get sore from nearly everything because everything is novel. Within a few weeks the same workouts stop producing soreness — yet that's exactly when muscle is being built fastest. If soreness tracked growth, it would increase as you adapted and got stronger. It does the opposite. The soreness fades while the gains keep coming. That single observation should end the debate, but the feeling is so visceral that it doesn't, so let's look at the actual mechanisms and data.

What is DOMS, actually?

DOMS is the pain and stiffness you feel 24 to 72 hours after a workout, and it's primarily a response to unaccustomed exercise and eccentric (lengthening) loading — not a measure of how productive the session was. It peaks one to three days post-exercise and fades on its own.

Two features matter. First, novelty: do an exercise your body isn't used to and you'll get sore even if you're highly trained. Repeat that exact exercise a week later and the soreness drops dramatically — the "repeated bout effect." Your muscle adapts to resist the soreness within one or two sessions, long before any meaningful size change happens. Second, the eccentric bias: lowering a weight under control produces far more soreness than lifting it, because lengthening contractions distribute force over fewer, more stressed fibers.

Here's the part most people don't know. For decades DOMS was assumed to be torn muscle fibers healing. The more careful work points elsewhere. A 2021 review by Wilke and Behringer argued DOMS likely "originates in the muscle-associated connective tissue rather than in the muscle itself" — the fascia, not the contractile tissue you're trying to grow. They went as far as proposing the name "delayed onset soft tissue stiffness." If a big chunk of what you feel is irritated connective tissue, using it to gauge muscle stimulus is measuring the wrong thing entirely.

Does soreness mean muscle damage?

Not reliably. Even as a marker of muscle damage — never mind growth — soreness is a poor proxy. How sore you feel does not track how much actual tissue damage occurred.

Researchers measure muscle damage with things like creatine kinase (a protein that leaks into the blood when fibers are disrupted), loss of force, and reduced range of motion. Soreness correlates weakly with all of them. The Wilke and Behringer review noted that "pain experienced upon movement and palpation did not correlate with plasma creatine kinase." You can have high soreness with modest damage, or serious damage with surprisingly little soreness. The pain dial and the damage dial are not wired together. So when someone says "I was so sore, I must have really worked it," they've stacked two unreliable inferences: that soreness predicts damage (it largely doesn't) and that damage predicts growth (it doesn't either, which is next).

What does the evidence say about damage and hypertrophy?

The strongest evidence says muscle damage is not the driver of growth — and may even be a side effect that the body learns to minimize. The most-cited demonstration comes from Damas and colleagues.

In a 2016 study published in The Journal of Physiology, Damas et al. tracked young men through 10 weeks of resistance training with muscle biopsies at week 1, week 3, and week 10. Early on, muscle damage was at its highest — and so was the spike in muscle protein synthesis. But that early protein synthesis didn't predict who grew. The authors described the initial response as "repair-oriented": the body was patching up damage, not building new muscle. Only later, after week 3, once the damage had been attenuated, did protein synthesis actually correlate with fiber hypertrophy (r ≈ 0.9 by week 10). Their blunt summary: "muscle damage does not have a role in skeletal muscle hypertrophic responses during prolonged RT."

Read that again. More damage did not mean more growth. The growth happened after the body got better at avoiding damage — which, not coincidentally, is the same window where soreness fades. This lines up with a broader body of work showing protocols that cause little muscle damage produce hypertrophy comparable to ones that cause a lot. Damage may accompany growth early on; it does not cause it. And since soreness is itself a bad proxy for damage, soreness is two steps removed from the thing you care about.

Why does chasing soreness backfire?

Because optimizing for soreness pushes you toward novelty, excessive eccentric loading, and recovery debt — none of which are the same as effective training. You end up engineering pain instead of stimulus.

If your goal is to be sore, the fastest route is to constantly change exercises (novelty), add huge stretched-position eccentrics, or do something silly like a leg day after months off. All of that produces spectacular DOMS and very little advantage — and the constant exercise-swapping actively prevents the progressive overload that builds muscle, because you can never load a movement you just started. Meanwhile, real soreness has a cost: it can reduce force output and the activation of the sore muscle in your next session, so the soreness you chased on Monday can quietly tax Thursday. Confusing soreness with effort also feeds junk volume — extra sets and exotic exercises added to "feel it more" that pile on fatigue without adding stimulus. The muscle groups that grow perfectly well with little soreness (delts and arms barely get sore for many lifters) get neglected, while the ones that scream (quads, hamstrings) get over-prioritized for the wrong reason.

What should you track instead of soreness?

Track your proximity to failure — how close each set comes to the point where you couldn't do another clean rep — because that, not soreness, is what's actually tied to growth. The good news is that proximity to failure leaves a measurable fingerprint that soreness doesn't: your reps slow down.

As a set approaches failure, every rep gets slower even when you're trying to move the bar as fast as you can. That velocity decay is graded and predictable. In a 2023 analysis in Sports Medicine - Open, Refalo and colleagues found bar velocity dropped about 25% by the time lifters hit true failure, versus roughly 13% when they stopped one rep short and about 8% when they stopped three reps short. Soreness can't tell those three sets apart — they might all feel "hard," and none might make you sore the next day. Velocity loss can. It's a real-time readout of effort while the set is happening, instead of a confusing pain signal a day and a half too late.

Here's a quick comparison of what each signal actually tells you:

How do you actually use this in the gym this week?

Stop scoring workouts by next-day soreness and start scoring them by how close each working set came to failure. Here's a concrete way to do it:

1. Pick a hard set target. For most hypertrophy work, aim to stop with about 1–2 reps in reserve. Reaching true failure occasionally is fine; living there isn't required. See how close to failure should you train for the nuance.
2. Watch the last two reps of each set. If the final rep moved at clearly slower speed than your early reps and your form held, you were genuinely close to failure. If the last rep looked identical to the first, you had reps left.
3. Calibrate your RIR honestly. Most lifters call "2 reps left" when it's really four or five. Periodically take a set to actual failure to recalibrate what your real ceiling feels like — your sense of effort is trainable. See how to calibrate your RIR.
4. Progress the same movements. Keep your exercises stable enough to add weight or reps over time. Constant novelty buys soreness, not gains.
5. Use soreness only as a recovery flag. Severe, lasting soreness means back off that muscle, not that you nailed it. Mild, fading soreness is neutral — neither a gold star nor a problem.

Where does Riven fit in?

Velocity loss is the one failure cue you can actually measure without lab gear, and that's exactly what Riven does: it's an iOS and Apple Watch app that reads your wrist motion (the watch's 100 Hz accelerometer and gyroscope) plus heart rate, measures how much your reps slow down across a set, and turns that into a 0–100 proximity-to-failure score per muscle group, in real time. It auto-detects your sets and counts reps from the wrist, so you're not fiddling with a phone. The whole point is to replace the unreliable scorecard — soreness, or "felt hard" — with an objective second opinion that beats guessing.

I'll be straight about the limits, because they matter. The wrist signal is a proxy: it reads roughly half the velocity-loss magnitude of a dedicated barbell linear position transducer at the same physiological fatigue, so it's directional, not lab-grade. And velocity is complementary to feel, not a universal cutoff — across nearly 3,000 measurements in a 2025 study by Paulsen and colleagues, lifting velocity explained only about 30% of the variance in perceived reps in reserve, and the relationship shifted with exercise, load, and set number. Heart rate is supporting context, never a standalone failure signal. So Riven isn't telling you a cosmic truth about your muscle — it's giving you a measurable, consistent reading of rep slowdown, which is a far better basis for decisions than waiting to see if you're sore tomorrow. If you want the deeper logic on why slowdown is the tell, see why your reps slow down at the end of a set.

FAQ

If I'm not sore, did I waste my workout?

No. Lack of soreness is normal and expected once your body adapts to an exercise — that's the repeated bout effect, and it happens fastest right when you're growing well. Judge the session by whether your working sets got close to failure (reps slowing, form holding), not by next-day pain.

Does more soreness mean I trained harder?

Not necessarily. Soreness mostly reflects how novel or eccentric-heavy the workout was, not how much effective stimulus you delivered. You can produce brutal soreness with a fresh exercise that does little, and minimal soreness with a productive, familiar one taken near failure.

Should I train a muscle that's still sore?

Use soreness as a recovery flag, not a badge. Mild, fading soreness is fine to train through. Severe soreness can reduce the muscle's force and activation in your next session, so it's worth waiting or training something else — see muscle failure vs fatigue for how to tell real readiness from leftover discomfort.

Is muscle damage necessary for growth?

The best evidence says no. Damas et al. (2016) found early muscle damage didn't predict who grew, and that growth tracked protein synthesis only after damage was attenuated. Damage often comes along for the ride, but it isn't the cause — mechanical tension and effortful sets are.

Can a watch really tell me how hard I trained better than soreness can?

It can give you something soreness can't: a real-time, in-set reading. Riven measures rep slowdown from your Apple Watch and scores proximity to failure live. The honest caveat is that the wrist signal is a proxy — roughly half the magnitude of a barbell sensor — and velocity only partly explains perceived effort. It's an objective second opinion that beats guessing, not a lab instrument.

Sources

• Damas, F. et al. (2016), Resistance training-induced changes in integrated myofibrillar protein synthesis are related to hypertrophy only after attenuation of muscle damage, The Journal of Physiology — https://pmc.ncbi.nlm.nih.gov/articles/PMC5023708/
• Wilke, J. & Behringer, M. (2021), Is "Delayed Onset Muscle Soreness" a False Friend? The Potential Implication of the Fascial Connective Tissue in Post-Exercise Discomfort, International Journal of Molecular Sciences — https://pmc.ncbi.nlm.nih.gov/articles/PMC8431437/
• Refalo, M.C. et al. (2023), Influence of Resistance Training Proximity-to-Failure, Determined by Repetitions-in-Reserve, on Neuromuscular Fatigue in Resistance-Trained Males and Females, Sports Medicine - Open — https://pmc.ncbi.nlm.nih.gov/articles/PMC9908800/
• Paulsen, G. et al. (2025), Exercise type, training load, velocity loss threshold, and sets affect the relationship between lifting velocity and perceived repetitions in reserve in strength-trained individuals — https://pmc.ncbi.nlm.nih.gov/articles/PMC12360324/
• Wikipedia, Delayed onset muscle soreness — https://en.wikipedia.org/wiki/Delayed_onset_muscle_soreness