Your Plan Isn't the Problem

The Context

Who's behind this

A little context on why I'm writing this.

A few months ago I finished the Looking Glass 100K — 62 miles through Pisgah National Forest, 16 hours moving through terrain that doesn't ask nicely. It's one of maybe a dozen marathon and ultra-distance races I've done over the years, plus a bike ride across the country when I was 22 and apparently had no concept of what was reasonable. I've spent a lot of years doing hard things in the mountains, learning — often the slow way — what actually works.

That's not a credential pitch. I'm not a coach, not a sports scientist, not a physical therapist. I'm a desk-job employee, a husband, and a dad to a two-year-old with a second kid on the way. The version of me who had unlimited training time and nothing competing for his attention is a decade gone.

What I do have is a compulsion to understand the things I care about — which means I read the research, run the experiments on myself, and try to figure out what actually transfers to someone training seriously while also being a full human being with obligations. That's what this newsletter is. Not expertise. Proximity.

The Framework

The plan isn't the product

Here's what most people get backwards about coaching: the plan isn't the product. The feedback loop is.

A training plan is a hypothesis. It says: if you do these sessions at these intensities with this progression, your body will adapt in this way. That hypothesis is based on general physiology, your current fitness, your event, and your timeline. It's a reasonable starting point.

But a plan can't read your data on Tuesday and know that Thursday should be modified. It can't see that your heart rate variability has been trending down for four days. It can't notice that you've been favoring your left foot and flag that your gait is drifting under fatigue.

The difference between a coached athlete and a self-coached one usually isn't the structure of their training block. It's the presence of someone who treats every completed week as input data and makes a call about the following week based on what that data says.

The Research

How errors compound

There's useful research on this. Tim Gabbett's work on the acute:chronic workload ratio — published in the British Journal of Sports Medicine in 2016 — showed that athletes who spike their weekly training load significantly above their rolling 4-week average are at substantially higher injury risk in the following weeks. Not marginally higher. Measurably higher, across multiple sports and athlete populations.

The practical implication: a single week of unintentional overload creates an injury risk window that lingers for 2–3 weeks after the spike. By the time something hurts, the cause is usually three weeks ago.

Most self-coached athletes catch problems when they become symptoms. A feedback loop catches them when they become signals.

I had a version of this happen recently. Early in my current training block, I started developing bilateral tenderness along my shins — classic early-stage MTSS, the kind that warms up within the first half mile and disappears at rest. Completely normal load-adaptation response at the start of a speed phase. Not alarming on its own.

But it needed to be caught, named, and monitored — not filed away and accumulated. Load was adjusted. A PT protocol was added. My wife, a licensed acupuncturist, administered treatment targeting the specific tissue. The problem resolved instead of progressing. That required someone paying attention.

The Gap

What self-coaching actually costs

Here's the math most people don't run.

A human coach who provides real individualized feedback — weekly check-ins, training adjustments, injury monitoring, race-specific strategy — costs $200–350 per month. For most people in the world of this newsletter (full-time job, family, real life), that's not accessible. Not because the value isn't there, but because the budget isn't.

So they train without the feedback loop. Errors compound. They're more likely to miss a race peak, accumulate a preventable injury, or spend a full training block executing a plan that stopped being right for them four weeks ago.

Most apps tell you what to do. Very few ask what you actually did, read that data, and tell you what it means for what comes next.

The Long Game

Building something that catches problems early

I've been thinking about what actually separates athletes who stay healthy across long training blocks from those who don't.

It's usually not talent. It's usually not plan quality. It's usually the presence or absence of a functioning feedback mechanism — something or someone watching the data, noticing the drift, and acting before the signal becomes a symptom.

That's a systems problem. And systems problems have systems solutions.

The long game isn't just about running longer. It's about building something that catches problems early — adjustments before they become setbacks, signals before they become injuries, data before it becomes a story you're telling your physical therapist.