Key Sessions Training Method Explained

← All philosophies

Your weekly hours9h

Fits your week. Coherent from 4 to 16 hours a week.

Where the time goes

Compare with

By time. Dixon publishes no percentage; his unit is a session count — 2–3 key sessions of 6–7 weekly.

A representative week

Show the week for

Across all three sports.

Mon

Strength + short run30 min whole-body strength, then 20 min easy run straight off it. Frequency, not load.

Tue

Bike intervals (key)60 min: 12 min build to 180 W, 6 × 3 min at 275–295 W off 3 min easy, 12 min easy.

Brick run15 min off the bike at 5:15–5:30/km. Easy means easy.

Wed

Swim, aerobic40 min technique and steady swimming — or nothing, if the week is under pressure.

Thu

Swim, sharp30 min: 10 × 100 m at 1:38/100 off 20 s rest. Short and quick, not a hard day.

StrengthSecond 20–40 min session of the week. Never stacked on a key day.

Fri

Short run25 min easy, or rest. Low stress by design — the weekend is the cluster.

Sat

Over-distance ride (key)3 h 15: mostly 150–185 W, with 2 × 20 min at 200–210 W in the back half.

Run off the bike15 min easy. Skill and frequency only.

Sun

Bike into the run45 min steady, straight into the run — deliberately on tired legs.

Simulator run (key)55 min: 5 min ramp, 5 min above race effort, 3 min easy, then 8, 10 and 12 min just above goal race effort off 3 min easy, 6 min easy.

What Tuesday looks like

60 minutes on the bike, and it is one of your two or three sessions that matter this week. 12 min easy building to 180 W, then 6 × 3 min at 275–295 W (110–118% FTP) with 3 min spinning easy at 130–150 W after each, then 12 min easy to finish. Rack the bike and run 15 min straight off it at genuinely easy effort — around 5:15–5:30/km, nowhere near race pace; the run is there to add frequency, not load. Then Wednesday is easy or nothing. If Wednesday quietly becomes a third quality day, you no longer have key sessions, you have five moderately hard ones.

Signature sessions

MIDWEEK BIKE (key). 60–75 min indoors. The staple hard day: 6 × 3 min at 110–118% FTP off 3 min easy, or 4 × 6 min at 100–105% FTP off 3 min. Finish with 10–15 min run off the bike at easy effort.

OVER-DISTANCE RIDE (key). 3–4 h, most of it at 150–185 W (60–74% FTP) for a 250 W athlete, with 2–3 × 20 min at goal 70.3 power (200–210 W) in the back half. This appears two, three or four times across a build, roughly every third or fourth week — not every weekend.

ACTIVATION RUN (key, off the bike, 25 min). 3 min easy running, then 10 × (20 s very fast / 40 s easy) for 10 min, then 10 min at race effort, then 2 min easy to finish. Short, sharp, cheap.

SIMULATOR RUN (key, off the bike, up to 60 min). Typically at the weekend, off a demanding ride. 5 min ramping up, 5 min above race effort, 3 min easy, then 8, 10 and 12 min just above goal race effort with 3 min easy between, then 6 min easy to finish — 55 min. This is the session that tests the run, not the long run.

LONG RUN. Anything over 90 minutes goes in no more often than every third week. Purple Patch Ironman athletes peak around 22–27 km; very few go beyond 29 km. Past two hours you are borrowing from the next two or three days, and you should plan to pay it back.

FREQUENCY RUNS (supporting). Most days carry something: 10–15 min off a bike, 15–20 min off a strength session, 20–40 min off a swim. Volume comes from how often you run, not how far, and none of it is written above easy.

SWIM. For a time-starved athlete, two 30-minute swims that are short, hard and interval-based beat one long aerobic session — e.g. 10 × 100 m at 1:38/100 (CSS minus 2 s) off 20 s rest, or 16 × 50 m at 47–48 s off 20 s.

STRENGTH. Two whole-body sessions of 20–40 min every week, year round, plus 5–10 minute bouts of stability and mobility. Heavier load out of season; in season the same two sessions shift to coordination, plyometric and tissue-health work. Dixon cites a 4–8% running-economy gain as the reason it is not optional.

Who it suits

Working professionals and parents with 6–16 hours a week and a 70.3 or Ironman on the calendar — this is the athlete the method was designed for, not a compromise it tolerates. It suits anyone whose weeks are unpredictable: when two of six sessions are named as the ones that matter, a wrecked week costs you supporting work rather than the plan. It suits injury-prone runners, because capping the long run and buying aerobic development on the bike protects the run more deliberately than any other method here. It suits athletes with a history of arriving at race day sick, flat or hurt, and athletes who under-sleep or under-fuel — Dixon's four pillars give recovery and fuelling a scheduled place rather than leaving them as good intentions. And it suits athletes planning to still be doing this in ten years.

Not for you if

If you genuinely have 20 or more hours a week and the durability to use them, this will cap you: the volume ceiling that makes the method safe is also a performance ceiling, and at those hours Dixon himself says the majority of training should be low intensity. If you are a novice runner, "lean into intensity" is the wrong instruction to hand you — the principle assumes an existing aerobic base, and high-intensity running on four hours a week is how first-year triathletes acquire Achilles problems. If you want a deterministic 20-week plan you can print in January, you will fight this: it re-plans continuously against a rolling three-week cycle. If your Ironman anxiety is about the marathon, the long-run cap is hard to accept and you will be tempted to quietly break it. If you have no access to strength training at all, two of the four pillars are missing. And if you plan by CTL ramp and TSS targets, this method does not think in those terms.

In a triathlon week

This is the one method here built around the three-sport time problem rather than around physiology, and it is why counting days beats counting minutes: two key sessions means two hard days, whatever sports they happen to sit in. Percentages cannot referee a hard bike, a hard run and a hard swim against each other; a session count can.

There is no published Purple Patch swim/bike/run split, and inventing one misrepresents the method. The allocation falls out of which key sessions you chose, your race, and which slots your week actually offers.

The bike is the aerobic engine and is deliberately used as a substitute for run volume — run volume carries the highest injury cost in triathlon, so aerobic development is bought on the bike and the run is protected by capping duration and raising frequency. Dixon's stated reasoning: a well-trained cardiovascular system from cycling reduces the physiological cost of running.

The run accumulates through frequency and through short runs off other sessions — 10 or 15 minutes after a bike, 15 to 20 after strength, 20 to 40 after a swim. Bricks are a frequency tool, not a hero session.

The swim, for a time-starved athlete, is short and hard rather than long and aerobic: pool time is expensive, and an adult-onset swimmer gains more from technique and speed than from aerobic volume. Sami Inkinen swam twice a week for 30 minutes, hard, and won an age-group world title.

What the evidence says

SUPPORTED. Strength training improving running economy in endurance athletes is among the better-supported claims in the field; Dixon's own cited range is 4–8%, and he references an eight-week heavy-resistance trial at 5%. (The 10% figure that circulates in summaries of his work is not what he says.) Sleep as the highest-yield recovery intervention, and post-session fuelling, are both well supported. The general principle that athletes at low volume benefit from a higher intensity fraction than elites is consistent with the low-volume interval literature. That meaningful long-course performance is achievable on roughly 10 hours a week is demonstrated — Sami Inkinen averaged about 10 hours a week across his career, took the 70.3 and Kona age-group world titles and went sub-nine in Hawaii — but an existence proof is not a population claim.

CONTESTED. The long-run cap. Ninety minutes to two hours, peaking at 22–27 km, is a coaching position sitting against the widespread practice of 2.5–3 hour long runs, and no controlled trial adjudicates it. Whether bike aerobic volume genuinely substitutes for run volume in producing an Ironman marathon is plausible and partially supported by the cross-training literature, but not established. The direction of "more intensity at low volume" is supported; the optimal fraction is unknown, which is precisely why Dixon declines to publish one.

LORE. The four pillars are a communication device, not a physiological model — useful, unfalsifiable. "Two to three key sessions" is coaching convention with no empirical derivation. Two challenge weeks plus a transition week versus 3:1 versus deloading by feel: no evidence favours any of them. The 48–72 hour spacing rule attributed to Purple Patch online appears nowhere in Dixon's own material and is contradicted by his use of consecutive demanding days. Strategic walk breaks are race-craft with strong anecdote and essentially no controlled evidence. The Sunday planning ritual is behaviour design — its value is adherence, not physiology, which for a real athlete is not a lesser thing.

How it goes wrong

The most common misreading is "train less." It is train less in total, harder in the sessions that matter, and actually recover. Cut the volume without adding the key-session intensity or the sleep and you simply get slower.

The second is the opposite failure and the one Dixon warns about hardest: hearing "lean into intensity" as licence to make everything moderately hard. His own line is that the biggest mistake a time-starved athlete makes is not doing the easy sessions easy. If all six sessions feel meaningful, you have six key sessions, and the design is gone.

Third: sneaking the long run back up. Athletes accept the framework and then run three hours anyway, for confidence. The cap is load-bearing — it is what makes the high-frequency running and the runs off the bike survivable.

Also common: laying an 80/20 ledger over a 9 h/week plan, which strips out the intensity that makes it work; treating the third week of the cycle as a rest week, when it contains a flash of high intensity and usually a weekend simulator; dropping strength in season, when what changes is the content and not the twice-weekly frequency; turning short frequency bricks into hero five-hour-ride-plus-hour-run efforts; and taking a 30-minute nap, when Dixon's ceiling is explicitly 10–15 minutes.

One thing widely attributed to this method is not his: the rule that key sessions must sit 48–72 hours apart. Purple Patch clusters demanding days on purpose — a short hard trainer session Friday, two to three hours of race-specific work Saturday, 90 minutes Sunday.

Sources: purplepatchfitness.com purplepatchfitness.com purplepatchfitness.com purplepatchfitness.com purplepatchfitness.com purplepatchfitness.com purplepatchfitness.com purplepatchfitness.com purplepatchfitness.com purplepatchfitness.com purplepatchfitness.com purplepatchfitness.com