There's a pattern every running coach recognizes instantly. Someone signs up for a race — a half marathon, maybe a full — and starts training about four weeks before the start line. Sometimes three. Sometimes two.
They're not lazy. They're not reckless. They just believe that when the moment comes, they'll figure it out. Sink or swim. It'll either work or it won't. And if it doesn't — well, at least they tried.
The problem is that a marathon doesn't care about your attitude.
What the water actually feels like
To be fair, jumping in isn't always a disaster. Four weeks of consistent running produces real adaptations: your cardiovascular system responds faster than most people think, your confidence grows, and having a race on the calendar creates urgency that nothing else replicates. For a 5K or 10K, if you're already reasonably active, a month of preparation can get you to the finish line in one piece.
So yes — sometimes you swim. And that feels great. And you tell everyone about it.
What you don't always see is how close to sinking you actually were
What's happening under the surface
The cardiovascular system adapts in two to four weeks. Everything else takes much longer.
Muscles, tendons, joints, and bones need months of consistent load to adapt safely. This is why most running injuries don't happen to complete beginners — they happen to people who started training hard and recently. The body simply couldn't keep up with the ambition.
Aerobic base — the foundation that makes long distances manageable rather than survival — is built over years, not weeks. You can sharpen your form in a month. You cannot build the engine.
Push the volume too fast and the consequences are predictable: bone stress reactions, knee pain, shin splints, IT band syndrome. That last one is worth knowing by name: the IT band is a thick strip of connective tissue along the outer thigh that stabilizes the knee with every stride. Inflame it through sudden overload and it produces a very specific sensation — a burning pain on the outside of the knee that stays quiet for the first few kilometers, then arrives like clockwork and gets worse with every step. It eases when you stop. It comes back the moment you run again. If you've ever had to limp off a course with pain on the outer side of your knee, you've already met it.
At the half marathon and marathon distances, this stops being an inconvenience and becomes the whole story.
Why we keep jumping in
The sink-or-swim instinct is deeply human. And there are very specific reasons it shows up so reliably in running.
Without a race on the calendar, there's no urgency — so people delay registration, and delay training right along with it. By the time they commit, the window is short.
A distance looks like a number on a screen. Until you've run it, you don't feel what it costs. Hence the genuine confidence: "I'm a fit person. I'll figure it out."
There's always someone nearby who ran a half marathon on minimal preparation and tells the story like a badge of honor. Those stories spread. Stories about DNS, DNF, and six weeks of physio don't.
And we live in a world that promises results in 21 days. The sink-or-swim mindset fits right in — right up until the body pushes back.
Learning to swim before you jump
The alternative isn't caution for its own sake. It's sequencing.
Start training first. Then pick a race that fits where you actually are. Build the base before you test it. Let the distance come to you — don't jump into water you haven't measured.
This is exactly how OMY! Sports works: we start with your current fitness and build a plan toward a specific goal. Not a generic template — a program built around your volume, your schedule, and your ambitions. And Rob, our AI coach, will analyze every workout and keep you on track all the way to the finish line.
Some people swim on instinct. Most of us need to learn first.