Training & Development
Improvement is a system, not luck
Idea in Brief
- Speed is an output, not a lottery — it comes from inputs (attendance, recovery, skill reps) that compound quietly into time.
- The clock lags the work — swimmers bank months of practice, then drop time in a jump; a plateau is the system loading, not stalling.
- Measure what you can see — praise the inputs you control daily (showing up, sleep, attitude), and let meets be read-outs, not verdicts.
Every swim parent knows the feeling at a meet: the result comes up, and you do the math in a half-second — faster or slower than last time? On a good day it’s relief. On a bad one it’s a small, quiet dread: what if this is the meet where it turns out my kid just doesn’t have it? It’s an exhausting way to follow a sport — refreshing the clock like a slot machine, hoping the next pull pays out. The good news is that improvement was never a gamble. It’s a system.
Swimmers don’t get faster at the meet. They get faster in the months before it, in a thousand unremarkable repetitions, and the meet just reads out the total. Speed is an output, and outputs come from inputs — show up, do the work, recover, repeat — that compound quietly until one day the body can do something it couldn’t before. Nobody wakes up two seconds faster. They arrive there one good, boring practice at a time.
So what are the inputs? The biggest is almost insultingly simple: attendance. The swimmer who’s in the water four times a week, week after week, beats the more talented kid who comes when they feel like it — not most of the time, nearly every time. After that it’s the unglamorous trio: sleep (where the body actually adapts to the work), food (the fuel for it), and skill reps — the underwaters drilled until they’re automatic, the stroke count nudged down a notch. None of it photographs well. All of it is what “getting faster” is actually made of. As David Karasek, who coaches the mental side of the sport, puts it: the tools are simple; it’s the daily application that’s hard.
This is why the clock can be so misleading in the short run. Work doesn’t convert to time instantly — it gets banked. A swimmer can train brilliantly for two months and see nothing at the next meet, then drop a chunk at the one after. That plateau wasn’t stalling; it was loading. Judge the system by any single result and you’ll panic at exactly the wrong moments and celebrate at semi-random ones. The plot only makes sense zoomed out.
Which points to a calmer, more useful thing to watch: the inputs you can actually see. You can’t control whether Saturday’s race drops time. You can absolutely notice whether your kid got to practice, slept, ate something real, and brought a decent attitude to a hard set. Those are the leading indicators — and unlike the clock, they’re available every single day. Praise them. “You made every morning practice this month” is a truer compliment than any time, because it’s about the thing that produces the times. Then trust the lag, and let the meets be read-outs instead of verdicts.
Here’s why this matters beyond your own blood pressure. A kid who believes speed is luck or raw talent is, deep down, a little helpless — there’s nothing to do but wait and hope they were born with it. A kid who believes improvement is a system has a lever: they can always pull on the inputs. That’s agency on the good days and resilience on the bad ones, because a slow swim doesn’t threaten their story — they trust what they’re building. This isn’t only a swimming idea. It’s what James Clear means in Atomic Habits — “you do not rise to the level of your goals, you fall to the level of your systems” — and what the researcher Anders Ericsson spent a career showing: that expertise is built through deliberate practice, not handed out at birth. It’s also the quiet link back to your swimmer’s goals: they get to own the goal, and trust the system that carries them to it.
The clock will do what it does. The best thing you can hand your swimmer is a simple, freeing belief: getting faster was never luck. It’s a system — and the system is theirs to run.
Share it with your swimmer
How you make the system visible shifts as they grow:
- Under 12 (you’re driving). Make the inputs the win. Celebrate the streak of practices, not just meet times — a simple “I showed up” chart does more at this age than any stopwatch. They learn early that getting better is something you do, not something you wait for.
- 12–15 (sharing the wheel). Help them see their own data. Look at the season together — practices logged, times over months, not weeks — so they spot the lag and the trend themselves. This is the age to connect a good meet back to the dull weeks that earned it: “remember those December mornings? That’s this swim.”
- 16+ (they’re driving). They run their own system now. Your main job is to not panic at a plateau out loud — your calm is part of their environment. When they’re frustrated, point them back to the inputs they control, not the clock they don’t.
Stay aligned with your coach
The coach designs the system — the sets, the cycles, the taper. You don’t need to understand the training plan to back it; you need to trust it through the lag. When the times go quiet, resist the urge to ask the coach to “do something.” A better question: “what should we be focused on at home — sleep, recovery, getting to practice?” It reinforces the coach’s system instead of second-guessing it, and it puts your energy on the inputs that are actually yours to influence.
Keep exploring
- Whose goal is it? Why the swimmer has to want it — own the goal; this is the system that gets you there.
- Best time, not placement: what actually matters — the output worth tracking, once you trust the inputs.
- A bad meet is information, not identity — how to read a slow swim when you trust the system behind it.
- The four stages of getting good: where your swimmer actually is — how a single skill climbs from clumsy to automatic inside that system.
Go deeper with the experts
- SwimPros Performance Academy — Olympian David Karasek’s coaching, built on “the tools are simple; the daily application is hard.”
- Atomic Habits, James Clear — the systems-over-goals case: you fall to the level of your systems.
- Peak, Anders Ericsson — the research that expertise is built through deliberate practice, not innate talent.