Dan Barber at Indy Monumental: A Full Time Job, 200 Pounds Lost and a Negative Split Marathon

He wrestled at 160 pounds his senior year of high school, the only time he had any real fitness, and played rec baseball that his dad coached. In his 20s he reached about 270 pounds, and he was down to about 220 by the time he married. In graduate school he climbed close to 300 pounds.

When he was 28, his dad had his first heart attack. Dan knew he needed to change, but he was not ready yet. Over the years he tried many things, each with a short win and then a slide back.

In November 2016 he had gastric sleeve surgery and lost about 170 pounds at first. CrossFit did not stick, and when Covid hit he had nothing to fall back on. His weight climbed back to about 270 pounds. In 2025 rowing brought some success, but he got bored again. Then a friend at church who was training for a 70.3 suggested he try a sprint triathlon.

His first long run, in June 2025 and after only two other runs, was in his words the classic try to do too much style, and he nearly hurt himself.

Looking back at his TrainingPeaks data from earlier in the year, you can see how far he had already come by May. His first weeks after surgery were easy rides, walks and short sessions, and hard work came back only once he had healed. His own comments from those weeks:

• December 11: back on the bike, Dan wrote that he was sore from "not sitting on a seat for almost two months."
• December 30: "I think my HR is just high for the first month."
• January 17: "I did notice my heart rate is much better than it has been," he wrote, "getting down lower near to what it was before surgery."
• January to March: his tests show his Critical Power rising from 168 to 187 watts and his Critical Speed from 9:06 to 8:01 per mile. Those were his tested numbers when he came to us.

His Garmin data tells the same story. His logged weight went from 170 pounds on January 1 to about 159 pounds when he started with Angela, and 155 pounds by late September. Since May his average daily pulse has eased from about 66 to about 62, and his heart rate variability has risen from about 33 to about 40 ms.

His body since May

Seven day averages of his daily pulse and heart rate variability, and his logged weight. The dashed line is the day he started with Angela.

Health shaped his whole year. His TrainingPeaks comments from early March show a week of fever, sinus trouble and a deepening cough, and he rested: "Skipping this today; need to rest." In September and October a tight left hamstring on the bike led him to work on his bike fit: "I think it is crank length and seat position. Going to fix."

Safety comes first in every decision we make, ahead of any race date or block. For Dan that meant starting from where his body was in May: a winter of coming back from surgery behind him, and a 70.3 three days before.

When heat and short sleep hit him a week before Ohio, the job became sleep, fluids, sodium and carbohydrate. When his hamstring talked on the bike, fit and position came before more load.

Read more in what StressLogic is and how we harmonize training with your life.

• March 21, Circle City 5K. 23:12, a 5K lifetime best, before he started with Angela.
• May 2, Indy Mini Marathon. 1:49:49, a half marathon lifetime best with a negative split.
• May 17, IRONMAN 70.3 Chattanooga. His first A race of the year. Three days later he started with Angela.
• July 11, IRONMAN 70.3 Muncie. Did not finish. He stopped in the swim.
• July 19, IRONMAN 70.3 Ohio. Raced with the swim cancelled for the field, after a Race Specificity block built around summer heat and fueling.
• August 20, RUN(317) Speedway 5K. 22:27, another 5K lifetime best, and 2nd in men 50 to 54.
• August 22, Eagle Creek Sprint Triathlon. Short and sharp, after a Race Specificity block for the sprint.
• September 6, Golden Harvest Half Marathon. 1:44:37, a lifetime best and 10th overall.
• November 7, Indy Monumental Marathon. 3:32:03, with a negative split of 4 minutes 47 seconds.

Road race times are official chip times. Triathlon splits are from his own watch files (elapsed time), not official results. From Dan's own race list.

A plan written in May cannot know what July or October will bring. These are the real changes we made to Dan's weeks after he started with Angela, and the reason behind each one:

• Late May and June, work travel. "Exhausted from travel. Got in at 1am. Up at 7. Long days in NYC." Sessions moved around his flights, and short ones still counted.
• June 22, short sleep. His house was being painted and his sleep was "here and there." He still finished the session, and the week held.
• July 2, a week before Ohio. Heat and short sleep left him "Tired and weak." Angela: "We're a week out, so the job now is sleep, fluids, sodium, and CHO topped up, nothing heroic."
• August 16, race week for the sprint. Angela on his load that week: "Load is low by design and fits race week."
• September 10, the hamstring. A tight left hamstring on the bike pointed to his fit: "I think it is crank length and seat position. Going to fix." Fit comes before more load.
• October 8 to 16, a retest. "Felt a bit way too easy" became a 400, an 800 and a 3200, and new zones on October 16. When targets stop fitting, we check the anchors.
• October 24, fueling before, not just after. A late workout and light eating made the back half of his 18.6 miles feel heavy, so the next long run started with carbs on board.
• Race week, two days off work. His own call, from what he learned earlier in the year. We built race week around it.

His training stress each week

Weekly TrainingPeaks training stress by sport.

Planned sessions done, month by month

Sessions on his plan that he completed, and those that did not happen.

The call comes from the week behind it. We look at the training he completed and how it is trending, whether key sessions held their target, whether easy work stayed easy, and what he told us about sleep, soreness, health, work and family.

Good numbers do not override a poor position to absorb more. A heavy stretch at work or a run of short nights can change the call while the training numbers still look ready. A skipped session in a busy month is information, and the plan adjusts around it.

Bike, Critical Power. Zwift, 3, 6 and 12 minute all out efforts.

Run, Critical Speed. 400 m, 800 m and 3200 m all out efforts.

* Round 1 values were calculated from his Strava files. The bike 3 minute effort came from a December 15 VO2max session, two and a half weeks before the other two, so treat that CP as approximate. Round 3 CS is from his October physiology profile. Run percentages are change in speed.

Critical Power (bike) and Critical Speed (run) mark the line between work you can sustain for a long time and work that will eventually unravel. We find the line in the field from your own short, hard efforts, then set your training zones from it. Dan's bike test used 3, 6 and 12 minute efforts and his run test used a 400, an 800 and a 3200.

Heart rate still matters. It tells us what the work cost you that day, and heat, sleep, stress and fueling all move it. So we read heart rate together with pace, power and feel.

On October 8, during a race intensity session, Dan wrote "Felt a bit way too easy." Angela answered: "OK well let's test." His race paces for Indy came from that October test.

More in how we calibrate with CP and CS testing.

From mid September his running sat between about 34 and 41 miles a week, and the long runs carried race work inside them. On October 17 he ran 18 miles with four race intensity pieces: "Felt absolutely amazing I was in peak flow state."

The marathon build: weekly run miles and the longest run each week

Late August to the week before race week.

Every run of 8 miles or more since May

His long runs from May to race day. Red bars are races. The dashed line is the day he started with Angela.

The 20 mile run in TrainingPeaks

October 10.

The 20 mile run, mile by mile

October 10: pace and heart rate for each mile.

October 17 in TrainingPeaks

18 miles with four race intensity pieces.

October 17: 18 miles with race intensity inside

Lap by lap pace and heart rate. Dark bars are the race intensity pieces.

This is Dan's performance chart, built from the training stress on every session he did. Fitness is the long running average, fatigue is the last week, and form is the gap between them.

Fitness, fatigue and form in TrainingPeaks

All sports, May 1 to November 10, 2026.

Fitness, fatigue and form, May to race day

Top: fitness, fatigue and run fitness. Bottom: form. Dotted lines are his races. The dashed line is the day he started with Angela.

On race morning his fitness sat at 74.4 and his run fitness at its highest of the year, with his form at plus 18: fresh, and still fit.

Every session Dan finished came to ANC, where we read the file and wrote back to him. These are the real session graphs from his coach's analysis for three of his last key runs. Pace is the blue line, heart rate the red line below, and the shaded bars are the targets in his plan.

October 24: 18.6 miles with four race intensity pieces

ANC · session graph

October 29: race intensity intervals

ANC · session graph

October 31: easy run with a tempo finish

ANC · session graph

It was the first time he raced the way he trains. "I figured that since I always train in blocks, I should race in blocks, too," he told us.

He followed his carbohydrate load over the last two days. The portable toilet line took almost twelve minutes, and he reached the corral with no real warm up. He started anyway, behind the 3:35 group, on purpose.

"I had my plan, and I wasn't going to keep up with the sign, because I was going to execute my plan."

Dan Barber, his race recap

He ran his first 5K at 8:22 per mile, inside the band. Around mile 9 a lace bite in his right foot made him stop for about a minute to relace his shoe. Through the middle miles his heart rate settled. In his words: "Settling in at 165 and 8:05, my thought was, I'm in a good place. I can do this."

He went through halfway in 1:48:25. From there every timing split was quicker than his first 5K. From 25K to 40K he ran 7:57, 7:59 and 7:55 per mile through the quiet stretch where the course empties out. "That's where my Ironman background really helped a lot," he wrote. When gradual hills slowed him, his watch told him, and he answered it. He ran the last 2.2 kilometers at 7:15 per mile and passed, in his words, "literally hundreds of people."

Race day in TrainingPeaks

His Indy Monumental file.

Every mile on his watch, with heart rate

First half in orange, second half in navy. The dashed line is the heart rate cap on his race plan.

Race day, as we saw it at ANC

ANC · session graph

On September 6, in the middle of his build, Dan ran the Golden Harvest Half Marathon in 1:44:37, a lifetime best, 10th overall. He ran his last mile at 7:15.

It was not a fast course. The roads stayed open to the public in a high traffic area, with a lot of tight 90 degree turns and four turnarounds. Dan says he lost a lot of time to them, and he still finished 5 seconds under his planned 1:44:42.

Golden Harvest Half Marathon, mile by mile

Pace and heart rate for each mile.

The four step plan on his watch added up to about 3 hours 31 minutes. He ran 3:32:03, with a minute stopped to fix his shoe, crowded roads where the course narrowed, and a cold start with no warm up.

Fueling went the way he practiced it. He carried his own bottles and took a gel each hour, about 90 g of carbohydrate an hour by his own count, and delayed a gel when his stomach rumbled.

His own lessons for next time are the kind we want athletes to write: keep the throwaway layer on until the start, plan the warm up around the corral, and know that tall buildings make early GPS pace unreliable.

• The durability question is answered. He held pace and heart rate together for 26.2 miles and ran the second half faster.
• Fueling is practiced. About 90 g of carbohydrate an hour on race day, and full sessions fueled in July heat.
• He knows how his body handles cold, and he has a plan for it.
• Two 70.3s are already behind him, so the full distance builds on racing he has done.

Yes, if the plan expects it. Dan's sessions moved around flights, meetings and work calls, and a heavy stretch got a lighter week. The block stayed the same while the dose changed.

Many working athletes can. Dan averaged about seven and three quarter hours a week after he started with Angela, all sports counted, with his run at roughly 34 to 41 miles a week in the marathon build.

Yes. Dan finished two IRONMAN 70.3s and a sprint triathlon this year, then gave the run its own blocks for Indy while the bike moved to easier work.

Not for most runners we coach. We cap marathon long runs at about three hours. Dan's longest run was 20.3 miles, and he ran the second half of his marathon almost five minutes faster than the first.

Many athletes can, with the right start. Dan's TrainingPeaks data shows he came back from surgery with easy riding and walking, and harder work only once his body was ready. By the time he started with Angela in May he had raced a 70.3, and we built from there.

The pace you can hold for a long time before fatigue climbs fast. We work it out from your own 400, 800 and 3200, then set your run zones and race pace from it.

Critical Power and Critical Speed describe the boundary between the heavy and severe intensity domains. Below it, effort can reach a steady state. Above it, fatigue builds toward the point where you have to slow down (Jones and colleagues, 2010; Poole and colleagues, 2016).

Durability describes how much, and how soon, your physiology drifts during long exercise. Two athletes with the same test numbers can look very different three hours into a long day (Maunder and colleagues, 2021).

Critical Speed can be estimated from recreational marathon runners' own training data, which is part of why we read the whole training history alongside formal tests (Smyth and Muniz Pumares, 2020).

These studies explain the ideas. Dan's zones, blocks and race paces came from his own tests and training.

Sources: Jones AM, Vanhatalo A, Burnley M, Morton RH, Poole DC. Critical power: implications for determination of VO2max and exercise tolerance. Med Sci Sports Exerc. 2010;42(10):1876 to 1890. DOI; Poole DC, Burnley M, Vanhatalo A, Rossiter HB, Jones AM. Critical power: an important fatigue threshold in exercise physiology. Med Sci Sports Exerc. 2016;48(11):2320 to 2334. DOI; Maunder E, Seiler S, Mildenhall MJ, Kilding AE, Plews DJ. The importance of durability in the physiological profiling of endurance athletes. Sports Med. 2021;51(8):1619 to 1628. DOI; Smyth B, Muniz Pumares D. Calculation of critical speed from raw training data in recreational marathon runners. Med Sci Sports Exerc. 2020;52(12):2637 to 2645. DOI