Julie Derron Was Nine Minutes Down at T2. She Almost Caught the Winner Anyway.

The IRONMAN 70.3 World Championship ran in Nice on September 12, and the women's race split into two different stories by the time the field hit the run. Taylor Knibb built a lead on the bike that nobody was going to close in normal circumstances: a new bike course record of 2:32:07, over a route that includes the Col de Vence climb, on top of exiting the swim already in the lead pack (USA Triathlon). By T2 she was out front by a margin most competitors would call the race over.

Julie Derron's race, on paper, was already decided. She came off the bike 11th, more than nine minutes behind Knibb, the kind of deficit that usually turns a world championship into a solo time trial for someone else's podium spot (TRI247). Then she ran 1:13:04 for the 13.1 miles into the finish, the fastest run of the day and a new championship run record, and worked her way up to second. She was still 5:34 behind Knibb with five kilometers left. She crossed the line 4:06 back, in 4:23:30, with Alanis Siffert third in 4:25:10 (Slowtwitch).

Knibb still won, comfortably, and nothing here is an argument that Derron should have. What's worth sitting with is the shape of that run, not just its time. A run split that fast, off a bike leg that hard, from that far back, is the kind of thing commentary usually files under grit or heart. Those words describe how it looked. They don't explain how it happened.

The two responses to being nine minutes down, and neither is what she did

Picture being handed that gap at T2, in a world championship, with cameras on you. There are two obvious ways to respond, and both are wrong in the same specific way: they're reactions to the scoreboard rather than plans for the next 90 minutes.

The first is to concede quietly. Run within yourself, protect the position you're actually going to finish in, treat the podium as somebody else's business today. That's a rational response to a nine-minute deficit and most age group athletes would take it without a second thought. It also guarantees the gap never closes, because you've decided in advance that it can't.

The second is to panic in the other direction: go out at a pace the deficit demands rather than a pace your fitness can actually hold, because nine minutes over 13.1 miles feels like it needs an immediate, dramatic answer. That's the version that usually produces a blazing first three miles and a walking last three, and it tends to cost more time in the fade than it ever clawed back in the surge. It's also the version that looks the most like "trying hard" from the outside, which is exactly why it gets rewarded with praise even when it loses more than it wins.

Derron's run was neither. The gap didn't close in one dramatic move early and then hold; it kept closing, from more than nine minutes down off the bike to 5:34 down with five kilometers to go, meaning she was taking time back for essentially the entire run rather than spending a finite reserve in one place and running on fumes after. A pace that keeps producing the same result for over an hour, on legs that already have 56 miles of biking in them, isn't an act of will she found at the start line. It's a pace she already knew she could hold before she started running it.

What makes that pace available on the worst possible day

This is where the story stops being about one race and starts being about training, because "hold a hard, honest pace on fatigued legs for over an hour" is not a skill that shows up because the situation calls for it. Coaches generally read a late fade, where pace or power drops while heart rate and perceived effort keep climbing, as evidence that the limiter isn't top-end speed at all. It's durability: the ability to sustain a pace you're already fit enough to hit, once real fatigue is in the picture. The fix for a durability limiter isn't wanting it more on race day. It's the unglamorous stuff done for months beforehand, tempo work held at real duration, long sessions that don't fall apart in their final third, running done specifically when the legs are already tired rather than always fresh.

None of that is visible from a results page, which is exactly why it gets skipped over in favor of the word "grit." Grit is a story you can tell about ninety minutes. Durability is a story about the twenty weeks before it, most of which nobody was watching.

Knowing the number beats trusting the feeling

There's a second piece to this that's easy to miss: Derron's run wasn't just sustainable, it was apparently paced to a target rather than raced to a feeling, given how evenly it kept producing time back over more than an hour. That only works if you actually know your number going in. A run leg off a triathlon bike is not a fresh 13.1 miles, and the pace your legs can genuinely repeat under that fatigue is not something most people can eyeball accurately in the moment, especially with a deficit sitting in their head telling them to go faster than that.

This is part of why running gets its own threshold pace in the app rather than borrowing a number built for a bike. Threshold pace, set from an athlete's own tested or logged data, drives real pace zones the same way FTP drives power zones for cycling, so the honest, repeatable effort for a run leg is a number you can check against rather than a guess you're making under a finish clock. A number like that is only useful if you trust it more than the adrenaline telling you the deficit needs something bigger right now, and that's a harder thing to do than it sounds when you're the one nine minutes down.

The overcorrection instinct doesn't stay on race day

The instinct behind the losing version of this, go big immediately to make up lost ground, shows up constantly outside of racing too, usually after something smaller than a nine-minute deficit. Miss two sessions in a week because work got ugly, and the pull is to stack extra volume into the days that are left rather than just picking the plan back up where it is. Have a check-in come back rough and the temptation is to prove it wrong with a hard session instead of an easy one. In both cases the "make up for it now" instinct is doing the same thing the panicked runner in Nice would have done: treating a gap as something that has to be closed immediately, by force, rather than something a sound plan closes on its own schedule.

This is part of why the app's "if today won't work" guidance on a session doesn't just say skip it or push through it. It states plainly how much that particular session actually matters to the block, what missing it really costs (which is often close to nothing for a single easy day), and what the shortest version that still counts looks like. The honest answer to "I'm behind" is almost never "add more, faster." It's closer to what Derron's split actually was: keep producing the same sound effort you were already capable of, and let it add up.

An honest limitation

This is one race, read from splits and results pages rather than from Derron's own training log, and elite triathletes carry a base of fitness that doesn't map cleanly onto anyone training around a job and a life. It's also possible, and worth saying plainly, that her deficit off the bike wasn't purely tactical: a bad swim, an off day on the bike, a mechanical, or a genuine strength gap between her cycling and her running could all produce the same number at T2, and a fast run afterward doesn't tell us which one it was. What the splits do support, without needing to guess at her training, is the shape of the response: steady rather than explosive, sustained rather than front-loaded. That part is a pacing lesson regardless of what put her nine minutes behind in the first place.