Brick Workout

A brick workout links two disciplines back to back in a single session, almost always cycling immediately followed by running. The name's origin is debated — some trace it to how heavy and unresponsive the legs feel running off the bike, others to the idea of stacking two sessions like laying bricks — but the mechanism it trains is well understood regardless of the etymology.

What it's actually rehearsing

A brick isn't primarily about cardiovascular fitness — an athlete already training bike and run separately is building that fitness elsewhere. What a brick specifically rehearses is the transition itself: legs recruit muscle fibers differently running immediately after cycling than running fresh, and pacing that feels sustainable on the bike can be badly miscalibrated for the run that follows. Athletes who never rehearse this tend to either run too aggressively off the bike in a race (blowing up early) or too cautiously (leaving time on the table), because the first time they feel that specific transition sensation is mid-race.

The common mistake

There's a pull toward making brick sessions long and heroic — a near-full-distance bike ride followed by a substantial run, done once, close to race day. A short run of 10–15 minutes off the bike, done regularly throughout a training block, gives far more rehearsal value than one exhausting session done rarely, because the transition sensation is what's being trained, not distance capacity. Frequency beats heroics here.

Where it fits in a plan

Bricks show up throughout a periodized build, not just near the race, and their placement interacts with the rest of the week's load — a brick stacked on top of an already-heavy day trains something different than one placed to specifically rehearse race-day pacing. That's part of why brick placement is a periodization decision, not a workout dropped in wherever there's a free slot.

Related terms