Two of them trained with me all summer, and they know their tempo pace. They know what it feels like when they’re working but still in control.

So their instructions were pretty simple.

1. Get to the front.

2. Run the pace we’ve been running in tempos.

3. Race from there.

They finished second and third.

The other two had been running for three weeks.

I gave them completely different instructions.

1. Stay together.

2. If you feel yourself getting out of breath, slow down.

3. I’ll tell you when you have a half mile left. I’ll tell you again when you have 400 meters left.

4. Then you decide when you want to go.

They finished eighth and tenth.

All four walked away happy.

And I walked away knowing a little more about each of them.

That’s about all I needed from the first meet.

The temptation after an early race is to make it mean more than it does.

It starts when you start scrolling the posted results.

One kid ran faster than you expected. Another was 45 seconds slower than you thought she would be. Somebody went out way too hard. Somebody you thought would be near the front disappeared half way through the race.

Before you even get the tent packed up, your brain is already rebuilding the season.

Maybe we need more speed.

Maybe our mileage is too high.

Maybe we need another threshold day.

Maybe that kid isn’t varsity.

Maybe everything is working.

Maybe nothing is working.

The first meet has a strange way of asking for a verdict.

I try not to give it one.

August is information. October is the test.

We didn’t taper for this race. I don’t taper for anything this time of year. In fact, I don’t taper until the post-season.

I’m not trying to squeeze every second of fitness out of them in August. I’m still training them.

Early meets are part of that training.

I want to see how they behave when somebody puts a number on their chest.

Do they blast the first 400 because everyone else did?

Can they settle into their target pace?

Can they run in a pack?

What happens when they get nervous?

What happens when somebody passes them?

Do they respond?

Do they panic?

Do they compete?

That information is often more useful to me right now than the final time.

My four freshmen are a good example.

If I had judged all four by the same standard, the two who finished eighth and tenth would look like they had the worse day.

They didn’t.

They did exactly what I asked them to do.

They stayed under control, and ran together. They got deep enough into the race to make a decision and then execute it.

For kids who had been running for three weeks, that was the lesson.

The other two were ready for a different lesson. They had enough training underneath them that I could tell them to trust a pace they already knew and take it to the front.

Same race.

Different athletes.

Different jobs.

That’s why I’m careful about what I change after an early meet.

There are three reactions that are really easy for good coaches to have.

The first is to overreact. A race goes badly on Saturday, so Monday’s workout goes in the trash. We add something harder because we’re nervous that we’re falling behind.

The second is to under-react. We tell ourselves it’s early, so nothing matters. But every race shows us something. If five kids all panic and sprint at the start, then there is something worth learning.

The third is to borrow workouts from the teams that beat us. They post their workout online, and suddenly their Monday looks a lot more attractive than the Monday I planned six weeks ago.

I understand all three.

Pressure makes certainty feel attractive.

But one race usually hasn’t earned the right to change very much.

So in the first 48 hours after a meet, I try to keep my decisions small:

• What am I willing to change this week? It’s usually something I actually observed. Maybe we need to practice the start. Maybe a group needs clearer pacing instructions.

• What am I leaving alone on purpose? This matters just as much. One slow race does not erase six weeks of training. If the work has been landing, I’m not changing it because Saturday made me uncomfortable. A race is a single data point, not the entire season.

• Who do I need to talk to? Sometimes the most important piece of information isn’t in the results. It’s the kid who says, “I got scared when everyone went around me,” or the assistant who noticed that three runners tightened up at the same place.

Then we go back to work.

Next week, the race gets another job.

Maybe we practice getting out cleaner.

Maybe we work on staying connected to a pack.

Maybe I give them a point on the course where they have permission to start racing instead of just running.

Then I watch again.

That’s how I want the early season to work.

Teach something.

Race.

Notice what happened.

Teach the next thing.

I’m not trying to go to the well every Saturday. I’ll save that for the races where losing means the season is over.

This weekend, I had four freshmen standing on the same starting line.

Two were ready to race from the front.

Two were ready to learn how to stay in a race long enough to make a decision.

Second. Third. Eighth. Tenth.

Four very different results.

I’m not sure the clock was the most important thing I learned from any of them.

Before you change Monday, what did Saturday actually teach you?

If this way of thinking about a season sounds familiar, it’s a big part of why I wrote Build, Don’t Borrow: The Distance Coach’s Guide to Training Architecture.

The book isn’t a collection of workouts to copy. It’s about building a training system you understand well enough to know what should change when reality shows up, and what should stay exactly the same.

Because reality always shows up.

Especially after the first meet.

Go build.

Then I end the book.

A little rude, when you think about it.

I spend the whole book walking you through 23 questions. Each one forces a decision about your program. What are you building? What kind of coach are you? How do you define training? How should the season progress? What belongs in the week? What tells you the training is doing its job?

By the last chapter those answers have started connecting.

You’ve got an Impossible Goal. A training model. A seasonal structure, standards, a race-execution model, a way to develop the next group coming into your program.

Or you’ve got pieces of those things.

Some answers are underlined in the book. Some are in the margins. A few are in a notebook. Several exist only in your head, where they’re competing for space with tomorrow’s workout, the kid whose shin started hurting yesterday, and the email you still owe a parent.

Then you hit the last page.

Go build.

Good luck, Coach.

Understanding the pieces of an architecture is a different thing from being able to see yours.

Your philosophy lives in your head. Your workouts live on the calendar. Your race plans are in a binder, your periodization is a spreadsheet, and the reasons behind all of it are spread across multiple seasons of decisions.

That’s exactly where I was when these questions started.

I didn’t need another chapter.

I needed somewhere to draw.

The book was missing one more page.

A blank one.

• • •

Before I go any further, thank you.

If you bought Build, Don’t Borrow, you trusted me with more than the price of a book. You trusted me with several hours of your coaching life.

It would’ve been easier to write a book of workouts. You could’ve flipped to the cross country section, found a twelve-week schedule, copied it into your calendar, and been done before dinner.

Instead, I gave you 23 questions.

Some of them are hard. A few make you define things you’ve coached for years without ever putting into words. Others make you take a position when “it depends” would be a lot more comfortable.

I asked you to do more work, not less.

So, you weren’t buying information. You were betting that answering those questions would eventually produce something worth owning.

I don’t take that lightly.

• • •

There’s a problem hiding inside the blank page.

Blank pages make us uncomfortable.

A blank training calendar feels unfinished. Every empty box looks like a decision we should’ve made already.

So, we fill it.

We pull the plan from last season. We dig through clinic notes. We remember a workout somebody described at dinner. We open the folder of PDFs we’ve been saving since 2017 and find the one with CHAMPIONSHIP in the title.

The page starts filling up.

Monday gets a long run. Tuesday gets a workout. Thursday gets another workout because two quality days sounds right. Saturday gets whatever the program on the other side of the state does on Saturdays.

By the time we’re done, every day has something in it.

Relief. The blank page is gone.

And we still haven’t decided what we’re building.

That’s the strange part about planning in this sport. We can make a hundred decisions without ever making the first one.

We choose workouts before deciding what job they do. We arrange the week before deciding what the week should produce. We build phases before naming the athlete who’s supposed to exist when those phases are over.

We start with training and hope it produces transformation.

That’s how I coached for years. I had books, clinic notes, spreadsheets, saved workouts, and enough information to look capable. What I didn’t have was a structure connecting any of it.

When the season behaved, the calendar looked brilliant.

When the season changed, I was lost.

• • •

The Solved Game

For a long time, I thought the problem was that we borrow too many workouts.

That’s part of it. But it starts one level up.

We borrow because we believe the right answer already exists.

Somebody has already figured out how to train a 5K runner. The right weekly structure is sitting inside a program that keeps winning. The right progression got presented at a clinic five years ago, and if we can just find those slides, we can stop guessing.

I call that belief the Solved Game.

The Solved Game says coaching is a closed problem with a correct answer waiting to be found.

If that’s true, the job is simple. Find the answer. Run it correctly. Hope the future cooperates.

The belief is attractive because it looks like humility. We’re learning from successful people. We’re respecting experience. We’re avoiding the arrogance of thinking we know better than coaches who’ve won more than we have.

Learning from other coaches isn’t the problem.

The problem starts when their answer becomes more trustworthy than the kid standing in front of us.

A workout from a State championship program feels safe because we know it worked. What we don’t know is why.

We don’t know what those athletes were ready for. What came before it. How the coach modified it for the second group. What the rest of the week was protecting. What he would’ve changed if it had gone badly.

We get the workout. We don’t get the decisions that produced it.

Then our kids respond differently. The varsity group looks great. The younger group is hanging on. One kid improves, another one’s shin starts barking, and the athlete who looked strongest in August is flat by the third week of September.

Now the borrowed answer doesn’t fit the question.

So, we go looking again. Another workout. Another presentation. Another successful coach with a different answer.

More information comes in. Certainty goes down.

• • •

The blank page is where the Solved Game is hardest to resist.

If coaching is already solved, a blank page is evidence that we don’t know enough. Surely an experienced coach would know what belongs there. Surely there’s a template. Surely somebody can show us the right answer, so we don’t have to risk drawing the wrong one.

Which is why handing you my finished architecture would be the easiest thing I could do.

I could give you my Impossible Goal, my training model, my periodization, my weekly structure, every standard I run inside my program.

You could copy all of it. Your page wouldn’t be blank anymore.

It also wouldn’t be yours.

An architecture somebody hands you is a borrowed plan with better packaging. It breaks the same way.

Your athletes won’t match mine. Your calendar will have different interruptions. Your freshmen show up with different backgrounds, your facilities create different constraints, and something that worked beautifully for my team will eventually run into a reality I never had to think about.

That collision isn’t a possibility. It’s the season.

The athlete who exists in Week 5 isn’t the athlete who existed in Week 1. Training changes the person it was built for. When it works, the plan stops fitting precisely because it worked.

Fixed target. No fixed path.

So, the page can’t just tell you what to do. It has to hold why you chose it. What the decision connects to. What you expect it to produce. What you’ll watch when the season starts pushing back.

A finished answer can’t do that for you.

You need somewhere to put your own decisions where you can see them.

• • •

Every field that builds something complicated separates design from construction.

An architect doesn’t start by deciding where the crew stands on Tuesday. The design settles what the building has to become, what carries weight, and which parts can’t move without affecting everything around them.

Then Tuesday makes sense.

I spent thirteen years in software before this, some of it teaching object-oriented analysis and design to development teams. Same lesson, different building. A list of features is a wish. Somebody has to decide how the pieces talk to each other, what happens when one fails, and which boundaries keep one small change from taking down the whole product.

Skip that and you don’t get a fast product. You get a product nobody can change.

We do it backwards.

We start with construction. What’s the workout Tuesday? How many miles this week? When does speed start?

Those are real decisions and they matter. But they’re decisions about materials and schedules. They don’t answer the question sitting underneath all of them.

What are we constructing on purpose?

Training Architecture flips the order. It starts with transformation and works down to training.

Before you pick Tuesday’s workout, decide what the athlete has to become by November. Before you build the week, decide what the week is responsible for producing. Before you change the plan, know which part of the structure is failing and what your change might disturb around it.

The workouts are still there. The calendar still matters.

Now they’re building something you chose.

That’s the page missing from the end of the book. A blank page with enough structure to help you draw your own.

So, I built it.

• • •

The Blueprint

It’s free, and it’s built to sit next to the book.

Open it and you’ll see the whole architecture on one page. The Impossible Goal sits at the top. The Training Architect is the foundation. Everything else takes its position between them.

That arrangement tells you where to start.

You start with the Impossible Goal, because it’s the transformation every decision below it has to serve. Without it you can still fill a calendar. You can assign mileage, schedule intervals, plan races, build a season that looks organized.

Organized toward what?

If you don’t know what you’re building, every workout is an isolated choice. You can judge whether it was hard. You can check whether the kid finished it. You can’t know whether it moved her toward the athlete you meant to create.

So, the first question isn’t what we do Monday. It’s who this athlete has to become by the end of the season.

Until that’s answered, Monday is an empty box waiting to be filled.

Then comes the Training Architect. That’s where you decide what kind of coach is doing the building.

Every architecture has an architect. Somebody has to decide what matters, what belongs, what doesn’t, what can be compromised and what gets defended. That’s you.

Your Training Architect names the convictions underneath the program. Your boundaries. Your constraints. The patterns you trust. The tradeoffs you’ll accept. The places you refuse to drift just because the season got hard.

Two coaches can chase the same Impossible Goal and design completely different programs. They may see different constraints, value different adaptations, hold different beliefs about how kids develop. Their architectures should show that.

Otherwise, they’re borrowed plans wearing personalized covers.

Only then do you build the Training Model.

Start with the Adaptation Protocol. What has to change, and why? Which capacities does the Impossible Goal require, how do they interact, and what do you believe produces them?

Then Periodization. When do those changes happen? Some adaptations set up others. Some take months to accumulate. Some have to be protected while another capacity gets the attention. A season can’t be a pile of equally urgent priorities. It has to unfold.

Only then the Weekly Structure, which answers a smaller question. Where does the work belong?

The week can’t settle what the Adaptation Protocol and Periodization haven’t settled. Start with the week and the boxes take over. Monday needs something. Tuesday needs something. Pretty soon every day has a workout, and the full calendar gives you the comforting appearance of a plan.

A full calendar mostly proves you’re good at filling boxes.

A calendar rewards speed. Architecture punishes shortcuts.

From there the rest builds on what came before. Your technical standards, your race-execution model, your development pipeline, your feedback system, and the language that lets everyone in the program hear the same thing when you talk.

Each piece has a place. Each piece depends on decisions you already made.

That’s why the Blueprint isn’t free-form. You don’t jump to whichever blank looks easiest. You don’t start with your favorite workout and work backward until you can justify it.

You start at the top and follow the structure down.

You don’t have to finish in one sitting. You probably shouldn’t.

Thinking is hard. Deciding what you believe is harder than copying somebody who’s already decided. Naming your tradeoffs is harder than pretending you don’t make any.

The Blueprint won’t do that thinking for you. That would defeat the whole point.

It gives your thinking somewhere to live. And because every part sits in relationship to the others, you can see whether what you’re building will hold the weight you’re about to put on it.

Take your time. You can’t skip the thinking.

And that’s how a blank page becomes an architecture.

• • •

The first time you open it you may have the same reaction I did when I saw the whole architecture in one place.

This is a lot.

It is.

A training program is responsible for changing human beings over time. It has to coordinate physiology, skill, competition, recovery, belief, language, and development while the athletes themselves keep changing. That was never going to fit on a cute one-page worksheet.

The Blueprint doesn’t make coaching simple. It makes the complexity visible.

That can be uncomfortable.

When your philosophy lives in your head and your workouts live on a calendar, it’s easy to assume they’re connected. Put every part of the program in the same architecture and those connections have to prove themselves.

You start noticing things.

The adaptation you say matters never shows up in your periodization.

The technical standard you preach has no place in your feedback system.

The race behavior you expect was never defined, much less taught.

The week has sessions you know how to coach but can’t explain the job of.

With my 2024 team I realized that our biggest gap was our ability to hold a fast pace for the duration of the race. We were aerobically weak. I made that my number one priority for the season, which caused me to completely redesign my tempo progression. We ran faster and longer than we ever had in practice. And, it paid off in the end with a State qualification.

None of that makes you a bad coach. It means the architecture is doing its job. It’s showing you the gap between the program you think you’re leading and the program your kids are actually running.

That gap was always there.

Now you can see it.

• • •

I knew a blank Blueprint would create another problem. You could read the questions, understand what they’re asking, and still wonder what a finished architecture is supposed to look like.

So, I put mine in there.

Inside the tool you can open a completed example built from the architecture I ran with the Mayde Creek girls in 2024.

It isn’t an answer key. Please don’t treat it like one. The last thing I want to do is write a whole book about building your own architecture and then hand you mine to borrow.

It’s there so you can see the relationships. How an Impossible Goal gives the program direction. How the convictions of the Training Architect turn into decisions inside the Training Model. How the Adaptation Protocol shapes Periodization, how Periodization gives the Weekly Structure meaning, how everything else grows out of those choices.

You’re looking at one coach’s reasoning made visible.

Some of my answers may help you. Some may make you think. A few may make you say you’d never do it that way.

Good. That might be the moment you find out what you believe.

Look through it. Follow the decisions from the top down. Notice where one answer creates the need for the next.

Then close mine and build yours.

• • •

The Blueprint is free.

You can start without making an account and your work saves in your browser. Make a free account and it saves for good. Leave, come back, keep building as the season moves.

That matters, because this isn’t something you finish Sunday night and file Monday morning.

Your architecture should stay close enough to argue with you.

When you’re not sure what belongs in the next phase, go back to it. When the weekly structure starts drifting, go back to it. When a kid responds differently than you expected, go back to it. When you’re tempted to borrow somebody else’s answer because yours has gotten hard to defend, go back to it.

The Blueprint won’t protect you from uncertainty. Its job is to keep uncertainty from separating you from your own reasoning.

You may change an answer because the athletes taught you something. Two parts of the architecture might turn out to contradict each other. And at some point, a conviction you’ve defended for years won’t survive the evidence standing in front of you.

That’s coaching.

The goal isn’t to create a document so perfect that you never have to think again. That would just be another version of the Solved Game. What you want is an architecture strong enough to guide your decisions and visible enough to change when reality demands it.

You’re not trying to become the coach who always has the right answer. You’re becoming the coach who knows how to make the next one.

• • •

There’s a moment in every season when the plan stops behaving like the plan.

A kid gets hurt. The meet schedule changes. The adaptation you expected doesn’t show up. The group that looked ready in June looks tired in September.

That’s usually when we go searching. We open the clinic notes. We pull an old schedule. We text somebody whose program is winning. We look for an answer that can rescue us from having to decide.

I’ve done it.

Here’s what it costs. The borrowed answer doesn’t know what you’re building. It doesn’t know your Impossible Goal, your athletes, your constraints, your tradeoffs, or the principles you won’t give up. It can tell you what another coach would do. It can’t tell you what belongs in your program.

So, you patch. The season limps into District. You finish a spot or two off where you thought you’d be, and the honest answer to what went wrong is that you don’t know, because there was never a structure to check it against.

Then next August you start over with the same folder of PDFs.

The Blueprint won’t make the decision for you either. It’ll do something more useful. It’ll bring you back to the decisions that made the program yours.

You’ll be able to look at the whole structure and ask what you were trying to build, what reality has taught you, and what has to change now.

You may still get it wrong. But it’ll be your call, made for your kids, inside a structure you understand.

And the next time reality disagrees with you, you’ll have somewhere to put what you learned.

That’s how the architecture gets better. That’s how you get better.

• • •

If you bought Build, Don’t Borrow, thank you. I hope it changed the questions you ask about training.

Now let’s keep your answers from disappearing into the margins.

Open the Blueprint.

Don’t start with Monday. Don’t start with the workout you already know you want to use.

Start with the Impossible Goal. Give it time. Write an imperfect answer. Sit with the discomfort of deciding what transformation your program exists to produce.

Then go to the foundation and decide who the architect is.

The first answer doesn’t have to be permanent. It does have to be yours.

At the top of this I said the book was missing one more page. A blank one.

I was wrong about that. A blank page would’ve left you with the same problem.

What the book was missing was a place where your answers depend on one another. Where convictions become decisions, decisions become structure, and the structure becomes a program capable of producing the transformation you meant to produce.

The book still ends with the same two words.

Go build.

• • •

P.S. If you’ve read enough of the book to know what you think, would you leave an honest review on Amazon? It doesn’t need to be long. A sentence about what it helped you see is plenty. The Amazon page can tell another coach the title, the price, and how many pages are inside. It can’t tell him whether those pages are worth several hours of his coaching life. Only another reader can do that.

I need to explain how that is possible.

Qualifying for the Boston Marathon has two doors. First, you run the qualifying standard for your age group. Then you wait, because more people run the standard than the race can hold, and every September Boston announces a cutoff: how far under the standard you had to be to actually get in. Nobody knows the cutoff when they race. You run your race, and then you wait most of a year to find out whether your time was good enough.

In December 2018, the day before the California International Marathon, I stood in an expo hall in Sacramento and listened to representatives from the Boston Marathon take questions.

Two months earlier, Boston had lowered the qualifying standards by five minutes. That was fun. Not.

But that day at the expo, the Boston people were reassuring. The five-minute cut was supposed to close the gap between the standard and the cutoff. In their words, “if you run the time, you should make the cutoff.”

The next morning was everything Sacramento promises. Forty-five degrees, sun, no wind. You dream about that forecast. I ran well through the final ten miles and crossed the line under the qualifying standard.

I had run the time. The people in charge of the race told me the time should be enough.

For nine months, I believed I had qualified for Boston.

The following September, they announced the cutoff.

I missed it by 26 seconds.

I was sick to my stomach. Talk about having your heart ripped out. Nine months of believing I won, erased by less than half a minute I never knew I was racing against.

The Night, and the Morning

My running buddies took me out that night to cheer me up. I gave myself exactly that long to feel sorry for myself.

I realized there were two stories I could tell about those 26 seconds, and I had to pick one.

The first story: bad luck. The bad luck story was true. The standard moved two months before my race. The officials guaranteed I would qualify. The cutoff was lower than anyone expected. I did everything that was asked of me and lost to a number that did not exist yet when I ran. Every word of that is accurate. It would make a great story.

It’s also worthless. There is no training plan to battle bad luck.

The second story: my design had no margin for error. I trained to hit the published standard, and I hit it. But the real goal was the standard minus whatever the running world decided to add that year, and my design left no room for the running world.

Both stories were true. Only one of them could be trained and improved on.

So the next morning I got focused and made a decision: the next time, I would train to finish ten minutes under the qualifying time. If I built for minus ten, then even on an off day, I would still be clear of whatever the cutoff ended up becoming.

The target was never the standard. The target was the cutoff…whatever that would be.

The Adjustment

A goal like that is just a wish until I can explain how I will accomplish it. This is where losing the visible game started paying me back, because I could read my own race.

I had run well over the final ten miles in Sacramento, but, at the same time, I was barely hanging on. I survived the pace instead of running the pace. Big difference.

So I changed a few key things in the next training cycle.

I needed a hell of a lot more time at marathon pace. I do my tempo runs at marathon pace, and I needed enough of that mileage that the pace stopped feeling like racing. I wanted the entire race to feel like a normal long run. I also needed more strength for those last ten miles, because barely hanging on was never going to cut ten minutes off anything. And since Sacramento has rolling hills and I am a flatlander (Katy, Texas…check it out…no hills!), I needed to find a place to train on hills. I found them in the small town of Bellville and ran every other long run out there until the ups and downs didn’t affect me.

There was no secret workout in that plan. It was an analysis of one race, turned into training. I knew why I missed qualifying before, so the miss became the new blueprint.

The Terrible-Great Day

The next time I ran CIM, in 2021, Sacramento did not cooperate.

It was like running inside a fog bank. One hundred percent humidity, no sun, about forty degrees the entire race. By the end my gear was soaked through. I threw my gloves away mid-race because they felt like bricks. And over the last six miles my hamstrings started cramping, like a sniper shooting electric shocks into the backs of my legs. I had never felt anything like that before.

But I finished seven and a half minutes under the qualifying standard.

It was not my best race. But that was the whole reason for the ten-minute margin. I built it so I would not need my best race. The conditions took a toll, the cramps took another, and the margin covered all of it with room left over.

A perfect day had left me 26 seconds short. A lousy day cleared everything by seven and a half minutes. Training at minus ten paid off.

Boston

I finally ran Boston in 2023, and I went in with zero intention of racing it.

I had worked about fifteen years to qualify for that race. I wasn’t going to ruin it by racing it! My qualifying time by then was 3:35 (I’m old!), and I still trained for a 3:25 marathon, even though I had no intention of going for another BQ. My goal? Run Boston in about 3:45, enjoying every step, high-fiving everyone, mashing every power-up sign, running under all the balloon arches, and stopping at Fenway to take a shot with my daughter and her husband. Zero pressure to perform.

I even turned the time display off on my Garmin. I didn’t want to know the time.

I had only one other goal: run all of the Newton hills, topped off with Heartbreak Hill, without a walk break. I had heard the scary stories. A flatlander is permitted a little intimidation.

I crested Heartbreak Hill, and my honest reaction was disappointment. “That’s it? That wasn’t hard at all.”

The last five miles into Boston run downhill, so I decided to have some fun with them. Every time I passed a mile marker I picked the pace up a little more. I didn’t get my shot at Fenway, though. I mean, there are a LOT of people watching the race through that section.

About fifty meters from the finish, I could finally read the clock.

I had run another Boston qualifier. Five minutes and twenty-nine seconds under my standard. While high-fiving strangers and being disappointed by Heartbreak Hill.

It cracked me up. I had spent years killing myself to run this time, and here at Boston I ran it having fun, because somewhere between Sacramento and Boston the pace had become normal. That was the goal I wrote after the 26-second failure. It took a few years to find out how completely it worked.

The best race of my life. Not the fastest. The best.

The Last One in the Door

One more thing, because the universe apparently keeps score too.

The next year, Boston announced the cutoff for the 2024 race: five minutes and twenty-nine seconds.

My margin, exactly, to the second. I was literally the last runner allowed into the field.

The race that once cut me by 26 seconds let me in by zero. I got my makeup Boston, and I ran it in 2024.

The Moral of the Story

So what did those 26 seconds teach me?

At the time, they were just a reading of my fitness on that day: I had no margin for error, and the second half of the race pushed me to my limit.

I missed my goal…to run Boston. Barely, but I still missed it, and it was the biggest athletic obstacle I’ve ever had to bounce back from in my life. So I learned from it. I made my adjustments, and I made sure it would never, ever happen again.

That is the invisible game.

The seven and a half minutes clearance in the fog was a result of playing the invisible game. So was the fitness to run qualifying pace like a normal long run. And so were two Boston Marathons.

That is what I meant last week when I called this the best argument for the invisible game that I know.

One more detail about this story.

I could analyze and improve my race because I built the training. Every tempo, every long run, had a reason I could explain. So when the result came back 26 seconds from my goal, I could walk back through the architecture and figure out exactly what was missing.

If I had been running somebody else’s training plan, this story ends in September of 2019. The plan would have barely missed, and I would never have known why, because you cannot understand a plan you didn’t build. A borrowed plan cannot explain its own failure, and the explanation of failure was the silver lining here.

That is why the book I have been mentioning in these newsletters is called what it is called.

Build, Don’t Borrow: The Distance Coach’s Guide to Training Architecture releases this Tuesday, July 28. It is everything I know about building your own training from the ground up, so that when a race goes sideways, you can figure out why and fix it.

If you have ever stared at a bad result with no idea what happened, I wrote it for you.

Some context for that number.

We had ten girls in the entire program. Six could run a 5K. We could not field a JV team. If you could cover 3.1 miles, congratulations, you were varsity. Our lineup was two seniors, two sophomores, and two freshmen.

The year before, that program qualified for State for the first time in forty years. So before the first day of practice, we named our goal: back to back. We’re going again.

And the season was cooperating. Top three at every meet. All season.

Then A&M.

Nineteenth.

I cannot offer you a bad-luck story, either. Nobody was sick. Nobody rolled an ankle. We raced badly. We raced scared. We looked like a team that did not belong in the conversation, and everyone watching knew it.

In our program, we have a rule for nights like that. We do not ask, “What did you do wrong?” Wrong points backward. It starts a blame conversation. We ask a different question: “What are you going to change?”

Every girl answered. Not something a teammate needed to change. Not the course. Not the weather. Something she would change.

Their answers were hard to hear, because these girls were doing everything I asked.

Which made my turn worse.

This is what I told a team of teenage girls, three weeks before District, with the whole season on the line:

“I’ve done something wrong with your training, but I don’t know what it is yet. I’ll figure it out.”

That was Friday morning.

I found the answer on Saturday. But to explain what I found, I have to tell you what I believed for the first twenty years of my coaching career. Because that is what I actually found, standing dead still in the middle of a road, eight miles into a long run.

The arrow

When I started coaching, I believed coaching was linear.

Here is the athlete at Point A. Here is where we want her in November, Point B. My job is the training plan that connects the two.

And to be fair to that arrow, everything on it is real. The mileage is real. The workouts are real. The splits, the schedule, the results. That is the visible game. You can watch every bit of it from the bleachers. It is the only game anyone ever taught me. Clinics teach it. Podcasts teach it. When two coaches meet at a gate, it is what we talk about. “What are y’all doing for summer mileage?”

For twenty years, whenever a season went sideways, I drew the same conclusion: I need a better arrow. Better workouts. A better plan.

And at A&M, that instinct showed up right on schedule.

But I was holding a good arrow. One of the best I had ever written.

The problem is that an arrow needs both ends to hold still.

Point B holds. The district meet is on the calendar, and it is not moving.

Point A starts moving the day training starts. The athlete at Point A does not stay at Point A. She does not even stay the athlete you think she is. The first three weeks of training change her. Which means week four is being applied to a different kid than the one you planned it for. And whatever week four does to her, week five inherits.

Training changes her. Recovery changes her. Success changes her, and failure changes her more. Then add everything you do not control. School. Family. Sleep. A growth spurt. Chemistry class.

And notice the strange part. The thing moving Point A is the arrow. The plan is what changes the athlete. You aim at a kid, and hitting her moves the target.

The better your plan works, the faster it stops fitting the kid it was written for.

Now put twenty kids on a roster. Twenty Point A’s, all moving, all in different directions, one shared Point B.

One arrow cannot point at twenty moving targets.

The two ends

So if the arrow is not the whole picture, what is?

Two things.

Up top: what you intend to build. Not the goal. The goal is a destination. “Back to State” was our goal. But “who does this team have to become to get back to State?” is a different question, and it has a construction answer. Maybe they have to get durable enough to handle three miles at 6:10 pace. Maybe they have to learn to race as a pack. Maybe you need five girls under twenty minutes. I call that the intended transformation.

That is Point B. And notice what just happened to Point B. It was never really the meet. The meet is just the day you find out whether you built it.

Down at the bottom: the team that is actually taking shape. Faster than you expected in one thing. Stalled in another. Carrying strengths and weaknesses that are not in your notes anywhere. I call that emerging reality.

That is Point A. And at A&M, mine was trying to tell me something I had not been listening to.

Your entire coaching life happens in the gap between those two points.

The other game

There is a name for the work that happens in that gap. Nobody puts it on the schedule. Nobody asks about it at the gate.

I call it the game within the game.

The visible game is played by everybody. Athletes, coaches, trainers, parents, the school. Its prize is the Impossible Goal, and the scoreboard settles it.

The invisible game has one player per side. The coach, and the season that happens by itself.

Because your athletes are going to become something this season no matter what you do. Train them or don’t. Plan or don’t. The season will transform them either way. Every program is running two candidate seasons at the same time: the one being constructed on purpose, and the one that happens by itself.

You are not playing against the coach on the other sideline. You are playing against that second season.

And it is a real game, because you can lose it.

Saturday

Which brings me back to that long run.

Saturday morning, I went out for twelve miles, alone, still carrying Friday morning’s promise. Somewhere in the middle, the answer stopped me cold. I stood still in the road.

All season, our race strategy had been simple: go get top-ten finishes. Race at the front. I believed in that strategy because I had proof. The year before, I watched my girls finish in the top ten. I had the results in a binder.

Standing in that road, I finally looked at this year’s team instead of last year’s results.

The girls who earned those top-ten finishes were now my three, my four, and my five.

My top two runners were my two freshmen. A year earlier, they were in middle school. They were not on anybody’s chart because they were not on anybody’s roster.

I did not have a team with top-ten runners. I’d had one. The year before. And I had kept coaching that team long after it stopped existing.

What I actually had was five girls who could all land between eleventh and twentieth. And that is not a weakness. That is a weapon. I just had not been aiming it at anything.

So we changed the race. Not the goal. The race.

One sentence: own eleven through twenty.

Three weeks later at District, our five scored fourteenth, fifteenth, sixteenth, eighteenth, and twenty-third. Nobody in the top ten. Second place as a team.

Two weeks after that, Regionals. Same race. Fourth place. Fourth qualifies.

State. Back to back.

We did not get more talented in those five weeks. We did not find a seventh runner. We finally ran the race that belonged to the team we actually were.

Two coaches, one parking lot

Here is the part of this story I keep coming back to.

Stand in that parking lot at A&M with me one more time, because there were two ways out of it.

Picture two coaches standing there. Same meet. Same nineteenth place. Same quiet bus.

One walks out knowing his kids are soft. They folded. They did not want it.

The other walks out knowing his design is wrong.

From the bleachers, those two coaches are identical. Same clipboard. Same result. Same drive home. Everything that separates them is invisible.

And one of them just lost his season. The other one is five weeks from State.

The invisible game gets played in parking lots, on long runs, in the truck on the way home. Nobody watches it. It decides everything.

What the game pays

The invisible game asks one question of every season: did anybody choose what the athletes became?

If you built the transformation on purpose, and you can explain why it happened, you keep it. You can build it again next year, with different kids.

If the season just worked out, that is not a system. That is luck. And luck does not repeat because you need it to.

This is the part of the game that took me longest to understand. I walked out of that parking lot with something better than a path back to State. I walked in one coach and walked out a better one. The explanation compounds. Judgment is the only trophy that does not graduate in the spring.

It is also the reason I spent two years writing Build, Don’t Borrow instead of publishing my training plan. A borrowed plan is somebody else’s arrow, aimed at somebody else’s Point A. The building is where the judgment comes from. That turned out to be the whole book, hiding inside one bad meet in October.

On Tuesday, I am telling this story from a stage at the THSCA convention, in front of a few hundred Texas coaches. If you are in the building, come find me. Ask me the question my own laws require me to answer: how did I know one bad meet was evidence instead of noise?

Short version: nobody blew up. One kid struggling is noise. Everybody struggling the same way at once is your design showing through.

When I started coaching, I thought this job was an arrow. I thought getting better meant better workouts and better plans.

Twenty years and one long run later, here is the whole job in one sentence.

Coaching is the continual reconciliation between intended transformation and emerging reality.

Hold your Point B. Read your Point A. And when they disagree, and they will, that is not the job going wrong.

That is the job.

Next week: the time I played both games myself and split them. I won the invisible game and lost the visible one by exactly 26 seconds. What those 26 seconds bought me is the best argument for the invisible game I know.

One athlete ran 350 miles over the summer.

Another ran 40.

Another ran zero and will confidently report 200 because teenagers occasionally treat honesty as an elective.

Fifteen freshmen are standing nearby. You know almost nothing about them. Middle-school times tell you who was fast three months ago. They do not tell you who trained over the summer, who has a history of shin pain, who can handle six days a week, or who is one hard workout away from disappearing.

Your new assistant is standing there too.

Athletic-period assignments were shuffled in July, and this is who you got. Maybe he is a football coach who has never attended a cross-country meet. Maybe she ran in college ten years ago but has never coached. Either way, there is nothing to hand this person.

No explanation of the training groups.

No map of the season.

No description of how the workouts progress.

No record of why you make the decisions you make.

Most of that exists in your head.

Your first meet is in two weeks.

Good luck, Coach.

So you do what the situation seems to require.

You divide the freshmen into groups by eyeball.

You write one workout with a few pace variations and hope it fits enough people.

You give the new assistant a stopwatch and tell him where to stand.

Then you begin collecting information the only way most programs know how: by watching what breaks.

By the second week, the athlete who claimed 200 summer miles strains a calf. The athlete who actually ran 350 miles is bored jogging with the group. A freshman who looked athletic on day one is complaining about her shins. Another freshman you placed in the slow group is clearly one of the best runners on the team.

The new assistant still asks you what to do every five minutes.

You are organizing practice, watching athletes, adjusting groups, explaining workouts, answering parents, handling injuries, and trying to figure out whether the entire plan needs to change before the first meet.

By the time you get home, practice is over.

Coaching is not.

You carry the whole thing into dinner, into the shower, and into bed.

And because all these problems appeared at the same time, they feel like separate problems.

The calf strain is an athlete-honesty problem.

The bored veteran is a grouping problem.

The freshman with shin pain is an injury problem.

The talented freshman in the wrong group is an evaluation problem.

The assistant is a staffing problem.

Your stress is a time-management problem.

That is how coaching problems usually arrive.

One at a time.

Visible.

Urgent.

Begging to be fixed.

The problem is that what you can see is not always the actual problem.

A symptom is not a diagnosis

A calf strain tells you something went wrong. It does not tell you what.

Maybe the athlete lied about summer training.

Maybe you had no reliable way to determine his current fitness.

Maybe the workout was appropriate for athletes who trained all summer and inappropriate for athletes who did not.

Maybe the progression advanced because the calendar said August rather than because the athlete had demonstrated readiness.

Maybe the strain was bad luck.

The injury is real. But “calf strain” is not a diagnosis.

It is a symptom.

The same is true of the new assistant.

You may conclude that the assistant is inexperienced, unmotivated, or simply not very helpful. But what exactly did you give that person to learn?

A workout on a whiteboard?

A few instructions before practice?

A collection of phrases that make perfect sense to you because you have lived inside the program for years?

The assistant may not be incapable.

The program may be impossible to learn.

That distinction matters.

Symptoms tell us where something hurts. They do not tell us why it hurts.

And when a problem creates urgency, coaches tend to treat the thing they can see.

A poor race leads to more intensity.

An injury leads to less volume.

Confused athletes lead to another meeting.

An overwhelmed coach downloads another planning template.

A weak assistant receives even fewer responsibilities.

Something visible changes, which feels like progress.

But activity is not the same thing as diagnosis.

One symptom can have several causes

Suppose three athletes develop lower-leg pain during the first month. The tempting response is to reduce the mileage for everyone.

That might be correct.

But the same symptom could have several different causes.

One athlete did not train all summer and increased volume too quickly.

Another trained consistently but is wearing shoes that should have been retired during the Obama administration.

A third has enough aerobic fitness to complete the workouts, but not enough structural strength to absorb the impact.

Same symptom.

Different causes.

The same thing happens with poor performances.

A team may struggle at the first meet because the athletes are tired from training.

Or because the opening pace was reckless.

Or because the groups were built from inaccurate information.

Or because the coach trained everyone as though they arrived on August 1 with the same preparation.

Or because it is the first meet and sixteen-year-olds occasionally do strange things when someone fires a gun.

The race result does not arrive with a diagnosis attached. The coach has to determine what the result means.

One cause can create several symptoms

Now look at the problem from the other direction.

Suppose your program has no dependable way to establish where each athlete currently stands. That one weakness can create several visible problems:

You place athletes in the wrong groups.

You give underprepared athletes too much work.

You give prepared athletes too little.

You discover injuries after they have already become serious.

You miss talented freshmen because they were placed with the wrong group.

You change the plan repeatedly because every new piece of information surprises you.

You spend the first month reacting to reality instead of working from it.

One underlying weakness.

Several symptoms.

This many-to-many relationship is why quick fixes are so unreliable.

Several causes can produce the same symptom.

One cause can produce several symptoms.

A change aimed directly at the symptom may provide temporary relief while leaving the condition underneath it untouched.

Then the symptom returns. Or it appears somewhere else.

The coach changes something else. The program accumulates changes without accumulating understanding.

That is the symptom-treatment trap.

The search for causes is not endless

At this point, diagnosis can sound impossible. If every symptom has several possible causes, where do you even begin?

Fortunately, the search space is not unlimited. Most recurring coaching problems trace back to one or more of nine places.

Not nine workouts.

Not nine training philosophies.

Nine questions about how the program itself works.

1. Does the program know what it is building?

Can you clearly state what the athletes or team should become?

Not merely the goal at the end of the season.

What capabilities must be built to make that goal possible?

When this is unclear, the program stays busy but drifts. Workouts happen. Meets happen. The calendar advances. But the parts do not form a coherent path.

2. Can the people involved see how the program works?

Does the reasoning exist anywhere outside your head?

Can an assistant understand the groups, progressions, priorities, and decision rules?

Can athletes connect today’s work to a larger purpose?

When the program is invisible, the head coach becomes the memory, interpreter, and operating manual.

3. Do you understand why your decisions should work?

Can you explain why a workout belongs where it does?

Can you name the assumptions behind the progression?

Could you replace the workout while preserving its purpose?

When the reasoning is borrowed or unclear, the coach owns the activity but not the logic behind it. That becomes a problem the moment reality stops matching the borrowed plan.

4. Do meaningful differences between athletes affect meaningful decisions?

The athlete who ran 350 miles and the athlete who ran zero are not the same athlete on August 1. Neither are the freshman who played soccer all summer and the freshman who has never trained consistently.

Treating them identically may be administratively convenient.

It is not coaching.

5. Can the program reliably see what is happening?

What tells you that an athlete is adapting?

What warns you that something is going wrong?

Are those signals available before the problem becomes obvious?

A system that cannot see reality has only two options: guess early or react late.

6. Does evidence support progression?

Why is the athlete ready for more?

Because three weeks have passed?

Because the next workout is already on the calendar?

Or because the athlete demonstrated the adaptation required to move forward?

Completing work and being ready for more work are not the same thing.

7. Can the plan change without losing its purpose?

August will not follow the plan.

Neither will September.

Athletes get sick. Weather changes. Meets move. Facilities disappear. Freshmen improve faster than expected. Veterans struggle.

A useful program must change without becoming random.

8. Can you turn information into a trustworthy explanation?

You may have splits, race results, conversations, soreness reports, attendance, and practice notes. That does not mean you understand what is happening.

Information is only useful when it can be combined into a story that remains accountable to the evidence.

9. Does the program learn over time?

What did last season teach you?

Where does that knowledge live?

What would disappear if an assistant left?

Does each freshman class enter a pathway that has been improved by the classes before it, or does every August begin another rebuild?

Those nine questions cover most of the places recurring coaching problems come from.

At first, it is tempting to call them root causes.

But that is not quite right.

These are not mistakes. They are properties.

A root cause sounds like one hidden defect waiting to be discovered.

Find it. Fix it. Problem solved.

Coaching systems are not that simple.

The nine areas above are better understood as properties the program either possesses or does not.

1. A healthy program has direction.

2. Its reasoning is visible.

3. Its coaches understand why the parts should work.

4. It responds to meaningful differences.

5. It can see what is happening.

6. Its progressions are supported by evidence.

7. It can adapt without losing the plot.

8. It can make sense of the information it collects.

9. It preserves learning over time.

Each property can exist in a healthy state or a faulty state.

When the property is healthy, it carries part of the program’s workload. When it is faulty, that workload does not disappear.

It transfers to the coach.

If the reasoning is visible, an assistant can learn and act.

If it is invisible, the head coach must explain and approve everything.

If the program can reliably see athlete response, problems can be addressed early.

If it cannot, the head coach compensates through constant vigilance.

If progressions are supported by evidence, the next step becomes defensible.

If they are not, the coach must rely on hope, memory, and anxiety.

This is why hardworking coaches become exhausted inside programs that appear organized from the outside.

The coach is carrying work the program itself should be carrying.

Healthy properties are built through repeated behavior

You cannot announce that the program now has better direction.

You cannot tell the staff to become more adaptable.

You cannot write “individualize more” on the whiteboard and call the problem solved.

Properties become healthy through repeated behaviors.

1. Define what you are building and use it to organize major decisions.

2. Get the program’s reasoning out of your head.

3. Compare what competition requires with what the athlete currently possesses.

4. Give every workout one clear job.

5. Plan the immediate work fully, but keep future work conditional.

6. Require evidence before increasing demand.

7. When you adjust, name the problem you are solving and the tradeoffs the change creates.

These are not motivational slogans.

They are habits that change how the program operates.

One behavior may strengthen several properties.

Getting the program out of your head helps assistants understand the work, preserves knowledge, and makes decisions easier to examine.

Requiring evidence before moving on improves progression, helps account for athlete differences, and forces the staff to pay attention to what is actually happening.

Giving every workout a job improves understanding, makes the plan easier to explain, and gives you a way to adjust when the original workout no longer fits.

There is no one-to-one formula.

Healthy programs are built through overlapping practices repeated until the system begins carrying more of its own weight.

The name for the whole structure

We have now described a program that:

knows what it is building,

understands the athletes standing in front of it,

connects meaningful differences to decisions,

explains why each part exists,

collects useful feedback,

requires evidence before progression,

adapts when reality changes,

shares its reasoning with the people expected to help,

and learns from one season to the next.

That structure has a name.

I call it training architecture.

Training architecture is not a prettier calendar.

It is not a training philosophy floating above the daily work.

It is not a collection of good workouts.

It is the connective structure between what you intend to build and the decisions, progressions, feedback, roles, and adjustments used to build it.

A training plan tells you what happens Monday.

Training architecture explains why Monday exists, who the work fits, what it should produce, how you will know whether it worked, and what can change without damaging everything around it.

That is the problem I worked through in Build, Don’t Borrow. I started with distance training because that was the problem directly in front of me: I had workouts, books, clinic notes, and plans, but I did not fully understand the structure connecting them.

Once that structure became visible, a larger problem appeared. Coaches also need ways to examine the decisions inside it.

What job does this workout perform?

What assumptions does this progression depend on?

What is different about this athlete?

What tradeoffs will this adjustment create?

What does the evidence actually support?

That is why I built the Run By Numbers Toolkit.

Not to make decisions for coaches.

To help coaches see the decisions they are already making more clearly.

August is an audit

August did not create the athlete who skipped summer training.

It did not create the unknown freshmen.

It did not create the new assistant.

It did not create the two-week deadline before the first meet.

August simply put enough pressure on the program to reveal what it could and could not do.

Could it establish where the athletes actually stood?

Could it let meaningful differences change the training?

Could it explain its reasoning to another coach?

Could it progress athletes based on evidence rather than the calendar?

Could it respond to new information without rebuilding everything?

Those are the questions underneath the symptoms.

So before you treat the calf strain, move the freshman, rewrite the workout, or decide the assistant is useless, pause long enough to ask:

What do we actually know?

What explanations remain possible?

What would help us distinguish between them?

The visible problem deserves attention.

But it may not be the problem.

It may be the first clue your training architecture has given you.

Two Sundays have come and gone without a newsletter. No warning, no explanation. If you wondered whether I’d run out of things to say about training, I understand. That’s usually what silence means.

This silence meant the opposite.

For the last two weeks I’ve been finishing the biggest thing I’ve ever built. Today you get to see all of it, before anyone else does.

But first, a confession about something I did to you back in June.

In the June 14 issue, I wrote a line I’d been carrying around for a long time:

You can borrow a workout. You can’t borrow a transformation.

And underneath it, almost in passing, I wrote that this is the line that sits underneath “build, don’t borrow.”

What I didn’t tell you is that Build, Don’t Borrow is the title of my book.

It’s been the title for two years. Every issue of this newsletter, the missing layer, the planning problem that isn’t one, the talent excuse, the plan that should come last, all of it has been me thinking out loud through pieces of the same argument. You’ve been reading the sketchbook.

On July 28, the building is done.

The book

Build, Don’t Borrow: The Distance Coach’s Guide to Training Architecture releases on Amazon July 28.

Twenty-seven chapters, built around the 23 questions every distance coach eventually asks and almost never gets a straight answer to. Real answers, not gestures. A few examples of what’s inside:

You’ll get the diagnostic I run before I plan anything: one 1600m time trial, converted into every training pace an athlete needs for the season. Not five tests. One.

You’ll get the Four Levers of Load, and you’ll see why volume, the number every coach watches, is only one of them, and why teams break in week six when a coach pulls two levers at once without knowing it.

And you’ll get the piece the whole book is built around: the PTG, a three-layer map with physiology on one axis, race paces on the other, and training roles connecting them. It’s the reason I can tell a parent exactly why her daughter is running mile repeats at 6:20 instead of racing pace on a Tuesday, and say it in one sentence. The system determines the purpose. The pace makes it executable.

It is not a book of my workouts. The world does not need another book of somebody’s workouts. It’s the architecture underneath them: why this piece goes here and not there, what holds weight and what’s decoration, and what to move when September breaks something.

Nineteen coaches read the manuscript before you heard a word about it. They left hundreds of margin notes, and their fingerprints made it a better book. One of them looked at his own program while he was reading and wrote this:

“Architecture is missing from my program, this describes it perfectly. Held together by hope.”

His program. Held together by hope. If you’ve ever coached a season like that, one good week from believing and one bad race from starting over, this book was written for you.

The Kindle edition is available for pre-order today. Paperback and hardcover go on pre-sale a few days before release.

You can also read the Introduction and the full first chapter right now, free. More on that at the bottom.

The drafting table

Here’s the problem with every training book ever written, including mine: you finish it, you’re convinced, and then the spreadsheet is still blank and practice is still coming.

The book teaches you to think like an architect. It can’t sit with you while you design.

So I built something that can. It’s called the Run By Numbers Coaching Toolkit: nine tools that walk through the same architecture as the book, using your athletes, your race times, your season.

Let me show you three of them, because “nine tools” means nothing until you see what one hands you.

The Capacity Profiler. You enter one athlete’s race times. It computes the ratios between them (the diagnostic from Chapter 6) and reads them against the balanced bands. You get the athlete’s profile: speed-dominant or endurance-dominant, fast or resistant, built to grind from the pack or built to close. You get the single highest-leverage gap holding them back, what closing it would look like in real times, and what all of it means for their training. Run it on your whole roster and you’ll know something about every kid that most coaches never learn about any of them.

The Workout Translator. You paste in a workout. One of mine, one of yours, one you found at a clinic in 2019. It tells you the architectural role that workout plays, what it actually develops (which is not always what you intended), the assumptions it quietly makes about the athlete running it, where it belongs in your season, what should come before and after it, which athletes it fits and which need it modified, how coaches commonly misuse it, and a decision checklist to run before you commit a Tuesday to it. Every workout you’ve ever collected suddenly has a spec sheet.

The Workout Modifier. You give it a workout and the athlete it wasn’t written for. It shows you which components are essential, the ones that define what the workout develops, and which are flexible. Then it hands you three modified versions that each preserve the adaptation, with the architectural reasoning attached. One workout, correctly translated for your varsity girl, your JV boys, and the freshman in his third week of running. Same purpose, three doses, zero guessing.

The other six work the same way at different altitudes: a single training role, a single week, an eight-week progression, the whole season designed backward from the goal.

Now, here’s what those tools are actually for, because it isn’t answers.

You know that coach. The one at the district meet who seems to carry the whole season in his head. Ask him why his kids ran hills on Tuesday and he doesn’t flinch, doesn’t cite somebody else’s program, just tells you what those athletes needed and why that was the way to get it. His athletes trust the plan because he can explain it. His assistants run their groups without hovering. When his team wins, everyone knows exactly whose thinking won.

That’s not a personality type. That’s a coach who can defend every piece of his program. The toolkit exists to make you that coach. It never hands you a plan and it never makes the call, because the day something you built wins a race, I want there to be no doubt about who built it. Your athletes, your reasons, your season. Yours to defend, and yours to win.

Every tool has a worked demo on the site. A real coaching scenario, start to finish, free, no account:

See the Run By Numbers Toolkit →

One thing worth knowing today: when the book launches July 28, the toolkit opens with it. Founding Coaches enrollment runs July 21 to 28, one week only, and founding coaches get the book included, bonus credits, and a live season-design call with me. The waitlist is on that same page if you want to be first through the door.

The front door

All of it lives in one place now: shawnsiemers.com

The book, the toolkit demos, a free interactive pace chart built from Chapter 16, and this newsletter’s new home base. I built the site the same way I’d tell you to build a season: every piece has a job, and I can tell you why each one is where it is.

Why am I telling you all this before anyone else?

Because there are 202 of you, and you were here first. Some of you have been reading since December, replying to issues, pushing back on ideas, telling me which paragraphs landed. This project got better because of that. Tomorrow I start talking about it on social media, and the noise will do what noise does.

But the first look belonged to you.

One more thing, and it’s the reason the timing matters.

If you’re coaching cross country this fall, the season you’ll live with in October is being decided right now, in July, before the first practice. You’ve read enough of this newsletter to know that filling the calendar isn’t the work. Deciding what your athletes are supposed to become, and building backward from that, is the work.

That’s the season I want to help you build. This time with more than a newsletter.

Start with the free chapter. It costs you an email address and fifteen minutes, and it will tell you whether the rest is for you:

Read the Introduction and Chapter 1 free →

And if you already know you want the drafting table, not just the blueprints:

See the Toolkit and join the founding waitlist →

See you Sunday. I have some catching up to do.

Shawn

You fill a calendar. Tempo on Tuesday, intervals on Thursday, long run Saturday. Phase the season, stack the weeks, taper at the end. An afternoon’s work and you’ve got something that looks like a program.

It took me years to figure out that the plan was never the hard part.

The hard part is the question sitting underneath it. The one I couldn’t answer for the longest time, even with a full calendar staring back at me: what is this athlete supposed to become by the end of it?

“Faster” isn’t an answer. Faster how. From what to what. By when. For which kid.

The plan is the part I built first. It should have been the last.

A plan is an answer. The question comes first.

When you pull a workout from a coach whose team won State, you’re borrowing an answer. Tuesday’s tempo is an answer. The 12-week progression a friend forwarded you is an answer.

What doesn’t come with it is the question.

That workout existed because another coach, looking at his own roster, decided what those athletes needed to become and built backward from it. The workout was the last thing he wrote down. The destination was the first thing he decided.

You get the answer. You don’t get the question. So when September comes and your number two runner picks up a stress reaction and you’re staring at the plan trying to figure out what to move, you can’t. You never knew why any of it was where it was.

I lived in that spot for years. It isn’t a planning problem. There were plenty of plans. It’s a destination problem.

You can borrow a workout. You can’t borrow a transformation.

This is the line that sits underneath build, don’t borrow.

A workout is portable. It’s a set of instructions for a body. Run this far, this fast, this many times, rest this long. You can copy it off a blog post and run it tomorrow.

A transformation isn’t portable, because it belongs to this kid. The freshman who showed up in August having never run a mile. The junior who’s fast but breaks down every October. The senior who’s done everything right for three years and is one good block from breaking 17 in the 5k. Each one is a different distance from where they need to be. Each one needs a different bridge built across that gap.

There’s no blog post for your roster.

The coach you borrowed from didn’t build a plan. He built a path for athletes who aren’t yours, toward a destination that isn’t yours, across a gap that isn’t shaped like your gap. Run his workouts on your kids and you’re running his answer to a question your athletes never asked.

The athlete is the thing under construction. Not the plan.

It’s easy to treat the athlete as the constant and the workout as the variable. The kid is who the kid is. Your job is to pick the right sessions and hope you chose well.

I had it backward.

The athlete is the variable. The athlete is the thing you’re building. The workout is just the tool you picked up to build it, and you can set it down and pick up a different one the moment it stops serving the build.

Treat the kid as fixed and you spend the season hunting for the workout that finally unlocks the talent you assume is in there.

Treat the kid as the thing being built and you spend the season turning whoever walked through the door into the team you need.

One of those depends on who shows up in August. The other one doesn’t.

Sorting isn’t the same as building.

There’s a quiet way a program can avoid the hard part without anyone deciding to.

Everybody runs the same workout. The kids who can handle it stay. The ones who can’t get hurt, or quit, or fade to the back and stop coming. By the end of the season, whoever’s left becomes the team.

Nobody designed that. It just happened. And it feels fair, because everyone got the same shot.

But nobody got built. They got sorted.

The talented ones were already talented in August. The season didn’t make them, it found them. And the ceiling on a program that runs this way gets set every year by whatever talent happens to walk in the door, because the program isn’t creating anything. It’s revealing who already had it.

I’m not pointing a finger here. I ran seasons like this myself before I understood the difference. From the outside it looks like coaching. The workouts are hard, the kids are tired, somebody’s winning. But strip it down and the season mostly did the work of a sieve, and whoever came through was likely coming through anyway.

A transformation is the opposite of a sieve. It’s a bridge. You’re not finding out who can already get across. You’re building the thing that carries the kid who couldn’t.

The body shows you why borrowed plans break.

This is the part you feel on a Tuesday.

Take a kid who’s never trained and put them on the same schedule as your varsity. For about three weeks it looks like it’s working. Their breathing gets easier. The easy days stop feeling hard. They feel fitter, because they are.

The aerobic system adapts fast. Heart, lungs, blood volume. Two or three weeks and a new runner feels like a different athlete.

But bone, tendon, connective tissue, all of it adapts on a timeline measured in months, not weeks. And it doesn’t care how good the lungs feel.

So the kid feels fit and pushes harder. Or they look fit, so they get more. The cardiovascular engine is writing checks the chassis can’t cash. By week six, they’re hurt.

That injury wasn’t bad luck. It was a transformation nobody designed. The borrowed plan assumed a body that could already absorb the load. The kid didn’t have that body yet. The whole point was to build that body first, and the plan skipped the step, because the coach it came from already had athletes who were past it.

You can’t borrow your way around biology. The bridge has to be built for the kid in front of you, not the one in someone else’s program.

The first decision is a destination, not a drill.

So if the plan is the last thing you build, what’s the first?

A destination. Something specific enough and demanding enough that the whole season has a reason to exist.

Not “let’s have a good year.” Not “let’s compete for Districts.” Those sound fine in August and have no teeth by October, when the weather’s turned and the meets get harder and a kid is standing on a course in the rain wondering why they’re out there. A feeling can’t answer that kid. A destination can.

The destination I mean is the one that makes you a little nervous the first time you say it out loud. The one that asks your team to become something they currently are not.

That word is the whole thing. Become. It assumes the team in front of you isn’t yet the team you’re describing, and that the season is the machine that closes the gap between the two.

That’s the transformation. Everything else in the architecture, the paces, the phases, the weekly pattern, the taper, the way you bring a brand-new runner along, all of it is structure in service of that one word. Built backward from who these athletes have to become.

Decide that first and every later decision has an address. Why this workout, this day, this week? Because of where we’re going.

I wrote a whole book about the questions underneath this one. Twenty-three of them.

The destination is the first one. Every other answer gets built backward from it.

The plan was the easy part. It always was.

The hard part, the part you can’t borrow, is deciding who you’re building.

Build, Don’t Borrow is coming soon. This is the ground it stands on.

At a lot of programs, losing three off the front of your lineup is the start of a rebuilding year. The kind of season where you tell the parents to be patient and you quietly lower the expectations.

That didn’t happen. In 2025, that team went to State.

Two of the three girls who stepped into those varsity spots were freshmen. Freshmen. They weren’t transfers, and they weren’t a lucky class that showed up fast. They had been running with me for two years already, since before they reached high school. The third was a sophomore who’d spent the prior season in my development group, mostly out of the spotlight, getting built. When the seniors left, there was no hole to fill. The next group just slid forward. They’d been getting ready for years.

That is not luck. That is architecture.

* * *

Last week I told you about Josh.

The freshman who came in fast, got loaded like a varsity runner, and was out of the sport inside of two years. I told you that was one hundred percent my fault. And I promised you there was another way to bring a new runner into a program.

This is the other way.

* * *

There are two ways to run a program. I think most coaches are running one of them without ever having decided to.

The first way is natural selection. It’s the default, and it’s everywhere. Everybody does the same workout. The kids who can handle it move up. The kids who can’t get hurt, or quietly fade to the back until they disappear. The coach doesn’t plan any of that. It just happens. At the end of the season, whoever is still standing becomes the team.

It feels fair because everyone got the same shot. That’s exactly why it’s so easy to keep doing.

But a natural selection program isn’t developing anyone. It’s sorting them. It takes the kids who walked in with talent and reveals which ones had it. The program never built that talent. It just held the door open and waited to see who could get through on their own.

Which means the program is only ever as good as the raw material that shows up. A great freshman class becomes a great senior class. A thin one becomes four years of mediocrity. The coach didn’t change. The system didn’t change. The only thing that changed was the kids who walked in the door.

The second way is a pipeline.

A pipeline is a decision to build the runner instead of waiting to discover them. New athletes get their own pathway. Not a different sport, not a lesser program. The same structure as everyone else, scaled to what their bodies can actually absorb right now. They run the same workout as the varsity kids, on the same days, with the volume and intensity dialed to where they are.

It’s more work. You’re running more than one plan at once, tracking different kids against different benchmarks. And you’re holding a talented freshman back when every instinct says turn them loose.

But the payoff is the thing natural selection can never give you. A pipeline manufactures contributors. It doesn’t need the right kids to walk in the door, because it builds the right kids out of whoever does.

That’s the whole difference. One program filters its runners. The other builds them. And that single choice is the difference between a program with a two-year memory and a program with a two-year future.

* * *

So how do you build a runner instead of filtering for one?

You start by getting one thing straight. A new runner doing less is not doing a worse version of the workout. They’re doing the right version.

Think about how medicine gets dosed. A 200-pound adult and a 60-pound kid can take the exact same drug. They do not take the same amount. Give the kid the adult dose and you haven’t “challenged” them. You’ve poisoned them. Give the adult the kid’s dose and you haven’t been “careful.” You’ve done nothing at all.

Training works the same way. The workout is the medicine. The dose is how much of it a particular body can take right now and adapt to.

When my varsity girls run a hard interval session, my new runners are on the same track, on the same day, running the same session. They’re just running the dose that fits them. Fewer reps and more rest, at a pace they can hold. Same medicine. Different amount.

That distinction sounds small. It is not. Because the new runner isn’t standing off to the side doing the “easy version” while the real team does the real work. They’re doing the work. Their work. The version that’s going to make them better the fastest, given where they are today. And they know it.

Remember those two freshmen who went to State?

I didn’t meet them as freshmen. I met them years earlier, before they had ever set foot in the high school. They ran with us over the summers. I gave them workouts, but I kept their mileage low and spent that time building strength and speed instead of volume. They went off and ran junior high cross country and track, and I kept guiding the training from a distance.

By the time they showed up as freshmen, they already had a base most kids don’t have until they’re juniors. And I still didn’t turn them loose. They’re fourteen. I kept the mileage conservative. They ran the varsity workouts, at a lower volume. The right dose.

Two years of that, and they weren’t fragile freshmen hoping to survive a season. They were ready to score at State.

That’s the part that’s hard to feel when you’re standing on the track in August looking at a kid with a Ferrari engine. Building is slow and patient. It does not produce a hero in September.

It produces a sophomore who’s a beast.

* * *

There’s one more piece, and it’s the one I think coaches miss the most. It has nothing to do with physiology.

A new runner who shows up in August is not a runner. They’re a person who signed up for a team.

That sounds like a minor distinction. It’s the entire game. A kid who believes “I am a runner” will tolerate the boring weeks and push through the months of slow work that building a body requires. A kid who still thinks of themselves as “someone trying this out” will quit the first time it stops being fun. In distance running, that’s about day four.

You cannot talk a kid into believing they’re a runner. I’ve tried. It doesn’t take. The identity gets built the same way the body does. Slowly, out of evidence.

The evidence is small and specific. I showed up every day this week. I ran twenty-five minutes without stopping for the first time in my life. The bar I could barely squat in August has forty pounds on it now. The coach called me out in front of the team for something I did right. The seniors know my name.

None of that is dramatic. All of it is identity being assembled, one piece at a time.

And this is why the dose matters more than coaches realize. When you put a new kid in a workout they can’t complete, you don’t toughen them up. You hand them evidence that they don’t belong. They watch the varsity kids finish the session and they think, that’s not me. I can’t do this.

But when the dose fits, they finish. They finish the same session as everyone else, scaled to them, and they finish it well.

They leave practice having succeeded, not having survived.

Do that four days a week for a season, and you don’t just have a fitter kid. You have a kid who has quietly decided they’re a runner. And a kid who has decided they’re a runner is the most coachable athlete you’ll ever have.

* * *

I’ll leave you with the same question I ask myself every August.

Look at your freshmen. Not the varsity. The brand-new kids who showed up three weeks ago and can barely finish a warmup.

In two years, which of them will score for you?

If you can point to them right now, by name, you have a pipeline. You already know who’s coming, because you’re the one building them.

If your honest answer is “I don’t know yet, we’ll see who sticks around,” then you don’t have a pipeline. You have natural selection. You’re waiting to find out which kids can build themselves, and quietly calling the ones who can’t a fact of life.

One of those answers is a program. The other is a roster that craters the day your seniors graduate.

I coached the second way for years. I lost a kid named Josh to it.

* * *

You don’t have to.

A couple of years ago, I started writing all of this down. How the onboarding actually works. How the entire program fits together so that no season rests on getting lucky in August. Everything I know about building runners instead of filtering them.

It turned into a book. It’s called Build, Don’t Borrow: The Distance Coach’s Guide to Training Architecture, and it comes out this summer.

If you want to know when it’s ready, the link is below.

https://shawnsiemers.com/build-dont-borrow

That’s it. No pitch.

There’s a kid on your roster right now who came in fast and looks like a gift. You don’t have to lose that kid the way I lost Josh.

You can build them instead.

I don’t use the word athletic for new cross country kids. Most of them show up soft, or slow, or both. And that’s fine. That’s the job. You build them.

This one was different. We’ll call him Josh.

Josh was fast out of the gate. Not “promising freshman” fast. Actually fast. Inside of a month he was running well enough to be my number seven. A varsity spot, as a freshman, in his first season. I couldn’t believe my luck.

By October, he was broken.

Nothing dramatic. Nothing you could point to on an X-ray. He just came apart. The speed left. The endurance left. He went from holding a varsity spot to fighting to finish races. At the District meet he couldn’t crack the top ten in the freshman race.

The freshman race.

A year later, he was out of the sport.

For a long time I told myself a story about Josh. That he was an early bloomer who hit his ceiling. That some kids just flame out. That it was one of those things.

That story was a lie. What happened to Josh was one hundred percent my fault, and it took me years to understand exactly how I did it.

* * *

Here’s the part that should bother you.

What happened to Josh happens in every program, every year, and almost nobody calls it what it is.

A new kid comes in. Maybe they’re fit from another sport. Maybe they’re just eager. They line up for the same workouts as everyone else, run them as hard as they can, and for a few weeks it looks like it’s working. Then somewhere around week six, they fall apart. They get hurt. Or they get discouraged and quietly stop showing up.

And the coach shrugs and calls it natural selection.

I get why. It feels true. You gave everyone the same workouts and the same chance to prove themselves. Some kids rose to it. Some didn’t. That’s just running, right? The sport thins the herd.

I believed that about Josh for years. It let me off the hook.

But natural selection isn’t a training philosophy. It’s what you call the wreckage when you don’t have one.

* * *

The priority with a new runner is not fitness.

It’s structural resilience.

That sentence took me a decade of coaching to understand, and it’s the thing I most wish someone had told me before I ever met a kid like Josh.

Because back then, I didn’t understand what was actually happening inside a new runner. When that kid gets faster in their first month, two completely different things are going on in their body. And they are happening at completely different speeds.

* * *

The first thing that adapts to running is your engine.

Your heart and lungs, and the blood moving through them. The aerobic system. Start jogging a few days a week and within two or three weeks it responds. Breathing gets easier. Easy paces stop feeling easy and start feeling slow. The engine is eager. It wants to grow, and it grows fast.

That’s the part everyone can see. It’s the part that feels like progress, because it is.

But there’s a second system, and it runs on a completely different clock.

Your bones. Your tendons. Your ligaments. The connective tissue that holds the whole machine together. Call it the chassis. The chassis is what absorbs the pounding. Every stride is a small collision with the ground, and a new runner takes thousands of them in a single practice.

And the chassis does not adapt in three weeks.

Tendons need months of repeated, gradual loading to get stronger. Bone takes twelve to sixteen weeks just to show a meaningful change in density. None of it is fast. None of it is visible. You can’t watch a kid’s tendons getting tougher the way you can watch their mile time drop.

This is where it goes wrong, and it’s worth slowing down for.

The engine adapts faster than the chassis can keep up with.

The kid feels fitter, because they are. Their aerobic system is responding right on schedule. So they push harder. Or you see the fitness and pile on more. Either way, the load goes up to match the engine.

But the chassis is still months behind. It is being asked to cash a check the engine wrote, and it doesn’t have the money yet.

That is not a toughness problem. It is a timeline problem. And by about week six, the bill comes due. Shin splints. A stress reaction that wasn’t there in September. The injury list for new runners is long, but the mechanism underneath it is almost always the same.

Now look back at Josh.

Josh wasn’t an early bloomer who hit his ceiling. Josh had a Ferrari engine bolted to a chassis that had been running for one month. I saw the engine, called him my number seven, and loaded him like a varsity athlete. His aerobic system could handle it. Everything else could not.

I didn’t lose Josh to natural selection. I lost him to a mismatch I didn’t know existed, and a training plan that treated a fourteen-year-old’s first season like it was his fourth.

* * *

I think about Josh a lot.

Not because he was the most talented kid I ever coached, though he might have been. I think about him because he is the clearest proof I have that talent was never the thing that needed protecting. The engine was never my problem. I had the engine. What I didn’t have was a plan that respected the chassis.

And babying him wasn’t the answer either. Timid coaching would have been its own kind of failure. The answer was to be precise. To understand that the kid who looks ready in August is not the same as the kid who is ready in August, and to train that difference on purpose.

I know that now. I didn’t know it then. Josh paid for what I didn’t know.

There are really only two ways to bring a new runner into a program. One of them produces a lot of Joshes. The other one is the reason that, years later, I can graduate three varsity seniors and sleep just fine.

Most coaches have never sat down and consciously chosen between the two. I hadn’t, back when it counted.

Next week I’ll show you the choice, and the system that turns a rebuild year into nothing more than a transition year. It’s the difference between a program that filters runners and a program that builds them.

It doesn’t matter if it’s a high school 3200m on a Friday night in March…or a marathon on a Sunday morning in November. Youth track, college cross country, masters 5k. The pattern shows up everywhere.

Watch the first finishers come through.

There’s something almost unfair about the way they look. Loose. Efficient. Quiet footfalls. Their cadence is HIGH and their ground contact time is LOW. They’re not pounding the surface…they’re skimming it. Each foot lands underneath the hip, loads for a fraction of a second, and releases. Over and over. Like a spring that never runs out of energy.

They look like they could go another mile.

Now watch the middle of the pack arrive.

The effort is visible now. You can HEAR it. Breathing has changed. Shoulders are climbing toward ears. Arms are starting to drift wide of the body. The stride is getting longer. Reaching forward instead of pushing back.

Speed is dropping. Work is increasing.

Then the back of the pack comes through.

Same race. Same distance. Same day. But these runners are working TWICE as hard to go HALF as fast. Something has broken down completely…and here’s what many coaches miss.

It didn’t break down at mile two.

It was broken before they ever crossed the start line.

Watch their feet.

That’s all I’m asking you to do. Just watch their feet.

The leaders are landing midfoot. Right underneath their center of mass. The foot strikes, the Achilles loads, the calf fires, and the athlete is already into the next stride before you can blink. There is ZERO wasted motion in that exchange.

The runners at the back are landing on their heels. Way out in front of their body. Every single stride begins with a braking force…like driving with one foot on the gas and one foot on the brake. The arms are flying outside the elbows. The torso is rotating left and right trying to compensate for the imbalance below.

The whole system is fighting itself.

And they have NO idea.

The finish line doesn’t lie.

Once you’ve seen a hundred finishes, you’ve probably noticed something. Something that once you see it, you can’t unsee it.

I’m sure you don’t need me to tell you that some kids are more talented than others. That’s real. But if you’ve filed what you just read under “genetics” and moved on…I want you to stay with me for a few more minutes.

Because here’s what I eventually figured out after nineteen years of standing at finish lines, watching workouts, filming strides, and timing splits down to the hundredth.

The gap between the front of the pack and the back of the pack is not just a FITNESS gap.

It’s a SKILL gap.

And skills…can be taught.

That changes everything.

If the problem is genetics, you’re a talent scout. You find the right kids, and you develop what they brought to you. Some years you have it. Some years you don’t. You’re at the mercy of your enrollment numbers and your feeder program and whatever ninth grader walks through the door in August.

But if part of the problem is SKILL?

Now you’re a coach.

Now you have something to work with regardless of who shows up.

That’s what this piece is about. Not a drill. Not a shoe recommendation. Not a technique checklist you laminate and hang in your locker room.

It’s about understanding WHY the finish line looks the way it looks…and what you can actually DO about it starting on day one with your newest runner.

Stay with me. This is where it gets useful.

What the Finish Line Is Actually Telling You

Let’s start with the heel strike.

When a runner’s foot lands in front of their center of mass…they are braking. Every. Single. Stride.

Think about what that means over the course of a 3200m race. That’s roughly 1,400 to 1,600 foot strikes depending on the athlete’s cadence. And if every single one of those foot strikes begins with a braking force, you are asking your athlete to overcome their own momentum 1,500 times before they cross the finish line.

No wonder they look the way they look at the end.

The physics are simple. When the heel strikes first, the leg is extended out in front of the body. The foot is dorsiflexed. Toes up, heel down. That position creates what biomechanics calls an impact transient…a sharp spike in ground reaction force that travels up through the heel, through the ankle, through the knee, through the hip.

Your athlete feels it as pounding.

You hear it as noise.

That slapping sound you hear from the back of the pack? That’s not effort. That’s inefficiency announcing itself on every stride.

Now watch what happens with the midfoot landing.

The foot arrives underneath the hip. Not in front of it. UNDERNEATH it. The ankle is in a neutral position. The foot is flat or slightly forefoot-loaded. And the moment it contacts the ground…the Achilles tendon loads like a spring.

Here’s where it gets interesting.

The Achilles tendon is one of the most powerful elastic structures in the human body. When it loads correctly it returns somewhere between 93 and 97 percent of the energy stored in it. Almost FREE energy. The athlete didn’t have to generate that with muscle. The tendon did it.

But it only works if the foot lands in the right place.

Land on the heel and you’ve bypassed the spring entirely. You’ve turned a biological masterpiece of elastic energy into a simple collision between bone and ground.

1,500 times per race.

And that’s just the foot strike.

The Brake You Didn’t Know You Were Pressing

Now let’s talk about what heel striking does to everything ABOVE the foot.

This is the part most coaches miss completely.

When you watch a runner whose arms are flying wide… whose hands are crossing the midline of their body… whose torso is rotating left and right with every stride… your first instinct might be to coach the upper body.

Relax the arms. Drive the elbows back. Quiet the hands.

And those cues aren’t wrong exactly.

But they’re treating the symptom instead of the cause.

Here’s what’s actually happening.

When a runner heel strikes and that braking force hits… the body has to compensate. The momentum that was moving FORWARD has been interrupted. The athlete’s center of mass has to recover. And the body does what bodies always do when they need to find balance…

It looks for it somewhere else.

The arms swing wide to counterbalance the rotational forces coming from below. The torso twists to try to maintain forward momentum despite the interrupted stride. The shoulders rise because the whole system is working harder than it should be just to keep moving in a straight line.

It looks like an arm problem.

It’s a FOOT problem.

Fix the landing… and watch how much of the upper body chaos resolves on its own. Not all of it. But enough that you’ll stop coaching arms and start coaching feet.

That’s the shift.

And here’s what makes this particularly important for distance runners specifically…

Sprinters can get away with a lot of mechanical inefficiency because their races are short. A 100m runner might take 45 strides. Inefficiency in 45 strides is survivable.

Your 3200m runner takes 1,500 strides.

Your cross country runner in a 5k takes somewhere between 3,000 and 3,500 strides depending on their height and cadence.

Inefficiency that costs you one percent per stride is CATASTROPHIC over a 5k.

The athletes at the back of the finish line aren’t just less fit. They are paying a mechanical tax on every single stride… and by the time they reach the finish line they are BROKE.

Running Is a Skill

I want you to sit with that for a second.

Not a given. Not a reflex. Not something kids arrive at your program already knowing how to do.

A SKILL.

And I know what you’re thinking. Everyone runs. Kids have been running since they were toddlers. By the time they show up at your first practice in August they’ve been running for fifteen years. How is running a skill they haven’t learned yet?

Here’s how.

Toddlers run on their forefoot. Watch a two year old chase a dog across the backyard. They’re up on their toes. Light. Quick. Their little legs are turning over fast and their arms are pumping and they look like tiny natural runners.

Then something happens.

They grow up. They start wearing heavily cushioned shoes with a thick heel. They sit in classrooms for seven hours a day. They walk on flat surfaces everywhere they go. And slowly… without anyone noticing… the natural movement pattern gets buried under years of modern life.

By the time they show up at your program they’ve been heel striking in cushioned shoes for a decade.

And nobody ever told them there was another way.

That’s not their fault. That’s just what happened.

But here’s the part that matters for YOU as their coach…

It means the pattern can be changed.

Skills can be learned. Skills can be taught. And more importantly… skills can be COACHED.

Which means the runner standing in front of you on day one… heel striking, overstriding, arms flying, torso rotating… is not a lost cause.

They’re a beginner.

And beginners need a teacher.

What Skill Acquisition Actually Looks Like

This is where coaches get impatient. And I understand it. You have a season to build. You have workouts to run. You have a meet schedule that starts in six weeks and a roster full of kids who need mileage.

The midfoot landing feels like something you teach once at the beginning of the year and then move on from.

It isn’t.

Here’s what it actually looks like.

You introduce the concept on day one. You explain what you’re looking for. You do the drills. The kids nod. Some of them try it. A few of them get a feel for it immediately and you think… great, we’re done.

You’re not done.

Week two you’re watching practice and half the kids are back to heel striking the moment the pace picks up. The new pattern hasn’t overwritten the old one yet. The old pattern is wired in deep… years of repetition deep… and the moment the athlete stops consciously thinking about it, the brain defaults back to what it knows.

So you cue them again.

Week three. Same thing. You’re on the infield watching intervals and you see it happening and you say something and they adjust mid-rep and then drift back again before the next one starts.

So you cue them again.

This goes on longer than you want it to.

And then one day… something changes.

You’ll know it when you see it. The stride quiets down. The cadence picks up almost imperceptibly. The arms settle. There’s a smoothness to the movement that wasn’t there before. It doesn’t look like they’re thinking about it anymore… because they’re NOT thinking about it anymore.

The pattern has been overwritten.

And they’ll come to you after practice and say something like… “Coach, something felt different today. I don’t know what it was, but my legs felt easier.”

THAT’S the moment.

That’s what you’ve been waiting for. That’s the skill locking in. And when it does…watch their times. Because the mechanical tax they’ve been paying on every stride just got a lot cheaper.

Be patient with this process. I know that’s hard when you’re staring down a six week pre-season. But you are not just building fitness right now.

You are building a runner.

And building a runner takes longer than building a fitness base…but it lasts a lot longer too.

The fitness you build this fall will fade over the winter.

The stride they learn this fall…they’ll carry for the rest of their running life.

That’s worth the patience.

What You’re Actually Doing on Day One

So what does this look like in practice?

Before I give new runners mileage…before I give them a workout…before I tell them anything about training paces or race strategy or what a tempo run is…

I teach them how to run.

Not a lecture. Not a PowerPoint. Not a handout about biomechanics.

I take them to the track and I watch them run a lap and I see what I’m working with. And almost without exception…the new runners are heel striking. Every one of them. Because that’s what happens when a kid grows up in modern shoes on flat surfaces without anyone ever teaching them differently.

Then we go to work.

Two Drills. That’s It.

I want to be clear about something before we get into this.

I am not giving you a twelve drill progression. I am not giving you a technique overhaul program that takes forty five minutes of practice time three days a week. I am not asking you to turn your distance practice into a sprint mechanics clinic.

I’m giving you two drills.

Two drills done consistently…with intention…over the course of a full season…will change the way your athletes run more than any fitness block you’ve ever built.

That’s a strong statement. I mean it.

Here’s the first one.

The Wicket Drill

You need cones. The small ones. One inch. The kind that looks like little orange pucks that you can buy in a bag of fifty for twelve dollars.

Set them up in a straight line down the track. Spacing depends on the athlete’s height and natural stride length…but a good starting point is about five and a half to six feet apart for most high school distance runners. Close enough that they CANNOT overstride. Close enough that landing on the heel in front of the body becomes physically awkward.

That’s the whole point.

The cones don’t teach the midfoot landing by telling the athlete what to do. They teach it by making the heel strike impossible to sustain comfortably. The athlete has to shorten the stride. They have to increase their cadence. They have to get the foot underneath the hip because there’s literally no room to put it anywhere else.

Constraints teach what cues can’t.

Here’s exactly how I run this drill.

Thirty meters of wickets. SPRINT through them. Not a jog. Not a stride. A sprint. I want the athlete moving fast enough that the mechanics are being tested under real neuromuscular demand…not rehearsed at a comfortable pace where anyone can look good.

Then ten more meters of open sprinting after the last cone.

No wickets. Just the pattern they just built…carried forward at full speed.

THAT ten meters is the whole point.

Because what I’m after isn’t pretty wicket running. I’m after transfer. I want to see whether the pattern they found inside the cones survives the moment the cones disappear. Whether the foot still lands underneath the hip when there’s nothing forcing it to. Whether the cadence stays high when the constraint is gone.

Sometimes it does. Sometimes it doesn’t yet.

Either way…I learn something.

Then they walk a full lap around the track. Full recovery. Not a jog. A WALK. Because this is not a conditioning workout. This is a skill session. And skill acquisition under fatigue is just practicing the wrong pattern faster.

We do this ten to twelve times in one workout.

Ten to twelve sprints through thirty meters of wickets…ten meters of open running after each one…a full lap walk between every rep.

By rep eight or nine you will start to see something happen. The pattern consolidates. The noise goes away. The stride that looked forced and mechanical in rep two starts to look…natural. Easy. Like it belongs to them.

Film rep two and rep ten side by side.

Show them the difference.

Watch what happens to their motivation for the rest of the season.

What About Your Veteran Runners?

Here’s where it gets really interesting.

Once an athlete has the skill…you don’t retire the wickets. You don’t pack them away in the equipment shed until next August when the new kids arrive.

You put them in the MIDDLE of workouts.

Think about what you’re asking a runner to do when they’re three quarters of the way through a hard tempo mile. They’re fatigued. Lactate is building. Their brain is looking for shortcuts. And the first shortcut the body reaches for under fatigue is the old pattern…the wired-in pattern… the one that was there before you ever started teaching.

Heel strike. Overstride. Let the arms go. Survive.

So what do I do?

I put the wickets down at the 250 meter mark of a 400 meter rep.

I put the wickets in the middle of a tempo mile.

Not at the start when they’re fresh and focused and running with intention. In the MIDDLE. When they’re working. When it’s hard. When the pattern is most likely to break down.

Because that’s the only place that matters.

Running through wickets at the beginning of practice when everyone is fresh is a rehearsal. Running through wickets at the 250 meter mark of your sixth 400 rep at 5k pace…THAT is a test. And passing that test…maintaining the pattern under real race-level demand…is what turns a skill being learned into a skill that’s owned.

Your veterans don’t need the wicket workout anymore.

They need the wickets to show up somewhere they don’t expect them.

Because once you have the skill…the work becomes keeping it.

And the finish line in October will tell you whether you did.

Barefoot Strides

The second drill is simpler. And for some athletes it’s more powerful than the wickets.

Find a patch of grass. Short grass. A football field works perfectly. An infield works. Anywhere the surface is soft enough that running barefoot is comfortable but firm enough that they can actually run.

Take the shoes off.

Then run.

That’s it.

I know that sounds too simple. But here’s what happens the moment a runner’s foot meets the ground without thirty millimeters of foam heel cushion between them…

The body figures it out IMMEDIATELY.

You don’t have to say a word. You don’t have to cue the midfoot landing. You don’t have to remind them about cadence or ground contact time or elastic energy return.

The nervous system already knows what to do. It’s been waiting under all that foam for years.

Landing on a heel without cushioning HURTS. Not injurious hurt…just immediate, honest, unmistakable feedback that says “that’s not right.” And the athlete adjusts. Instantly. Without coaching. Because the ground itself is doing the teaching.

Four to six strides. Easy effort. Focused attention.

Then put the shoes back on…and run a stride immediately after.

What you’re looking for is transfer. Does the pattern they just found barefoot carry over into the shoe? Sometimes it does right away. Sometimes it takes a few sessions. But over time…the barefoot stride recalibrates what the shod stride feels like.

They start to recognize the difference from the inside.

And that internal recognition…that felt sense of “this is right” versus “this is wrong”…is worth MORE than any external cue you will ever give them.

One important note on this drill.

Barefoot running is a TOOL. Not a training philosophy. Not a lifestyle. Not a reason to throw away their shoes and run fifty miles a week on the track in socks.

I’ve seen coaches go too far with this. They read something about barefoot running being natural and they start pulling kids out of their shoes for long runs and tempo workouts and then wonder why they’re dealing with stress reactions in November.

Use it as a diagnostic. Use it as a reset. Five minutes at the beginning of practice twice a week is plenty.

The shoes go back on. Every time.

The Mistakes That Will Slow You Down

Now let’s talk about what NOT to do. Because there are three mistakes I see coaches make with this…and any one of them can derail the whole process.

The first one is overstriding cues.

When you tell a runner to “run tall” or “drive the knee” or “push off harder”…you are often accidentally encouraging a longer stride. And a longer stride for a heel striker means the foot is landing even FURTHER in front of the body than it already was.

You meant to help. You made it worse.

Watch your language. The cues that work for midfoot landing are about QUICKNESS not length. Quick feet. Light contact. Fast turnover. Short and fast beats long and slow every single time for distance runners.

The second mistake is shoe interference.

Not all running shoes are created equal for this work. A shoe with a twelve millimeter heel-to-toe drop is literally built to encourage heel striking. The geometry of the shoe tilts the foot forward…which means the heel is the lowest point…which means it hits first.

You don’t have to put your whole team in zero drop shoes tomorrow. That’s a recipe for Achilles problems and calf injuries and angry parents.

But it’s worth knowing. And it’s worth having a conversation with athletes who are deeply committed heel strikers about whether their shoe choice is working against their mechanics.

A four to six millimeter drop shoe is a reasonable middle ground for most high school distance runners. Enough cushion to protect developing tissue…low enough drop to stop fighting the foot strike you’re trying to build.

The third mistake is expecting it to happen fast.

I already told you this. But I’m telling you again because it’s the one that gets coaches every year.

You will teach this in August. You will see progress in September. You will think you’re done in October. And then you’ll watch your athlete heel strike through the back half of a hard workout in November and wonder what happened.

Nothing happened. This is just how skill acquisition works.

The pattern is not permanent until it’s permanent. Until it runs on autopilot under fatigue…under race pressure…under the conditions that matter most…it is still being built.

Keep cueing. Keep drilling. Keep watching.

The day it locks in is coming.

You’ll know it when you see it.

The Finish Line Again

Go back to where we started.

The finish line of a distance race. Any distance race. Any level. Any time of year.

You’ve watched hundreds of them. Maybe thousands. And now you can’t unsee what you know.

The leaders aren’t just more talented. They aren’t just more fit. They aren’t just running on better genetics or better lungs or better everything.

They’re running on a skill that somebody taught them…or that they stumbled into on their own…or that their body figured out over years of high mileage until the inefficiency became too expensive to sustain.

However they got there…they got there.

And the runners at the back?

They’re not lost causes. They’re not slow because slow is what they are. They’re paying a mechanical tax on every single stride…3,000 times in a 5k…and nobody has ever shown them there’s another way to run.

That’s not a talent problem.

That’s a COACHING problem.

And coaching problems have coaching solutions.

You now know what to look for. You know why the finish line looks the way it looks. You know what’s happening at the foot…what it does to everything above the foot…and why fixing it requires the patience of someone who understands that skills aren’t installed in a single practice.

They’re built.

Rep by rep. Drill by drill. Cue by cue. Season by season.

One day your athlete will come off the track after a hard workout and tell you something felt different today. They won’t be able to explain it exactly. They’ll just know that something clicked.

You’ll know what happened.

And you’ll know it was worth every wicket drill…every barefoot stride…every time you said something on the infield when it would have been easier to say nothing.

The finish line doesn’t lie.

Neither does the stride you built to get there.

One Ask

If this piece made you think differently about something you thought you already understood…

Pass it to one coach who needs to hear it.

Not a mass forward. Not a blast to your whole staff email list. One coach. The one who’s been coaching long enough to have opinions but is still curious enough to change them.

That’s who this newsletter is for.

And if you’re not subscribed yet…now’s a good time.

There’s more where this came from.

I want to tell you what’s going to happen to you that morning, before it happens. Not because I’m guessing. Because I’ve watched it happen to good coaches every spring for nineteen years, and I’ve done it myself.

You’re going to tense up. You won’t notice it. And your athletes will run worse because of it.

* * *

This is what tensing up looks like when you can’t feel it from the inside.

You let your athletes lead warm-ups all season. At the championship meet, you start stepping in. You tell them when to take a drink. When to start their first stride. When to take out their spikes and spike up. The kids who’ve been running their own routine for three months are being managed for the first time. They look at you a little sideways. They don’t say anything. But the thing they trusted, their own process, has been quietly revoked. Their confidence is no longer in their hands. It’s in yours. And yours are shaking.

Or you start rewriting the script. The relay order swapped on the morning of the race. The warmup cut short. Not because the meet schedule changed.

Because you changed.

The race plan rewritten twenty minutes before the gun.
The kid who’s been a front-runner all season is now told to sit and kick.

Or you decide to read the heat sheets out loud. Their two-miler ran 9:24 last week. “You’re going to have to go with him on the second lap.” Your athlete has trained all season to run his own race. Now, twenty minutes before the start, he’s told to run someone else’s. He runs the first 800 chasing someone else’s pace. He runs the last 800 wondering what happened.

None of this sounds like much.
It feels like coaching.

* * *

But your athletes only hear one thing.

“The plan we’ve used since February isn’t enough for today.”

They don’t think this consciously. They just catch it. Something’s different. The coach is moving differently. He sounds different. The jokes he made all year aren’t coming today. He paused before his pre-race talk in a way he never paused in March.

None of this is decoded. It’s just felt.

“This must be more serious than April. I should be more serious too.”

Then the body follows.

Their shoulders climb. Their warmup heart rate is six beats higher than it was at any meet that month. Their stride shortens by an inch they’ll never notice.

By the time they’re on the line, they’re already a different athlete than the one you’ve been training.

You can’t shut these channels off: The cadence of your voice, whether you make the same jokes you’ve made for twelve weeks, the pause before your pre-race talk.

None of these are decisions you make.
They’re leaks.
And kids are antennas.

This is the part of coaching that doesn’t show up in training.

* * *

Here’s what’s actually happening underneath all this.

Your athletes have been borrowing your nervous system since February. They didn’t decide to borrow it. You didn’t decide to lend it. It’s how athletes work.

They read the cadence of your voice, the way you stand at the team campsite, your words. Their own state shifts to align with yours.

Sixteen weeks of practice. Seven regular season meets. Two post-season meets. They’ve been running on the version of you that they know.

Then at the championship meet, you hand them a different one.

You didn’t add anything for them.
You took away the steady thing they were standing on.

That’s why the same fit athlete who ran 4:17 in mid-April runs 4:25 at the championship meet. Eight seconds across 1600 meters is what tension on the inside looks like on the clock.

I need you to remember this next part.

Your job at the championship meet isn’t to feel calm. Your job is to behave calmly.

Because your athletes aren’t borrowing what you feel. They’re borrowing what you do.

* * *

Every change you’re tempted to make on meet day will feel like coaching. That’s what makes it hard to catch.

The micromanaging will feel like attention to detail. The last-minute change will feel like strategy. Reading the heat sheets out loud will feel like preparation.

It isn’t.

It’s your discomfort looking for a place to land, and the only place it can land is on them.

The test is simple.

If you wouldn’t have done it in March, don’t do it in May.

* * *

If you’ve coached long enough to have been here before, you already know what I’m describing.

You know the drive home that night. You replay the day and notice you sounded different all day, and you can’t recall when it began. The text from your assistant the next morning: “You good?” Your wife in the parking lot, casually, not making it a thing. “You seemed off out there.” And you brushed it off because you didn’t have a name for what she was noticing.

If this is your first championship meet as a head coach, you don’t know that drive yet. I’m telling you about it now so you don’t have to take it.

* * *

Be the same coach.

That’s the whole job.

Ask me what we ran on a Tuesday in October of 2011. I have no idea. Ask me what I said to the team after a bad race that year. Couldn’t tell you.

Those seasons blurred together because the goal had nothing to do with the training. It sat on the whiteboard. The plan sat on a separate piece of paper. They were in the same room. That’s about it.

By 2021, I’d figured that part out. I’d been using what I call an Impossible Goal for about seven years by then. Not a slogan. Something the whole program answers to, specific enough to actually show up in your training.

But I still needed one for this team. This group of girls.

The year before, Covid had changed everything. Both my boys and girls teams finished 4th at Regionals. Most years, 4th qualifies you for State. Not that year. Only the top three went. We watched individuals qualify. The team stayed home.

That next summer, I’m on the easy last mile with the girls. We’re just talking. I don’t remember exactly what I said, but we were talking about what this season needed to look like.

Allie said, “Plan A State. Plan B. There is no Plan B.”

Everybody stopped running.

I’d been doing this long enough to know exactly what she’d just given us. That was our Impossible Goal, and it came from a 16-year-old on a cool-down jog.

We put it on the back of our team shirts. Every workout I wrote already connected back to Plan A because that’s how I build. But now I could explain it in their words. When a race went sideways, we talked about what to adjust to protect Plan A. When a sophomore asked why we were doing a particular workout, I didn’t have to reach for coaching jargon. Five words she already believed in did the work for me.

Those girls finished 2nd in the Region. Qualified for State.

We executed Plan A.

I’ve had goals that sat on a whiteboard all season and I’ve had goals that held the whole thing together. The whiteboard ones are the seasons I can’t remember.

Does your goal make decisions for you? Can your athletes tell you why today’s workout matters, in their own words, without you in the room?

This is one of the 23 questions I explore in Training Architecture: 23 Questions Every Distance Coach Should Answer Before Writing a Single Workout. The book is coming soon. If you want to know when it drops, you’re already in the right place.

Why Nobody Can Do This Part for You

Two weeks ago I showed you the framework. The four pieces of a training architecture: the Training Model, the Feedback Loop, the Shared Language, the Athlete Development Pipeline. I walked you through each one and showed you what changes in your coaching life when those pieces are in place.

But I ended with something I hadn’t unpacked yet.

The architecture doesn’t build itself. It doesn’t defend itself when the season gets hard and the temptation is to scrap the structure and just react. Someone has to make the structural decisions — draw the boundaries, define the constraints, choose the patterns, manage the tradeoffs — and hold the whole thing together when everything around it is trying to pull it apart.

That someone is the architect. And in your program, the architect is you.

My first two years of coaching, I was the most prepared confused person you’ve ever met.

I had notebooks. Stacks of them. I had PDFs printed from every coaching forum I could find. I bought every distance running book available — Daniels, Lydiard, Canova, Pfitzinger, Vigil. I could sit down with you and talk for an hour about what Daniels did with his intervals. I could explain Lydiard’s base-building philosophy. I could walk you through Canova’s approach to specific endurance.

I knew what everybody else did.

I had no idea what I should do.

I’d sit down to write a training plan and it was really just a series of workouts. Good workouts. Workouts I’d pulled from coaches I respected. But there was no thread connecting them. No logic underneath that told me why this workout on Tuesday instead of that one. No continuity from one week to the next. I was a cover band playing greatest hits from all these coaches I admired, but I didn’t have my own sound. I could play their songs. I just couldn’t write one.

And the thing is, from the outside, it probably looked fine. The workouts were solid. The kids were running. We had a schedule. But I knew. I knew that every week was a fresh scramble. I knew that when something went wrong — an injury, a bad race, a weather change — I had no way to adapt because there was nothing holding the plan together. I’d just find another greatest hit to plug in and hope it worked.

That went on for about two years.

Then one day I recognized the feeling.

Before coaching, I’d taught myself to program. And for the first stretch of that, I had the exact same experience. I could look at other people’s code. I could copy functions. I could build things that worked, sort of, but I had no idea why they worked or how to fix them when they broke. I was assembling pieces without understanding how the pieces related to each other.

What changed wasn’t learning more syntax. It was learning to think architecturally. The big questions — how does everything connect? What are the rules for how the pieces play together? What stays fixed and what adapts? — those were the questions that mattered. Not “how do I code this specific thing” but “how is the system shaped?”

Once I started asking those questions in software, everything fell into place. The details didn’t change. The details were always fine. What changed was the structure holding the details together.

Sitting at my kitchen table, staring at another week of borrowed workouts, I realized coaching was the same problem. I didn’t need more workouts. I didn’t need another book. I needed to stop playing other people’s music and figure out what I actually believed about how distance runners develop. I needed to answer the questions that sat above the workouts — the architectural questions that would make every detail below them make sense.

That was the shift. Not a new workout. Not a new book. I started building a system instead of borrowing pieces from other people’s systems.

That shift — from collecting details to building architecture — changed what I did. But it didn’t happen all at once. Because knowing that you need architecture is only half of it. The other half is knowing who’s building it.

And that part took longer.

I’ll give you the simplest way I can say this: two coaches can look at the exact same set of athletes, the exact same calendar, the exact same championship meet six weeks away, and design two completely different systems. Both can work. Both can win. They’ll look nothing alike.

One coach might build a system that’s structured around relationships and culture. Every workout is designed to create belonging. The meet schedule is chosen to build team identity. The hard days are hard because the group goes through them together. That coach is a Connector, and their architecture reflects it.

Another coach might build a system that’s structured around data and feedback. Every workout has a measurable target. Race results get analyzed within 24 hours. The training plan adjusts based on what the numbers say, not how the last practice felt. That coach is building from a completely different set of convictions, and their architecture looks completely different.

Neither is wrong. Both are aligned. And aligned systems outperform borrowed ones every single time, because when the plan breaks — and it always breaks — the coach who built the system from their own beliefs knows how to adapt it. The coach who installed someone else’s blueprint is lost. They don’t know why the pieces were arranged the way they were, so they can’t rearrange them when reality shifts.

That’s what I mean when I say the architect matters. The framework I showed you last week — the Training Model, the Feedback Loop, the Shared Language, the Pipeline — those are the pieces. But the shape they take, the decisions they encode, the way they fit together? That comes from the person building them.

So who are you?

I don’t mean that in a philosophical way. I mean it practically. When you’re coaching at your best — when you’re in your element, fully locked in, not performing, not imitating, just coaching — what does that look like?

For me, the answer took a while to find. But when I found it, it was obvious. I’m a systems thinker. I came from software. I think in frameworks, connections, structure. When I look at a training problem, I don’t see a workout that needs fixing. I see a system that isn’t aligned. That’s my natural lens. It’s not better or worse than anyone else’s. It’s just mine.

Once I got clear on that, something happened that I didn’t expect. Decisions got easier.

Not because I had better information. I’d always had plenty of information. But because I had something to run decisions through. I had beliefs that were specific enough to actually make calls for me.

Early in my career, I’d have a bad Tuesday workout and spend the rest of the evening second-guessing myself. Were the paces wrong? Was it the wrong workout for this point in the season? Should I have done something different with the recovery? I’d go back and forth, change the plan for Thursday, then change it again on Wednesday night. My athletes never knew if the plan was real because I didn’t know if the plan was real.

At some point I committed to a belief: patterns over time reveal truth better than single workouts. That’s a conviction, not a piece of information. And the “therefore” that falls out of it changed my coaching life: I don’t change the plan based on one bad day. I look at three to four weeks. If the pattern says something’s off, I adjust. If it’s one workout, I stay the course.

That single belief eliminated probably 80% of the anxiety I used to carry on Tuesday nights. Not because Tuesday stopped mattering. But because I stopped treating every Tuesday like a verdict on the whole season.

I have a handful of those opinions. Not twenty opinions. Not a comprehensive coaching philosophy document that fills a binder. Five beliefs that are specific enough to make real decisions.

I believe athletes develop faster when they understand the system they’re training in. So I explain the why before the what. Every time. If an athlete can’t tell me why we’re running this workout today, I haven’t done my job.

Another one: championships are built from systematic daily excellence, not motivational moments. That belief means I don’t give speeches. I don’t hype. I build habits and let the data tell the athletes they’re improving. Confidence that comes from evidence is the only kind that holds up on the starting line at State.

And the one that probably changed my program the most: race-day execution comes from rehearsal, not hope. We start simulating championship conditions from the first week of practice. By the time we get to the state meet, my athletes have rehearsed that race fifteen to twenty times. They’re not nervous. They’ve done this before.

Each of those beliefs eliminates an entire category of daily debate. I don’t agonize over whether to motivate or just train. I don’t wonder whether to explain the workout or just give them the paces. Those questions are already answered. The opinions answered them a long time ago.

That’s what strong opinions do. They don’t make you rigid. They make you free. Every opinion that’s strong enough to decide for you is one fewer decision you have to carry on your back every day. And coaching has enough daily decisions to bury you. The architect’s job is to resolve as many of them in advance as possible, so the ones that remain are the ones that actually require judgment.

That’s the identity side of the architect role. Who you are and what you believe. But there’s a practical side too. The architect doesn’t just decide what they believe and then coast. There’s actual daily work.

Go back to the diagram from last week.

Along the bottom, underneath everything else, there’s a bar labeled “The Training Architect.” Inside it are the responsibilities that describe what the architect actually does: components, boundaries, constraints, patterns, tradeoffs, visualization, defending from drift, feedback loops.

Those aren’t abstract concepts. They’re the real work of holding a system together across a season.

Components are the building blocks of your architecture. Your training zones. Your workout categories. Your weekly rhythm. Your race classification system. Each one has to be defined clearly enough that everyone in the program — you, your assistant, your athletes — means the same thing when they use the word. The architect decides what the components are. That’s a structural decision, not a workout decision.

Boundaries are where one thing ends and another begins. Where does “endurance work” stop and “stamina work” start? Where does the off-season end and the pre-season begin? When does a developmental athlete become championship-ready? These divisions aren’t obvious. They’re choices the architect makes, and they shape everything downstream. If you haven’t drawn the boundary, your program will draw it for you — and it won’t draw it where you want it.

Constraints are the things you can’t change that your architecture has to account for. Your calendar. Your climate. Your facilities. Your roster. I coach in Houston. There are no hills. August feels like running inside a sauna. Those aren’t problems to solve. They’re constraints to design around. The architect doesn’t fight constraints. The architect builds the system to work inside them.

Tradeoffs are the hardest part. Every decision in your architecture means giving up something else. If you emphasize aerobic development early, you’re accepting that your athletes won’t look sharp in early-season races. If you taper aggressively before a championship, you’re accepting that you’re giving up training volume during the peak of the season. There’s no architecture that gets everything. The architect’s job is to know which tradeoffs serve the goal and which ones undermine it — and to make those tradeoffs on purpose rather than stumbling into them by accident.

And then there’s defending from drift.

This is the one nobody talks about. Because drift is quiet. It doesn’t announce itself. It just happens. Week by week, one small compromise at a time, your architecture shifts away from what it was designed to do.

You planned to keep Tuesday as a hard aerobic day but the kids looked tired so you made it moderate. Then next Tuesday the same thing happened. And the week after that. Three weeks later, you don’t have a hard aerobic day anymore. You didn’t decide to cut it. It just drifted away. Nobody noticed until the fitness wasn’t there in October and you couldn’t figure out why.

That’s drift. And defending against it is a daily job. The architect has to keep looking at the structure from above and asking: is this still the system I designed? Or has reality slowly reshaped it into something else?

This isn’t about being rigid. The architecture should adapt. But there’s a difference between a deliberate adaptation and a slow erosion that nobody authorized. The architect is the one who knows the difference.

I said earlier that the arguments about “the right way to train” are a non-argument. This is why.

There is no right way to train. There’s the way that makes sense to you. The way you can explain and defend. The way you can adapt when the unexpected hits. The way that lets you handle a weather change, an injury, a bad race, a roster surprise — and still hold the system together because you built it and you know why every piece is where it is.

When your architecture is yours, you stop worrying about what the champion down the road is doing. You stop second-guessing yourself after reading a training thread online. You stop trying to import pieces from other programs and hoping they’ll fit. You stop because you don’t need to. You have a system that works because it was built by someone who knows exactly what they believe and exactly why each piece exists.

That can’t be copied. It can’t be installed. It can’t be handed to you at a clinic or downloaded from a website. It has to be built by you, from your convictions, for your athletes, aimed at your goal.

That’s the part of coaching that nobody in the industry is teaching. They’ll sell you the workouts. They’ll sell you the periodization model. They’ll sell you the race strategy. But nobody sells you the ability to be the architect of your own program. Because it’s not a product. It’s a capability. And capabilities aren’t transferred. They’re formed.

I still open those milk crates from time to time. The ones with the colored ink plans and the coaching notes from my first two years. I learn from them differently now. I’m not trying to figure out what Lydiard’s secret was anymore. I’m not trying to reverse-engineer Canova’s periodization. I read them and I see coaches who knew exactly who they were. Coaches whose plans looked different because their convictions were different and their athletes were different. The architecture was always there. I just didn’t have the eyes to see it yet.

Your architecture won’t look like mine. It shouldn’t.

But it does need an architect.

And that’s you.

I ended that article with a promise: I’d show you what I found underneath.

I’m going to keep that promise. But before I show you the framework, I need you to see something else first. I need you to see what coaching looks like without it.

Because if you don’t feel the problem in your bones, the solution won’t mean anything.

* * *

It’s Sunday night. You’re sitting at the kitchen table with your laptop open and a blank week in front of you.

What are you running on Tuesday?

You did a hard workout last Tuesday. It went okay. Does that mean you keep going with the same idea, or was it time to shift to something different? You had a plan back in July when the season felt clean and organized, but that was before one of your top kids missed two weeks with a rolled ankle, before the weather went sideways for ten days, before that early-season meet turned out to be more competitive than you expected and now your athletes are more tired than they should be in week four.

So, the plan you wrote in July doesn’t match the team in front of you anymore. You know that. But you don’t have a clear way to adjust it, so you’re sitting here trying to rebuild the logic of your own season from memory. What were we emphasizing? Where were we heading? What was Tuesday supposed to accomplish in the bigger picture?

You pick something. It’s a good workout. It’ll be fine.

But Wednesday you’re doing it again. And Friday. And the following Sunday. Every week the puzzle resets. Every week you’re the only person who can solve it. The entire logic of your program lives inside your head, and some weeks you’re not even sure you can see it yourself.

That feeling — that constant low-grade hum of “am I doing this right?” — never fully goes away. You learn to coach through it. But it’s always there.

* * *

You went to a clinic last summer. Great speaker. The room was packed. You took four pages of notes and drove home with that feeling you get when everything suddenly seems possible. You were going to overhaul your interval progressions. You were going to change how you structured your long runs. You had three specific ideas, and you couldn’t wait to try them.

Two weeks later, you’d gone back to what you were doing before.

Not because the ideas were bad. You actually liked them. But once you got back to practice and started trying to fit them into your existing program, things got murky. Was the new interval scheme producing different results? Were your athletes responding better to the adjusted long run structure? You weren’t sure. The times looked about the same. Effort looked about the same. Nothing was clearly better and nothing was clearly worse, and after ten days of uncertainty you just defaulted to what felt familiar.

And here’s the part that bothers you: this has happened before. After the clinic in 2022. After you read that book on periodization. After you spent a weekend studying that coach’s program on YouTube. Every time, the pattern is the same. New ideas go in. They float around for a while. Then they quietly disappear because you have no way to evaluate whether they’re actually working.

You don’t lack follow-through. Your program just has no mechanism for testing a new input and seeing the result. You’re trying things in the dark. And when you can’t see the effect, the new thing dies and the old habits come back.

* * *

You wake up sick on a Tuesday. Fever, can’t go to practice. You text your assistant: “Run the tempo workout. Twenty minutes, moderate pace.”

Your assistant runs practice. The kids get through it. Nobody gets hurt. From a logistics standpoint, it was fine.

But when you check in the next day and look at what the kids actually ran, the paces are all over the place. Two of your varsity runners went too hard because “moderate” means something different to them than it does to you. A few of the younger kids jogged it because nobody told them what pace to target. Your assistant did their best, but they were working off a two-sentence text message and their own interpretation of what you meant.

The workout happened. But it wasn’t your workout. It wasn’t the stimulus you were going for. And now you’re spending Wednesday trying to figure out whether Tuesday set the week back or just wasted a day.

And then the real thought hits you: you can’t take a sick day. You can’t hand off a hard workout. You can’t even have a real conversation about training with your own staff because the meaning behind every word — what “tempo” means, what “easy” looks like, what “moderate” actually translates to in terms of pace — lives entirely inside your head. None of it is written down. None of it is shared.

You are the only person in your program who speaks the language. And that means you’re the single point of failure. Not because your assistant isn’t capable. Because the vocabulary of your program was never made explicit.

* * *

You just had the best season of your career.

Five seniors. All of them competitive. A deep, tight squad that carried each other through hard workouts, pushed each other in races, and held the team together when the season got tough. They set the tone at practice. They modeled the culture. They made the younger kids want to be part of something. You qualified for the state meet, and for a few weeks in November everything clicked.

Then they graduated.

And the following August, you’re looking at a roster of kids who weren’t part of that group. They weren’t in the pack. They didn’t absorb the culture the way the seniors did. They’re not bad kids. They just aren’t ready. The gap between what you had last November and what you have now is enormous, and it’s not just a talent gap. It’s a readiness gap. A maturity gap. A “they don’t know how to compete yet” gap.

The program didn’t dip. It cratered. And you’re starting over.

You’ve seen this happen to other programs. Maybe you told yourself it wouldn’t happen to yours. But it did, because every kid on the roster was getting essentially the same experience regardless of where they were in their development. The freshmen did a scaled-down version of the varsity workout. The JV kids trained with varsity when they could hang and dropped off when they couldn’t. There was no deliberate pathway moving athletes from entry to development to competitive readiness. When the experienced kids left, there was nothing underneath them.

Every coach who’s been through this knows the feeling. You didn’t just lose athletes. You lost the program. And rebuilding from scratch every time a strong class graduates is exhausting in a way that makes you wonder how long you can keep doing this.

* * *

I lived every one of those scenes.

Sunday nights staring at a blank screen. Clinic notebooks gathering dust. Workouts that fell apart the one day I wasn’t there. A program that cratered after my best senior class walked at graduation. All of it.

And for years I treated them as separate problems. The Sunday night thing was a planning problem. The clinic thing was a follow-through problem. The assistant thing was a communication problem. The rebuild was just bad luck with roster turnover.

They’re not separate problems.

They are all symptoms of the same missing piece. And it took me a long time to see that, because in coaching we don’t have a name for what’s missing. We have names for everything around it — periodization, philosophy, culture, leadership — but not the thing itself.

I came from a world that did have a name for it. Before I coached, I spent thirteen years at a software company building enterprise systems and methodology courses. And in that world, what I’m describing had a simple, specific name.

They called it architecture.

Architecture is the set of structural decisions that organize everything in your program into a coherent whole: the training, the feedback, the language, the development pathway. It’s not a plan and it’s not a philosophy. It’s what makes plans and philosophy actually function together.

And when it’s missing, you get exactly what I described above. You carry everything in your head. Nothing connects. Every decision is a fresh puzzle. And the program depends entirely on your daily energy to hold it together.

I’ve spent eighteen years building an architecture for coaching. Not copying anyone else’s. Building my own, from my own convictions, for my own athletes, inside my own constraints.

This is what it looks like.

* * *

* * *

Take a second to look at the whole picture before I walk you through it.

What you’re seeing is a training architecture. It has a goal at the top that drives everything. It has four major pieces, each one solving a different coaching problem. And it has a set of responsibilities along the bottom that describe the work the coach does to keep it all running.

I’m going to walk you through each piece. For every piece, I’ll tell you what it is, what it does, and what changes in your coaching life when you have it. And if you recognized yourself in any of those scenes I described earlier, you’ll start to see which piece you’re missing.

The Impossible Goal

At the top of the diagram is the Impossible Goal. This is the thing the entire architecture serves.

It’s not a motivational slogan on the locker room wall. It’s a clear, specific, measurable target that’s big enough to force you to build something real in order to reach it.

For me, that goal was qualifying for the Texas 6A State Cross Country Championship. Not hoping to qualify. Not “maybe if we have a good year.” Actually qualifying. From a Title 1 school. With athletes who, in most cases, walked onto our team because they’d been cut from other sports.

That kind of goal changes the math. If you say, “we want to have a good season,” you don’t need architecture. You can coach by instinct, react to what happens, and see where you end up. But if you say, “we’re going to State,” every decision in the program has to serve that target. What you train. How you measure it. What language you use. How you develop athletes across years. The goal shapes everything underneath it.

Everything I’m about to describe exists because of that target at the top. Without it, the rest of the framework has no purpose. With it, every piece has a reason to exist.

* * *

The Training Model

This is the largest piece of the architecture, and it’s the one that directly addresses the Sunday night problem.

The Training Model organizes your training decisions into layers. Not a single plan that you write in July and hope survives until November. A set of layers, stacked on top of each other, where each layer answers a different question and each layer is shaped by the one above it.

There are four layers. I think of them as four questions: What and why? When? Where? How?

The first layer answers: What are we building, and why does it matter right now?

Every event demands specific physical capacities. A 5K runner needs aerobic endurance. They need the ability to hold a hard pace without fading. They need closing speed. They need race-specific fitness that transfers from workouts to competition. Your event tells you what capacities matter, and your coaching philosophy tells you what order to develop them in.

This first layer is where you define those capacities and their sequence of emphasis. It’s where you make the fundamental training decisions that everything else flows from. Not “what workout do I run?” but “what am I trying to develop in my athletes right now, and why this capacity before that one?”

Most coaches skip this layer entirely. They jump straight to scheduling workouts without ever defining what those workouts are supposed to produce. That’s like a builder pouring a foundation without knowing how many stories the building will have. You might get lucky. But when something goes wrong, you have no way to diagnose where the problem is because you never defined what you were building in the first place.

The second layer answers: When does each emphasis get its window?

Once you’ve defined what capacities you’re developing and in what order, you need to schedule them across the season. This is periodization. But it’s periodization with a purpose above it, not periodization as a standalone calendar.

The difference matters. A periodization plan without that first layer above it is just a sequence of phases with names attached. “Base phase. Build phase. Sharpening phase.” The names sound good, but what’s actually changing between them? What’s the emphasis shifting from and to? Why this phase now instead of later? Without the capacity definitions above it telling it what to emphasize and in what order, your periodization is floating. It’s a calendar with dates, not a plan with logic.

With that first layer anchoring it, periodization becomes meaningful. Each phase has a clear emphasis because the layer above it defined what’s being developed. Each transition between phases has a reason. And when reality forces you to adjust — and it always does — you know what to protect and what to flex because you understand what each phase was designed to accomplish.

The third layer answers: Where does the work land in the rhythm of a week?

This is where the training becomes visible to your athletes. The first two layers are decisions that live in your head and your planning. This layer is what your team actually sees and experiences. Monday through Saturday. Which days are hard, which are easy, which are medium. What role each day plays.

I think of this as rendering. The current phase tells you what the week needs to accomplish. This layer renders that into actual days. If you’re in a phase that emphasizes building aerobic endurance, the weekly structure puts a longer effort on one day, a moderate steady run on another, easy recovery between them, and maybe a short speed session to keep the legs honest. If the phase shifts to race-specific fitness, the weekly structure changes to match. The days aren’t random. They’re a product of the phase, which is a product of the capacity plan, which is a product of your goal.

When coaches tell me their athletes don’t know what to expect week to week, this is usually the layer that’s missing. The weekly rhythm should be consistent enough that your athletes feel the pattern and predictable enough that they know what’s coming. Not rigid. But structured. Athletes who know what to expect are calmer, more focused, and harder to rattle on race day. Athletes who are constantly guessing are anxious before they ever toe the line.

The fourth layer answers: How do athletes execute the work?

This splits into two parallel pieces: technical standards and race execution.

Technical standards are about how the athlete runs. Posture, foot strike, arm carry, relaxation at speed. These aren’t afterthoughts. An athlete who can hit the right pace but does it with terrible mechanics is borrowing time from their body. The technical standards in your program define what “good form” means for your athletes and how you teach and reinforce it.

Race execution is about how the athlete competes. Pacing strategy. Pack running. Surging. How to manage the first 400 meters of a cross country race when everyone goes out too fast. How to close the last 800 when your legs are screaming. This is where training meets competition, and it’s where programs that rehearse outperform programs that hope.

The whole stack works because of one rule:

Every layer is constrained by the one above it. The weekly structure doesn’t invent itself. It’s driven by the phase. The phase doesn’t invent itself. It’s driven by the capacity plan. And the capacity plan doesn’t invent itself. It’s driven by what your event demands and what your goal requires.

When you have this, Sunday night changes. You open your laptop and you’re not starting from zero. You know what capacity you’re emphasizing this month. You know what phase you’re in. You know what role Tuesday plays in the weekly rhythm. The workout isn’t a fresh decision you have to invent. It falls out of the structure. The logic is visible. The puzzle stops resetting every seven days.

That’s not a small thing. It changes what Sunday night feels like.

* * *

The Feedback Loop

The Training Model tells you what to do. The Feedback Loop tells you whether it’s working.

This is the piece that addresses the clinic hangover. The reason new ideas don’t stick isn’t that you lack follow-through. It’s that your program has no built-in way to evaluate whether a change is producing a different result. You try something new, you watch for a couple weeks, you can’t really tell, and eventually the old habits win because familiar feels safer than uncertain.

The Feedback Loop solves that by answering three questions.

What do you collect?

Not everything. Not every split from every workout for every athlete. That’s a trap. If you’re tracking twenty things, you’re actually tracking nothing because you can’t see the signal through the noise.

The question is: what are the specific signals that tell you whether your training model is producing the adaptations you designed it to produce? For a distance program, I think in terms of data families. Times and splits tell you what athletes actually did. Effort ratings tell you how hard it felt. Fatigue and soreness scores tell you whether they can absorb the load. Each family answers a different question, and together they give you a picture you can’t get from any one number alone.

A kid runs 6×400 meters in 78, 79, 80, 82, 85, 88 seconds. That’s one family. The splits tell you there’s a fading pattern. But is that a fitness problem or a pacing problem? You don’t know until you check the second family: the athlete says the effort was 8 out of 10. Now you know. They were near their limit and they were fading. That’s a signal that the session was too ambitious, or that fatigue from earlier in the week is showing up. One number gives you a fact. Two families give you a diagnosis.

When do you collect it?

Some data matters every day. Some matters once a week. Some only matters at transition points between phases. If you’re reviewing everything every day, you’re not monitoring your program. You’re drowning in data.

The key is cadence. Daily check-ins might be as simple as a fatigue rating from each athlete before practice. Weekly reviews happen on a set day — I do mine on Sundays — where you look at the patterns from the week and compare them to what the training model said you were trying to accomplish. Monthly or phase-transition reviews zoom out further: are the trends moving in the direction the architecture predicted?

Cadence matters because coaching is full of noise. One bad workout doesn’t mean the plan is broken. One great workout doesn’t mean you’ve cracked the code. Patterns over time are what matter. And you can only see patterns if you’re looking at the right intervals.

How do you respond to what you see?

This is where most coaches have nothing at all. And I mean nothing.

They see a number. They react. Sometimes they panic. Sometimes they ignore it. Sometimes they make a change on Tuesday that they reverse by Thursday because something else looked different. There’s no protocol. No decision rules that connect what the data says to what you actually do next.

A response protocol doesn’t have to be complicated. It can be as simple as: if fatigue scores spike for three or more athletes on the same day, I pull back intensity for 48 hours. If a split pattern shows consistent fading over two consecutive workouts, I check whether the weekly structure is giving enough recovery between hard days. If effort ratings are low but splits are on target, I take that as a green light.

These aren’t rigid rules. They’re guardrails. They keep you from overreacting to one data point and they keep you from ignoring a pattern that’s trying to tell you something.

Now think about the clinic hangover. You come home with a new interval progression. With a Feedback Loop in place, you don’t just try it and hope. You define what signal you’re looking for. You set a timeframe. Three weeks, four weeks. You watch the specific data families that would show whether the new approach is producing the adaptation you expect. At the end of the window, you know. The idea either earned its place in your architecture, or it didn’t. That’s not a guess. That’s an evaluation.

That’s why ideas start sticking. The ideas aren’t better. You can just finally see whether they work.

* * *

The Shared Language

This is the smallest piece of the architecture. It’s also the one coaches skip most often. And it’s the piece that quietly creates the assistant coach gap.

Your program has a vocabulary. Words you use every day at practice. “Easy run.” “Tempo.” “Race pace.” “Recovery.” “Hard day.” You know what those words mean. You have a feel for them. When you say “tempo,” you have a specific range of effort and pace in your mind.

But does your assistant have the same range in their mind? Do your athletes? Does the freshman who just joined the team three weeks ago?

Almost certainly not. Because the definitions live in your experience. They were never written down. They were never formalized. They were never made into a shared reference that anyone in the program can point to and say, “This is what that word means for us.”

In my program, I anchor pace definitions to percentage of each athlete’s current 1600-meter time. That gives me a reference point that’s objective, measurable, and individualized. “Tempo” isn’t a vague concept. It’s a specific percentage range that translates to a specific pace for each runner. When I say tempo, my assistant knows what I mean. When my assistant says tempo to my athletes, the athletes know what pace to hit. The word means the same thing to everyone.

That’s a choice I made. Your anchor might be different. You might use percentage of 5K pace, or heart rate zones, or even a color-coded system. The specific choice matters less than the fact that you’ve made one and made it explicit.

When the language is shared, everything shifts. Your assistant doesn’t have to guess. Your athletes don’t have to interpret your mood to figure out how hard to run today. When you miss a practice, the workout can still be your workout because the language carries the intent even when you’re not there to deliver it. When a sophomore transfers in mid-season, you can get them integrated in days instead of weeks because the vocabulary is documented, not tribal.

And it goes beyond paces. How do you name your training phases? What do you call the different types of race effort? How do you categorize meets? When you say, “this is a practice meet,” does every athlete know what that means in terms of effort, expectations, and goals? When you say, “this is a championship meet,” does the energy in the room change because everyone knows the difference?

Shared language sounds small. But every miscommunication in your program traces back to a definition that somebody assumed was obvious. Making the language explicit is how you stop being the only person who can run your own program.

* * *

The Athlete Development Pipeline

The first three pieces govern how you train. This one governs who you’re training and where they are in their development.

This is the piece that prevents the senior exodus.

Think about it: a freshman who walked on to the team three weeks ago and a senior who’s been in your program for four years are not the same athlete. They don’t have the same fitness or race experience. They don’t have the same understanding of how your program works. They should not be getting the same experience.

But in most programs, they do. Everybody runs the same workout. Maybe the volume is scaled. Maybe the freshmen run four reps instead of six. But the structure is identical. There’s no deliberate pathway that moves an athlete from “I just showed up” to “I’m ready to compete at the championship level.”

The Athlete Development Pipeline defines that pathway.

In my framework, there are three stages. Entry is where new athletes learn the basics: how to run at an honest easy pace, how the program works, what the expectations are. They’re learning the culture and the language. Success at this stage isn’t a fast time. It’s consistency, showing up, and beginning to understand what your program is about.

Development is where athletes build. They’re past the orientation stage. Now they’re learning to train with purpose. They’re starting to see the connection between workouts and performance. They’re developing the physical base and the competitive instincts that will eventually make them contributors. A sophomore who negative splits every workout and never misses practice is a Pipeline success even if they’re not on the varsity yet.

Championship ready is the top of the Pipeline. These athletes understand the training. They know the language. They’ve been through pressure and they know how to compete. They can execute a race plan, not just run hard and hope. Getting an athlete to this stage takes years, not weeks. And that’s exactly the point.

When you have a Pipeline, you’re not just coaching the kids in front of you this season. You’re building the kids who will carry the program in two years. The seniors graduate, and instead of a crater, there’s a class of juniors who’ve been developing inside a deliberate structure since they were freshmen. They’re not the same athletes. But they’re prepared. The program doesn’t collapse. It reloads.

That’s what turns a series of seasons into an actual program.

* * *

Now I want to circle back to something I wrote about last week, because it connects directly to what you’re seeing in this diagram.

I talked about how I spent two years studying championship coaches. I wrote out their training plans in colored ink and spread them across the table, convinced that if I could just lay them all side by side, I’d find the hidden pattern. The secret.

There was no secret. The plans were all structured differently. Nothing matched.

What I eventually realized was that I’d been studying their details and expecting to find their architecture. But you can’t find architecture by looking at details. Architecture is what produces the details. It’s the invisible structure underneath that determines what workouts get chosen, how they’re sequenced, why certain things get emphasized at certain times.

That’s why borrowing a championship coach’s training plan doesn’t work. You’re copying one piece of their architecture — the weekly structure, the workouts — and trying to drop it into a program where the other pieces don’t exist. There’s no capacity plan above it telling it what to emphasize. There’s no feedback loop beside it telling you what’s working. There’s no shared language underneath it that lets anyone else in the program execute it the way you intended. There’s no development pipeline feeding athletes into it at the right stage.

The plan wasn’t wrong. The plan was never the thing that made their program work. The architecture was.

And that’s not a failure of effort or intelligence. It’s a failure of structure. The coaching industry teaches you to look at the plan. Nobody teaches you to look at what’s holding the plan up.

* * *

Your architecture won’t look like mine. It shouldn’t.

The whole point of everything I’ve been writing in this newsletter is that architecture has to be yours. Built from your convictions. Designed for your athletes. Aimed at your goal. What carries across isn’t the shape of the framework. It’s the fact that there is a shape. That there’s something underneath the daily decisions holding them together.

But a picture on a page doesn’t coach anybody.

The architecture doesn’t build itself. And it doesn’t defend itself when the season gets hard and the pressure mounts and the temptation is to throw out the structure and just react. Someone has to make the structural decisions — draw the boundaries, define the constraints, choose the patterns, manage the tradeoffs. Someone has to hold the whole thing together when everything around it is trying to pull it apart.

That someone is the architect. And in your program, the architect is you.

Next week: What does it actually mean to be the architect of your own program? And why that role is the one thing no clinic, no book, and no other coach can do for you.

Before I coached, I spent thirteen years at a software company called Rational Software. We built enterprise software and methodology courses. We taught organizations how to design complex systems. And in that world, architecture wasn’t a buzzword or a luxury. It was just how things worked. You didn’t ship software without it. Nobody even questioned it.

Architecture was the air we breathed. It was so ingrained into how we thought about building things that it didn’t need a name. It was just the obvious first step: before you write a line of code, you figure out how the system is shaped. What the components are. How they relate. What’s separated, what’s connected, what adapts and what stays fixed.

Then I left that world and started coaching high school distance running.

And over the next several years, I slowly realized something was missing.

* * *

It wasn’t one moment. There was no dramatic breakthrough. It was more like a hundred small observations stacking up until I couldn’t ignore the pattern anymore.

I’d go to coaching clinics. I’d read training books. I’d study the programs that were winning championships. And I kept finding the same three things.

Definitions. What lactate threshold means. How VO2max works. The energy systems and their characteristics. All correct. All useful.

Workouts. Tempo runs, interval sessions, fartlek variations, race-pace work. Good samples. Plenty to choose from.

Training plans. Week-by-week schedules from coaches who had won. Progressions that looked logical on paper but jumped between intensities without any clear rationale for why things were ordered that way.

All of it was correct. None of it was connected.

* * *

I wasn’t just reading this stuff casually. I was hunting.

I have three milk crates in my office filled with notes. Two years of obsession. Lydiard. Daniels. Canova. Vigil. Every book I could get my hands on. Clinics, online threads, anything that looked like it might have an answer.

I spent about a month writing out their training plans in different colored ink. That’s a lot of work because none of them just hand you a plan. You have to piece it together from chapters and lectures and interviews. But I did it. I was convinced that if I could just lay them all out side by side, I’d finally see the pattern. The thing that connected them. The Secret.

I laid them out on the table and stared at them for a long time.

They were all structured entirely differently. Nothing matched. There was no common plan. No hidden formula I’d been missing.

I remember thinking, “There’s nothing here.”

It bothered me for weeks. I had done everything I was supposed to do. I had studied the best coaches in the history of distance running. I had put in the work. And I still couldn’t see what made their programs work. All I could see were details. Workouts, paces, volumes, phases. Pieces. But no structure holding the pieces together.

Then one day it connected. Before coaching, I’d spent thirteen years building software systems. And there was never one system for building software either. Every project was different. What carried over wasn’t the plan. It was the philosophy and the structure that fit that philosophy.

I looked at those colored ink plans again.

That’s what Lydiard was doing. That’s what Canova was doing. They weren’t following a system. They were building from their own philosophy. And the plans looked different because the philosophies were different and the athletes were different.

I’d been looking at the wrong level the whole time.

I still open those milk crates. I looked through one of the folders yesterday. I still learn from those coaches. I’m just not trying to figure them out anymore.

* * *

The entire coaching education industry is selling details.

Clinics sell details. Books sell details. Social media is wall-to-wall details. Every podcast, every forum thread, every coaching conference is packed with workouts, drills, periodization models, motivational strategies, race tactics. Details, details, details.

And coaches keep consuming them. Keep trying them. Keep wondering why they don’t stick.

Because details without architecture is just activity. It feels productive. You’re busy. You’re doing things. But nothing compounds. Nothing connects. You’re not building. You’re just... doing.

And that’s not the coaches’ fault. The industry never taught them the layer underneath.

* * *

What Architecture Isn’t

When most coaches hear the word “architecture,” they think of something they already have. Their practice schedule. Their team rules. Their periodization plan.

None of those things are architecture.

A training plan tells you what to do on Tuesday. Architecture is what makes Tuesday’s workout make sense inside the whole season. A philosophy tells you what you believe. Architecture is how those beliefs become structural decisions that hold up under pressure. Team rules, periodization models, captain structures? Those are all components. Important ones. But a component isn’t the architecture any more than a foundation is a house.

In software, we thought about this in three layers.

Knowledge is understanding what something is. What a database does. What a function is. What an object does.

Details are the specific pieces you build. A specific workout. A specific drill. A race strategy for Saturday.

Architecture is the set of structural decisions that make all those details fit together into a system that actually works.

The coaching world has knowledge. It has more details than anyone could use in a lifetime. What it doesn’t have is architecture.

* * *

What I Started to See

Once I had this lens, I started seeing a pattern everywhere.

The programs that won consistently weren’t just running better workouts. They had structure underneath. The coach might not call it architecture. They might not even be able to name what they were doing. But when you looked closely, it was there. Every component of their program served a clear purpose. Every decision had a place to live. The system was coherent, even if the coach built it on instinct rather than intention.

And the programs that struggled? No matter how hard the coach worked, no matter how many clinics they attended, no matter how many plans they copied from the champion down the road? They were missing that layer entirely.

The gap wasn’t effort. It wasn’t talent. It wasn’t even knowledge.

It was structure.

The successful coaches had built architecture, even if they did it unconsciously. The struggling coaches were trying to succeed with details alone. And details alone, no matter how good they are, don’t hold up when things get complicated.

* * *

What Architecture Actually Does

I’m not ready to lay out the full framework yet. That’s coming. But I want to give you a feel for what changes when architecture is present, because it’s not abstract. You feel it every single day at practice.

Think about the most common decision you make as a coach: What workout do I run on Wednesday?

Without architecture, that’s a fresh decision every time. You sit down, think about it, weigh options, look at what you did last week, try to remember what phase you’re supposed to be in, and make a call. Tomorrow you do it again. Friday you do it again. Every day is a new puzzle, and you’re the only one who can solve it.

With architecture, Wednesday’s workout falls out of the structure. You know what phase you’re in. You know what that phase emphasizes. You know what role each day plays in the week. The answer is already there. You’re not deciding. You’re executing a design.

That same shift happens everywhere. When an athlete stops improving, architecture tells you which layer the problem lives in instead of leaving you to guess. When reality changes mid-season and the plan stops working, architecture lets you adapt the details without scrapping the whole system. The season evolves instead of collapsing.

It’s the difference between carrying everything on your back and having a structure that carries weight for you.

* * *

Why This Matters

I said in my last article that good coaches are leaving the profession. That they’re burning out. That they’re drowning.

This is why.

They’re drowning because they’re making every decision from scratch. They’re burning out because the entire operation runs on their daily energy. They’re leaving because nobody ever showed them there was another way to build a program.

What they need isn’t more knowledge. It isn’t more workouts. It’s structure. A way to organize everything they already know into a system that doesn’t depend on them being “on” every single day.

Architecture doesn’t replace the coach. It just means the coach isn’t doing everything alone anymore. The system starts carrying some of the weight.

And it has to be yours. Just like you can’t copy someone else’s coaching identity, you can’t install someone else’s architecture and expect it to work. It has to be built on your convictions, designed for your athletes, aimed at your goal.

That’s why copying the champion’s training plan never works. You’re not copying their architecture. You’re copying their details. And details without architecture is just activity.

* * *

Architecture is why some coaches get better every year while others just get older. It’s why some programs survive a coaching change and others collapse the day the coach leaves.

It’s the layer that nobody in coaching education is teaching. And most coaches don’t even know it’s missing. They just know something isn’t working, and they can’t figure out what.

I couldn’t either. Not for a long time. Those milk crates can tell you that.

Next week: What does a training architecture actually look like? I’ll show you the shape of the framework I’ve been building for eighteen years.

I’m not telling you this to brag. I’m telling you because I need you to understand something: I shouldn’t be an outlier.

What I do isn’t magic. It’s not superhuman charisma or endless energy. I’m not working 80-hour weeks. I don’t have elite talent walking through my door. And yet, year after year, we go to State.

Meanwhile, coaches all around me—talented, dedicated, passionate coaches—are burning out and leaving the profession. Not because they don’t care. Not because they can’t coach. But because they’re drowning in a system that demands they BE the system.

And nobody’s talking about the real problem.

Why Coaches Burn Out

Here’s what I see happening:

You wake up every day knowing that if YOU don’t motivate them, they won’t show up. If YOU aren’t “on,” the workout falls apart. If YOU take a day off, everything regresses. The whole operation runs on your daily energy, your constant presence, your ability to push, inspire, cajole, and carry.

It’s exhausting.

You’ve got the same number of hours in the day as everyone else, but somehow you’re:

• Planning every workout from scratch

• Making endless decisions about who runs what

• Having the same conversations over and over

• Rebuilding team culture every August

• Firefighting behavioral issues that should have been settled weeks ago

• Wondering why things that worked last year aren’t working this year

  

And here’s the killer: You look at successful programs and think, “Well, they have better athletes” or “That coach is just naturally gifted” or “I’d win too if I had their resources.”

But that’s not it.

The Real Problem

Most coaches are drowning in tactics because they never built architecture.

Let me explain what I mean.

Tactics are the daily decisions you make: today’s workout, this conversation, that race strategy, how to handle this situation. Tactics are essential. But they’re also endless. Every day brings new tactical decisions. If your entire coaching life is tactics, you’re on a treadmill that never stops.

Architecture is different. Architecture is the foundational structure you build once that makes tactical decisions obvious. It’s the framework that creates coherence so you don’t have to make the same decision 47 different ways. It’s the invisible system that keeps running whether you’re having a good day or a bad day.

Here’s the problem: Most coaches mistake procedures for architecture.

They think:

• “I have a practice schedule” = architecture ✗

• “I wrote down team rules” = architecture ✗

• “I named team captains” = architecture ✗

But that’s just doing the things coaches are supposed to do. It’s surface-level organizational stuff. And it doesn’t solve the core problem: You’re still carrying all the weight.

What Architecture Actually Is

Real architecture isn’t a list of procedures you post on the wall once and forget about.

It’s the philosophical foundation that creates logical coherence across everything you do. It’s:

• The Impossible Goal that everything in your program points toward

• The training philosophy that makes the “why” behind every workout visible

• The principles (not rules) that create freedom within clear boundaries

• The invitation that lets athletes self-select into excellence instead of you policing them

• The clear path from where you are to where you’re going—no guessing, no hoping, just focused execution

When you build real architecture, something shifts:

You stop making endless decisions because the system makes them obvious. Athletes stop needing you to motivate them because they understand where the program is going and why. When workouts get difficult, they know the goal demands it—so they’re focused instead of questioning. Assistant coaches can actually help because they’re working within a coherent framework, not just following your personality. Championships stop being nerve-wracking because you’re just running the system you built.

The Difference in Real Terms

Let me give you a concrete example.

Without architecture: An athlete shows up late to practice. You have to decide: Do I bench them? Depends on who it is, what the circumstances were, how I’m feeling today, what I said last time this happened to someone else. You make a call. Tomorrow, someone else is late. You make another call. By mid-season, nobody knows what the actual standard is because you’ve been making it up case by case.

With architecture: Your architecture includes a clear principle: “You want to be great or you don’t. I coach the committed.” When someone is late, you don’t need to handle it—the team does. Their teammates get on them about it because everyone understands what alignment with the goal looks like. The architecture is self-regulating. The standard holds without you having to enforce it.

See the difference? One approach puts every decision on YOU. The other creates a system that runs itself.

What Becomes Possible

When you actually build architecture—real architecture, not just procedures—here’s what changes:

1. You Can Scale Without Burning Out

Your program works with 12 athletes or 50 athletes because it’s not dependent on your personal attention to each individual. The system handles onboarding. Veterans teach rookies. Leadership emerges naturally. You’re not the bottleneck anymore.

I’ve coached teams as small as 8 and as large as 40. Same architecture. Different tactical adjustments. But the foundation doesn’t change based on roster size. That’s the point.

2. Your Program Survives Your Absence

You can take a day off without everything falling apart. Assistant coaches can run practice because they’re working within a framework, not trying to replicate your personality. Athletes know what to do because the path is clear.

More importantly: when you eventually leave (retirement, new job, whatever), the program doesn’t collapse. The culture perpetuates. The next coach inherits a system, not just a roster.

3. Athletes Develop Faster

When athletes understand the “why” behind every workout—how today connects to tomorrow, how this drill serves the Impossible Goal—they stop being passive recipients of your coaching and become active participants in their own development.

They start making better decisions on their own. They self-regulate. They hold each other accountable. You’re not micromanaging; you’re guiding.

And here’s the kicker: athletes who understand the architecture can run workouts you’ve never explicitly taught them. They get the principles, so they can apply them in new situations.

4. Championships Become Expected

This is the one that sounds arrogant until you experience it.

When you have real architecture, championships aren’t about getting lucky or hoping everything comes together. They’re about executing the system you’ve been building all season.

You walk into State and you’re not nervous. You’re excited. Because you’ve been preparing for this specific moment since August. Every workout pointed here. Every principle reinforced this. The athletes know exactly what to do because the architecture made it obvious.

It’s not calm, but it’s expected. You built toward this. Now you execute.

The Enemy

So why don’t more coaches build architecture?

Because we’ve been trained to do something else: copy the winners.

Go to a coaching clinic. Watch what happens. Everyone’s taking notes on the champion’s training plan. What workouts do they run? What drills? What weekly structure?

And then we go home and try to implement it. And it doesn’t work. Or it works for a while and then falls apart. Or it works with one group of athletes but not another.

Why? Because we copied the tactics without understanding the architecture beneath them.

The successful coach didn’t just stumble onto a magic workout sequence. They built a coherent system based on THEIR philosophy, THEIR non-negotiables, THEIR understanding of development. The tactics flow from that foundation.

When you copy the tactics without the foundation, you’re building on sand.

The Copy Culture tells us:

• Someone else has THE answer

• You just need to find the right training plan

• The successful coach has a secret you need to discover

• Your job is to implement what works elsewhere

And that’s exhausting. Because you’re always looking outside yourself for validation.

Always wondering if you found the right system yet. Always one bad season away from scrapping everything and starting over with a new guru’s plan.

Stop Doing This

Here’s what changed everything for me:

But first, let me tell you where I was before that change.

Early in my coaching career, I did exactly what everyone else does. I went to clinics. I took notes on the champion’s training plans. I bought books. I tried this system for a season, then switched to that approach when it didn’t work. I was constantly looking for THE answer—the workout sequence, the periodization model, the secret that would unlock consistent success.

And you know what happened? I was drowning.

Not because the systems were bad. But because I was trying to layer someone else’s architecture onto my foundation. I’d implement their tactics without understanding their philosophy. I’d run their workouts without knowing why they designed them that way. And when things didn’t work (which they inevitably didn’t), I’d scrap everything and start over with a new guru’s plan.

I was exhausted. Overwhelmed. And I was starting to wonder if maybe coaching just wasn’t for me.

Then I stopped.

I stopped looking for THE system and started building MINE.

I stopped going to clinics to copy workouts and started going to learn principles I could adapt to my philosophy. I stopped asking “What does the champion do?” and started asking “What do I believe about development? What are my non-negotiables? What kind of architecture fits who I actually am?”

“Screw it, I’ll do it myself.”

That was the turning point.

Not because I’m smarter than other coaches. Not because I have some special gift. But because I built something authentic to me—rooted in my philosophy, my values, my understanding of how athletes develop.

And here’s the thing: you can learn from others without copying them. I’ve learned tons from great coaches. But I take bits and pieces that fit MY architecture. I don’t wholesale import someone else’s system and hope it works.

Your architecture has to be yours. Built on your bedrock. Otherwise, it won’t hold under pressure.

What I’m Exploring

I’ve spent the last few months unpacking what I actually do that’s different. Not the tactics (those change year to year based on the athletes I have). But the architecture. The foundational thinking that’s been consistent across 18 years, eight State qualifications, two State champions, and countless athletes who showed up as misfits and left as competitors.

I’m starting to see a framework. A way of thinking that’s transferable even though the tactics aren’t. A structure that works whether you’re coaching distance running or sprints, teaching Algebra or English, leading a team of 10 or 50.

I don’t have all the answers yet. But I know this much: The burnout problem won’t be solved by adding more tactics. It’ll be solved by teaching coaches to think like architects.

I’ll be exploring this more in the coming weeks. If you’re a coach who’s tired of carrying all the weight, who wants to build something sustainable, who’s ready to think differently about what coaching actually is—stay tuned.

This might be the conversation we’ve been needing to have.

Not at the beginning.
Not confidently.

Usually after a sigh.

“I mean… you don’t understand.
I just don’t have the talent.”

It’s said the same way people say:

• “We just don’t get good kids here.”

• “Our school’s different.”

• “You should see who we’re working with.”

I always nod.
Not because I agree.
Because I recognize the feeling.

I’ve heard that sentence at clinics, at meets, leaning on fences, standing in parking lots with coffee that’s been reheated twice.

I’ve never bought it.
Not once.
Not in 18 years.

And it’s not because I think talent doesn’t exist.

It’s because I know exactly where that sentence comes from.

When I was younger, coaches decided what I wasn’t before I ever had a chance to show what I was.

Too small.
Didn’t look the part.
Wrong build.

It didn’t matter what I could do.
They’d already decided what I couldn’t.

And I remember making a quiet promise to myself back then.

If I ever coached, I would never look at a kid and decide their ceiling for them.
I’d give them room.
I’d let them prove it.
Or fail trying.

That belief followed me everywhere I coached.
It still does.

Here’s something I didn’t understand at the time, but see clearly now.

Most coaches don’t say “I don’t have the talent” because they’ve evaluated every kid honestly.

They say it because it’s exhausting to sit with uncertainty.

It’s comforting to believe the problem is permanent.
Because permanent problems don’t require uncomfortable decisions.

Once you call it a talent issue, you can stop looking.
And that relief feels like clarity.

It isn’t.
But it feels close enough.

When I took over the girls program at Mayde Creek, the numbers didn’t exactly inspire confidence.

Twelve girls.

One had ever broken 21:00.
Most were north of 22:00.

The school hadn’t qualified for State in forty years.

You could’ve called that a talent problem.
Plenty of people already had.

But standing there with that roster, I didn’t see what was missing.

I saw raw materials.

So instead of wishing for different athletes, I started trying to understand the ones I had.

I stopped asking the questions everyone asks.

Not:
“Who’s fast?”

But:
“Who adapts?”

Not:
“Who has talent?”

But:
“Who responds to training stress without falling apart?”

Not:
“What do we lack?”

But:
“What could these kids become if we stop deciding too early?”

I started watching for different signals.

Not hero workouts.
Not perfect splits.

Things like:

• Split ranges tightening

• Recovery improving

• Athletes running better under more stress, not worse

I found a freshman with elite consistency.
Not elite times. Consistency.

A sophomore whose pacing made more sense than her results.
Juniors who didn’t need motivation — they needed structure.

The same kids other programs would’ve labeled “nice depth.”

Year one, we finished second at District.
Qualified for Regionals for the first time since 2008.

Year two, same result. Still building.

Year three, second at District again — but this time third at Regionals.
And for the first time in the 40-year history of the school, we qualified for State.

This past year was my fourth.

I had ten girls.
Ten.

Remember where we started.
One girl under 21:00 when I arrived.

This year, our top five were all under 20:00.

In four years:

• A new school record of 17:25

• A District champion

• Three All-State honors

Same school.
Same zip code.
Same excuses sitting there if I wanted them.

I didn’t take them.

When coaches tell me, “I don’t have the talent,” I don’t argue.

I just know they’re asking the wrong question.

When coaches look at their roster, they see what’s missing. I see what got overlooked — the same way I was.

If you believe champions are born, you’ll coach with limits.
If you believe they’re built, you start seeing raw material everywhere.

You’re not waiting on talent.

You’re deciding whether you’re willing to build it.

And the uncomfortable truth is this:

Talent has less to do with what’s standing in front of you
and a lot more to do with how well-trained your eyes are.

If you read this straight through, you’ll notice something.

I never told you what workouts to run.
I never gave you a formula.
I never explained “how.”

That’s intentional.

Because this isn’t a knowledge problem.
It never was.

It’s a seeing problem.

And once you see it differently…

you can’t unsee it.

Not because my legs were done. Because my mind had already decided this was over.

Let me back up.

Last summer, doctors found a tumor on my right hip, right about where my hip flexor lives. Surgery took an 8.5-inch by 2-inch strip of tissue, all the way down to the muscle fascia. Then came 32 radiation treatments to the same spot. My hip doesn’t look like it used to. When I run, it doesn’t feel like it used to.

But this was Houston. And Houston means I run with my daughter Anna.

Anna has cerebral palsy and is quadriplegic. When we run marathons, she rides in a Hoyt race chair and I push. We’ve been doing this together for 12 years. Sitting this one out wasn’t something I even considered.

So, we lined up on Sunday morning, and we started running.

By mile 3, I knew something was wrong. My hip wasn’t firing with any power. Sharp pain right in the area where they’d cut. This wasn’t normal race discomfort. This was my body telling me something had changed.

By mile 5, I was questioning whether I could finish. I started mentally scanning the course for a good place to pull off, somewhere my wife could get to us with Anna’s van.

And by mile 8, I was in a full spiral.

I wanted my hip to feel better. I wished I had signed up for the half marathon. I was sad that my body wasn’t what it had been before cancer. I was embarrassed at how slow we were moving.

I was waiting for something, anything, to send me a signal that this was going to be okay.

Nothing came.

Here’s the thing: I’ve watched coaches do this for 18 years. I did it myself early in my career when things weren’t working.

The workout that’s falling apart. You planned 6x800 at goal pace. By rep 3, splits are off. By rep 5, it’s ugly. You’re standing there watching, waiting for something to click. Scanning their faces, hoping to see energy. All you see is flat.

The meet where nothing is going right. Your athlete is struggling. You gave them a race plan. They abandoned it at the 400m mark. Now you’re watching helplessly, hoping they figure it out. Hoping the adrenaline kicks in. Hoping they remember what you told them.

The season that feels stuck. You’ve tried three different approaches. You’ve read the articles. You’ve listened to podcasts. You keep looking for the thing that will fix what’s broken, some new plan hiding in someone else’s system.

Same pattern. Every time.

You’re waiting for your environment to send you a signal that things are okay. You’re waiting for happy faces. And when they don’t come, when all you get is sad faces, you spiral. You get frustrated. You start questioning everything. You look for somewhere to place the blame.

What if the problem isn’t your plan, your athletes, or your circumstances?

What if the problem is how you interact with your environment?

What if you’re forcing your own negative experience by the way you’re orienting yourself to the situation?

At mile 8, I realized I was doing exactly this. And what happened when I shifted changed everything, not just about the race, but about how I understand pressure, decision-making, and what separates coaches who hold their nerve from coaches who crumble.

I want to teach you what I learned. Not theory. A framework you can use the next time everything is falling apart.

Part 1: The Framework

What Is an Inflection Point?

An inflection point is any moment where conditions change, the plan breaks, and you must choose, without certainty, without enough information, without a safety net.

You didn’t choose it. It chose you.

The plan you had no longer fits. Information is incomplete. The future is opaque. And a decision is required now.

These moments come in different sizes.

Career-defining inflection points are the ones everyone talks about. State championship tactical decisions. Responding to a serious athlete injury. Program-threatening conflicts with administration. They’re rare and high visibility.

Season-shaping inflection points happen a few times a year. Your top runner transfers. The team looks flat at a key meet. You have to decide whether to peak for conference or save it for regionals.

Weekly inflection points are more common than you think. The tempo workout that feels like you’re running in a swamp, 88 degrees with brutal humidity, and the plan still says tempo. An athlete shows up emotionally off. Splits aren’t where they’re supposed to be.

Daily micro-moments happen constantly. An athlete asks, “Why are we doing this?” How do you respond? What does your face say during a hard rep? What do you tell them when they fail?

Here’s what I’ve learned: daily and weekly moments are where capacity, your ability to stay active and keep authoring when the plan breaks, is actually built. By the time the career-defining moment arrives, you’ve either practiced authorship a thousand times or you haven’t. There’s no cramming for inflection points.

At every inflection point, you have exactly two options. Two paths. Two orientations.

The one you choose determines everything that follows.

The Two Orientations

When an inflection point arrives, something is happening inside you that nobody teaches at coaching clinics.

You’re making a choice, usually without knowing it. The choice is: where is my anchor?

Am I looking outward for validation? Or am I acting outward regardless of what comes back?

Passive Orientation

When you’re in passive orientation, your anchor is external. You’re waiting for the environment to tell you who you are and whether things are okay.

I call what you’re waiting for an MRV, a Measurable Result of Value. Think of it as a happy face or a sad face. Every interaction with your environment delivers a verdict.

Happy faces: Someone calls you a great coach. Your team wins. Athletes hit their splits. The plan works.

Sad faces: The plan breaks. Athletes underperform. A colleague criticizes your approach. You’re running slower than you wanted.

When you’re in passive mode, you’ve turned everything in your environment into a tether, something you’ve assigned (without its consent) the job of validating your identity.

Your athletes become tethers. Your training plan becomes a tether. Meet results, the weather, your hip that won’t stop hurting, all tethers.

You’re essentially conducting an orchestra of external elements, desperately trying to get them all to play happy music.

But here’s the thing: none of those instruments signed up for the orchestra. They’re all playing their own music. The athletes don’t know they’ve been assigned the role of validating your identity. The training plan doesn’t know. The meet results don’t know. The weather certainly doesn’t care.

You’re frantically waving a baton at things that aren’t listening.

I’ve been this coach. You probably have too.

Pacing nervously at a meet. Watching splits like I’m waiting for a verdict. Every result either inflates or deflates me. After a bad race, needing to explain why it wasn’t my fault. After a good race, riding high, until the next sad face knocked me back down.

That was me at mile 8. Waiting for my hip to feel better. Wishing circumstances were different. Embarrassed about how I looked to others. Looking outward for a happy face. All I was getting was sad faces. And I was spiraling because of it.

When you’re in passive mode, everything that happens feels like it’s happening to you. The inflection point arrives and you’re swept downstream. You freeze, react, or outsource the decision because the moment feels like something happening to you.

Active Orientation

When you’re in active orientation, your anchor is internal. You act outward regardless of what comes back. Your identity isn’t constructed from validation; it’s formed through action.

In active orientation, your communication with the environment returns VOID.

That’s a programming term. When a function returns void, it does its job without sending anything back. The action is complete in itself.

When you’re active, you observe results without interpreting them as verdicts on who you are. Results still happen. You still see them. But you don’t ask, “What does this say about me?” You ask, “What happened? What can I learn?”

I’ve noticed something about coaches at meets. There are coaches who pace around the whole time. Nervous energy. Watching splits like they’re waiting for a verdict.

And there are coaches who seem… settled. Not arrogant. Just present. Like they already know how this is going to go. Not because they know the outcome, but because the outcome doesn’t define them.

I’ve been both of those coaches at different times in my career. The difference wasn’t my athletes.

The active coach can be honest with athletes because they’re not seeking happy faces from them. They can make unpopular decisions. They can hold their nerve in the moment that matters. The action flows outward for the athletes’ benefit, not back toward the coach for validation.

Same pressure. Same circumstances. Completely different experience.

When you’re passive, every inflection point feels like something happening to you.

When you’re active, the same moment becomes something you author.

The Entry Point: Venturing

So how do you shift from passive to active? Is it just a mindset trick? Do you just decide to be positive?

No. There’s only one way in. Venturing.

A venture is action under uncertainty with outcomes owned.

That’s it. That’s the entry point. There is no other door into active mode.

Three things make it a venture:

Uncertainty. You don’t know if it will work. You can’t know. The future is opaque.

Action. Not thinking. Not planning. Not hoping. Doing something.

Ownership. Whatever happens, you own it. No excuses. No blame. It’s yours.

Here’s what most advice gets backwards.

Common advice says: “Build confidence, then take risks.”

Reality works the opposite way. You take the risk, you own the outcome, and confidence is what remains afterward.

You can’t think your way into active mode. You can’t study your way in. You can’t declare your way in.

You can only venture your way in.

Each venture you survive, each choice you make and own, builds faith that you can venture again. The faith isn’t a prerequisite for the leap. The faith is a consequence of having leaped.

The more you venture, the more you become someone who can venture.

This matters for how we think about failure.

The coach who ventures and fails is in a completely different position than the coach who freezes and fails.

The venturing coach learned something. They have data. They formed conviction, even if the conviction is “I won’t do that again.” They’re stronger for the next inflection point. The venture, even in failure, built faith.

The frozen coach learned nothing except that they freeze. And that knowledge doesn’t build faith. It erodes it. Each frozen moment makes the next freeze more likely.

The enemy isn’t failure. The enemy is paralysis.

The Real Question

When an inflection point arrives, the real question isn’t “What’s the right call?”

You can’t know that. Information is incomplete. The future is opaque.

The real question is: Will I author this moment, or will I let it author me?

Both paths lead to uncertainty. Freezing doesn’t give you safety, it just gives you uncertainty you didn’t author. Venturing doesn’t give you certainty, it gives you uncertainty you did author.

But only one path leaves you as the author.

Part 2: The Proof

Let me take you back to Houston.

Mile 8. I’m looking for a place to quit. My hip is screaming. My pace is embarrassing. Anna is having a rough day. Spastic cerebral palsy can do that. It can trip her nervous system for no apparent reason. She’s fighting the chair instead of relaxing into it.

I’m deep in passive mode. Waiting for something to change. Wanting my body to cooperate. Wishing I had made different choices. Embarrassed about how this looks.

And then I thought about this framework.

I’ve been working on these ideas for months. Active and passive orientation. Inflection points. The architecture of formation. I’d been writing about it, teaching it, building a course around it.

And I realized: I am 100% guilty of passive thinking right now.

I had turned my hip, my pace, the crowd, even the race itself into tethers. I was assigning them the job of telling me whether this was going to be okay. I was conducting an orchestra that wasn’t listening.

No wonder I was spiraling.

So, I made a decision.

I said to myself: “Not today. Not a chance. I’m going active right now.”

I pulled the chair over to the side of the road. Straightened Anna up. She was listing to one side and uncomfortable. I gave her a kiss on the forehead.

And I said it out loud: “No more complaining. We’re finishing and we’re having fun.”

I had no idea if I could finish. The hip still hurt. Nothing external had changed.

But I was done waiting for happy faces.

That was my venture. Uncertainty, I genuinely didn’t know if my body would hold up for 18 more miles. Action, I declared the shift and changed my focus. Ownership, whatever happened from here was mine.

I stopped looking at my watch. I decided to run by feel instead of pace.

I changed what I was paying attention to. Instead of monitoring my hip and scanning for signs of hope, I started noticing everything around me. The crowd. The other runners. The neighborhoods we were passing through. I got curious instead of desperate.

I set new goals, not outcome goals, but action goals:

We’re going to run every hill well.

When we hit the big crowd sections, I’m going to run at a pace that fires people up. I want them screaming Anna’s name.

Mile 26 is going to be our fastest mile.

None of these required my hip to feel better. None of them depended on external validation. They were things I could author regardless of what came back.

What happened next still surprises me.

Almost immediately, within half a mile, my attitude shifted. Not because anything external changed. The hip still hurt. The pace was still slow. But my relationship to it was completely different.

My stride changed. Without consciously deciding to, I started putting myself in a better position to take the pounding off my hip. I wasn’t fighting the limitation anymore. I was working with it.

Anna’s body responded to my energy. Her nervous system started to relax. She stopped fighting the chair and settled in. Kids feel your energy. So do athletes. They know when you’re passive and when you’re present.

I found myself going through parts of the course I used to dread and smiling. The hills that had always felt like punishment became opportunities to run well. The long stretches between crowded sections became quiet, focused miles instead of desperate slogs.

Same course. Same conditions. Same hip. Completely different experience.

Somewhere around mile 15, I realized I was in a flow state. The same feeling I had at Boston in 2023, the first time I understood what flow felt like in competition. I didn’t know if I’d ever feel it again after cancer. But there it was.

I took all my focus off the end result and literally lived in the moment. I didn’t know what mile I was on for long stretches. Not because I was checked out, but because I was fully checked in. Present. Authoring.

The crowded sections were electric. When you’re pushing a chair with someone in it, people respond. But they respond differently when you’re moving with purpose versus when you’re surviving. I ran those sections with energy, and the crowd gave it back. Anna’s name echoing off the buildings.

Mile 26 was our fastest mile of the race.

We finished.

The result isn’t the point.

We didn’t set any records. The time was slow by any objective measure. My hip is still recovering.

The point is what happened when I stopped waiting for my environment to rescue me and started authoring the moment instead.

Same body. Same pain. Same race. Different orientation. Different experience. Different outcome.

The marathon was my laboratory. But the results aren’t limited there.

Part 3: The Application

This isn’t a marathon thing. This is a pressure thing.

Every coach faces inflection points. Moments where the plan breaks. Where nothing is working. Where you’re tempted to wait for something external to change.

The question is: what will you do in that moment?

Recognizing Passive Mode

Here’s how to know you’re in it:

You’re scanning for signals that things are okay and not finding them. Watching athlete faces during a hard workout, hoping to see energy. Checking split times, hoping they’re good enough. Looking at results, hoping the numbers move.

You’re hoping something will click. Waiting for the workout to turn around. Waiting for an athlete to find another gear. Waiting for the team to suddenly get it.

You’re frustrated that circumstances aren’t cooperating. Angry at the weather. Frustrated with the schedule. Annoyed that your athletes aren’t responding the way you want.

You’re mentally searching for blame. If only we had better facilities. If only that athlete hadn’t transferred. If only administration supported us more.

You’re waiting for permission to feel confident. Needing external validation before you trust your own judgment. Looking for happy faces before you believe this is going to work.

Any of that sound familiar?

Making the Shift

What I did at mile 8 wasn’t complicated. It was a decision. Here’s what it looks like translated to coaching:

Name it.

Recognize you’re in passive mode. Say it to yourself: “I’m waiting for happy faces right now.”

That recognition alone is a major step forward. Before awareness, an inflection point feels like being swept downstream. After awareness, it feels like a threshold. You can see both paths.

Declare the shift.

Say it out loud if you have to. “Not today. We’re going active.”

This sounds silly. Do it anyway. The declaration creates a line. Before the line, you were passive. After the line, you choose something different.

Change your focus.

Stop watching for verdicts. Start acting for their benefit.

Instead of scanning athlete faces hoping to see energy, pour energy into them. Your presence. Your voice. Your body language. Stop extracting and start depositing.

Instead of watching splits hoping they improve, coach the next rep with full presence. Be so locked into what’s happening right now that the future splits become irrelevant.

Instead of hoping the workout clicks, make an adjustment. Own it.

Venture.

Make a choice without certainty.

Here’s the part that can’t be shortcut: you have to act. Not think about acting. Not plan to act. Act.

The venture doesn’t have to be big. Cut the workout. Change the recovery. Say the hard thing to the athlete who needs to hear it. Call an audible on the race plan.

You don’t need to know it’s the right call. You need to own the call.

Stay in the moment.

The dark thoughts come from living in the outcome. What if this doesn’t work? What if they don’t respond? What if we lose?

Active mode lives in the action. What’s the next rep? What does this athlete need to hear right now? What’s the adjustment for this situation?

The outcome is not yours to control. The action is.

The Bigger Truth

You can’t control whether your athletes perform. You can’t control the weather, the competition, the schedule, or the administration. You can’t control whether your hip decides to cooperate 8 miles into a marathon.

But you can control your orientation.

And that orientation changes everything, not just for you, but for the people counting on you.

Your athletes feel it when you’re passive. They feel it when you’re scanning their faces for validation. They feel your anxiety, your frustration, your waiting. And it infects them.

They also feel it when you’re active. They feel your presence, your conviction, your authorship. And it steadies them.

The coach is the system. Your orientation is their environment.

At mile 8, I had a choice. Stop or continue.

But the real choice was deeper than that.

The real choice was: Am I going to wait for this to get better? Or am I going to author this moment regardless of what comes back?

That’s the choice you have at every practice. Every meet. Every moment the plan breaks.

You can wait for happy faces that may never come.

Or you can venture. Act under uncertainty. Own the outcome. And become someone who can do it again.

The inflection point is coming. It always is.

What are you going to choose?

Shawn Siemers has coached cross country and track for 18 years, qualifying teams for the Texas State Meet 9 of the last 10 years. He writes about building programs that win at Run by Numbers. This was his first marathon since cancer treatment. He and Anna finished together.

Two camps. Very distinct.

The first camp is curious. They slide into my DMs with questions. “What AI tool are you using?” “How do you actually use it with your athletes?” “One of my fears is that AI is just pulling from bad data on the internet, how do you deal with that?”

The second camp is not curious. They’re defensive. “AI won’t replace me.” “AI can’t do what I do.” “I don’t want a machine coaching my team.”

Here’s what I’ve noticed: the first camp asks questions in private. The second camp makes declarations in public.

My likes on AI posts are down compared to my other coaching content. But my DMs are up. It’s almost like coaches are afraid to publicly acknowledge interest in using AI as a coaching tool. Like it’s something to hide.

I get it. I understand the hesitation. But I think the resistance is based on a misunderstanding, both of what AI actually is, and of what coaching actually is.

What coaches think AI threatens

The fear isn’t really about technology. Coaches use technology all the time. GPS watches, heart rate monitors, video analysis, timing systems. Nobody protests those.

AI feels different because it “thinks.”

Or at least, it feels like it does. And if it thinks, then maybe it can do what we do. Maybe it can replace us.

That’s the fear underneath “AI can’t do what I do.” It’s not confidence. It’s anxiety dressed up as confidence.

But here’s the thing: AI doesn’t think the way you think.

AI is pattern recognition at scale. It’s been trained on massive amounts of text, books, articles, research, conversations. When you ask it a question, it generates a response based on patterns in that information.

Useful? Yes. Magic? No.

You’ve watched thousands of reps. You’ve seen athletes break through and athletes break down. You’ve stood on the infield in the heat and the cold and the rain and made decisions that mattered. All of that experience has formed you into someone who sees things other people miss.

AI hasn’t experienced any of that.

It can process information about what fatigue looks like in split times. But it can’t watch your athlete’s shoulders tighten on the third rep and feel the shift. It doesn’t have a gut.

That’s the part AI can’t touch. And it’s the part that matters most.

The fear that won’t go away

“AI will replace coaches.”

I’ve heard this from more people than I can count. And I understand why the fear exists. But it’s based on a misunderstanding of what coaching actually is.

If coaching were information delivery, books would have replaced coaches a century ago. You could hand an athlete a training plan, point them to the library, and say, “Good luck. See you at the meet.”

But that’s not coaching.

Coaching is formed judgment applied in real-time to specific humans in specific contexts.

It’s looking at your athlete on a Tuesday in November and knowing, not calculating, knowing, that today is the day to push harder. Or today is the day to back off. That knowing doesn’t come from information. It comes from formation. From years of watching, deciding, learning, adjusting.

AI can give you more information. It can help you see patterns. It can help you think through scenarios. But it cannot stand on the infield, look an athlete in the eye, and make that call.

That’s human. That’s you. And no amount of pattern recognition is going to replace it.

What AI actually is (and isn’t)

Let me clear up a few things that I think would help coaches engage with AI more confidently.

1) AI isn’t “taking your whole program.”
In my workflow, I’m not uploading my entire team, my season plan, and a folder of athlete diaries. I’m sharing specific slices of data (like splits) to think through a problem in the moment. If privacy matters in your district, keep it simple: anonymize names, share only what you need, and treat it like a conversation tool, not a storage unit.

2) AI isn’t a live web search dressed up as a coach.
The fear I hear in my DMs, “AI is just aggregating bad data from the internet,” misunderstands how this works. It’s generating responses from patterns in what it was trained on, not pulling fresh information from random websites mid-conversation.

Can it be wrong? Yes. Which is why you stay in the loop.

3) The quality of what you get depends on how you engage with it.
Coaches who ask good questions get useful responses. Coaches who ask vague questions get vague answers.

If you walk up to AI and say “Make me a training plan,” you’ll get something generic and probably useless.

If you bring your actual data, ask specific questions, and probe the responses, you’ll get something that helps you see what you were missing.

What AI actually does for me

Let me get specific about how I use this.

I enter split data from workouts going back months. Every athlete, every rep, every split. Then I have a conversation.

I don’t use fancy prompts. I don’t have some secret formula. I just ask questions:

“Are there any positive trends you can identify with specific athletes?”

“Any negative trends?”

Sometimes it’s nothing. Patterns that don’t matter.

But very often, it surfaces something I didn’t see.

Here’s a real example. We were doing 6×800 in cross country. One athlete kept fading on reps 4 and 5, then magically rallied to hit rep 6 right on schedule.

I missed it, because rep 6 looked “fine” and my brain basically stamped the whole workout APPROVED.

AI didn’t invent anything. It just surfaced the pattern and asked the annoying question I should’ve asked: “Why does the fade show up on 4 and 5, but not 6?”

That question led to a conversation. We found out the fade was more mental than physical, and we built a simple strategy the athlete could use in workouts and races.

That’s coaching. AI just handed me the flashlight.

And here’s the thing, when I go back and look at the data myself, it’s often staring me in the face. I just didn’t see it because I was too close, too busy, or looking at the wrong thing.

AI didn’t create the insight. It pointed at something I missed.

If it’s a negative trend, I start playing what-if games. What happens if I modify training for this athlete? What if I adjust recovery? I run scenarios before I make changes.

If it’s a positive trend, I let my training continue. But now that pattern is at the forefront of my mind when I watch that athlete train. I’m looking for confirmation. I’m paying attention differently.

That’s not AI coaching my team. That’s AI helping me coach my team better.

The conversations I’m actually having

People assume using AI means typing in a prompt and getting an answer. Like a magic 8-ball for training plans.

That’s not how I use it.

I have probing conversations. Back and forth. Clarifying. Challenging. Asking follow-ups. It’s less like asking an oracle and more like thinking out loud with a colleague who’s read a lot and doesn’t get tired.

I’m looking for patterns at the individual level and the team level. I’m playing out what-if scenarios, like testing a strategy for our post-season meets before we actually run them. I’m comparing historical data and incorporating weather information to get an apples-to-apples comparison between performances months apart.

I use it to get a second pair of eyes on workout progressions. On my training plans. On how to handle severe weather scenarios. I coach in Houston, so crazy hot weather on meet day is not unusual.

The key word there is second.

AI is a second pair of eyes. A thinking partner. Not a replacement.

The best use of AI isn’t “give me the answer.” It’s “help me think through this.”

Where AI stops and coaching starts

I want to be honest about something: AI can be wrong.

It can generate confident-sounding responses that are completely off-base. There’s no built-in alarm that fires every time AI should be uncertain. Sometimes it just sounds sure when it shouldn’t be.

This is why the human has to stay in the loop.

You’re not supposed to take AI’s output and blindly implement it. You’re supposed to take that output and evaluate it against your own judgment and observation.

Does this match what I’m seeing on the track? Does this make sense for this athlete, in this context, at this point in the season?

If something AI surfaces doesn’t pass your gut check, trust your gut. You’ve earned that gut. It was built over years of watching and deciding and learning.

The goal isn’t to outsource your judgment. The goal is to extend your observation, so your judgment has more to work with.

The coach is still the system

Here’s what I believe: the coach is the primary variable. Not the plan. Not the technology. The coach.

A great coach with a mediocre plan will outperform a mediocre coach with a great plan. Every time.

AI doesn’t change that equation. It amplifies it.

Give AI to a coach who doesn’t know what to look for, and they’ll get a bunch of “insights” that go nowhere.

Give AI to a coach who’s been formed by years of watching athletes, making decisions, learning from mistakes, and they’ll see things they couldn’t see before.

The coach who uses AI isn’t replacing themselves. They’re extending their system. They’re making their observation sharper, their pattern recognition faster, their scenario planning more thorough.

The coach is still the system. AI just makes the system more powerful.

The real threat isn’t AI

Coaches who resist AI aren’t protecting something sacred. They’re falling behind.

The fear is that AI will replace coaches. But that’s not how this works.

AI won’t replace coaches.

But it will widen the gap between coaches who see more and coaches who choose to see less.

Not because AI is magic. Because observation matters. Because seeing patterns earlier matters. Because stress-testing your decisions before you make them matters.

Every competitive advantage in coaching comes down to this: can you see what others miss, and can you act on it before they do?

AI is a tool for seeing more. That’s it. What you do with what you see is still entirely up to you.

The coaches who refuse to look through the lens aren’t noble. They’re just choosing to see less.

Where this is going

I’m not just talking about this. I’m building toward it.

I believe AI-enhanced coaching is the future. Not AI-replaced coaching. AI-enhanced. The coach at the center, with better tools for observation, pattern recognition, and decision-making.

I’m putting my time and energy into figuring out what that looks like. Building tools for coaches who think this way. I’m not ready to share them yet, but when I am, you’ll hear about it here first.

If you’re reading this newsletter, you’re probably the kind of coach I’m building for. The kind who wants to see more, not less. Who isn’t threatened by a tool that makes observation easier. Who understands that the coach is still the system, and always will be.

The coaching world is splitting. One side is curious. The other side is defensive.

I know which side I’m on.

— Shawn

I’ve been coaching high school cross country and track for 18 years. 8 consecutive XC State qualifications — 9 of the last 10 years. 2 State champions and 3 podium finishes in track, all in Texas 6A. Somewhere along the way, I figured out what I was doing.

But I figured it out backwards. I was doing it for a decade before I understood it.

In 2022, I coached Emanuel Galdino to the 6A State Championship in the 1600m. He ran 4:06 and won going away.

But that’s not the story.

The story is the strategy we used — and what happened after.

We knew how the race favorite liked to run. He’d go out at 60-61 for the first lap, drop to 64 for the next two, surge at 800m, and turn the last lap into a kicker’s race. If you let him control the pace, he’d outkick you at the end. He’d done it all season.

Emanuel is fast. But he’s not a kicker. His top-end speed is maybe 90% of the guys he was racing against. In a kick, he loses.

But Emanuel has something else. He’s a metronome. Whatever split I ask him to hit, he hits it. Every time. I used to joke that I didn’t need my stopwatch — I knew he’d run exactly what we planned.

So we made a different kind of plan.

Emanuel would open at 61.5. Then — instead of dropping to 63 like everyone expected — he’d hold 61.5. The whole race. Four laps at the same pace. No surge at 800m. No tactical games. Just relentless, grinding consistency that nobody in that field had ever seen before.

We spent the month before State rehearsing that exact pace. Over and over. He hadn’t even qualified through Area and Regionals yet, and we were already drilling the State final.

It worked. The confusion at the start of the second lap broke the field apart. Two of Emanuel’s friends realized what was happening and went with him — they ended up on the podium. The race favorite, the one who’d controlled every race all season, finished 8th.

Before the race, I shared the plan with two close friends. Both are coaches I respect.

They said all the right things. “I love this plan.” “This gives him a real chance to win.”

After the race, both of them said something different.

“I thought you were insane.”

“That was a ballsy move. I was hoping Emanuel wasn’t going to blow up.”

One of them told me later: “I’d never have my kids run that strategy. But you were so convinced it was going to work that I just supported you and said ‘Yeah, yeah, that’s gonna work’ — and I didn’t mean a word of it.”

He was humoring me. And I had no idea.

When I’ve explained the strategy to other coaches since, the response is always the same: “That’s crazy. No way I’d have thought of that — and even if I had, I wouldn’t have done it.”

Their response surprised me.

And that surprise is what sent me down a rabbit hole I’m still in.

Because from where I stood, the plan wasn’t crazy. It was obvious. I knew Emanuel’s fitness. I knew his precision. I knew his competitors’ patterns. The strategy wasn’t a gamble — it was the logical move given everything I understood about the situation.

But apparently, what felt obvious to me looked insane to everyone else.

Why?

That question wouldn’t leave me alone. I started pulling on it. What was I seeing that they weren’t? What was I willing to do that they wouldn’t? And why did I trust my own judgment when the conventional move was to play it safe?

The answers didn’t come quickly. But they came. And they changed how I understand coaching — not just what I do, but why it works.

That’s what this newsletter is about.

Not workouts. Not periodization theory. Not “here’s my tempo run philosophy.”

This is about the stuff underneath. The part nobody talks about at clinics because it’s harder to package into slides.

I’ll share what I’ve learned about why some coaches freeze at the decisive moment while others act with clarity. Why copying programs doesn’t work — even when the program is good. Why information can be transferred but judgment cannot.

I’ll share stories. Failures, mostly. The moments when I got it wrong and what they taught me.

And occasionally, I’ll share something that might make you uncomfortable. A question you’ve been avoiding. A pattern you’ve been pretending not to see.

Here’s what I won’t do.

I won’t tell you what to believe. That’s yours to figure out.

I won’t hand you a system to follow. Following someone else’s system is probably what got you here.

I won’t pretend I have all the answers. Eighteen years in, I’m still learning.

If you’re looking for someone to give you a plan, this isn’t the right newsletter.

But if you’ve ever known exactly what call to make — and talked yourself out of it because no one else would have done it — then maybe we have something to talk about.

I’m Shawn. I coach in Katy, Texas. I’m still figuring this out.

Welcome to Run by Numbers.

—Shawn