Podcast Episode: Triathlon Baseline Testing Weekend

Pip: Before you can train smarter, you have to admit you don't actually know where you're starting — which is a harder pill to swallow than any threshold test.

Mara: Tri Peak Athlete, LLC is doing exactly that work. Today we're covering what it means to establish a true performance baseline before the training load even begins. Let's start with the benchmarking weekend itself.

Benchmarking Performance Baselines

Mara: The central question here is deceptively simple: where is each athlete right now? Not where they think they are — where the data says they are, across swim, bike, run, strength, recovery, and readiness, all at once.

Pip: The post on the Benchmark Testing Weekend lays out the rationale plainly: "The goal is not to chase a personal record. The goal is to establish a repeatable baseline that we can compare against later in the program."

Mara: That distinction matters enormously. A baseline only has value if it's reproducible under consistent conditions, which is why athletes were asked to arrive rested, normally hydrated, eating familiar foods, and with all wearable tech charged and synced.

Pip: And the testing itself spans a lot of ground — run pace, heart rate, cadence, and threshold markers; swim CSS and stroke data; bike FTP and power; plus Kinvent force and asymmetry testing for neuromuscular output. That's a lot of signal to gather before a single training block begins.

Mara: What holds it together is the model the post describes: training load feeds into recovery, recovery into readiness, readiness into objective performance, and performance back into the next training demand. The baseline is the first reference point for that whole loop.

Pip: Which is where the recap post, "Benchmark Weekend Recap: Building the Baseline with Kinvent, Winback and ReadyOS," gets honest about what data alone can't do.

Mara: Right — the recap makes the point directly: "A number by itself does not coach an athlete. Heart rate needs context. Power needs context. HRV needs context." The goal is how those pieces begin telling the athlete's story, not just filling a spreadsheet.

Pip: One athlete carries more fatigue at higher power. Another reports feeling great while objective testing says otherwise. A third shows an asymmetry invisible in pace data alone. That's the whole argument for layering Kinvent, Garmin wearables, TrainingPeaks compliance data, and athlete-reported readiness together.

Mara: And Winback recovery sessions are built into the weekly structure from the start — Monday for recovery after the weekend load, Friday for preparation before it — so the integration is observable across the full training cycle, not just on test day.

Pip: The baseline isn't the finish line. It's the first question mark the program is designed to answer.

Mara: What stays with me is that the whole system is built around learning the individual athlete, not averaging across a group.

Pip: Which means the most interesting data is still ahead — when training load rises and the gaps between what athletes feel and what the numbers show start to widen.