How to run faster: speed work for recreational runners

Photo by Bohdan Hyrovych on Pexels

You’ve been running consistently for a while. You finish your runs, you’re proud of that, and you should be. But somewhere along the way, the thought crept in: I want to get faster. Maybe you’re chasing a sub-30 minute 5K, trying to break 55 minutes for a 10K, or just tired of watching the same people disappear into the distance at your local parkrun.

Speed work is the answer — but not the complicated, track-obsessed, interval-heavy version you might be picturing. For recreational runners with three or four runs a week, a job, a family, and a body that needs actual recovery time, speed training has to be practical. That means the right sessions, done at the right effort, without wrecking the rest of your week.

This article will walk you through what speed work is, which types actually matter for runners like you, how hard to push, and how to fit it all together without burning out or getting injured.

Why most recreational runners don’t get faster

Running more doesn’t automatically make you faster. If you do all your runs at roughly the same medium-effort pace — not easy, not hard, just kind of moderate — your body adapts to exactly that. It gets very efficient at running at that pace, and not much else.

Getting faster requires occasionally asking your body to do something it finds uncomfortable. That’s what speed work does. It pushes your cardiovascular system, your muscles, and your running economy (how efficiently you use oxygen) beyond what your steady jogs demand. The result, over several weeks, is a body that can sustain a faster pace for longer.

The other reason recreational runners plateau is trying to do too much too soon. One sprint session wrecks your legs, you skip two easy runs, your week falls apart, and you’re back to square one. The goal here is finding the minimum effective dose — enough to make you faster, not so much that it derails everything else.

The three types of speed work worth knowing

You don’t need to understand exercise physiology to use these. Here’s a plain-English breakdown:

For most recreational runners, one session per week that falls into one of these categories is enough to start seeing results. Two is fine if you’re running four or more days a week and recovering well. Three is almost certainly too many if you’re not already structured in your training.

What paces should you actually run?

This is where things often go wrong. Runners either go too easy (in which case it’s just a moderately hard run, not speed work) or too hard (which causes the kind of soreness that derails the next three days).

Here’s a rough guide based on your current easy pace. If you don’t know your easy pace, it’s the speed at which you can hold a full conversation — typically 60–90 seconds per km slower than your 5K race pace.

These are starting points, not gospel. On a bad day, your tempo might feel like an all-out effort at a slower pace — and that’s fine. Adjust to effort, not just the number on your watch. If your breathing is ragged and you can’t string a sentence together during a tempo run, you’re going too hard.

How to add speed work to a real-life week

If you run three days a week, a simple week might look like this:

• Tuesday: Easy run, 40–50 min at conversational pace
• Thursday: Speed work session (intervals or tempo)
• Saturday: Long run or parkrun

That’s it. One quality session among three runs. Protect the easy days — they’re not junk miles, they’re recovery that lets Thursday actually work.

If you run four days a week, you could add strides to the end of one easy run (they take about 8 minutes and won’t tank your recovery), or slot in a second quality session in place of one easy run — but only if you’re consistently sleeping enough and not feeling ground down.

One thing worth flagging: speed work only works if your aerobic base is solid. If you’re still building consistency — say, you’ve been running less than six months — focus on showing up regularly before adding intensity. The 5K personal best training plan on this site is a good entry point if you’re working toward a specific goal.

The session most runners underuse: strides

Strides are possibly the most underrated speed tool for recreational runners. They’re short enough (20–30 seconds) that they won’t trash your legs, but they teach your body to move faster — which is the whole point.

Here’s how to do them properly:

1. Finish your easy run, but leave 10 minutes at the end.
2. Find a flat stretch of path or road (a grass football pitch works well).
3. Accelerate smoothly over the first 5 seconds, hold near-max speed for 10–15 seconds, then ease off.
4. Walk back to the start. That’s your rest. Repeat 4–6 times.

You’re not sprinting flat-out. Think 85–90% of maximum effort — fast, controlled, with good form. Your stride should feel fluid, not desperate.

Do these once a week consistently for four weeks and most runners notice a genuine change in their leg turnover and how comfortable faster paces start to feel.

How long before you see results?

Be honest with yourself here: speed work takes time to show up in race results. Research in sports science consistently shows that meaningful VO2 max adaptations take around 6–8 weeks of consistent training to appear. You might feel better in two to three weeks, but the actual performance gains — a parkrun PB, a faster 10K — typically need 6–10 weeks of regular quality sessions to materialise.

That’s not a reason to delay. It’s a reason to start now and be consistent rather than doing five sessions in a panic fortnight before your race.

What will you likely notice first? Running at your old easy pace starts to feel genuinely easy. That’s the adaptation working. Your body’s ceiling has lifted.

Mistakes to avoid when starting speed work

Going too hard, too often. One quality session wrecked your legs — so you skip Thursday’s easy run. Then you feel behind, so you run Saturday hard instead of easy. Now you’ve done two hard sessions in a week with no real recovery. This is how injuries happen.

Ignoring warm-up. Don’t roll out of bed and launch into 400m intervals. Spend at least 10–15 minutes running easy before you push the pace. According to guidance from the NHS, warming up gradually prepares your cardiovascular system and reduces injury risk — especially for higher-intensity exercise.

Running every interval at the same pace regardless of how you feel. If rep 7 of 8 is significantly slower than rep 1, that’s not a failure — that’s useful information. Either you went too hard on the early reps, or you need more rest. Both are fixable.

Doing speed work when you’re already fatigued. If you had a terrible night’s sleep and your legs feel heavy, swapping the interval session for an easy run is not weakness. It’s just smart training. There’s a fine line between productive discomfort and digging yourself into a hole — and if you’re already familiar with the signs of overtraining, you’ll want to read about how to avoid overtraining while marathon training to keep that balance right.

The honest takeaway

• Start with one speed session per week. Strides or a short tempo run are the best entry points — they give you the stimulus without the recovery hit of hard intervals.
• Your easy pace on non-speed days genuinely matters. If it’s too hard, your quality sessions suffer. Keep easy runs easy: conversational, breathing through your nose if possible.
• Expect 6–8 weeks before you see meaningful results in your race times. Don’t give up after two weeks because nothing has changed.
• Effort matters more than pace. The numbers in the table above are guides. On a humid Tuesday evening after a long work day, running to effort — not the watch — is the right call.
• Consistency beats intensity every time. Eight weeks of one well-executed speed session per week will do more for your running than four weeks of three brutal interval sessions followed by injury. Build the habit, then build the intensity.

Next read: Interval training for 10K improvement: a real runner’s guide