The 10% Rule Is Running Lore, Not Science
The rule everyone follows has no documented origin and no research to back it up
At my run club this past weekend, fall races were on everyone's mind. Half marathons, marathons, a few trail runs and triathlons - and the inevitable conversation about training came up. Several runners were mapping out their plans, talking through how much they could add each week to get ready in time.
Most of them were planning increases that felt responsible because they were structured around the 10% rule
The 10% rule is one of those pieces of running advice that gets passed around so confidently it sounds like established science. Add no more than 10% to your weekly mileage, and you'll stay injury-free. It's simple, it's memorable, and almost every runner has heard it at some point.
The problem is that nobody knows where it came from, the research doesn't support it, and it ignores most of the variables that drive injury risk.
Nobody Knows Where It Came From
Carl Foster, director of the Human Performance Laboratory at the University of Wisconsin-La Crosse, has stated that the origin of the 10% rule is "lost in history" and that "whether it is right is undocumented."
Dr. Ron Diercks, who researched the rule directly, put it more bluntly: "nobody found out if it works or what is the basis of it." He compared its adoption in the running community to faith - people follow it because it's been repeated often enough that it feels true.
The 10% rule is primarily based in running and training lore. There’s no physiology or research to back it up. Just lore.
Even if the rule had solid research behind it, the arithmetic breaks down across the range of volumes runners actually train at.
A runner starting at 1 mile per week, following the 10% rule, would add 0.1 miles in week 2. That's not a training increase - it's a rounding error. The rule produces meaningless guidance at low volumes.
At high volumes, the opposite problem emerges. A runner doing 70 miles per week would add 7 miles in a single week - a load increase most coaches would consider aggressive. The rule only approximates something useful in a narrow middle range, which most runners pass through quickly in either direction.
The False Confidence It Provides Costs Runners Real Training Time
The 10% rule tells runners to limit weekly mileage increases to 10% or less. One metric to stay under, and you're being responsible with your training. That’s it. Simple and easy to follow.
The 10% rule feels like protection. But the problem is that mileage is one of many variables that determine training load - and for most runners, it's not even the most important one. A runner who adds tempo runs, hill repeats, and back-to-back long runs while staying within a 10% weekly mileage increase hasn't managed their load carefully. They've managed one number while everything that drives injury risk increases.
When those runners get hurt, they have no framework to explain what went wrong. They were following the rule. The rule just wasn't tracking anything that matters. So they blame themselves - their fitness, their body, their commitment - when the problem was never any of those things.
The rule does more than fail to protect runners. It takes the blame off the framework and puts it on the runner.
The Rule Measures the Wrong Thing
The intuition behind the 10% rule isn't wrong. Gradual increases are safer than sudden spikes. The problem is that load comprises more variables than weekly mileage can capture.
The musculoskeletal system adapts more slowly than the cardiovascular system. A runner's aerobic fitness can handle higher volumes long before their tendons, bones, and connective tissue have caught up with the demands placed on them. That gap is where most running injuries originate, and a percentage of weekly mileage doesn't capture it at all.
Intensity is the variable the rule misses entirely. A runner who keeps mileage flat but adds tempo runs, hill repeats, and interval sessions in the same week has increased their training load significantly. The cardiovascular demand goes up. The musculoskeletal stress goes up. The 10% rule sees none of it because the mileage number didn't change.
Daily load spikes may matter more than weekly totals. A runner who takes two rest days and then does a massive long run has spiked their single-day load dramatically - even if the weekly mileage percentage looks conservative. The distribution of load across the week matters as much as the total.
The factors that drive injury risk - training history, musculoskeletal adaptation rate, biomechanical deviations, recovery capacity, injury history, individual genetics - don't appear anywhere in a weekly mileage percentage. Two runners can follow the 10% rule identically and have completely different injury outcomes based on these variables alone.
The Research Doesn't Back It Up
In 2008, researchers at the University of Groningen split 532 runners into two groups. One followed 10% weekly mileage increases over 13 weeks. The other followed 50% increases over 8 weeks. Injury rate: 20.8% versus 20.3%. Essentially identical.
If the 10% rule were protecting the first group, the numbers would look different, but they don't.
This was followed up by a 2012 study by Nielsen et al. that found something equally inconvenient: uninjured runners increased their volume by an average of 22.1% per week - more than double what the 10% rule allows. The data shows no meaningful connection between following the 10% rule and staying injury-free.
I see a version of this play out with runners all the time. Runners who only get out once a week - sometimes within the 10% mileage guideline on paper - show up with more aches, more soreness, and more recurring issues than runners who spread their mileage across three or four shorter efforts. The weekly total looks responsible. The single-day spike is the problem.
What to Track Instead of a Percentage
The questions worth asking before you add to your training load aren't about percentages. Are you adding volume and intensity at the same time? Are you recovering between sessions? Do you have a history of specific injuries that need to be managed? What does your musculoskeletal load look like across the whole week - not just the mileage total?
Those questions don't produce a simple rule, but they produce a better picture than the one the 10% rule gives you.
The signals that tell you when you're pushing too far show up in tendons and joints before they show up in aerobic capacity. Fatigue that doesn't resolve with a normal recovery window. Soreness that's localized rather than diffuse. These are the indicators worth tracking - not whether last week's mileage was within a preset percentage of the week before.
I'm currently managing this in an Ironman build, where running, cycling, and swimming volumes and intensities across all three disciplines contribute to the total load simultaneously. There's no single number to apply a percentage to, and the load from one discipline directly affects the others' recovery capacity. The 10% rule has no useful application here - but the questions above do.
The runners at my club talking about their plans felt responsible. They were following the rule, but the rule just wasn't tracking anything that mattered.
Are you managing your training load - or just managing your mileage?