Sweet Spot Training Workouts That Actually Work

Sweet spot training — defined as 88–94% of your FTP — has become one of the most reliable tools for cyclists, triathletes, and cross-training runners who cannot afford to spend hours on the bike every week. The zone sits just below threshold: hard enough to drive real aerobic adaptation, easy enough to repeat without requiring days of recovery.

That balance is the point. Ride here consistently and you get more fitness return per hour than almost any other intensity — which is why structured sweet spot workouts have moved from niche coaching strategy to mainstream training staple.

What Is Sweet Spot Training and How Is It Defined?

Sweet spot training occupies a specific band on the power scale: 88–94% of your FTP, or Functional Threshold Power. FTP is the highest average power, in watts, you can sustain for roughly one hour. If your FTP is 250 W, your sweet spot range runs from 220 W to 235 W — hard enough to feel purposeful, manageable enough to repeat across multiple sessions.

On the effort scale, sweet spot sits above Zone 2 endurance (55–75% FTP) and below full threshold work (95–105% FTP). It bridges the tempo and threshold zones, which is precisely what makes it physiologically productive. Training here drives increased mitochondrial density, improves lactate clearance, and gradually raises your aerobic ceiling.

The zone was formalised by Hunter Allen and Andrew Coggan in Training and Racing with a Power Meter, which established the power-zone framework most coaches and platforms use today. Coach Joe Friel subsequently adopted and popularised sweet spot work in his own periodization models, cementing its place in structured endurance training.

Why Do Time-Crunched Athletes Rely on Sweet Spot Training?

The core argument is efficiency. A 60–90 minute sweet spot session delivers a near-threshold training stimulus — the kind that previously required either longer rides or more painful efforts. For athletes managing 6–10 hours per week, that matters enormously.

To understand why, consider how training stress scales across zones:

Recovery cost rises steeply above sweet spot. Threshold and VO2max sessions demand 48–72 hours of easy riding before you can train hard again. Sweet spot typically requires 24–48 hours — meaning two quality sessions fit into a standard week without digging a recovery hole.

Researcher Stephen Seiler's work on polarized training does caution against this "grey zone" for elite athletes who can log 15-plus hours weekly. His model favours a strict hard/easy split at high volumes. For amateur athletes with limited hours, though, sweet spot offers a pragmatic middle ground — enough stimulus, manageable fatigue.

That trade-off deserves honest acknowledgement: sweet spot accumulates fatigue faster than Zone 2. Dosage matters. Two sessions per week is the standard ceiling, not a starting target.

What Are the Best Sweet Spot Workouts?

The following workouts use a 250 W FTP as the reference point. Adjust every power figure to your own current FTP.

1. 2×20 min at 90% FTP (225 W), 5 min rest — The classic aerobic base builder. Total time in zone: 40 min. Approximate TSS: 70–75. Start here if you are new to structured sweet spot work.
2. 3×15 min at 92% FTP (230 W), 4 min rest — Slightly higher intensity for riders who complete 2×20 consistently. Total time in zone: 45 min. Approximate TSS: 75–80.
3. 4×10 min at 94% FTP (235 W), 3 min rest — Shorter intervals make this accessible for beginners building tolerance. Total time in zone: 40 min. Approximate TSS: 65–70.
4. 1×40 min at 88% FTP (220 W), sustained — An aerobic tempo block focused on building duration at the lower end of the range. Total time in zone: 40 min. Approximate TSS: 60–65.
5. Pyramid: 10–15–20–15–10 min at 90% FTP (225 W), 3 min rests — Adds variety and reduces monotony. Total time in zone: 70 min. Approximate TSS: 95–100.

Start at 88% FTP and increase intensity only after you can complete the full target duration consistently. To anchor these targets accurately, use the 20-minute test protocol from Coggan and Allen: ride all-out for 20 minutes, then multiply your average power by 0.95.

How Do You Fit Sweet Spot Sessions Into a Weekly Plan?

For an athlete training 8–10 hours per week, a structured week might look like this:

Joe Friel's periodization model recommends limiting sweet spot to two sessions per week during the base phase. Moving into the build phase — when threshold and VO2max work enters the picture — sweet spot drops to one session per week, with the higher-intensity efforts taking priority.

Never stack two consecutive sweet spot days. Your body needs 24–48 hours of easy riding or rest between hard efforts, and back-to-back sessions accumulate fatigue without producing proportional adaptation.

When Should You NOT Use Sweet Spot Training?

Sweet spot is not always the right tool. Four situations call for a different approach:

1. Peak race week. Fatigue from a sweet spot session takes 48–72 hours to clear. Doing one too close to race day risks arriving at the start line flat.
2. High cumulative fatigue. If your form score (TSB in the TrainingPeaks ATL/CTL model) drops below −30, sweet spot miles become junk miles. Your body cannot absorb the stimulus productively.
3. Fewer than three months of structured training. Aerobic base — built through Zone 2 — should come first. Sweet spot is more productive once the engine can support repeated quality intervals.
4. Recovery weeks. Intensity should drop, not hold at 88–94% FTP. Recovery weeks exist to let adaptation happen.

Seiler's research reinforces this: athletes logging 15-plus hours weekly may benefit more from a strict polarized approach than from sweet spot accumulation. More volume changes the equation.

One practical test worth applying: if you cannot hold target power within ±5 W for the full interval, the session is either too hard or your fatigue is too high. Stop and convert the ride to Zone 2. PlanWatts flags fatigue state and adjusts workout prescriptions accordingly, removing the guesswork for riders using the platform.