How to Run Off the Bike: Brick Run Technique for Triathletes
Why your legs feel like jelly off the bike and the exact 4-step technique fix that gets you running smoothly within 200 meters of T2.
By Lotte
Running off the bike feels awful for one specific physiological reason — your legs are pumping blood for cycling, not running, and your muscle firing pattern is completely different. This guide explains the science, the 4-step technique fix (high cadence, short strides, relaxed shoulders, controlled breathing), and how to make brick runs a strength instead of a survival exercise.
Key takeaways
- 1The 'jelly legs' feeling is real — caused by blood pooling in cycling muscles and a different muscle firing pattern
- 2Cadence is the fix: aim for 90+ steps/min in the first 500m to override the cycling rhythm
- 3Short strides + slight forward lean = smoother transition (don't try to 'open up' early)
- 4Do brick workouts weekly during 70.3/Ironman build — they're the highest-specificity session in triathlon
- 5First 1 km should feel easy — pacing comes after, not before, your legs find rhythm
In this article
- 1Quick answer: how do I stop feeling so bad in the first km?
- 2Why your legs feel like jelly (the science)
- 3The 4-step brick run technique (in detail)
- 4How to structure brick workouts in training
- 5What to wear and carry for a fast T2
- 6Common brick run mistakes (and how to fix them)
- ⚖Brick run pacing by distance
- ?Frequently asked questions
Quick answer: how do I stop feeling so bad in the first km?
The 4-step fix for the first 500 meters of every triathlon run:
- Cadence first — count to 180 in your first 60 seconds (180 footstrikes/minute). High cadence overrides the cycling rhythm fastest.
- Short strides — feel like you're running 'on top of' the ground, not stretching forward. Stride length opens up naturally after ~1 km.
- Relax shoulders and arms — drop them, shake them out for 5 seconds in the first 200 m.
- Controlled breathing — match your breath to footfalls (3 steps in, 2 steps out) to settle the nervous system.
Ignore your pace for the first km. Heart rate will be elevated regardless. Your legs will 'unlock' between 800–1500 m once the run-specific blood flow pattern kicks in.
Why your legs feel like jelly (the science)
Two things happen the moment you step off the bike:
1. Blood is in the wrong place. Cycling pumps blood primarily to the quads and glutes. Running needs blood in the calves, hamstrings, and feet too. Your cardiovascular system needs 60–90 seconds to redistribute.
2. Muscle firing pattern flips. Cycling is a smooth, circular concentric contraction. Running is impact-based eccentric loading. The neural pathway that fires your stride is essentially asleep for the first few hundred steps.
3. Your perceived effort lies. Heart rate stays elevated from the bike for ~5 minutes, so a moderate run feels like an all-out effort. This is why pacing by HR alone in early run miles is dangerous.
The solution is bike-to-run specificity — training the transition itself, not just running fresh.
The 4-step brick run technique (in detail)
Step 1: Force the cadence. Use a metronome app, music at 180 BPM, or your watch's cadence alert. Aim for 88–92 steps per minute (each foot). High cadence prevents over-striding, the #1 cause of brick run injury.
Step 2: Short, light strides. Imagine you're running over hot coals. Foot contact should be brief and directly under your hip — NOT reaching forward. Over-striding hammers your quads (which are already tight from the bike).
Step 3: Relax the upper body. Cycling tightens shoulders, neck, and lats. Drop shoulders, shake arms out at 200 m and 500 m, run with hands loose. Tense upper body wastes ~5% of your run pace.
Step 4: Pace by feel for 1 km, then check the watch. Your HR will read high; ignore it. After 1 km, glance at pace — by then your legs are running, not cycling.
For full run-pacing technique see our pacing strategy guide.
How to structure brick workouts in training
Brick = bike + run, back to back, with <5 minute transition. The goal is specificity, not exhaustion.
Beginner sprint (weeks 1–8):
- 30 min easy bike → 10 min easy run, once per week
Intermediate Olympic (weeks 1–10):
- 60 min Z2 bike + 20 min Z2 run, once per week
- One race-pace brick: 40 min bike with 3×5 min at 70.3 effort → 15 min run with 3×1 min at 5K pace
70.3 build (weeks 6–12):
- 90–120 min bike (incl. 2×20 min at race power) → 30–45 min run at 70.3 pace
- Weekly minimum: one long brick = your most important workout of the week
Ironman build:
- 4–5 hour ride → 30 min run off the bike (don't make this run too long — recovery cost is high)
Pair these with our 12-week sprint training plan, Olympic distance plan, or Ironman 70.3 plan.
What to wear and carry for a fast T2
Brick-friendly setup saves 60–90 seconds in T2 and saves your legs from extra fumbling:
- Elastic running laces (Lock Laces, Yankz) — slip-on in 3 seconds
- Race belt with number pre-attached — no fumbling with pins
- Tri socks (or no socks for sprints) — quick on, low friction
- Run cap or visor — flip on while running, not in transition
- Pre-set gels on belt or in pockets — don't reach into bags
Practice T2 as part of every brick workout. Set up a mini transition zone at home or the parking lot: rack the bike, change shoes, grab race belt, run. Three repetitions saves you 2 minutes on race day.
For full transition setup see our triathlon transition setup guide.
Common brick run mistakes (and how to fix them)
Mistake 1: Starting too fast. Heart rate is high from the bike, so 'easy' pace feels like 5K effort. Run the first km 20–30 seconds/km slower than goal pace, then settle in.
Mistake 2: Skipping bricks because they're hard. The first 5 are awful. By workout 10, the legs adapt and the feeling diminishes. Consistency is the only fix.
Mistake 3: Doing too much. Beginners try 90-min ride + 60-min run. Recovery is brutal. Keep brick run portion to 25–40% of your bike duration.
Mistake 4: Forgetting hydration. Walk for 10–20 seconds out of T2 while drinking, then start the run. A sip in T2 is worth more than 3 sips at the first aid station.
Mistake 5: Wearing race shoes for every brick. Train in your regular daily shoes, race in carbon-plated if you use them. Brick mileage in carbon shoes wears them out too fast.
Brick run pacing by distance
| Race | First km vs goal pace | Settle-in distance | Walk aid stations? |
|---|---|---|---|
| Sprint (5K) | +10 sec/km slower | 500 m | No |
| Olympic (10K) | +15–20 sec/km slower | 1 km | Optional (sip-and-go) |
| 70.3 (21.1 km) | +20–30 sec/km slower | 2 km | Yes — 10–20 s walks |
| Ironman (42.2 km) | +30–45 sec/km slower | 3 km | Yes — walk full stations |
Frequently asked questions
How long until brick runs feel easier?
Most beginners notice major improvement after 6–8 weekly brick sessions. The 'jelly legs' feeling never fully disappears, but you learn to override it with cadence and pacing.
Should I do a brick run before every race?
Yes — at minimum, a 10-min jog after your race-week practice ride. It primes your nervous system for the bike-to-run transition.
What's the longest brick I should do for a 70.3?
Most plans cap brick runs at 45–60 minutes, even off a 3-hour ride. Going longer wrecks recovery for the rest of the week without adding race-specific fitness.
Can I do a brick on a Zwift trainer + treadmill?
Yes — and indoor bricks are easier on the body (no road impact, no heat). Just keep the T2 transition realistic (2–3 minutes, not a 10-minute break).
Why do my hamstrings always cramp on brick runs?
Usually under-hydration during the bike + over-striding off the bike. Drink consistently on the bike (500 ml/hour), and force cadence > 90 in the first km.