9 Common Beginner Running Mistakes (and What to Do Instead) | Runthatfits

Common Beginner Running Mistakes

Runthatfits TeamOctober 2, 202611 min read

Almost every problem new runners hit traces back to the same handful of errors — and most of them are encouraged by advice that sounds sensible. The nine that matter, and what the evidence says to do instead.

Why beginners get injured

Novice runners carry roughly twice the injury rate of experienced runners.1 Talent and body type have little to do with that gap. Most of it comes down to a small set of decisions made in the first few months, which are easy to get wrong because the wrong version feels like trying harder.

These are the nine that account for most of it.

1. Running too fast

This is the most common error by a distance. New runners run their easy runs at moderate effort, because slow feels unproductive.

The cost is specific. Moderate intensity generates a lot of fatigue while sitting below the threshold that drives high-intensity adaptation, so you pay most of the recovery cost and collect a fraction of the benefit. Meanwhile the elite endurance athletes people are implicitly imitating spend roughly 75–80% of their training at low intensity.2

Running slowly is harder than it sounds. It takes a lot of patience to hold back for the weeks it takes a beginner to build enough running fitness to start adding different types of session.

Instead, use the talk test: if you can’t speak in complete sentences, slow down. Expect to walk hills.

Two things make it much easier. Skip the music, which tends to pull your pace up with it, and try an audiobook instead. And if you can afford one, get a heart rate monitor that links to your watch, either an arm band or a chest strap. Running to heart rate ranges rather than pace will help you massively.

2. Increasing distance too quickly

Week four arrives, your breathing is easy, and it seems obvious you could do more. Your cardiovascular system has adapted, but your tendons and bones have not; they remodel over months, not weeks.

A 2014 study following 874 novice runners3 found that increases in weekly distance above 30% over a two-week window were associated with a specific injury cluster: runner’s knee, IT band syndrome, shin splints and patellar tendinopathy.

Avoid spikes rather than chasing a precise percentage, and take a down week every third or fourth week.

Balance any increase in distance by running all of the extra at a very easy pace. My rule is not to run fast while you’re increasing distance, only once you’re used to it. You’ll still get faster running slowly at low heart rates.

3. Skipping rest days

Adaptation happens between sessions, not during them. Running on consecutive days early on is the most reliable way to turn a sensible plan into an injury, and enthusiasm makes it very tempting.

When you’re starting out, run three times a week with a rest day between each; back-to-back days are a flat no at this stage. As your endurance and stamina build, running some consecutive days is fine, provided the second run is short, flat and slow. If you want to move on off days, walk, cycle or swim. Non-impact activity adds aerobic work without adding to the tissue load. See active recovery vs rest days.

4. Buying the wrong shoes

A gait analysis at a running store is a useful starting point and will help you discover the type of shoe you need. For beginners, the answer is almost always the same: a well-cushioned, comfortable daily trainer.

New runners go wrong when they buy for speed or novelty. Shoes with nylon or carbon plates are built for racing and faster sessions, not for the slow, easy miles a beginner should be running. Nigg and colleagues’ review of four decades of footwear research4 points the same way, with comfort a better filter than any technical feature.

So go for a cushioned daily trainer that feels comfortable when you run in it, and leave a thumb’s width at the toe. Avoid the latest models, which cost more. A line from a few years ago does the same job, provided it doesn’t have a nylon or carbon plate.

5. Stretching instead of strengthening

Static stretching before a run is the classic warm-up ritual, and there is moderate to strong evidence that it does not reduce overall injury rates.5

The interventions with better support are dull by comparison: hip strength for runner’s knee, calf strength for shin splints, and sensible load progression above all.

Warm up by walking, then running slowly, and move those ten minutes to strength work twice a week.

6. Running through pain

Beginners often can’t tell normal training discomfort from an injury signal, so they either panic at every ache or ignore everything.

You can learn the difference. Diffuse muscular soreness that eases as you warm up and settles within 48 hours is a normal training response. Sharp, localized pain (particularly on a bone) that worsens during a run and persists afterward is not. Shin splints run through for months become tibial stress fractures.

If you can cover the painful spot with a fingertip, or the pain increases as you run, stop and get it assessed. A useful rule of thumb is the 24-hour test. Discomfort that has cleared by the following morning was training; discomfort still there a day later was too much.

7. Doing too much, too soon

This one is related to mistake 2 but distinct. It means starting at a volume that would be reasonable for someone six months in, because the first run felt fine. It usually does, and the consequences arrive at week three.

When you’re a beginner, the best thing you can do is form the habit of running three times a week. That change to your life takes time to adjust to, on top of the physical effort of each run.

Be realistic about this stage: almost no one enjoys much of the beginning of running. It’s hard, but the rewards after it are high, so the effort is worth it. After around 20 runs, most people have built enough fitness and endurance to start enjoying their running and progressing without it feeling like such a chore.

Start lower than feels necessary and let the plan be boring. Couch to 5K starts with one-minute intervals for a reason. Aim for consistency (three runs a week, every week) rather than distance or speed.

8. Obsessing over form and cadence

New runners spend a lot of energy trying to land midfoot, shorten their stride, or hit 180 steps per minute. The evidence that any particular footstrike pattern prevents injury is weak, and deliberately changing one shifts load elsewhere. Forefoot striking moves stress from the knee to the calf and Achilles, which trades one problem for another.

Forget about running form at the beginning. Focus on running slowly and not exceeding your limits, and let form emerge from running consistently at easy effort. Most technique faults that matter are simply what running too fast looks like, and they resolve on their own once the effort comes down. Cadence adjustment is a targeted tool for someone already dealing with knee pain, not a beginner project.

9. Getting fueling wrong

Fueling your running correctly matters, but beginners tend to overcomplicate it with gels, sports drinks and recovery shakes for runs that don’t need them. Your training at this stage is low intensity, so you don’t need special or extra fuel for it, especially if you’re running to lose some weight. Over time, your body will adapt to fueling your runs from fat as well as carbohydrate.

The opposite error matters too: cutting food back hard while starting to run. Recovery slows, adaptation stalls, and injury risk rises because tissue repair is compromised.

Stick to a balanced, normal diet with carbohydrate and protein, and skip the running-specific products for now. The anabolic window is far wider than 30 minutes,6 so precise timing matters much less than eating well overall.

The ones that aren’t mistakes

Several things beginners worry about don’t matter much.

Being slow is one. Pace at the start predicts nothing about where you end up; what matters is consistency over months.

Walking is another. Walk breaks are the mechanism the entire beginner literature is built on, so there’s no failure in taking them, and walking up hills to hold easy effort is the correct call.

Not looking like a runner doesn’t matter either. Running economy is trainable, and appearance is irrelevant to it.

Missing a run changes nothing on its own. The damage comes from abandoning a plan entirely after missing one session, and far more people stop running for that reason than through injury.

An uneven spread of runs across the week is fine too. Three runs on whatever days fit your life beats a perfect schedule you can’t sustain, provided you’re not stacking them consecutively.

Nor do you need a structured session plan at the beginning. Your plan is three slow runs a week until you’ve done roughly 20 runs. Distance can go up and down depending on how each run goes and how much time you have. Aim for 20-minute runs at first, building to 30 minutes after a few months. The goal is to feel comfortable nipping out for a quick run and getting on with the rest of your day. If running is taking over a large part of your day, you’re doing too much, running too fast or running too far.

The pattern underneath all nine

Seven of the nine are versions of the same thing: doing more, sooner, than your connective tissue has adapted to. Running fast, running further, running on rest days and starting too high are the same error in different clothes.

The other two are about effort in the wrong place, whether that’s shoes built for racing rather than easy miles or stretching when strength work would serve you better.

Your fitness will improve faster than your tissues, and the gap between them is where injuries live. Almost all beginner running advice is, at bottom, about managing that gap.

For your first 20 runs

  • Keep easy runs easy. Use the talk test, not a pace target.
  • Avoid load spikes above ~30% over two weeks, and take a down week every third or fourth week.
  • Keep rest days. No back-to-back runs at first; later, a consecutive day is fine if it’s short, flat and slow.
  • Buy a cushioned, comfortable daily trainer, ideally an older model without a nylon or carbon plate.
  • Swap pre-run stretching for twice-weekly hip and calf strength work.
  • Pinpoint pain, or pain worsening through a run, means stop.
  • Eat a balanced, normal diet. Easy beginner runs don’t need special fuel, but don’t cut food back hard either.

Running as a beginner is about adapting your life to become a runner, not about a race or a finish time. Once you are one, it’s likely to stay with you for the rest of your life.

I’ve been running easy for over five years, and it makes up the majority of my running. It’s what made me enjoy running in the first place, and it’s why I still do.

This article is general information, not medical or coaching advice.

References

  1. Kemler E, Blokland D, Backx F, Huisstede B. Differences in injury risk and characteristics of injuries between novice and experienced runners over a 4-year period. The Physician and Sportsmedicine, 2018. tandfonline.com
  2. Silva Oliveira P, Boppre G, Fonseca H. Comparison of polarized versus other types of endurance training intensity distribution on athletes’ endurance performance: a systematic review with meta-analysis. Sports Medicine, 2024. ncbi.nlm.nih.gov
  3. Nielsen RØ et al. Excessive progression in weekly running distance and risk of running-related injuries: an association which varies according to type of injury. Journal of Orthopaedic & Sports Physical Therapy (JOSPT), 2014. jospt.org
  4. Nigg BM et al. Running shoes and running injuries: mythbusting and a proposal for two new paradigms: ‘preferred movement path’ and ‘comfort filter’. British Journal of Sports Medicine, 2015. pubmed.ncbi.nlm.nih.gov
  5. Small K, Mc Naughton L, Matthews M. A systematic review into the efficacy of static stretching as part of a warm-up for the prevention of exercise-related injury. Research in Sports Medicine, 2008. tandfonline.com
  6. Aragon AA, Schoenfeld BJ. Nutrient timing revisited: is there a post-exercise anabolic window? Journal of the International Society of Sports Nutrition, 2013. ncbi.nlm.nih.gov

Topics

← Back to the Knowledgebase