He Ran a 1:36 Half. Six Weeks Later: 2:57 Marathon

He ran a 1:36 half marathon. Six weeks later: a 2:57 marathon — double the distance, nearly forty seconds per mile faster. Every race calculator says that cannot happen. It predicted 3:22. Here is why it was wrong, and why it might be wrong about your autumn marathon too. Race predictors assume two things: that your half was a maximal, tapered effort, and that the runner on marathon day is the same runner who raced it. Neither was true. His half was a checkpoint — placed mid-block, run controlled on trained legs, back in normal training the next morning — and he was improving every week on a plan built around his limiting factors, not a generic template. In this video: why calculators misread runners on an upward trajectory, the checkpoint half that reveals real marathon readiness, five athletes who broke their predictions by 19 to 55 minutes, the signs your training is attacking the right targets, and why years of running experience did not predict any of it. Book a Performance Strategy Call — 15 minutes, bring your training, and I will tell you honestly whether it is attacking the right things, and whether coaching with me is the right way to get you on that trajectory: https://coaching.allin.run/checkpoint 00:00 A 1:36 half, then a 2:57 marathon 00:27 Why every marathon prediction was wrong 02:10 A plan built on your limiting factors 03:24 The checkpoint half: pacing on tired, trained legs 04:22 Five athletes, one pattern 06:00 Signs your marathon training is working 06:56 Years of running experience didn't matter 07:45 From a 1:41 half to sub-3? 08:53 Have you been training the right way? #marathontraining #sub3marathon #runningcoach