From Symptom to Cause: The Diagnostic Grid for Runners
Knee pain from kilometre five, a side stitch, no progress: the diagnostic grid that traces your symptom back to load, technique, gear or training control.
Sport: Laufen · Level: Beginner
Introduction
Almost every running problem has one of four causes: your training load, your technique, your gear or the way you steer your training — and the symptom tells you which one it is. This guide flips the usual order: you are not looking for the right chapter, you are looking for your symptom.
This is not about how running is done correctly. It is about what your pain or your missing progress actually means — and which guide holds the fix. Because most runners tinker at the wrong end: new shoes, when training load is the problem.
Good news up front: a simple hip and core programme cut injuries to hips and legs among novice runners by roughly a third over 24 weeks [1] — for ten minutes twice a week.
What you need
Your training log from the last four weeks. Most answers are in the calendar, not in the body.
A phone video from the side, 20 seconds — without footage you are debating a feeling, not technique.
The mileage on your running shoes — gear is the cause you can rule out in five minutes.
Honesty about pace: can you speak a full sentence while running? That tells you more than any heart rate watch.
Two weeks of patience per hypothesis — plus a second pair of eyes.
Step by step
1. Rule out red flags first
Pinpoint bone pain, numbness, swelling or pain that stays while you walk belongs to a doctor, not in this grid.
2. Look at the calendar, not at the body
What did you change in the last two to four weeks — volume, pace, surface, shoes? The body reports overload with a delay: the trigger is almost never yesterday's run.
3. Rule out gear before you change technique
Shoe mileage, lacing, socks, clothing — in that order. A gear problem makes every technique correction useless.
4. Only then technique — and only with video
Watch one single moment in the footage: the instant your foot touches down. If it lands clearly ahead of your hip, you have found your candidate.
5. Steering and conditioning last
That leaves intensity distribution, volume, recovery, strength — the most common causes of "I am not improving", and the rarest causes of acute pain.
Common mistakes
"Ten minutes in, I get a stitch under my ribs."How to tell them apart: the timing reveals the cause. If it shows up in the first minutes of almost every run and your last meal was less than two to three hours ago, it is digestion. If it only shows up when you run faster than usual and never at comfortable pace, it is pace and breathing. Fix: walk, press on the spot, exhale hard and audibly — if it clears within one to two minutes, the diaphragm was involved. Go deeper in "Breathing Technique in Running" and "Basic Nutrition & Hydration for Beginner Runners".
"My knee speaks up from kilometre five."How to tell them apart: do not ask the knee, ask the calendar and the stairs. If it also hurts walking downstairs and after long sitting, it is not tied to your running stride — the trail points to hip and core strength. If it only shows up while running, at roughly the same kilometre every time, and is gone the moment you walk, it points to technique and load. Fix: eight weeks of a hip and core programme, twice a week — exactly that cut injuries among novice runners by roughly a third [1]. Continue in "Strength and Stability Training for Runners" and "Injury Prevention & the 10 Percent Rule".
"My shins burn after every run."How to tell them apart: point at it with one finger. If the pain spreads a hand's width along the inner shin edge and warms out during the first minutes, it is the classic overload pattern of a volume jump, hard surface and long strides. If you can point at a coin-sized spot, it gets worse during the run and hurts while walking — you stop. Fix for the diffuse pattern: halve your volume for two weeks, softer surface, shorter strides. Continue in "Fundamentals of Running Technique and Posture".
"I am completely out of breath after five minutes."How to tell them apart: speak a full sentence while running. If you cannot, your pace is the cause — not your fitness. If you can and still gasp, it is your breathing pattern: shallow chest breathing instead of deep belly breathing. The ten-minute test separates both from a harmless third option: if it gets noticeably easier after eight to ten minutes and stays that way, that was just your cardiovascular system warming up. Fix: two weeks at talking pace only, walking breaks explicitly allowed. Continue in "The Right Beginner Pace & Pacing" and "The Run-Walk Method".
"I have been running for months and I am not getting any faster."How to tell them apart: open your last ten runs and look only at the spread between the slowest and the fastest. If it is under roughly one minute per kilometre, you run everything in the same medium-hard zone — grey zone, not a talent problem. Among recreational long-distance runners the distribution was pyramidal: about 69 percent easy, 17 percent moderate, 14 percent hard [2]. If the spread is wide but your volume has been identical for months, the stimulus is missing; if every single run feels heavy, recovery is missing. Fix: two thirds of your runs almost embarrassingly slow, plus two strength sessions per week — in studies they improved running economy by 2 to 8 percent [3]: same pace, less oxygen. Continue in "The 80/20 Rule: Smart Training Control".
"The first two thirds are fine, then everything falls apart."How to tell them apart: ask how the collapse feels. If the same pace simply gets more expensive — heart rate climbs, stride shortens, head stays clear — it is your aerobic base: among performance-matched 10 km runners, those doing regular long runs needed only 3.1 percent more oxygen after 90 minutes, the others 6.0 percent [4]. If instead hunger, shakiness and tunnel vision arrive and a gel brings you back, it was energy. And if your first kilometres were faster than planned, the collapse was programmed right there. Fix: one long run per week, deliberately slow, with carbohydrates from 75 to 90 minutes onwards. Continue in "The Long Run: Building Your Aerobic Endurance Base".
"The first steps out of bed pull in my Achilles tendon."How to tell them apart: here too the answer is in the calendar, not on the shoe rack. Almost every Achilles story has a trigger two to four weeks earlier: a new shoe model with a different drop, the first hilly loop, a jump in volume. If the stiffness warms out during the first running minutes and is then gone, it is an adaptation response to exactly that change. If it persists while running, or the tendon is thickened and tender to pressure, get it looked at. Fix: undo the change from three weeks ago instead of rebuilding your technique. Continue in "Foot Strike: Heel to Forefoot" and "Finding the Perfect Running Shoe".
"After every longer run I have blisters and sore spots."How to tell them apart: the location is the diagnosis. Heel means the foot slides, so lacing is to blame, not the sock. Toe tips mean the shoe is too short or too narrow — and because your foot swells in heat and over distance, you only notice beyond a certain range. Broad areas on the ball of the foot mean moisture, so cotton socks go. Inner thighs, armpits and nipples are not a shoe question at all but a seam question. Fix: note the spot first, then change exactly the one matching thing. Continue in "The Perfect Basic Kit for Beginner Runners".
Safety notes
These symptoms are reasons to stop, not training tasks:
Pinpoint bone pain that gets worse during the run.
Swelling, redness or heat in a joint.
Numbness or tingling in foot, toes or leg.
Pain that stays while you walk normally or wakes you at night.
Chest pain, pressure on the chest, persistent dizziness or unexplained breathlessness.
What is behind these is decided by an examination, not by a video. This guide sorts training problems — it makes no diagnosis and suggests no treatment. For everything without a red flag the best advice stays unspectacular: ten minutes of hip and core work twice a week [1].
Pro tip
The most expensive mistake in troubleshooting is not the wrong hypothesis, it is three changes at once.
New shoes, shorter strides, less volume in the same week: if the knee goes quiet afterwards, you know nothing. If it gets louder, you know even less.
Change one thing, give it two weeks, write down the result. It feels agonisingly slow and is still the fastest route.
FAQ
Why does my knee hurt when I run?
Usually one of three trails: a training jump in the last two to four weeks, too little hip and core strength, or technique and shoes. You tell them apart by what happens outside of running: if it also hurts walking downstairs and after long sitting, the trail points to strength. Only while running, gone the moment you walk, means technique and load.
How do I know whether my pain is still harmless?
Three questions: can you point at a coin-sized spot with one finger? Does the pain get worse during the run instead of better? Does it stay while you walk normally? Three times yes means stop and get it checked. Diffuse, warms out, gone while walking points to a load issue instead.
What helps against a side stitch when running?
Switch to brisk walking immediately, press your fingers onto the spot and exhale hard and audibly. If the stitch clears within one to two minutes, the diaphragm was involved. For the future the timing decides: right at the start after eating means more distance from the meal, only at high pace means two weeks slower.
Key Takeaways
The trigger for your symptom is almost always two to four weeks old — check the training calendar first, not your technique.
Pain you can point at with one finger on a coin-sized spot and that gets worse during the run is not a technique issue but a doctor appointment.
Ten minutes of hip and core work twice a week cut injuries among novice runners by roughly a third [1] — the best diagnosis is the one you never need.