Building the Launch Pad: My System for 2026

From the Lab Series Recap

In Part 1 — FTP Isn’t a Ceiling, It’s a Launch Pad, I challenged the idea that FTP is a finish line.

It’s not a number to hold — it’s a system to launch from.

That post reframed performance as metabolic integration: the ability to surge, clear, and sustain above threshold, not just test well below it.

Then in Part 2 — The FTP Paradox: When Higher Isn’t Better, I showed what happens when we chase the wrong kind of FTP.

I learned that a “high” FTP built on glycolytic power looks impressive but fails under race stress.

The goal isn’t to make FTP bigger — it’s to make it cheaper.

That means lowering metabolic cost, improving clearance, and expanding usable power.

Now, in Part 3 — Building the Launch Pad: My System for 2026, I’m putting those lessons into practice.

This is where the theory becomes structure.

It’s how I’m applying the SMART approach — specific, measurable, achievable, relevant, and time-bound — to engineer a 400 W system that’s durable, repeatable, and race-ready for 2026.

⸻

The Next Phase

After a season built on control and precision, 2026 is about expression — taking everything I’ve built and turning it into a 400 W system.

Not 400 W on paper.

400 W that’s repeatable, raceable, and resilient.

That requires structure. Every ride this season must be specific in intent, measurable in outcome, achievable in execution, relevant to racing, and time-bound inside the calendar.

In short — it has to be SMART.

⸻

Strong Heart, Low RPM — Specific

I’m targeting stroke-volume expansion — the heart’s ability to pump more blood per beat — through long, low-cadence efforts at 240–265 W and 60–75 rpm.

Each session has a clear purpose: force the heart to adapt mechanically under steady aerobic tension.

This is the foundation that turns endurance watts into useable, fatigue-proof power.

⸻

Tempo Durability — Measurable

Tempo work ( 270–300 W ) is where I test stability.

I track progress through:

• Heart-rate drift < 5 bpm

• Lactate < 2.5 mmol/L

• Normalized ≈ average power

When those align, I know my aerobic system is holding.

This makes every ride measurable — not by vanity metrics, but by metabolic control.

⸻

Surge-and-Clear — Achievable and Relevant

Race power is chaotic. Surge-and-Clear trains control within that chaos:

30–40 s bursts at 130–150 % FTP, then 2–4 min at 90–95 % FTP.

Early reps flood the system; later ones teach it to stabilize and recover while still producing power.

It’s tough but achievable — and directly relevant to real race demands: accelerations, counters, and bridging moves.

Metabolic Profiling — Time-Bound

Testing keeps me accountable.

Each training block is scheduled with defined checkpoints:

Phase	Focus	Time Frame
Nov – Jan	Cardiac base, low-RPM strength	12 weeks
Feb – Apr	Tempo & clearance build	10 weeks
May – Jul	Race-specific Surge-and-Clear	12 weeks
Aug	400 W expression & taper	4 weeks

Each test verifies LT1, confirms LT2, and adjusts training load.

The system evolves on schedule — not by guesswork.

The SMART System in Practice

Day	Focus	SMART Tie-In
Mon	Rest / Mobility	Achievable – recovery as training
Tue	Surge & Clear	Relevant – simulates race intensity
Wed	Endurance Ride	Specific – cardiac and mitochondrial load
Thu	Low-RPM Strength	Specific + Measurable – torque & stroke volume
Fri	Tempo Durability	Measurable – drift and lactate control
Sat	Simulation Ride	Relevant + Time-bound – race rehearsal
Sun	Recovery Spin	Achievable – autonomic reset

It’s not rigid — it’s intentional.

SMART doesn’t mean perfect; it means purposeful.

From the Lab

This year isn’t about chasing more watts — it’s about chasing more meaning behind every watt.

I’ve done the unstructured work before; it built fitness, not function.

Now, each week fits inside a deliberate system that balances volume, recovery, and intent.

By August, I don’t just want to test 400 W.

I want to race it — after hours in the red, with composure and confidence.

That’s not luck.

That’s what happens when every session is SMART — Specific, Measurable, Achievable, Relevant, and Time-bound.

A Word of Caution

What I’ve outlined here is my SMART framework — built around my physiology, thresholds, and race demands.

These numbers, intensities, and progressions work because they’re anchored to my test data, fatigue patterns, and goals.

Your SMART framework might look different — and it should.

Specific, measurable, achievable, relevant, and time-bound only work when they reflect your system.

That’s the real lesson: train with intent, but always train for your own physiology, not someone else’s file.

Continue the Series

If you missed the earlier chapters of this FTP trilogy, start here:

• Part 1 — FTP Isn’t a Ceiling, It’s a Launch Pad
  Why FTP isn’t the finish line — it’s the foundation that everything above it depends on.
• Part 2 — The FTP Paradox: When Higher Isn’t Better
  How chasing a high lab number can backfire — and why lowering lactate cost made me faster.

Together with Part 3 — Building the Launch Pad: My System for 2026, these posts form the full From the Lab FTP Series — a roadmap for turning data into race-ready durability.

Fuel your next breakthrough. Don’t miss new insights, workouts, and the launch of SMART Cycling.