When I decided to run my first 10km, I honestly thought it would just be a case of “run a bit more each week” and show up on race day. Simple.
It wasn’t.
What I learned pretty quickly is that training for a 10km isn’t just about running—it’s about how you structure your week, how you prepare your body before each run, how you recover afterwards, and how often you slow down more than you think you should.
This is the routine that actually worked for me, along with the things I wish I’d taken more seriously from the start.
The Training Schedule That Made It Click
At the beginning, I was doing what a lot of beginners do: running randomly, pushing too hard, and wondering why my legs weren’t keeping up.
Once I switched to a simple structure—three runs a week, slowly building distance—it all started to make more sense.
A basic 8-week flow looked something like this:
In the early weeks, the focus was just consistency. Short runs (2–3km) that didn’t leave me exhausted. The goal wasn’t fitness yet—it was habit.
Then gradually, one run each week became the “long run.” This is where things started to change. First 4km, then 5km, then eventually 7–8km. Not fast. Just steady.
By the final week, I wasn’t trying to get fitter anymore—I was just trying to arrive at race day feeling like I hadn’t wrecked myself beforehand.
That shift alone made a huge difference.
What I Eat Before a Run (and What I Stopped Doing)
This part took me longer than I’d like to admit to figure out.
Early on, I either ran completely empty or ate too much too close to a run. Both were mistakes.
What worked better was keeping it simple:
If I was running in the morning, something light like a banana or toast with honey was enough. If it was later in the day, I’d eat a normal meal a couple of hours before—nothing heavy, nothing greasy, nothing that would sit in my stomach.
The biggest lesson here was this: you don’t need to “fuel like an athlete” to run 10km—you just need to avoid making it harder than it needs to be.
And hydration mattered more than I expected. Not chugging water right before running, but just being consistently hydrated during the day.
Stretching: The Thing I Used to Skip (and Paid For)
I used to think stretching was optional. Something you should do, but didn’t really matter if you skipped.
Then shin splints showed up.
Now I don’t skip it.
Before a run, I stopped doing static stretching and started doing a proper warm-up instead—light movement, leg swings, walking lunges, a bit of jogging. It felt almost too easy, but it made running feel smoother almost immediately.
After runs, I slowed everything down. Calves, hamstrings, quads—nothing intense, just holding stretches and letting my body settle.
It’s not exciting, but it’s one of the biggest reasons I stopped feeling constantly tight and sore.
The Importance of Taking Breaks (Even When You Don’t Want To)
This was probably the hardest mental adjustment.
When you start seeing progress, it’s tempting to just keep running more. But that’s usually when things start going backwards.
I learned that rest days aren’t “breaks from training”—they are part of training.
Some of my biggest improvements didn’t happen on running days. They happened on the days I didn’t run at all.
That’s also when my shin splints started calming down. Not from pushing through them, but from actually stepping back.
Now I see rest days as maintenance. Not optional. Necessary.
Zone 2 Running: The Most Boring Thing That Helped the Most
If there’s one thing I ignored at the start that I now think is essential, it’s this.
Zone 2 running basically means running at a pace where you can still talk comfortably. Not gasping, not pushing—just steady.
At first, it feels too slow. That’s the problem. Most people (including me) assume “faster = better”.
But Zone 2 is where endurance actually builds.
It’s what allowed me to go further without feeling wrecked afterwards. It improved recovery. It made longer runs feel less intimidating over time.
Once I stopped trying to make every run feel like a workout, my progress actually sped up.
What the Whole Thing Really Taught Me
Training for a 10km wasn’t about discipline in the way I expected.
It wasn’t about pushing harder every week.
It was more about learning when to slow down, when to stop, and when “easy” actually means “effective”.
The schedule helped, but the real change came from everything around it:
- Eating light before runs instead of overthinking it
- Warming up properly instead of rushing out the door
- Stretching after runs instead of skipping it
- Taking rest days without guilt
- Running slower than I thought I should
Final Thought
By the time I got to race day, I wasn’t wondering if I could finish anymore. I already knew I could.
And that’s probably the biggest takeaway from the whole experience: training for a 10km isn’t about proving anything on the day. It’s about building enough consistency beforehand that the finish line just becomes the natural result of everything you’ve already done.
The Training Schedule That Made It Click
At the beginning, I was doing what a lot of beginners do: running randomly, pushing too hard, and wondering why my legs weren’t keeping up.
Once I switched to a simple structure—three runs a week, slowly building distance—it all started to make more sense.
A basic 8-week flow looked something like this:
In the early weeks, the focus was just consistency. Short runs (2–3km) that didn’t leave me exhausted. The goal wasn’t fitness yet—it was habit.
Then gradually, one run each week became the “long run.” This is where things started to change. First 4km, then 5km, then eventually 7–8km. Not fast. Just steady.
By the final week, I wasn’t trying to get fitter anymore—I was just trying to arrive at race day feeling like I hadn’t wrecked myself beforehand.
That shift alone made a huge difference.
What I Eat Before a Run (and What I Stopped Doing)
This part took me longer than I’d like to admit to figure out.
Early on, I either ran completely empty or ate too much too close to a run. Both were mistakes.
What worked better was keeping it simple:
If I was running in the morning, something light like a banana or toast with honey was enough. If it was later in the day, I’d eat a normal meal a couple of hours before—nothing heavy, nothing greasy, nothing that would sit in my stomach.
The biggest lesson here was this: you don’t need to “fuel like an athlete” to run 10km—you just need to avoid making it harder than it needs to be.
And hydration mattered more than I expected. Not chugging water right before running, but just being consistently hydrated during the day.
Stretching: The Thing I Used to Skip (and Paid For)
I used to think stretching was optional. Something you should do, but didn’t really matter if you skipped.
Then shin splints showed up.
Now I don’t skip it.
Before a run, I stopped doing static stretching and started doing a proper warm-up instead—light movement, leg swings, walking lunges, a bit of jogging. It felt almost too easy, but it made running feel smoother almost immediately.
After runs, I slowed everything down. Calves, hamstrings, quads—nothing intense, just holding stretches and letting my body settle.
It’s not exciting, but it’s one of the biggest reasons I stopped feeling constantly tight and sore.
The Importance of Taking Breaks (Even When You Don’t Want To)
This was probably the hardest mental adjustment.
When you start seeing progress, it’s tempting to just keep running more. But that’s usually when things start going backwards.
I learned that rest days aren’t “breaks from training”—they are part of training.
Some of my biggest improvements didn’t happen on running days. They happened on the days I didn’t run at all.
That’s also when my shin splints started calming down. Not from pushing through them, but from actually stepping back.
Now I see rest days as maintenance. Not optional. Necessary.
Zone 2 Running: The Most Boring Thing That Helped the Most
If there’s one thing I ignored at the start that I now think is essential, it’s this.
Zone 2 running basically means running at a pace where you can still talk comfortably. Not gasping, not pushing—just steady.
At first, it feels too slow. That’s the problem. Most people (including me) assume “faster = better”.
But Zone 2 is where endurance actually builds.
It’s what allowed me to go further without feeling wrecked afterwards. It improved recovery. It made longer runs feel less intimidating over time.
Once I stopped trying to make every run feel like a workout, my progress actually sped up.
What the Whole Thing Really Taught Me
Training for a 10km wasn’t about discipline in the way I expected.
It wasn’t about pushing harder every week.
It was more about learning when to slow down, when to stop, and when “easy” actually means “effective”.
The schedule helped, but the real change came from everything around it:
- Eating light before runs instead of overthinking it
- Warming up properly instead of rushing out the door
- Stretching after runs instead of skipping it
- Taking rest days without guilt
- Running slower than I thought I should
Final Thought
By the time I got to race day, I wasn’t wondering if I could finish anymore. I already knew I could.
And that’s probably the biggest takeaway from the whole experience: training for a 10km isn’t about proving anything on the day. It’s about building enough consistency beforehand that the finish line just becomes the natural result of everything you’ve already done.
Leave a Reply