Case Study: Master Cycling FTP Progression Applying Decision Rules

You hit your 40s or 50s, follow your training plan to the letter, watch your watts on the bike, but your FTP won't budge. You do the intervals, put in the hours, and the number stays exactly the same. In the worst-case scenario, you actually start going backwards.

The traditional answer is that you need more intensity. The biological reality is that your capacity to absorb that intensity has changed. Stagnation in a master athlete is rarely a lack of effort. It is a fatigue management problem and the absence of clear rules on what to do when the plan collides with reality.

This article details how we use data-driven decision rules to manage injuries, control load, and force threshold progression in master athletes, using real cases from our methodology.

The myth of "I'm not improving"

When an athlete reports they aren't improving, the first step is never to change the plan. The first step is to verify actual execution. We review the weekly TSS (Training Stress Score) chart. We look for the zig-zag pattern that indicates progressive overload followed by recovery.

Almost always, the athlete believes they hit every session, but the data shows gaps. Hours are missing, or the intervals aren't in the prescribed power range. If the zig-zag doesn't exist and the TSS line is flat, there is no stimulus for adaptation.

But when execution is perfect and the plateau is real, context like age, weight, and specificity comes into play. Losing 1 beat per minute of maximum heart rate per year is basic physiology. Swimming more isn't going to make you run your half marathon any faster. To move your FTP, we need to look at how mechanical stress is distributed versus metabolic stress.

Case Sylmarie: FTP progression and the 2+1 structure

Sylmarie is a 60-year-old master triathlete and 70.3 finisher. She came to us with plantar fasciitis that prevented her from running normally. On a static plan, this means stopping training altogether or training through the pain until you get a stress fracture.

We applied a strict decision rule: running pain higher than 3 out of 10 means immediate substitution. We don't diagnose; we refer to a doctor. On the training side, we redistributed the load.

We substituted the run with elliptical sessions and focused the block on the swim and the bike. We also adjusted the architecture of her training. Standard plans use 3+1 blocks (three weeks of load, one week of deload). For a 60-year-old athlete, three weeks accumulate too much systemic fatigue. We switched to a 2+1 structure.

The methodology flexed to accommodate age and injury, keeping the athlete progressing without aggravating the damaged tissue.

Case Antonio: 70/20/10 redistribution and the WKO5 model

Antonio was preparing for an Ironman when a chronic shin issue flared up. Stopping training completely months out from the race would ruin the preparation. The decision was to manage the injury without a full stop, using the bike as the primary vehicle for his aerobic engine.

We applied a drastic load redistribution: 70% bike, 20% swim, 10% run. The rule was explicit: a good swim and a strong bike split buy you all the time you need to complete the marathon, even if you have to walk parts of it.

For that 70% on the bike to be effective, we actively fed his model in WKO5. This requires max efforts at specific durations to keep the power curve accurate. Running speed was reintroduced only through explicit, negotiated-risk options, ensuring the shin could handle the impact.

Antonio completed his Ironman. The case demonstrates how a return protocol and smart redistribution maintain long-term retention in the face of the unexpected.

The decision rules behind the data

The difference between a PDF plan and real coaching isn't Tuesday's workout. It's what you do on Wednesday when Tuesday went wrong. Our core logic operates on inflexible rules.

Missed weeks and returns

If you miss a full week of training due to travel or work, the rule is clear: spend 2 to 3 days completing only the prescribed duration, stripping out all the intensity. Then, pick up the plan exactly as written.

If you miss 2 weeks or more, the protocol changes. We insert two return weeks (easy Z1-Z2 zones plus short activations). At the end, you re-test and reset your zones. Usually, the numbers drop. You accept the new reality and work from there.

Illness: Fever vs. Congestion

The presence of a fever dictates the response.

• With fever: Zero training. No exceptions. You resume when you've been fever-free for 24 hours and feel good, at a reduced intensity.
• Without fever (just congestion): Drop the intensity but keep moving. Regenerative sessions. Key sessions are downgraded to a decision based on your Rating of Perceived Exertion (RPE). If marathon-pace blocks don't feel like the usual RPE, you complete the distance in Z2. You cover the 13 to 16 miles (21 to 26 km) either way, but without forcing the nervous system.

Post-illness intervals feel disproportionately hard, and it's not worth forcing them. The physiological cost outweighs the adaptive benefit.

Compromised race week

You reach the week of your goal race and lose two days to delayed flights or work stress. The instinctive reaction is to squeeze workouts into the remaining days. The rule dictates the opposite: reframe the situation. Count the missed days as your taper.

In your remaining days, insert 30-minute activations: a warm-up, 4 sprints of 100 to 150 meters, and a short block at race pace. The work is already done; you just need to fire up the nervous system.

The boundary of athlete responsibility

Handing over these rules requires an athlete willing to read their own data. Take the case of Andrea, who ran her first marathon in 4:06 in Toronto. She was taught how to interpret her Intensity Factor (IF) and her pace-to-heart-rate decoupling (Pa:HR). This allowed her to self-manage when conditions varied.

Conversely, the system has limits. An athlete who demands a session-by-session analysis regardless of their own execution of the rules consumes disproportionate hours. In cases of workload abuse, the service is cleanly terminated. The methodology gives you the framework and the rules; the execution is still yours.

The trap of forcing the threshold (The counterargument)

The logical argument against this conservative approach is simple: if you want to improve, you have to suffer more. If your FTP is stuck at 210W, you should program blocks of 5×8 minutes at 105% until the body caves and adapts.

That argument is correct if you are 25 years old. At that age, the endocrine system absorbs the brute force and repairs muscle damage overnight.

In a master athlete, forcing intensity when systemic fatigue is high doesn't generate adaptation; it generates a two-week medical timeout. The compounding consistency of training three months at 90% of your maximum capacity is mathematically superior to training two weeks at 105% followed by an injury. Decision rules don't exist to hold you back. They exist to keep you on the playing field long enough that your threshold has no choice but to go up.