Brick Workouts: When They Actually Help and When You're Wasting Energy
Most triathletes either do too many bricks or not enough. Here's what the research says about frequency, types, and how to track whether they're actually improving your T2 run.
The Brick Workout Paradox
Brick workouts - back-to-back sessions in two disciplines, typically bike-to-run - are one of the most debated training methods in triathlon. Some coaches program them every week. Others barely use them. Most age-group triathletes fall into one of two camps: they either do bricks religiously because "that's what triathletes do," or they skip them entirely because they're hard and unpleasant.
Both approaches are wrong. The research is clear that brick training improves transition run performance. But the frequency most athletes default to is higher than what the evidence supports, and the way they execute bricks often creates more fatigue than adaptation.
Why Your Legs Feel Like Concrete Off the Bike
Before getting into programming, it helps to understand what's actually happening when you clip out and start running. That heavy, wooden-legged feeling in T2 isn't just "in your head." It's a cascade of physiological events.
Blood flow redistribution. During cycling, your body directs blood primarily to the quadriceps, hip flexors, and glutes in a pattern optimized for a pedaling motion. When you start running, demand shifts rapidly to the hamstrings, calves, and tibialis anterior. This redistribution takes time - typically 8-15 minutes for most athletes. During that window, your running muscles are working with suboptimal blood supply.
Altered muscle recruitment patterns. Cycling is concentric-dominant - your muscles shorten under load. Running demands a rapid stretch-shortening cycle with significant eccentric loading on every foot strike. Your neuromuscular system needs to switch coordination patterns, and the first 10-15 minutes of running off the bike show measurably different kinematics compared to a fresh run. Research by Millet and Vleck (2000) in Medicine and Science in Sports and Exercise found that triathletes' running economy was significantly worse immediately post-cycling compared to a standalone run.
Glycogen depletion. Depending on bike duration and intensity, your muscle glycogen stores may be substantially depleted before you start running. This primarily affects longer-course racing but plays a role even in Olympic distance events.
Neural fatigue. Hours of repetitive pedaling create central fatigue that reduces your ability to recruit muscle fibers effectively. This is distinct from peripheral muscle fatigue and explains why your legs feel "unresponsive" rather than just tired.
The good news: your body adapts to all of these transitions. The question is how much brick training you need to drive that adaptation.
What the Research Actually Shows
The evidence on brick workout effectiveness is surprisingly consistent. Brick training does improve T2 run performance. But the dose required is lower than most athletes assume.
A 2015 study by Bonacci et al. in the Journal of Science and Medicine in Sport found that triathletes who incorporated regular bike-to-run sessions showed improved running economy off the bike compared to those who trained the disciplines separately. The key finding: the adaptation was primarily neural. Athletes learned to switch recruitment patterns faster, not because their muscles changed but because their nervous system got better at the transition.
Walsh et al. (2017) in the European Journal of Applied Physiology showed that even a single brick session per week was sufficient to maintain transition-specific adaptations in trained triathletes. Adding more brick sessions didn't produce proportionally more adaptation - it just added more fatigue.
This makes physiological sense. The adaptation you're training is a skill - the ability to switch from cycling neuromuscular patterns to running patterns efficiently. Like most skills, it responds to consistent low-dose practice better than high-volume cramming.
The Diminishing Returns Curve
Here's the practical framework most coaches who work with the research land on:
One brick per week is the high-value sweet spot for most triathletes. This is enough to maintain and improve the neural adaptation without creating excessive cumulative fatigue. During base and build phases, this is all most athletes need.
Two bricks per week can be justified during race-specific phases, particularly for long-course athletes who need to practice fueling and pacing strategies in a fatigued state. The second brick should serve a specific purpose beyond "more bricks."
Three or more bricks per week is almost certainly overtraining for anyone who isn't a professional. The additional fatigue cost far outweighs the marginal adaptation benefit. You're better off using that training time for standalone quality sessions in each discipline.
The trap most age-groupers fall into: they do a hard brick on Saturday, feel accomplished, then do another on Tuesday because their training plan says so. By Thursday their run quality has cratered, and they can't figure out why their standalone tempo run felt terrible. The answer is that they're carrying bike-to-run fatigue into sessions where they should be running fresh.
Types of Bricks and When to Use Each
Not all bricks serve the same purpose. Matching the type to your training phase matters more than just doing "a brick."
Short Transition Bricks (10-20 min run off the bike)
Purpose: Neural adaptation - teaching your body to switch patterns quickly.
When: Base and early build phases. This is your bread-and-butter brick. Ride at moderate intensity for 60-90 minutes, then run 10-20 minutes at an easy to moderate pace. The run doesn't need to be hard. You're training the transition, not your run fitness. These are low-cost, high-value sessions that won't wreck your next day's training.
Race-Simulation Bricks (30-60+ min run off the bike)
Purpose: Specificity - practicing race-day pacing, fueling, and mental management in a fatigued state.
When: Late build and race-specific phases, no more than once per week. Ride at target race intensity for 75-120 minutes, then run at target race pace for 30-60 minutes. These sessions are demanding and require 48-72 hours of recovery. Don't schedule quality sessions the day before or after.
Easy Recovery Bricks (easy spin + easy jog)
Purpose: Active recovery with transition practice - keeping the neural pathway active without adding training stress.
When: Recovery weeks or the day after a hard session. A 30-40 minute easy spin followed by a 15-minute jog. Heart rate stays in zone 1-2 throughout. These sessions almost don't count as training load but still reinforce the bike-to-run pattern.
Reverse Bricks (run-to-bike)
Purpose: Different fatigue pattern, useful for athletes who also race duathlon or want to build bike strength on pre-fatigued legs.
When: Sparingly, during build phases. Running first and then cycling reverses the typical fatigue pattern. Your cycling power will be suppressed, which can be useful for teaching your body to ride efficiently when tired. Less directly applicable to triathlon T2 but valuable as a training stimulus. Some coaches use these to build mental toughness for the back half of a long bike leg.
Common Mistakes
Always going hard. The most common brick mistake is treating every brick like a race simulation. Most of your bricks should be moderate intensity with a focus on the transition itself. Save the hard efforts for race-specific phases.
Doing bricks too close to race day. A hard brick session in the final 10 days before a race creates fatigue that won't fully resolve by race morning. Your last serious brick should be 2-3 weeks out. In the final two weeks, if you do any bricks at all, keep them short and easy.
Ignoring standalone run quality. If your brick sessions are so frequent or intense that your standalone runs suffer, you've overcorrected. Your run fitness still develops primarily from running fresh. Bricks are a supplement, not a replacement.
Not tracking the right metrics. Most athletes log their bricks but don't systematically compare brick run performance to fresh run performance over time. Without that comparison, you can't tell if your transition adaptation is actually improving.
Tracking Brick Adaptation Over Time
The best way to measure whether your brick training is working: compare your T2 run pace to your fresh run pace at the same effort level over a training block.
At the start of a build phase, you might see a 30-45 second per mile pace difference between your fresh easy run and your post-bike easy run at the same heart rate. Over 8-12 weeks of consistent weekly bricks, that gap should narrow. If your fresh easy pace is 8:30/mile at 140bpm and your brick run pace at the same heart rate drops from 9:15 to 8:50 over a training block, your transition adaptation is working.
This requires consistent data collection. Log your brick runs separately from standalone runs. Note the bike duration and intensity that preceded each brick run. Compare pace at matched heart rates, not just raw pace, since cardiac drift from the bike session will inflate your heart rate.
If you're tracking with Strava or Garmin, your brick runs and standalone runs are all mixed together in your training history. Pulling them apart and comparing trends is tedious to do manually but extremely valuable.
This is one area where athletedata.health adds real value. By connecting to Strava and your wearable simultaneously, it can identify which runs followed bike sessions, compare pace-to-heart-rate relationships between brick and fresh runs, and show you whether your T2 adaptation is trending in the right direction across a training block. Your AI coach sees the pattern even when the raw data is scattered across sessions.
The Bottom Line
Brick workouts work. The neural adaptation they build is real and measurable. But more bricks is not better bricks. One quality brick per week is enough for most triathletes. Match the brick type to your training phase. Track your brick run performance against your fresh run performance to verify adaptation. And never let brick volume erode the standalone session quality that builds your actual fitness in each discipline.
The goal isn't to suffer through as many bike-to-run transitions as possible in training. The goal is to make race-day T2 feel unremarkable - just another part of the race, not a crisis. Consistent, moderate-dose brick training gets you there faster than grinding yourself down with three hard bricks a week.
Want AI coaching that tracks your brick run adaptation automatically? Start your free trial.