A client texted me after a session last month, half proud and half complaining: "I can barely walk today. Best leg session in months." I wrote back that the session was fine, and that the reason he could barely walk had nothing to do with whether it was good.
Soreness is not a scoreboard. It measures novelty, not quality. A session that leaves you wrecked told you it was new, not that it worked.
The confusion is old and it feels true from the inside. You train, two days later the stairs hurt, and the ache reads like a receipt. Proof the work landed. But the ache is not measuring the thing you think it is. Soreness shows up when you give a muscle stress it is not accustomed to. New exercise, new range, new volume, a long enough layoff. The body is not sore because it grew. It is sore because it was surprised.
Look at where soreness is loudest and the story falls apart. The first session of a new block is often the sorest week of the whole program, and it is also the lightest, by design. A beginner's first month produces the most brutal DOMS of their training life, and they are lifting weights that will look like a warm-up in a year. Run a hard 10k and your legs will ache for two days, and running builds almost no muscle at all. If soreness tracked quality, none of that would happen.
Here is the part that actually costs you. The moment you treat soreness as the goal, you start programming to produce it. And the fastest way to stay sore is to keep changing the stimulus. New exercises every week. New angles. Constant variety, because familiar work stops making you sore once your body stops being surprised by it. You end up chasing the ache, and to keep chasing it you rotate away from the exact movements you were supposed to be progressing. You never run a lift long enough to add weight to it, because the version of the lift that would let you add weight is the version that stopped making you sore.
That is the trap. Soreness fades precisely when a lift is working, because working means your body adapted, and adapted means no longer surprised. The lifter who optimizes for soreness is optimizing for the one signal that a lift is still new. They mistake unfamiliarity for effectiveness, and they build a training history full of movements they did three times and abandoned.
I am not telling you soreness is meaningless. It is a signal, and it is worth reading. In week 1 of a new block, or coming back from time off, soreness tells me the stimulus is unaccustomed, which is useful information about where a client is. It tells me to be conservative with the next session's load. What it does not tell me is whether the training is good. Those are different questions, and the ache only answers the first one.
What I watch instead is boring and it is the whole job. Is the load on the bar higher than it was three weeks ago at the same RPE. Is the bar speed holding. Are the reps clean at the top of the range before I add weight. That is the scoreboard. It lives in your training log, not in the stairwell the next morning. A lifter who added five kilos to a lift over a block and never got sore once had a better block than the lifter who was wrecked every week and moved the same weight the whole time.
Soreness is a fatigue signal, and fatigue is a cost, not a product. You manage it, you do not farm it. The physiology has been written to death by now, and it all lands in the same place: DOMS tracks novelty and eccentric stress, not the growth or the strength you are actually training for. I learned it the slow way, in a stretch where I kept changing my accessory work to stay sore and watched my main lifts stall for two months while my legs ached the entire time. I was busy. I was not progressing. The soreness was all I had to tell me I had done anything, and it was lying.
This is for the lifter who leaves the gym and grades the session by how it feels the next morning. Stop. Grade it by what the bar did and what it will do next week. The session that quietly moves you forward often feels like nothing at all. The one that leaves you limping usually just means you did something your body had not seen in a while. Feeling worked and having worked are not the same, and the ache cannot tell them apart. Your training log can.