Tom: 47W FTP gain in 12 weeks

This rider is 52, about 3 years into cycling. And for the last 12 weeks, he averaged roughly 7 to 8 hours per week. His modeled FTP went from 220 watts to 267 watts. That's 47 watts, about 21%. If you train consistently, you do events, and you feel like you're not improving as fast as you should, I'm going to show you what a realistic training week can do. And I'm going to crack open the block and show you what those 8 hours actually looked like and why it worked. And stick around because at the end I'm going to give you the exact weekly template so you can copy this 8hour structure. First I want to show you the block at a high level because the story is in the weeks. What stands out here is not perfection. It's consistency. There's green everywhere. The weeks stick together. There aren't big gaps from one hard day turning into three dead days. That's the first reason the line moved. Okay. Next, I'll show you what 8 hours actually was because this is where people get misled. An 8-hour week can be junk or it can be targeted. And this was simple. Three buckets. Bucket one, very easy aerobic volume. Bucket two, one to two focused sessions. And bucket three, a long ride that builds durability. No magic bullets, just a repeatable pattern. So, let's break that down. Bucket one, easy volume. Most of the hours were steady and repeatable indoors. And that can look boring, but that's kind of the point. This is what builds the engine and lowers the cost of riding hard later. And it's what stops the quality days from turning into survival days. A lot of riders who feel stuck spend too much time in the middle. Medium hard rides that feel productive, but they slowly accumulate fatigue and they ruin the next key session. Here, the easy rides stayed easy enough that the hard days actually worked. And a quick reset. I am not going to walk you through every single session in this block. I've done that elsewhere. What's more important here is that the thing that made these 8 hours actually work and its agency. You'll see it in two places, the focused sessions and the end of the week durability ride. In the focused sessions, it shows up as what I call adaptive training. And just to be clear, when I say adaptive, I don't mean the plan magically changes itself. I mean the rider has permission and a clear rule for deciding how the session ends on the day. There's the same intent, the same target range, but the endpoint adapts to what's happening in the work, not what was typed into the calendar. Bucket two, focused sessions done with control. This is where most plans look neat on paper and have predictable progressions like 3x 10, 2x 20, 4x 8, but the stimulus isn't the set in the program. It's what actually happens while you're doing it. And at threshold or tempo, fixed durations can be arbitrary because time to exhaustion varies between riders and it changes as you train. So instead of asking, did I hit the time? We ask one question. Am I still in control? Meaning, is power stable? Is cadence stable? Is the effort starting to get expensive for the same output? If control is holding, you can extend a little. If control breaks, you stop or downshift. And that's it. Let me show you the clearest example of this from this block. Here's the workout written neatly on paper. And here's the moment the plan would normally end the work. At this point, the timer says done. But the signal says it's still clean. Power is steady. Cadence is holding. So, we don't stop just because the clock beeped. We let it run until the signal actually changes. And this is where the interval ended. Not because it hurt more, but because holding the same output started to cost more. The work gets less stable and you're about to lose repeatability. So, a quick reset because this gets misunderstood. This isn't go longer to be tough. It's finish the work while you still can and you're writing clean. And this only showed up once or twice in the whole block. And that's normal. It's a tool you use when the signal is clear, not a gimmick you force every week. And bucket three, the long ride and the durability dial. Now, let's get to the long ride. This is where a lot of riders either build durability or they keep fading late, even if their fitness is decent. But the long ride has a risk. If you overcook it, you don't just ruin that ride, you can ruin the entire next week. So, we use a week level decision rule. The long ride has structure, but the rider decides the cost based on what the week has felt like. Instead of hit the exact power no matter what, the question is, given the fatigue that I'm carrying right now, what's the hardest ride I can do that I can still recover from? Some weeks you get steady endurance with a strong finish. Some weeks you get a bit of tempo. On a heavy week, you keep it controlled and you finished feeling like you could have done it again tomorrow. That's not soft. It's smart. It's what keeps the next week intact. Now, I want to show you the proof of that. Key sessions still happened. Long rides still happened. No forced reset or light start to the next week because one day went too deep. That's the compounding effect. Now, we go back to the chart because that's what you clicked for. Over the last 12 weeks, MFTP moved from about 220 to 267. 47 watts. 21%. Does that guarantee race results? No. Your event is the proof. But this kind of change that makes improvement realistic because it's built on a block that held together. All right, the last part here. What can you copy from all of this? Here's what an 8hour week should look like for most serious cyclists. Most of it is easy enough and that doesn't steal from key days. One to two focus sessions where you bank quality minutes, not hero moments. One long ride every week, but you choose the cost so next week still happens. If you want a simple template, do two to three easy rides, 45 to 90 minutes. One threshold or tempo session where the goal is control and accumulated minutes. One harder day if you can recover or another focused session. One long ride, two and a half hours to four hours with the durability dial and the two decision rules. Inside sessions, the duration sets the shape. The signal decides the end point. End of the week, the ride has structure, but you decide the cost. If you get those two right, you bank more quality work when it matters, and you stop buying junk fatigue that wrecks the next week. And when the next week stays intact, the block compounds and that's how you make eight hours a week count. Or maybe you only have four hours, then you need a completely different approach altogether that I cover in this video. And a quick note so we don't get stuck arguing about the chart. MFTtp is a model estimate. It moves in steps when the athlete proves something in the training files. So I'm not claiming one workout caused this. I'm showing you the training pattern that made the change plausible.