Run By Numbers
Build, Don't Borrow, book cover
Coming Soon

Build, Don't Borrow

The Distance Coach's Guide to Training Architecture

by Shawn Siemers

Not a training plan. The thinking that produces training plans. Build a coaching system that's yours, from 23 questions every distance coach should be able to answer.

More information isn't making you a better coach. It's making you a more confused one.

You've read the clinic handouts. You've got a shelf of training books with the good chapters dog-eared. You could quote three different coaches on how to build a base phase, back to back, without pausing.

None of it has made you feel less lost, because you don't actually have a knowledge problem. You already have more information than most coaches will ever collect. Nobody ever showed you how the pieces you've collected are supposed to fit together, so every season still gets built the same way: a guess, dressed up in a spreadsheet.

Build, Don't Borrow started as one coach's attempt to solve that for himself, years before it became a book for every coach stuck in the same fog.

That Was Me

From Chapter 1

That was me from 2010 to 2012. Reading everything. Going to every clinic. Collecting workouts from every successful coach I could find. Working harder every season and getting more confused, not less. I had all the pieces. I couldn't see how any of them connected.

If you'd asked me, 'Why is this workout on this day in this week of this phase?' I could have given you an answer. It wouldn't have been a very good one.

You have a philosophy. You have a plan. But the space between them is still guesswork. … That space is where I lived for years. It's not a fun neighborhood. You can survive there. I did. But you never stop feeling like you're one bad week away from the whole thing falling apart. Because you are.

23 questions. One architecture.

Build, Don't Borrow is built around 23 questions every distance coach eventually runs into: how long a training cycle should be, what order to progress systems in, how to balance a week, how to taper. Most coaches never get a straight answer to any of them. They get a workout instead.

This book answers the questions. Not with a plan to copy, but with a way of thinking that produces your own answers. At the center of it is a three-layer blueprint: the physiological zone a workout is training, the race pace it's built around, and the role it plays in your season's progression. Place a workout on all three layers and the good-workout-or-bad-workout question disappears. What's left is whether it fits what your team needs right now.

That's the shift the whole book is built around: from collecting other coaches' answers to building your own.

The 23 questions you've never gotten a straight answer to

Twenty-seven chapters across five parts. The full architecture, start to finish.

Introduction

  • 1Distance Training Has an Architecture

Part 1: The Impossible Goal

  • 2What Are We Building Toward?

Part 2: The Training Architect

  • 3The Coach-Architect

Part 3: The Training Model

  • 4How Do You Define Each System? What is Their Relationship to Other Systems?
  • 5Why Are Some Paces Given Using Physiological Terms and Others With Race Paces? How Do They Relate?
  • 6Is There an 800, 1600, 3200, 5K Profile of a Successful Runner?
  • 7How Long is Each Training Cycle?
  • 8What Order Should Systems be Progressed?
  • 9How Do You Know Which Combination of Systems to Use? And When?
  • 10How Do You Balance Training?
  • 11Is There a Methodology?
  • 12Are There Training Patterns to Follow?
  • 13How Do You Manage Progressions Within a Cycle? From Cycle to Cycle?
  • 14How Much Recovery For Each System?
  • 15How Long Should Each Work Unit Be?
  • 16How Do You Choose a Starting Point? A Goal Point?
  • 17Is There a Menu of Workouts For Each System? And a Planned Progression?
  • 18How Many Iterations? What is the Goal of Each Iteration?
  • 19Do You Plan by Pace or by System?
  • 20How Long for Each Pace? What Pace Do You Emphasize in Which Cycle?
  • 21What Does a Sample 1-Week or 2-Week Pattern Look Like?
  • 22How Do You Coach Tactics for Each Type of Race?
  • 23What Do You Do for Strength Training?
  • 24How Do You Taper?

Part 4: The Athlete Development Pipeline

  • 25How Do You Start New Runners?

Part 5: The Feedback System

  • 26The Architecture Must Be Built Before You Can Measure It
  • 27If It's Yours and It Breaks, You Learn. If It's Borrowed and It Breaks, You're Lost.

From the book

The LEGO Problem

Here's the best way I can describe what was wrong. Imagine you love LEGOs. You own thousands of pieces: every shape, every color, every specialty brick. You've watched every master builder video. You've bought instruction books from the best builders in the world and followed them step by step. You can build incredible structures when someone else designs the plan.

Now someone hands you a blank table and says: 'Build something original. Build a structure that solves this specific problem for your specific situation.' And you freeze. You don't freeze because you lack pieces. You have more pieces than you'll ever need. You don't freeze because you haven't studied enough. You've studied more than most coaches. You freeze because you've never learned how the pieces fit together. You don't know why this brick goes here and not there. You wonder what keeps a structure standing or causes it to collapse. You're unsure which connections support weight and which are for looks.

So you do the only thing you know how to do: you start pirating. You grab a foundation from one instruction book, a wall design from another, and a roof from a third. You stitch them together and hope. The result is a Frankenstein. It might stand, it might not. But you can't tell someone why it works. And when a piece breaks, you can't fix it because you didn't build it from understanding. You built it from imitation.

That was my coaching. I had all the LEGOs. I watched all the best builders. I could follow anyone's instructions. … The worst part wasn't that it sometimes failed. The worst part was that when it worked, I couldn't tell you why. And when it didn't work, I couldn't identify what broke. I'd tear it down and start borrowing from someone else.

From Build, Don't Borrow, Chapter 1

What the beta readers said

Feedback collected through an anonymous beta-reading platform, margin note by margin note. Nobody was being polite to my face.

You did a great job building the entire architecture in a way that was clear, tangible and will be easy to execute. Can't wait to buy a copy when it's published.
Beta reader, distance coach in Southern California, after finishing the book
When it hits the shelves I want my assistant coaches to read it. I want them to challenge me and themselves to build something better.
Beta reader, on the final chapter
Architecture is missing from my program, this describes it perfectly. Held together by hope.
Beta reader, on Chapter 1
Best explanation of these concepts I've ever read.
Beta reader, on the training-systems chapter
This is golden, and something I wish someone would have told me my first years.
Beta reader, XC coach in Minnesota, on choosing starting and goal points
I've been using your questions, adapted to work for my team, for the past 2 years, and this was always the hardest to answer. The explanation was very helpful.
Beta reader, XC coach in Minnesota, two years using the questions
Great book, great resource! Can't wait to buy it and share with fellow coaching friends.
Beta reader, after finishing the book
Most of us have been there, and I sometimes feel like I'm still there when I design my season.
Beta reader, on Chapter 1

Nine straight trips to State. Here's the system underneath them.

Twenty years coaching cross country and track at a Texas 6A program.

  • 9 straight XC State qualifications.
  • State champions, 1600m and 400m.
  • 3rd place, 1600m, State meet.
  • A first career designing software systems. That's where "architecture" came from in the first place.

Read the first chapter free.

Enter your email and I'll send you the Introduction plus the full first chapter, right away.

Get the preview by email. Unsubscribe any time.

Releasing July 28, 2026

Build, Don't Borrow

Pre-order on Amazon

Print edition coming soon.

The Toolkit

The book asks the 23 questions. The toolkit helps you answer them for your team.

Nine tools, same architecture as the book. Each one lays out the options and the tradeoffs for your team. None of them hand you the plan or make the call. That part's still yours. Every card opens a worked demo: a real coaching scenario, start to finish, no account needed.

Save My Founding Spot

Founding enrollment opens July 21. Founding Coaches get the book, 200 bonus credits, and a live season-design call.