Field results · Week 12
The Spartan Lit the Fuse. The Data Kept It Burning.
It started with a 5K Spartan four years ago — the first structured run of my life after twenty-plus years in the gym. It took several more Spartans, a lab panel, and a watch I learned to stop arguing with before the promise finally stuck. Twelve weeks into the plan, the numbers moved. Here are the receipts.
Boundary
One man’s data, honestly reported.
This is a personal field report, not a study and not a protocol prescription. Heart symptoms, abnormal heart-rate alerts, medications, cardiovascular risk, and exercise clearance belong with qualified healthcare professionals.
- Educational field notes, not medical advice.
- No clinician reviewed this page.
- Use qualified professionals for diagnosis, treatment, medication, supplement, and testing decisions.
The origin
Four Spartans, one pattern, and the year it finally broke.
Four years ago
A 5K Spartan with a friend.
My first structured run, ever. Twenty-plus years at the gym and I had always strayed from cardio — lifting was the identity, running was the thing I avoided. The race itself was not the point. The discipline was: I had to train cardio just to be comfortable out there.
The annual pattern
Train. Race. Promise. Stop.
The Spartan became an annual commitment, and so did the broken promise that followed it. Every year I said I would stick with cardio after the race. Every year I didn’t. The spark was real — but it was dim, and it took several Spartans to fully manifest.
Why it kept breaking
No data meant no evidence anything was changing.
The training broke down after every race for a boring reason: I couldn’t see the changes. Effort with no scoreboard feels optional. When the race disappeared from the calendar, the only feedback left was how I felt — and “fine” is not a training plan.
The data era
Labs, honest zones, and a weekly number.
Function Health labs gave me the why. The Garmin gave me the scoreboard — once I fixed the zones it was grading me against. Now I am fully invested in ten miles a week, not because a race demands it, but because the data finally shows me what the work is buying.
The two catalysts
Structure started the engine. Data kept it running.
Catalyst one
A structured event forced a training routine.
The Spartan got my body into the rhythm of actually training cardio instead of dabbling in it. That is what a race on the calendar does: it converts “I should run” into a schedule. But structure borrowed from a race date has an expiration — mine expired every year at the finish line.
Catalyst two
Actionable data made the routine self-sustaining.
What the races could never give me was proof between them. Overnight HRV, resting heart rate, pace at a given heart rate — clear metrics that move slowly but visibly. The promise I could never keep on willpower became easy to keep once the trend line was watching.
“Data is going to increasingly motivate or demotivate people. My goal is for it to motivate you.”
The twelve weeks
What the plan actually was.
The split
Zone 2 base, Zone 4 on schedule.
The same system that came out of my 70%-in-Zone-5 wake-up call: most running volume held in Zone 2, with Zone 4 intervals given a scheduled, bounded job. No heroic runs. No accidental redlines.
The volume
Ten miles a week, defended weekly.
Not an impressive number — a repeatable one. Ten miles a week is the dose I can defend against work, family, and a child who does not believe in sleep. Consistency was the experiment; mileage was just the unit.
The iron
Lifting stayed. Muscle stayed.
The non-negotiable: cardio could not cost me the strength work. Twelve weeks later the lifting routine is intact and muscle mass is holding — the “running eats your gains” fear did not survive contact with a measured, mostly-easy running dose.
The constraint
Built around real sleep, not ideal sleep.
I am a dad of a sleepless child. Some weeks, engineering seven hours of sleep was harder than any interval session. The plan had to absorb that — bad-sleep mornings downgraded the day instead of deleting the week.
The receipts
Week 12, by the numbers.
Overnight HRV vs baseline, holding five straight days
Resting heart rate — the lowest reading I have ever logged
Weeks of the Zone 2 / Zone 4 split at ~10 miles per week
Lifting sessions sacrificed; muscle mass maintained
Being added from the watch — receipts over claims.
The overnight HRV climb out of the old baseline — the 25% jump and the five-day hold.
Being added from the watch — receipts over claims.
The first 49 bpm resting heart rate on record, after twelve weeks of the split.
Being added from the watch — receipts over claims.
The unglamorous part: ten miles a week, mostly Zone 2, actually completed.
The honest middle
The weeks the data refused to clap.
The mornings that felt like a scam
There were weeks where I did everything right — fought my way to seven hours of sleep, which for me is a logistics operation, not a habit — and woke up to an HRV reading equal to or worse than the day before. That is the moment most people quit the data. I nearly did.
Gradual is the honest speed
The results were not immediate. Nothing about this trend moved week to week — it moved across weeks, and only if I kept feeding it. The 25% jump did not arrive as a jump. It arrived as a drift I only believed once it held for five consecutive days.
Why I kept going anyway
Because the runs themselves started feeling great, and because I finally had a scoreboard that could not be argued with. Data is going to increasingly motivate or demotivate people. My goal — for myself and for anyone reading this — is to set it up so it motivates you.
Training log
A living record. Updates land here.
Week 12 · 2026-06-10
HRV up ~25% from baseline and steady for the last five days. Resting heart rate hit 49 for the first time. Runs feel great, lifting intact, muscle mass holding. The plan continues — updates will land here as the training progresses.
Sources and next reads
The system behind the numbers.
Zone 2 / Zone 4 learning curve
The system this experiment ran on: the 70%-in-Zone-5 run that started everything, and the interval structure that replaced it.
HRV after 40
How Garmin grades overnight HRV against your own baseline — the guide that explains every number in this report.
Resting heart rate after 40
The explainer behind the 49: what resting heart rate measures, what is normal at 40+, and why a trained low number is an adaptation, not an alarm.
VO2 max after 40
The engine metric this kind of training ultimately moves, and how to make the watch’s estimate trustworthy first.
Fitness systems for busy fathers
The constraint layer underneath these twelve weeks: compressed mornings, interrupted sleep, and rules for training through both.
What’s next: the manual override
The training moved the baseline. The breath protocols move the moment: three 90-second exhale tools that pull the same vagal brake this report watched climb overnight.
Garmin epix Pro review
The watch that produced every receipt on this page — and why its HRV, sleep, and readiness loop became the daily behavior layer.
Garmin support: HRV status explained
Garmin’s own documentation of how training, sleep, nutrition, and habits influence the overnight HRV signal this report tracks.
FAQ
The results questions, answered dry.
How long does it take to improve HRV with Zone 2 training?
In my case: twelve weeks of a consistent Zone 2 / Zone 4 split at roughly ten miles per week before HRV rose about 25% above baseline and held. The movement was gradual — several weeks showed flat or even worse readings despite decent sleep. Individual timelines vary widely with age, training history, sleep, and stress, so treat any single timeline, including mine, as one data point rather than a promise.
Can running lower your resting heart rate?
Consistent aerobic training is one of the most reliable ways to lower resting heart rate over months — a stronger heart moves more blood per beat, so it needs fewer beats at rest. Mine reached 49 bpm for the first time after twelve weeks. A low resting heart rate in a trained person is typically an adaptation; a low rate alongside dizziness, fainting, or fatigue is a clinician conversation, not a trophy.
Did adding ten miles a week cost you muscle?
No — and that was the non-negotiable condition of the whole experiment. The lifting routine stayed intact, and muscle mass held across the twelve weeks. The dose matters: most of the running was genuinely easy Zone 2, which interferes far less with strength work than the every-run-is-a-race pattern I used to default to.
Why is my HRV not improving even with good sleep?
Mine did the same thing for stretches of this experiment — seven hours of sleep followed by an equal or worse reading. One night is weather: heat, alcohol, late meals, stress, illness, a hard training day, or normal variation can flatten the signal. The useful frame is the multi-week trend against your own baseline, not the morning-after scoreboard. If weeks of consistent training and sleep produce a steady decline instead of a plateau, that pattern is worth a closer look.
Will you keep updating these numbers?
Yes. This page is a living field report — the training log above gets a new entry as the stats progress, including the months where the trend stalls or reverses. The whole point of this experiment is honest data over a highlight reel.
Is this medical advice?
No. This is one person’s training data, honestly reported, with the context to interpret it. HRV and resting heart rate are fitness signals, not diagnostics. Heart symptoms, abnormal heart-rate alerts, medications, cardiovascular risk, and exercise clearance belong with qualified healthcare professionals.
Important note
This page reports one person’s training data and will be updated as the experiment continues, including stalls and reversals. HRV and resting heart rate are fitness signals, not diagnostics. Heart symptoms, abnormal heart-rate alerts, medications, cardiovascular risk, and medical testing belong with qualified healthcare professionals.