15 Marathon Mistakes, Backed by the Evidence

Marathon training produces a lot of confident advice, and confident advice is not the same thing as evidence. This is a curated list, not an exhaustive one: for each mistake, we name the mechanism (why it actually hurts you), the strongest study behind it, and the fix — with the strength of the evidence stated plainly rather than implied.

Part I — Training-phase mistakes

1. Spiking a single long run — not breaking "the 10% rule"

The community version of this mistake is "I ramped mileage too fast." The research says the weekly number almost everyone tracks isn't the one that matters.

A University of Groningen trial split 532 novice runners into a standard 8-week program and an "extra careful" 13-week program built around the 10% rule, and found essentially identical injury rates — 20.8% vs 20.3% (Buist et al., 2008). Spreading the same buildup over five extra weeks bought nothing measurable. What actually predicts overuse injury, in a 5,205-runner Garmin-tracked cohort spanning 588,071 sessions, is a single run that exceeds your longest run of the prior 30 days — a 10-30% spike carried a hazard-rate ratio of 1.64, and anything over 100% pushed that to 2.28, while week-to-week mileage change showed no relationship at all (Frandsen et al., BJSM 2025). A separate cohort tied progressions over 30% in two weeks to specific injuries — patellofemoral pain, IT band syndrome, shin splints (Nielsen et al., 2014).

The fix: stop budgeting weekly mileage increases and start budgeting your longest single run. Keep it at or below your longest run of the past 30 days; if you do go past it, keep the step small and don't repeat it the following week. We go deep on the exact numbers, plus a full build-by-stage plan, in Your First Marathon.

2. Running your "easy" days too hard

This is the "grey zone" trap: easy runs and long runs creeping up toward threshold pace because conversational feels too slow to be "real training."

Seiler's foundational descriptive work found elite endurance athletes across sports spend the large majority of training at low intensity, with the rest concentrated at genuinely hard efforts rather than the middle (Seiler & Kjerland, 2006). A controlled comparison found this "polarized" distribution produced larger gains than threshold-heavy, high-intensity, or high-volume approaches (Stöggl & Sperlich, Front Physiol 2014). And in a small trial of 12 sub-elite runners, the group training 81% of volume at low intensity improved their 10K time more than a group that trained more at moderate-to-high intensity (Esteve-Lanao et al., 2007). The mechanism: low-intensity volume drives mitochondrial density, capillarization, and fat oxidation at a much lower fatigue cost, which is exactly what protects your legs for the smaller dose of hard running that actually needs to be hard.

The fix: if you can't hold a conversation, you're not running easy. Reserve race-pace and faster work for structured sessions, and let your long runs build aerobic durability rather than rehearsing goal pace end to end. Training paces, explained has the zone-by-zone breakdown.

3. Skipping the weight room

Of everything on this list, strength training has the best evidence behind it — and it's the one most first-timers skip because it doesn't feel like "marathon training."

A meta-analysis of 25 randomized trials and 26,610 participants found strength training cut overall sports-injury incidence to under a third and roughly halved overuse injuries specifically (RR 0.527) (Lauersen et al., BJSM 2014). It's not just protective — a systematic review of 469 trained runners found strength work improved running economy by 2-8% without adding meaningful mass (Blagrove et al., 2018), and a separate meta-analysis put the average economy gain around 4% (Denadai et al., 2017). Mechanistically, heavy and eccentric loading increases tendon stiffness and bone density and improves hip/knee stabilization under the exact repetitive load a marathon build imposes.

The fix: 2-3 sessions a week of heavy, progressive multi-joint lifts — squat, deadlift, hip thrust, lunge, calf raise — at ≥80% 1RM for 2-4 sets of 3-6 reps, plus hip/glute stability work. A token 10-minute bodyweight circuit is a different, much weaker intervention than what the meta-analyses above tested — don't expect the same payoff from it.

4. Letting life stress not count as training load

Your body doesn't distinguish a hard tempo run from a brutal week at work — both draw from the same recovery budget, and generic plans that only track running volume miss this entirely.

The overtraining continuum is well described by joint ECSS/ACSM consensus: functional overreaching resolves in days to two weeks and can even boost fitness afterward; non-functional overreaching causes performance decrements lasting weeks; overtraining syndrome involves months of decline with mood, immune, and autonomic disruption (Meeusen et al., 2013). There's no single definitive biomarker, but a controlled 2-week overload study found nocturnal heart rate rose ~3.2% in runners who ended up overreached, versus a ~2.8% fall in those who adapted normally — and combining nocturnal HR, readiness-to-train, and pace-at-heart-rate correctly separated the two groups over 85% of the time (Nuuttila et al., 2024).

The fix: monitor subjective wellness, sleep, and resting-HR trends alongside training, and treat a bad week at work as a reason to ease off, not push through. Recovery, done right and how to raise your HRV both go into the tracking side of this.

5. Never taking a deload week

This one follows directly from #4: adaptation happens during recovery, not during the overload itself. A block that never backs off is a block that never lets supercompensation finish — fatigue just keeps stacking until something (performance, or a tendon) gives.

The fix: schedule a reduced-load week roughly every 3-4 weeks and after your biggest long runs. It's cheap insurance against both the injury risk in mistake #1 and the overreaching risk in #4.

6. Panicking — or not tapering — in the final weeks

Two failure modes live under one heading here: showing up to the start line still fatigued from a training block that never eased off, and the opposite — "taper tantrums," where sudden extra rest feels like lost fitness and triggers a last-minute cram session.

Neither is supported by the evidence. A meta-analysis of 27 studies found the optimal strategy is a roughly 2-week taper that cuts volume 41-60% while holding intensity and frequency steady, producing a reliable performance benefit (Bosquet et al., 2007) — a finding a later meta-analysis of 14 studies confirmed, while also showing VO₂max and running economy don't change during the taper (Wang et al., PLoS ONE 2023). That last point is the key: the benefit comes from shedding accumulated fatigue while fitness itself is preserved, not from continuing to train.

The fix: cut volume progressively by 40-60% over 1-3 weeks, keep some intensity and frequency, and expect a few days of "phantom" heaviness or restlessness — that's normal taper physiology, not detraining.

7. Trusting a pace calculator more than your own long runs

Riegel's formula (T₂ = T₁ × (D₂/D₁)^1.06) is the basis for most race-time predictors, including AI tools that dress it up in new packaging. It's well-calibrated up through the half-marathon — and then it systematically overshoots the marathon.

Analyzing thousands of recreational runners, one study found Riegel predicted marathon times "at least 10 minutes too fast for half of runners," while models that incorporated actual weekly training mileage cut prediction error roughly in half (mean squared error 208-228 vs. 381 for Riegel alone) (Vickers & Vertosick, 2016). The reason is structural: Riegel was fit to record performances — athletes optimally trained for every distance they raced — which describes almost no recreational marathoner, and no formula built on shorter-distance times can see the glycogen-driven "wall" coming.

The fix: use a calculator for a starting range, not a target, and weight your actual long-run fitness and weekly mileage more heavily than any single number. Feed a recent race into the Race Time Predictor — then pad the result rather than trusting it literally.

8. Skipping heat acclimatization — and not adjusting effort on a hot morning

Heat is a bigger performance tax than most training plans admit, and it hits slower runners hardest, which is backwards from what most people expect.

Across seven marathons, top male finishers slowed progressively more as heat rose — 1.7%, 2.5%, 3.3%, then 4.5% off course record across rising heat-stress quartiles — and finishers further back in the field showed a noticeably steeper heat penalty than the leaders (Ely et al., 2007). Across nearly 1.8 million finishers, the performance sweet spot sat around 4-10°C air temperature, with the exact optimum shifting by pace and sex (El Helou et al., 2012). The body also imposes an anticipatory slowdown — pace drops before core temperature actually reaches dangerous territory — so "just push through" isn't how heat-limited pacing works. Roughly 10-14 days of heat exposure (training in heat, or a post-run sauna) expands plasma volume, lowers your sweating threshold, and improves performance in the heat.

The fix: for a warm goal race, build in a 10-14 day heat block beforehand; on race morning, revise pace targets down from the start rather than trying to hold a number the weather won't permit — pace by effort using the Heart Rate Zone Calculator instead.

Part II — Race-day mistakes

9. Starting too fast

If this list has a single marquee mistake, it's this one. It is the best-documented recreational-runner error in the entire field-data literature.

Analyzing 190,228 New York City Marathon finishers, researchers found every group of runners showed a positive pace profile — everyone slows down — but the less successful runners showed far more pace variability (CV 8.3-14.4%) than the fastest ones (CV 6.6-7.8%) (Santos-Lozano et al., 2014). Across 14 US marathons and 91,929 performances, the average second-half slowdown was 15.6% for men and 11.7% for women, with men roughly three times as likely to slow by 30% or more (Deaner et al., 2015). And in an analysis of over 4 million race records, 28% of men and 17% of women "hit the wall" outright — a sustained slowdown of at least 25% over 5+ kilometers — and when it happens, the average magnitude is a brutal 37-40% below the runner's own baseline pace (Smyth, PLoS ONE 2021).

The fix: target even or slightly negative splits, deliberately hold back in the first 5-10K when adrenaline and crowd energy distort your sense of effort, and rehearse your target pace on long runs so it's familiar rather than aspirational on race day. Our sub-3 and sub-4 guides and the Race Strategy Calculator can help you build a real split plan instead of a hopeful one.

10. Racing hills by pace instead of effort

GPS pace lies to you on hills, and the lie is worse on the way down than most runners expect.

A classic study measuring the metabolic cost of running from -45% to +45% grade found cost rises steeply uphill and bottoms out around a -10% downhill grade before rising again on steeper descents (Minetti et al., 2002). But that metabolic curve understates the real danger of downhills: the eccentric muscle contractions involved in braking on a descent cause disproportionate muscle damage — elevated creatine kinase, soreness — even when the metabolic cost looks manageable. That's the mechanism behind runners who feel fine on a downhill course through halfway and fall apart in the final miles.

The fix: run hills by effort, not pace — accept a slower number going up, and resist hammering the downhills even though they feel "free." If your race has a significant net-downhill profile, train some downhill running beforehand to build eccentric tolerance.

11. Under-fueling carbohydrate — hitting the wall

Even lean runners carry enough stored fat for several marathons. The problem is the small carbohydrate tank, and it runs out on a predictable schedule if you don't refill it.

A model of marathon energetics that accounts for intensity, muscle mass, and glycogen stores found more than two-fifths of runners report hitting the wall from glycogen depletion alone (Rapoport, PLoS Comput Biol 2010). Sports-nutrition guidelines recommend 30-60 g of carbohydrate per hour for efforts of 1-2.5 hours, and up to roughly 90 g/hour for longer efforts — but only using multiple transportable carbohydrate sources (glucose plus fructose), since a single sugar source tops out oxidation around 60 g/hour (Jeukendrup, 2014).

The fix: carb-load in the 36-48 hours before the race, and start taking in carbohydrate early — 30-45 minutes in, not once you feel the crash coming — at a rate scaled to your pace and gut tolerance.

12. Getting hydration and sodium wrong

This mistake runs in two directions, and the more dangerous one is the opposite of what most runners are guarding against.

The ACSM Position Stand on fluid replacement advises avoiding dehydration beyond about 2% of body mass while also explicitly avoiding overdrinking (Sawka et al., 2007) — because exercise-associated hyponatremia (dangerously low blood sodium) is driven primarily by overconsuming hypotonic fluid combined with the body's own water-retention response, not primarily by sodium lost in sweat (Third International EAH Consensus, Hew-Butler et al., 2015). Severe cases cause cerebral edema and can be fatal — it's a genuine medical risk, not a minor inconvenience next to dehydration.

The fix: drink to thirst rather than on a rigid schedule, don't force down water at every aid station "just in case," and use sodium-containing fluids or food, especially on hot days or if you're a salty sweater. If you can, weigh yourself before and after a long run to estimate your own sweat rate rather than guessing.

13. Trying something new on race day

The oldest rule in endurance sport — "nothing new on race day" — is old because ignoring it is common and the consequences are unglamorous.

GI symptoms are genuinely common in endurance athletes: one review found 30-50% of athletes report gastrointestinal complaints during racing, and these symptoms are a leading cause of underperformance and DNF (de Oliveira, Burini & Jeukendrup, 2014). During hard exercise, blood is shunted away from the gut toward working muscle, which slows digestion — so an unfamiliar high-carbohydrate load hits a compromised system. The gut is trainable, though: a 2-week "gut-training" protocol of repeated carbohydrate exposure during exercise reduced GI symptoms and improved performance, even though the exact physiological mechanism wasn't fully pinned down in the trial (Costa et al., 2017).

The fix: rehearse your exact race-day products, timing, and volumes on long runs starting around 6 weeks out, ramping gradually from ~30 g/hour toward your race target.

Part III — Recovery mistakes

14. Skipping the recovery window

The finish line feels like the end of the story. Physiologically, it's the start of a different one that takes over a week to resolve.

A marathon produces measurable muscle damage and inflammation — creatine kinase and myoglobin rise sharply and peak around 24-48 hours post-race, staying elevated for roughly 7-10 days, alongside a transient dip in immune function. Post-exercise carbohydrate restores glycogen fastest in the first few hours, and co-ingesting protein reduces soreness and speeds functional recovery.

The fix: in the first few hours, prioritize carbohydrate, protein, fluids, and sodium; keep the first 1-2 weeks to easy or active recovery only; and gate your return to hard running on restored function and wellness — not just the absence of soreness. Recovery, done right and what your heart rate does after exercise cover the tracking signals that are more reliable than how your legs feel.

15. Mistaking a bone-stress injury for normal soreness

Most post-marathon aches are ordinary DOMS. A small minority are a bone that's losing the argument with repetitive load — and treating the second like the first is how a two-week problem becomes a two-month one.

Bone stress injuries occur when repetitive load outpaces bone's remodeling capacity. The strongest single predictor by a wide margin is a prior bone stress injury (odds ratio 4.99), with female sex a secondary risk factor (odds ratio 2.31) (Wright et al., BJSM 2015); high weekly mileage and low energy availability are widely cited as additional contributors in the broader clinical literature (Warden, Davis & Fredericson, 2014). The clinical tell that separates the two: DOMS is diffuse, roughly symmetrical, and eases within days. A bone stress injury is focal — a specific point on the bone — worsens with continued running rather than warming up and easing like tendon pain, and can progress to hurting at rest or while walking.

How solid is each claim, really?

Caveats worth keeping in mind

Nearly all of the injury and load-management evidence here is observational — large cohorts can show that runners who spike a long run get hurt more often, but not that the spike is the sole cause, since "feeling good enough to run long" and "about to break down" are hard to fully disentangle in a dataset. The pacing statistics come from genuinely massive datasets (hundreds of thousands to millions of finishers), which makes the direction of the finding very reliable, but doesn't tell you what any individual runner should have done differently on a specific day. And a handful of numbers that circulate widely in this space — a precise heat-penalty slope by finishing position, a flat "8-10°C" optimal race temperature, specific bone-stress risk factors attributed to the wrong study — didn't hold up under a direct check against the primary source and were corrected or dropped rather than repeated here.

Individual variability is large throughout: sweat rate, glycogen storage, gut tolerance, and injury susceptibility all differ substantially between runners. Treat every fix above as a strong population-level default, not a guarantee for you specifically.

The takeaway

Almost none of this is exotic. Cap your longest run instead of your weekly total, run your easy days genuinely easy, lift twice a week, hold back at the start, fuel and hydrate on a rehearsed plan instead of an improvised one, and give your body the 7-10 days it actually needs before training hard again. None of it requires a training plan overhaul — most of it is a handful of specific numbers, applied at the specific moments the evidence says they matter.

References

1. Buist I et al. (2008). No effect of a graded training program on the number of running-related injuries in novice runners: a randomized controlled trial. Am J Sports Med. 36(1):33-39.
2. Frandsen JSB et al. (2025). How much running is too much? Identifying high-risk running sessions in a 5200-person cohort study. Br J Sports Med. 59(17):1203-1210.
3. Nielsen RO et al. (2014). Excessive progression in weekly running distance and risk of running-related injuries: an association which varies according to type of injury. J Orthop Sports Phys Ther. 44(10):739-747.
4. Seiler S, Kjerland GØ (2006). Quantifying training intensity distribution in elite endurance athletes: is there evidence for an "optimal" distribution? Scand J Med Sci Sports. 16(1):49-56.
5. Stöggl T, Sperlich B (2014). Polarized training has greater impact on key endurance variables than threshold, high intensity, or high volume training. Front Physiol. 5:33.
6. Esteve-Lanao J et al. (2007). Impact of training intensity distribution on performance in endurance athletes. J Strength Cond Res. 21(3):943-949.
7. Lauersen JB, Bertelsen DM, Andersen LB (2014). The effectiveness of exercise interventions to prevent sports injuries: a systematic review and meta-analysis of randomised controlled trials. Br J Sports Med. 48(11):871-877.
8. Blagrove RC, Howatson G, Hayes PR (2018). Effects of strength training on the physiological determinants of middle- and long-distance running performance: a systematic review. Sports Med. 48(5):1117-1149.
9. Denadai BS et al. (2017). Explosive training and heavy weight training are effective for improving running economy in endurance athletes: a meta-analysis. Sports Med. 47(3):545-554.
10. Meeusen R et al. (2013). Prevention, diagnosis and treatment of the overtraining syndrome: joint consensus statement of the ECSS and ACSM. Eur J Sport Sci. 13(1):1-24.
11. Nuuttila O et al. (2024). Morning versus nocturnal heart rate and heart rate variability responses to intensified training in recreational runners. Sports Med Open. 10:118.
12. Bosquet L et al. (2007). Effects of tapering on performance: a meta-analysis. Med Sci Sports Exerc. 39(8):1358-1365.
13. Wang Z et al. (2023). Effects of tapering on performance in endurance athletes: a systematic review and meta-analysis. PLoS ONE. 18(5):e0282838.
14. Riegel PS (1981). Athletic records and human endurance. American Scientist. 69(3):285-290.
15. Vickers AJ, Vertosick EA (2016). An empirical study of race times in recreational endurance runners. BMC Sports Sci Med Rehabil. 8:26.
16. Ely MR et al. (2007). Impact of weather on marathon-running performance. Med Sci Sports Exerc. 39(3):487-493.
17. El Helou N et al. (2012). Impact of environmental parameters on marathon running performance. PLoS ONE. 7(5):e37407.
18. Santos-Lozano A et al. (2014). Influence of sex and level on marathon pacing strategy: insights from the New York City race. Int J Sports Med. 35(11):933-938.
19. Deaner RO et al. (2015). Men are more likely than women to slow in the marathon. Med Sci Sports Exerc. 47(3):607-616.
20. Smyth B (2021). Fast starters and slow finishers: a large-scale data analysis of pacing at the beginning and end of the marathon for recreational runners. PLoS ONE. 16(5):e0251513.
21. Minetti AE et al. (2002). Energy cost of walking and running at extreme uphill and downhill slopes. J Appl Physiol. 93(3):1039-1046.
22. Rapoport BI (2010). Metabolic factors limiting performance in marathon runners. PLoS Comput Biol. 6(10):e1000960.
23. Jeukendrup AE (2014). A step towards personalized sports nutrition: carbohydrate intake during exercise. Sports Med. 44(Suppl 1):S25-33.
24. Sawka MN et al. (2007). American College of Sports Medicine position stand: exercise and fluid replacement. Med Sci Sports Exerc. 39(2):377-390.
25. Hew-Butler T et al. (2015). Statement of the Third International Exercise-Associated Hyponatremia Consensus Development Conference. Clin J Sport Med. 25(4):303-320.
26. de Oliveira EP, Burini RC, Jeukendrup A (2014). Gastrointestinal complaints during exercise: prevalence, etiology, and nutritional recommendations. Sports Med. 44(Suppl 1):S79-85.
27. Costa RJS et al. (2017). Gut-training: the impact of two weeks repetitive gut-challenge during exercise on gastrointestinal status, glucose availability, fuel kinetics, and running performance. Appl Physiol Nutr Metab. 42(5):547-557.
28. Wright AA et al. (2015). Risk factors associated with bone stress injuries in physically active individuals: a systematic review and meta-analysis. Br J Sports Med. 49(23):1517-1523.
29. Warden SJ, Davis IS, Fredericson M (2014). Management and prevention of bone stress injuries in long-distance runners. J Orthop Sports Phys Ther. 44(10):749-765.
30. Marcora SM, Staiano W, Manning V (2009). Mental fatigue impairs physical performance in humans. J Appl Physiol. 106(3):857-864.
31. Van Cutsem J et al. (2017). The effects of mental fatigue on physical performance: a systematic review. Sports Med. 47(8):1569-1588.

This article is for general education and isn't medical advice. If you're new to distance running, returning from injury, or managing a health condition, clear a marathon build-up with your clinician before you increase volume or intensity.