You rode well. Power was steady, the nutrition went down, you came off the bike feeling like you had ridden within yourself. Then you start running and your legs belong to somebody else. Your cadence is choppy, your hips feel bolted shut, your breathing will not line up with your stride, and the number on your watch is thirty seconds per kilometre slower than it should be for the effort you are producing.
Most athletes read that sensation as a fitness problem and respond the obvious way: more brick sessions. That response is usually aimed at the wrong target. The bike-to-run transition is not one problem. It is four separate physiological problems that arrive at the same instant and then resolve on completely different timelines. Three of them fade within about ten minutes whether or not you have trained them. The fourth gets progressively worse the longer you run, and it is the one almost nobody trains for.
Understanding which is which changes what you do in training, and more importantly, what you do in the first kilometre of a race.
Why does running off the bike feel so much harder?
Running off the bike feels harder because four things happen at once: your nervous system is still running a cycling motor pattern, blood is redistributed for a seated posture, convective cooling collapses when your speed drops, and glycogen is already partially spent. Most of it resolves within ten minutes.
That last point is the one worth sitting with. The signature "jelly legs" sensation, the one athletes describe as running through wet sand, is largely a transient neuromuscular and vascular event with a predictable half-life. It is not a verdict on your run fitness. Athletes who understand this stop panicking in the first kilometre, which is precisely when panic does the most damage to a race.
What is actually happening in your legs in the first ten minutes?
Cycling and running are close to opposite movement problems. Cycling is a closed-chain, concentric-dominant action performed in a fixed plane, at a fixed hip angle, with your bodyweight supported by the saddle. The pedal never surprises you. There is almost no eccentric loading, almost no impact, and almost no requirement for elastic recoil.
Running is the reverse. It is an open-chain, impact-driven action built on the stretch-shortening cycle, where the tendons and fascia of the lower leg store and return energy on every ground contact. It demands eccentric control at the point of landing that cycling never asks for.
When you step off the bike after 60, 90 or 180 minutes, your motor cortex has spent that entire time reinforcing one recruitment pattern and now has to run the other. Laboratory work using kinematic capture consistently shows the same cluster of changes in the opening minutes of a transition run: shortened stride length, elevated cadence relative to pace, increased trunk forward lean, greater ground contact time, and reduced knee flexion at the swing phase. Your body is running with the mechanics of a cyclist.
There is a postural component too. Time in an aggressive position leaves the hip flexors shortened and the glutes relatively quiet, which is the exact combination that produces a low, shuffling gait and pushes you toward overstriding when you try to force pace. The hip extension range you rely on for efficient running is temporarily unavailable, so your stride is generated by reaching forward rather than driving back.
The vascular side compounds it. Cycling in a seated, forward-flexed position pools blood in the working leg musculature and lower body. Standing up and running changes venous return and the pressure gradients your cardiovascular system has been managing for hours. There is a genuine redistribution period, and it is why some athletes feel briefly light-headed in the first two minutes of T2.
The measurable consequence of all of this is a running economy penalty. Studies comparing transition running against fresh running at matched pace generally find an increased oxygen cost in the range of a few percent up to double digits in less-trained athletes, with the gap narrowing as the run progresses. You are paying more oxygen for the same speed, which is exactly what "harder for no reason" feels like from the inside.
Why does your heart rate lie to you off the bike?
Here is the trap that ruins more brick runs than anything else. In the first several minutes off the bike, perceived effort and heart rate point in opposite directions.
Your legs are screaming. Meanwhile your heart rate, if anything, may sit lower than expected because cardiac output was already elevated on the bike and the running stimulus has not yet been reflected in the number. Athletes see a heart rate that looks acceptable, conclude that they are fine, and push the pace to match the number rather than the sensation.
Then the delay closes. Heart rate climbs to where the work actually is, core temperature is already rising, and the athlete who forced the opening kilometre now has nothing left for the second half of the run. The classic race-day pattern of an aggressive first kilometre followed by a progressive collapse is very often a heart rate lag problem dressed up as a pacing problem.
The practical answer is to treat heart rate as unreliable for roughly the first eight to ten minutes off the bike and pace by cadence and breathing instead. Both respond immediately. Neither lags.
Is heat the real reason your brick run falls apart?
This is the mechanism that receives the least attention and probably deserves the most.
On the bike you are moving at 30 to 40 kilometres per hour. That airflow is doing an enormous amount of thermoregulatory work for you through convective and evaporative cooling. Your sweat evaporates efficiently, and the air moving across your skin carries heat away continuously. You are, in effect, riding inside a wind tunnel that you built yourself.
Then you rack the bike and start running at 12 to 15 kilometres per hour. Airflow drops by roughly two thirds in an instant. Metabolic heat production stays high or increases, and the primary cooling mechanism you have been relying on for hours largely disappears. Core temperature, which may have been stable through the entire bike leg, starts climbing immediately and does not stop.
This is the one penalty that does not decay. The neuromuscular disruption fades in ten minutes. The blood redistribution sorts itself out in five. Thermal load moves the other way: it is smallest at the moment you start running and largest at the finish. If your brick run feels survivable at minute five and catastrophic at minute forty, the explanation is usually thermal rather than muscular, and it compounds with the fluid deficit and the sweat rate you accumulated on the bike.
That has a direct training implication. Heat adaptation is arguably a more efficient intervention for your run split than additional brick volume, because it targets the limiter that actually grows over the course of the run rather than the one that resolves on its own.
How does bike pacing decide your run split?
More than almost anything you do in training.
The bike leg is where the glycogen is spent and the thermal debt is accumulated. Time spent above threshold power on the bike is disproportionately expensive, because the metabolic and thermal cost of surges is not linear and does not average out. Two athletes can finish a bike leg with identical normalised power and completely different run splits, depending on how variable their power was getting there.
This is why variability index matters. Riding a steady 0.7 intensity factor with a variability index near 1.0 leaves you in a fundamentally different physiological state than riding the same average power with repeated efforts into and out of Zone 4. The second athlete has burned through more carbohydrate, generated more metabolic heat, and accumulated more peripheral fatigue for the same displayed number.
The uncomfortable conclusion for most age-group triathletes is that their run problem is a bike pacing problem. If you are consistently running well below your open-run capability, the first place to look is not your run training. It is your power file.
Do more brick sessions actually fix the problem?
Partly, and less than most athletes assume.
Brick training does produce real adaptations. Repeated exposure improves the speed of the neuromuscular switch, so the mechanical disruption resolves faster and the running economy penalty shrinks. It also builds the specific muscular tolerance for running on pre-fatigued legs, and it removes the psychological shock of the sensation, which is not nothing.
But the returns arrive quickly and then flatten. Once the transition is familiar, additional brick volume mostly adds fatigue cost without adding much adaptation, and it does so at high recovery expense. Bricks are among the most demanding sessions in a triathlon week. Athletes who run two or three of them per week routinely find that their quality run sessions degrade, which costs them more than the brick sessions gain.
The defensible position is that brick training is a skill and tolerance session, not an endurance session, and should be dosed accordingly. One meaningful brick per week during a specific preparation block is enough for most age-group athletes. What matters far more is how you ride and how you execute the first kilometre.
How should you structure brick training?
Not all bricks train the same thing. Choosing the wrong format is why many athletes accumulate brick volume without improving their race performance.
| Session type | Structure | What it actually trains |
|---|---|---|
| Micro brick | 20 min bike / 10 min run, repeated 3 to 4 times | Speed of the neuromuscular switch. The highest adaptation per unit of fatigue. |
| Transition run | Full bike session, then 15 to 20 min run at race effort | First-kilometre execution and pacing discipline under realistic fatigue. |
| Race simulation | Race-distance bike at race intensity, then 30 to 45 min run | Fuelling, thermal tolerance, and pacing rehearsal. Use sparingly, treat as a race. |
| Off-the-bike strides | Easy ride, then 6 to 8 x 20 sec strides | Mechanics under mild pre-fatigue with almost no recovery cost. |
The micro brick is the most underused and, for most athletes, the most efficient. It delivers three or four transitions in a single session rather than one, which is exactly what you want if the adaptation you are chasing is the speed of the switch itself. Race simulation sessions are the opposite: high value, high cost, and appropriate perhaps two or three times in a build.
What should you actually do in the first kilometre?
This is where the physiology becomes tactics. Five things, in order.
Set cadence before you set pace. Deliberately run a high, light cadence for the first three minutes, above your normal race cadence. This does two things: it prevents the overstriding your shortened hip flexors are pushing you toward, and it forces a shorter, quicker ground contact that reengages elastic recoil faster. Do not chase pace. The pace will come to you.
Run the first kilometre by breathing, not by watch. Your breathing rhythm is an immediate and honest signal. Heart rate is not, for the reasons above, and pace is misleading because your economy is temporarily impaired.
Accept a slow first kilometre. Deliberately targeting five to ten seconds per kilometre slower than race pace for the opening kilometre costs you almost nothing and protects the remaining ninety percent of the run. Athletes who bank time in the first kilometre almost always give it back with interest.
Start cooling immediately. The first aid station is not optional. Ice at the neck and under the arms, water over the head and down the front of the tri suit. You are fighting a thermal problem that begins the second your airflow disappears, and the earlier you intervene, the flatter the core temperature curve.
Open your posture. Tall chest, relaxed shoulders, and a conscious effort to extend at the hip. Everything about the last few hours has taught your body to stay closed and forward. Undo it on purpose.
Three penalties fade. One grows.
Relative limiter load from the moment you start running. The neuromuscular and vascular penalties resolve on their own. Thermal load does not.
The bottom line
Brick runs feel bad for reasons that are real, measurable, and mostly temporary. Your nervous system needs a few minutes to change programs. Your blood needs a few minutes to redistribute. Your economy is genuinely impaired, and then it recovers. None of that is a fitness verdict, and none of it justifies the panic that ruins so many opening kilometres.
The thing that does not recover is heat. It is smallest when you start and largest when you finish, and it interacts with everything you did on the bike to get there. Which is why the two highest-leverage interventions for your run split are not more brick sessions. They are riding with less variability and arriving at T2 with a smaller thermal and fluid debt than the athlete beside you.
Train the switch. Then go fix the bike leg.
