The first time you get off the bike and try to run, your legs will feel like they belong to someone else. Knees lifting on their own schedule, calves refusing instructions, a stride that feels like a fast-forwarded impression of running rather than the real thing.
That feeling has a name — every triathlete knows it as jelly legs — and it has a fix. The fix is called a brick workout, and it works faster than almost any other adaptation in endurance sport. Cyclists new to running off the bike typically run 10 to 15 percent slower than they would fresh. With consistent brick training, that gap narrows to 1 to 5 percent. Not over years. Over weeks.
This guide is for cyclists — riders adding running as cross-training, eyeing a first duathlon, or facing any event where the bike ends and the legs have to keep going. If you're training for an Ironman, the periodised version lives in the Ironman brick sessions guide; this article assumes the bike is your first sport and running is the new arrival.
What a brick actually is
A brick is two disciplines trained back-to-back with minimal rest between them — rack the bike, change shoes, start running. In practice it almost always means bike-to-run, because that's the direction that hurts. Running to cycling is a gentle handover; cycling to running is the hardest transition in multisport, which is exactly why it rewards rehearsal.
The name's origin is disputed — some say it's how your legs feel, some credit the run/bike pairing of early duathlons. The legs explanation survives because everyone who's done one immediately understands it.
Here's what matters: a brick is not simply a ride and a run that happen to share a morning. The training effect lives in the transition — those first five to ten minutes off the bike where your body renegotiates what "legs" means. A brick with a coffee and a shower in the middle is just two sessions.
Why your legs mutiny — the actual physiology
Cycling and running both use your legs, which fools people into thinking they're neighbouring movements. Mechanically, they barely share a postcode.
On the bike, your hips and knees move through a fixed, machine-defined range. Your hip never fully extends — it can't; the pedal circle won't allow it. There's no impact, no stretch-shorten cycle, no moment where a tendon loads elastically and recoils. Your cadence sits at 85–95 RPM, your torso is folded forward, and the bike bears your weight.
Running inverts nearly all of it. Full hip extension every stride. Elastic loading through the Achilles and calf. An upright trunk your core now has to stabilise. Roughly 180 foot strikes a minute, each one absorbing two to three times your body weight.
When you dismount and start running, two problems collide. The first is neuromuscular: your nervous system has spent the last hour grooving the pedalling pattern — firing your quads in a closed circle — and it keeps firing that way for several minutes after the movement changes. The muscles running depends on most, the calves and glutes and hip flexors in their running roles, are being conducted by a brain still playing the wrong sheet music. The second is circulatory: an hour of cycling distributes blood flow in a cycling-specific pattern, and the redistribution to running's demands isn't instant.
The result is the drunken-legs sensation of every first brick. It is not weakness, not poor fitness, not a sign running isn't for you. It's a switching cost. And like most switching costs, it collapses with rehearsal.
How fast it improves
This is the encouraging part. The bike-to-run transition is a skill adaptation more than a fitness adaptation, and skill adaptations are cheap.
An untrained cyclist running off the bike loses 10 to 15 percent of their normal pace — a runner who'd hold 5:30 per kilometre fresh finds themselves at 6:00–6:20 and working harder for it. Athletes who brick consistently see that penalty shrink to 1 to 5 percent. Seasoned duathletes get so close to fresh-legged pace that the transition effectively disappears.
Most of the improvement front-loads. The difference between your first brick and your fifth is dramatic; the difference between your fifteenth and your twentieth is polish. Which leads to the most important programming rule in this article.
One or two a week. That's the ceiling.
Because bricks train a skill that adapts quickly, more is not better. One brick a week is enough for most cyclists; two is the maximum worth doing. Beyond that you're not sharpening a transition — you're just accumulating running fatigue on tissue that, if you're new to running, is still months away from full adaptation.
Quality over quantity applies here more than almost anywhere in training. A focused brick — deliberate transition, controlled pace, attention on cadence and posture in those first minutes — beats three sloppy ones. Keep any other runs in your week separate from rides, on fresh legs, so tendons and bone get clean recovery. If you're still building basic run durability, do that first with the cyclist's first 5K plan and add bricks once 20 minutes of continuous running feels routine.
The 8-week brick progression for cyclists
This progression assumes you can already run 15–20 minutes continuously on fresh legs. The rides are rides you'd be doing anyway — the brick just changes what happens when you get home.
| Weeks | The ride | The run off the bike | |-------|----------|----------------------| | 1–2 | 45–60 min easy | 10 min walk/jog — 3 min jog, 1 min walk | | 3–4 | 60 min with some tempo | 15 min easy jog, continuous | | 5–6 | 75 min easy-to-steady | 20 min run at easy pace | | 7–8 | 90 min with intervals | 20–25 min steady run |
Weeks 1–2. The only goal is introducing the transition. Ride easy, then head straight out for ten minutes alternating three minutes of jogging with one minute of walking. It will feel strange. That's the point — you're paying the switching cost in its cheapest instalments.
Weeks 3–4. Add some tempo to the middle of the ride so you dismount with genuinely tired legs, then run fifteen easy minutes without walk breaks. Focus on quick, short steps — aim for a cadence around 170–180 steps per minute. Overstriding on jelly legs is how people hurt themselves.
Weeks 5–6. The ride lengthens, the run reaches twenty minutes. By now the first five minutes off the bike should feel odd rather than alien. Pace stays conversational.
Weeks 7–8. Ride ninety minutes with proper interval work, then run twenty to twenty-five minutes at a steady — not hard — effort. This is duathlon-realistic: quality bike fatigue, controlled run. If you can finish week 8 running within a few percent of your fresh pace at the same effort, the adaptation has landed.
Two details make every session in this plan work better. Set up your transition before you leave — shoes by the door, laces loosened, so the gap between disciplines stays under five minutes. And spin an easy gear at higher cadence for the final five minutes of every ride; it primes the neuromuscular switch and is the closest thing to a legal head start.
The whole progression also works indoors, and in winter that's often the better version: turbo session, shoes waiting beside the trainer, out the door or onto the treadmill inside two minutes. The trainer actually sharpens the stimulus — no freewheeling, no traffic lights, just continuous pedalling followed immediately by running. If your brick habit needs to survive a Northern European January, this is how.
Form off the bike: three cues
The first ten minutes of a brick run reward deliberate technique, because your default patterns are the ones the bike just spent an hour overwriting. Three cues cover it.
Cadence up, stride short. The classic off-the-bike error is a long, lopey stride — your hip flexors are shortened and cranky from riding, and overstriding asks them for range they don't currently have while spiking the braking load on every footfall. Aim for 170–180 steps per minute, feet landing under your hips. It will feel like mincing. It looks completely normal and it's mechanically the safest thing you can do on scrambled legs.
Run tall. You've been folded at the hips since you clipped in. Stand up out of it: eyes to the horizon, hips pushed subtly forward, like a string pulling from the crown of your head. Most of the "my legs won't extend" feeling off the bike is actually a torso still shaped like a cyclist.
Let the arms lead. Arm swing and leg cadence are neurologically coupled — drive a quick, compact arm rhythm and the legs entrain to it. When the legs feel like they belong to someone else, the arms are the part of the machine you still fully own. Use them.
None of this is permanent technique work; it's scaffolding for the transition window. By minute ten your normal running form shows up and you can stop thinking about it.
Fuelling: the sloshing stomach problem
Running jostles your gut in a way cycling never does, and the discovery usually arrives mid-brick, unpleasantly.
The rule: eat and drink in the final thirty minutes of the ride, and keep it light. A gel, a few sips — nothing solid, nothing heavy, no heroic 750ml of bottle-emptying because the ride is nearly over. You want to start the run fuelled but not full. For bricks under two hours total, you frankly don't need much; the session ends before glycogen becomes the limiter. Practise the habit anyway, because if you ever race a duathlon, in-ride fuelling discipline is the difference between running the second leg and enduring it.
Anything bigger than a light top-up — proper food, a full bottle — wants to be at least 60 to 90 minutes before the run portion. Your stomach will conduct its own experiments on the exact numbers. Run them in training, not on a start line.
Who actually needs bricks
Be honest about which of these you are, because it sets the dose.
The duathlon-curious. Run-bike-run events are the natural playground for cyclists who've added running, and the bike-to-run leg is where they're won and lost. For you, bricks are non-negotiable race prep: follow the eight weeks above, then keep one weekly brick with race-specific intensity.
The event rider with a transition. Adventure races, multisport sportives, anything where you get off the bike and immediately need functioning legs. One brick a week for the final six weeks before the event covers you.
The cross-training cyclist. You're running for bone density, time efficiency, and variety, and the brick's appeal is logistical — one shower, one time slot, two sessions. Completely valid, and for time-crunched riders often the only way a run happens at all. Once every week or two is plenty, and the weekly schedule guide shows where it slots among your other sessions.
The mistakes that undo it
Running too hard off the bike. Your perceived effort is scrambled for the first ten minutes — pace feels harder, so cyclists with good engines push to compensate, land on their normal pace anyway, and turn a skill session into an interval session. Run by effort, accept the slower kilometres early, and let the pace come back to you as the legs come online.
Making the run long. The adaptation lives in the transition. Minutes twenty-five to forty of a brick run cost real recovery and teach you almost nothing minutes one to twenty didn't.
Treating every brick as a fitness test. Chasing pace numbers on tired legs, week after week, is how a smart stimulus becomes an overuse injury. The metric that matters is the shrinking gap between your fresh pace and your off-the-bike pace at the same effort — not the absolute number.
The jelly legs go away. Faster than you'd think, with less work than you'd fear. A handful of deliberate sessions and the transition that once felt like someone swapped your legs becomes just another part of training. That's the whole trick — and now you know it.