Slowtwitch’s coaching advice puts easy runs and gradual mileage in focus. Here is how runners over 35 can interpret it alongside the evidence.
Slowtwitch’s feature “The Most Common Mistakes New Runners Make” discusses familiar training errors with Brad Hunter, a triathlon coach at Purple Patch Fitness. His central message is straightforward: keep easy running genuinely easy and build volume progressively rather than constantly finishing at your limit.
The title addresses beginners. But Hunter also includes experienced runners returning after a break, making the discussion relevant to ambitious athletes whose expectations may still reflect an earlier period of training. The useful question is not whether you already know these principles. It is whether your current training still reflects them.
Hunter advises runners to slow down on easy days while maintaining reasonably good form. Rather than making a particular pace the objective, he puts the emphasis on how the running feels and how the runner moves. The feature supplies no universal pace or heart-rate target.
That changes the standard for a successful easy run. Under Hunter’s approach, success is not making an ordinary training day look impressive. It is allowing the session to remain easy instead of turning it into another demanding effort.
His mileage advice follows the same logic. Hunter recommends adding volume progressively and leaving some capacity in reserve. He warns against a build-up that leaves the athlete constantly feeling “maxed out,” including when an experienced runner comes back after time away.
The feature also addresses pushing through injury and skipping strength work. Sleep and adequate food receive attention, as does the assumption that walking represents weakness. Taken together, Hunter’s advice asks runners to judge training by its purpose rather than by how much effort they can display.
Slowtwitch’s article is a coaching feature rather than a research report. It presents Hunter’s recommendations but does not cite a study or provide original injury or performance data. His experience supplies a practical perspective, not experimental proof that the recommendations produce a particular outcome.
Relevant research context comes from a summary of a 2025 observational cohort. That study followed 5,205 runners for 18 months and analyzed 588,071 running sessions. The summary reports that runs more than 10% longer than the runner’s longest outing in the previous 30 days were associated with higher overuse-injury rates.
The comparison matters: it concerned an individual run relative to the previous month’s longest run. It was not a test of a weekly-mileage formula. Because the study was observational, it also did not establish that staying below that increase prevents injury or that exceeding it causes injury.
Strength training has a separate evidence trail. A summary of a 2024 systematic review reports that some strength-training approaches improved running economy. That finding is not itself proof of faster race times or fewer injuries, and the secondary summary is not a substitute for assessing the underlying review in full.
The practical distinction is between related questions. How quickly to increase a long run is one question. Whether a particular strength approach improves running economy is another. Neither should be turned into a broader promise simply because the advice sounds sensible.
The feature does not report age-specific findings or test whether its recommendations work differently for runners aged 35 to 65. Its relevance to this audience comes from the training situations Hunter discusses, especially returning after a break. It is not evidence for a separate masters-age prescription.
Hunter’s cue offers a useful way to review an easy day: was maintaining an old pace more important than keeping the effort easy? That is a question about the purpose of the session, not a demand to hit another performance marker.
For an experienced athlete, familiar pace numbers can become an expectation rather than a neutral observation. Hunter’s advice puts the intended effort first while retaining reasonable form. There is no need to turn that into a new pace target that every runner must match.
This is a useful distinction for ambitious athletes. Taking an easy day seriously does not require making it harder. In the coaching approach presented here, restraint is part of carrying out the session as intended.
Hunter explicitly warns that experience does not exempt a returning runner from building progressively. A past training block may explain your ambitions. It does not describe the running you have completed recently.
The cohort finding gives that discussion a more precise focus: compare a proposed long outing with the longest run in your recent training. Looking only at a weekly total can miss the particular single-session increase examined in that study.
For a training review, those are distinct questions: how much running is being added overall, and how different is the longest session from recent outings? Hunter’s broader guidance concerns progressive volume. The research summary draws attention to the second question.
Our discussion of mileage expectations after time away addresses a related planning issue. The relevant starting point is the training that has actually happened, not the schedule that was originally written.
Hunter recommends considering swimming, cycling or strength work during a running injury when the injury allows those activities. His return-to-running example emphasizes rebuilding frequency before extending individual sessions.
That example is not a medically validated timetable. The feature does not specify diagnoses, readiness tests or clinical clearance criteria. Decisions about appropriate activity and readiness to resume running belong with a qualified clinician who can assess the individual injury.
The useful coaching principle is narrower than a rehabilitation plan: returning to running does not have to mean immediately returning to long runs. Frequency and session length are separate decisions. Hunter’s example gives priority to re-establishing regular running rather than making each outing substantial.
Hunter argues for keeping strength work in the training mix, particularly for runners experiencing injuries. The review summary adds a performance-related reason to consider certain strength approaches through its findings on running economy.
Those are different reasons, and they deserve separate evaluation. Strength work should not be assigned every possible benefit simply because it is a recurring recommendation in running advice.
A practical planning question is what the strength session is intended to contribute. Another is where that session belongs alongside demanding running. Keeping those questions explicit makes the discussion more useful than treating strength work as an undefined extra that must fit somewhere.
Hunter recommends aiming for seven to eight hours of sleep and eating enough to support training demands. The feature presents these as practitioner recommendations without quantifying their effects or establishing an athlete-specific target.
For a runner reviewing a training block, the practical point is to include these habits in the conversation rather than discussing mileage alone. Hunter’s framework considers what supports the running as well as the running itself.
That is a broader view of preparation, not a reason to make every night or meal another competitive score. Personal sleep or nutrition concerns warrant qualified guidance rather than assumptions drawn from a general coaching article.
Hunter challenges the idea that walking signals weakness. He says walk breaks can help keep stress low on easy days and suggests that planned walking may help some runners avoid a larger late-race slowdown.
The shift is in how the option is judged. Under his approach, walking can serve the purpose of a session rather than represent a failure to complete it properly.
There is no obligation to add walk breaks simply because they appear in the feature. The useful takeaway is that a runner can consider them without treating continuous running as the only acceptable way to train or race.
Slowtwitch’s feature offers a clear coaching perspective: easy days should stay easy, volume should build progressively, and returning runners should not confuse previous experience with current preparation. Strength work and supporting habits belong in the discussion without being assigned unsupported benefits.
For Reendure, the value is in keeping ambition and evidence together. The cohort summary gives a reason to pay attention to abrupt single-run increases. Hunter’s advice provides a practical framework for reviewing the purpose of everyday training.
Neither requires a wholesale change to an established plan. A useful starting point is simply to ask whether easy sessions remain easy and whether planned running reflects recent training. The objective is not to do less by default. It is to make deliberate choices that match the work you are ready to do.
Follow ReEndure for practical insights on endurance training, recovery, nutrition and healthy aging. Stay connected for new articles, research led guidance and ideas to help you perform better for longer.
Read practical ideas on endurance training, recovery, nutrition and healthy aging to keep progressing for years to come.
Read the Blog