Hansons Marathon Method

The Hansons Marathon Method explained: a structured marathon plan with a 16-mile long run cap, three "something of substance" days, and cumulative fatigue instead of one huge long run.

The Short Answer

The Hansons Marathon Method is the marathon system in Hansons Marathon Method by Luke Humphrey, drawn from the coaching of Kevin and Keith Hanson and the Hansons-Brooks Distance Project. Its central idea is that you do not need to run 20 miles in training to be ready to run 26.2. Instead, you run a lot of mileage across six days a week, put hard, marathon-specific work on legs that are already tired, and let cumulative fatigue stand in for the fatigue of a very long run.[1]

The shape of the method, in the order that matters:

1. Six running days a week, with the weekly volume spread out. Mileage is higher and more evenly distributed than in most plans, with no single huge day.
2. Three "something of substance" (SOS) workouts a week. One speed or strength session, one tempo session and one long run. Everything else is easy.
3. A long run capped at 16 miles. This is the part everyone argues about.
4. Marathon-pace work that is long and frequent. The tempo runs are done at goal marathon pace, not at threshold pace, and they grow to as much as 10 miles.
5. Easy days that are really easy, because the whole structure only works if the legs are fresh enough to do the SOS days properly.

Who it suits: runners who can run six days a week, already have a base, and want a structured, highly prescriptive marathon-specific plan without ever doing a 20-miler. Who it does not suit: runners with a history of injury from high weekly volume, anyone who cannot fit six days of running, and anyone who needs the psychological reassurance of a long 20-plus mile run before race day.

Compared with the other systems in this guide, Hansons is the most marathon-specific and the most prescriptive. It uses pace names that map onto the Daniels paces, but it puts far more time at marathon pace than Daniels does, and it places its long run well below what Pfitzinger asks for.[2][3]

Where the Method Comes From

The Hansons-Brooks Distance Project is a post-collegiate training group founded by brothers Kevin and Keith Hanson in Michigan, with athletes sponsored by Brooks. The group has produced Olympic marathoners and is where the training philosophy was developed and tested on elite runners.

Luke Humphrey is a coach who trained with the group, and he wrote the book that translates the group's training into plans for amateur runners: Hansons Marathon Method: Run Your Fastest Marathon the Hansons Way (VeloPress, first published in 2012, with a later revised edition).[1] There is also a half marathon companion book from the same authors.

What this means for how much to trust it: the method comes from an elite coaching group, adapted for amateurs, and it has a large following. It has no controlled trial behind it, and no head-to-head comparison against Daniels, Pfitzinger or McMillan plans exists. The honest summary is the same as for the other systems: sound physiology, credible coaches, many people who have used it, and no proof that it beats the alternatives.

The Core Idea: Cumulative Fatigue

Most marathon plans work like this: do a long run that leaves you wrecked, recover, repeat. The long run is where you find out what the last six miles of a marathon feel like.

Hansons works differently. The argument is that the last 16 miles of the marathon are not like the last 6 miles of a 20-mile long run on fresh legs. They are like running at goal pace while carrying the fatigue of the whole race so far. The method tries to reproduce that state rather than that distance.

The mechanism it relies on:

• A long run on Sunday is run on legs that are already tired from Thursday's tempo and Friday's easy run.
• A tempo run at marathon pace on Thursday is done after Tuesday's strength session and a Wednesday rest day.
• Every quality session is done while the previous days' work is still in the legs.

So the runner is practicing marathon pace in a pre-fatigued state, many times a week, rather than once in a hard long run.

What the physiology supports and what it does not

The reasonable part. Fatigue in the later stages of a marathon does depend on more than raw distance: glycogen depletion, muscle damage and loss of running economy all matter, and running on tired legs is a real stimulus. Spreading mileage across six days also lets a runner accumulate more weekly volume than a lower-frequency plan would, and the link between weekly volume and marathon performance is well supported in coaching practice. See The Aerobic System.

The part that is a claim, not a finding. "Cumulative fatigue is a good substitute for a 20-mile run" is the method's hypothesis. It has not been tested head-to-head. The physiological adaptations that a very long run drives (glycogen storage, fat use, leg durability over three hours of impact) respond to time on your feet, and a 16-mile long run at a moderate pace is about two hours for many runners. Whether that is enough for a 3:30 marathoner is a question the runner answers by trying it, not one the book has settled.

The honest framing: Hansons and Pfitzinger are two reasonable answers to the same question, "how do I build marathon-specific endurance," with different trade-offs. One spends its fatigue budget on a few very long runs. The other spends it across the whole week.

The Three SOS Workouts

SOS stands for "something of substance." These are the only hard days of the week.

1. Speed and Strength Sessions

The plan has two phases of this day, and they change over the build.

Speed work (early weeks). Intervals at roughly 5K to 10K pace, mostly 400m to 1200m reps, with short recoveries. The goal in the book is to build a base of speed and economy before the marathon-specific work takes over. At VDOT 50, 5K pace is about 6:25/mile (19:56 for the 5K, from VDOT and Pace Tables), and I pace is 6:16/mile.

Strength work (later weeks). Longer intervals, from about a mile up to several miles, at a pace slightly faster than goal marathon pace. The book's guidance is roughly 10 seconds per mile faster than goal pace. At VDOT 50 with a goal marathon pace of 7:06/mile, that is around 6:56/mile, which sits close to Daniels' T pace of 6:51/mile. The recoveries are short jogs.

Daniels equivalent: the speed phase corresponds to I and R pace, and the strength phase corresponds to the upper end of M pace blending into T pace. The two systems agree on the intensities. They disagree on how much time to spend at marathon pace and how to arrange the week.

2. The Tempo Run

Purpose: Practice marathon pace on tired legs.

• Run at goal marathon pace, not threshold pace
• Starts short and builds up to as much as 10 miles at pace within a longer run
• Placed on Thursday in the standard weekly layout, after earlier hard work

This is the most distinctive intensity choice in the method. Most systems prescribe tempo runs at threshold pace (Daniels' T pace, Pfitzinger's lactate threshold runs). Hansons puts its main tempo work at marathon pace. See Lactate Threshold for why threshold running matters, and note that the Hansons strength days are where this system gets its threshold-adjacent work.

The consequence is that a Hansons marathoner spends many more miles at goal pace than a Daniels or Pfitzinger marathoner. That is excellent specificity. It is also a lot of marathon-pace work for a runner who has not yet found out whether the goal pace is realistic. If the goal pace is too ambitious, every tempo day is a struggle and the method punishes you for it.

3. The Long Run

The cap: 16 miles.

• The long run builds up to 16 miles and stops there
• It is run at an easy pace, but the earlier weeks and the tired legs make it harder than the same distance fresh
• Placed on Sunday, after a Thursday tempo and Friday and Saturday easy runs

The method's defense of the cap is that the long run is meant to be run on fatigued legs, so 16 miles after a hard week is a different stress from 16 miles after a rest day. The method also argues that beyond about 16 miles the injury and recovery cost starts to outweigh the benefit, and the marathon-pace tempo runs cover the specificity.

The criticism is equally simple: a first-time marathoner who has never run past 16 miles has never experienced the hours between 2:15 and 3:30 on their feet. Some runners find that the first time they see mile 20 is race day, and mile 20 is where things often go wrong.

Whichever view is right for you, the cap makes the plan easier to recover from week by week, which is a real benefit for runners who have broken down in other plans.

The Easy Days

Easy running is not optional in this system. It is what makes the SOS days possible.

• Easy runs fill the other days, typically a few miles up to 6 to 10 miles depending on the plan level
• They are run at a conversational effort. For paces, use the E range in VDOT and Pace Tables: 8:03-9:04/mile at VDOT 50
• A runner who runs easy days at moderate pace makes the next SOS day worse, and the plan degrades into six medium days

This is the same warning as The Easy/Hard Rule: the system only works if easy days are actually easy. The six-day structure raises the stakes on that, because there are fewer rest days to absorb sloppy pacing.

A Typical Week

The book provides complete plans at beginner and advanced levels. The shape of a week, rather than a copy of any particular plan, looks like this:

• Monday: Easy run
• Tuesday: SOS - speed (early) or strength (later)
• Wednesday: Rest
• Thursday: SOS - marathon-pace tempo
• Friday: Easy run
• Saturday: Easy run
• Sunday: SOS - long run (up to 16 miles)

Both plans run six days a week. The beginner plan opens with a few weeks of easy running before the SOS days start and peaks lower; the advanced plan starts the SOS work sooner and puts more miles into each day. Peak weekly mileage rises through the build, with the advanced plan reaching the same 55-70 mile range that the comparison page lists. Follow the book for the exact distances; this page does not reproduce them.

What to notice: the hard days are never adjacent. After Thursday's tempo come two easy days, then Sunday's long run, then an easy Monday. The easy runs around each SOS day are not filler; they protect the quality of the SOS day.

How Hansons Compares

See McMillan Running for that system's own details. Treat the table as an orientation, not a measurement.

For a longer treatment of choosing among systems, see Comparing Training Systems.

Who Should Use It

It is a good fit if:

• You have a base of consistent running and can already handle weekly mileage in the 40s and up
• You can run six days a week without injury
• You like a plan that tells you exactly what to do each day
• You have recovered poorly from very long runs in the past
• You want to practice marathon pace a lot, and your goal pace is realistic

It is a poor fit if:

• You are a first-time marathoner on very low mileage
• You break down under frequent running, even at easy pace. See Injury Prevention
• You cannot protect your easy days, because of work, stress or a hilly commute
• You do not trust a marathon you have not run past 16 miles for, and the doubt will cost you more than the plan gains
• Your goal pace is a guess. Hansons has little room for a wrong guess because the tempo runs are done at that pace. Set it from a recent race result using the pace tables, and read the marathon prediction cautiously. The VDOT caveat applies: a 5K does not tell you what your marathon base is.

Fueling and Recovery Under the Method

The six-day structure leaves little slack, so the basics matter more:

• Fueling. Long marathon-pace tempo runs are a good rehearsal for race-day fueling. See Fueling and Nutrition
• Sleep and recovery. The plan assumes you recover between SOS days with easy running rather than rest. If that is not true for you, the plan will feel like a slow slide. See Recovery and Adaptation
• Strength work. The book is mostly about running, not about gym work. Strength training is covered in Strength Training for Distance Runners and fits on the easy days
• Tapering and race week. See Race Day Execution

What the Evidence Does and Does Not Say

What we can say:

• Weekly volume is a strong correlate of marathon performance, and Hansons delivers a lot of it across six running days
• Practicing goal pace many times is specific preparation
• The method comes from an elite group that has used it for years

What we cannot say:

• That a 16-mile long run is as good as a 20-mile long run for a given runner. This is untested head-to-head
• That cumulative fatigue replicates the late-race state of a marathon
• That Hansons produces faster marathons than Daniels, Pfitzinger or McMillan at the same volume. No trials exist

How to decide: match the method to the runner you actually are. The best marathon plan is the one you can complete without getting hurt. For a lot of people, that is the plan with the fewest ways to fail on the days that matter.

Key Takeaways

1. The long run is capped at 16 miles and the method replaces long-run fatigue with cumulative fatigue
2. Three SOS days a week: speed or strength, a marathon-pace tempo, and the long run
3. Marathon-pace tempo runs of up to 10 miles are the signature intensity choice
4. Easy days must be easy, or the whole structure falls apart
5. It is prescriptive and high-volume, so it suits experienced runners who can run six days a week
6. Your goal pace has to be realistic, because you will run a great deal of it
7. No head-to-head evidence exists for or against the method; choose on fit, not on reputation

---

References

[1] Humphrey, L., with Hanson, K. & Hanson, K. (2012). Hansons Marathon Method: Run Your Fastest Marathon the Hansons Way. VeloPress. - The source of the SOS workouts, the 16-mile long-run cap and the cumulative fatigue approach.

[2] Pfitzinger, P., & Douglas, S. (2019). Advanced Marathoning (3rd ed.). Human Kinetics. - For comparison with the medium-long-run approach.

[3] Daniels, J. (2013). Daniels' Running Formula (3rd ed.). Human Kinetics. - For the E, M, T and I paces used in the comparisons above.

---

Next: Comparing Training Systems