The short answer: IT band syndrome is a load related injury, meaning it shows up when training volume or intensity rises faster than the body can adapt. It accounts for roughly 10 to 12% of all running related injuries. Stretching, foam rolling, and manual therapy can ease the pain temporarily, but none of them fix the actual cause, which is almost always the programming.
Table of Contents
Sharp pain on the outside of the knee, caused by the iliotibial band being repeatedly loaded faster than it can adapt. It’s one of the most common running injuries, and it’s also one of the most misunderstood, because the pain shows up at the knee while the actual cause is almost always somewhere else entirely: the training plan.
Because it’s a load related issue. The tissue can’t adapt fast enough to the increase in running volume or intensity it’s being asked to handle. That’s the actual definition, and it points directly at training structure, not bad luck or bad anatomy.
The fix for an overuse injury is never more of what caused it. It’s proper progression, calculated for the individual runner, not a generic template applied the same way to everyone.
Because they treat the symptom at the knee, not the training error that caused it. A systematic review of conservative treatments for IT band syndrome found no clear consensus on which combination of stretching, manual therapy, or other passive treatments works best, and that’s not surprising once you understand why.
These approaches can genuinely ease pain in the short term. But if the underlying training plan is still progressing volume or intensity faster than that runner can adapt to, the pain simply comes back once running resumes at the same flawed pace. That’s the band-aid problem in a sentence: it treats where it hurts, not why it started hurting.
Runners who’ve struggled with IT band syndrome for years, sometimes on their own, sometimes with other coaches or trainers, almost always share the same training history: generic plans, cookie cutter schedules, or progression that wasn’t matched to their actual current fitness. Over years of coaching, this is a pattern I’ve now seen play out hundreds of times.
Not because of a new stretch. Not because of a new strengthening routine. Because the programming, the actual root cause, finally got fixed.
Precise, individually calculated progression, meaning volume and intensity increase at a rate that specific runner’s body can actually adapt to. That’s Smart training, and it’s the piece missing from almost every case of chronic IT band syndrome we see.
This is the same principle covered across the rest of this training approach: How to Train for a Marathon Without Injury and What Is Customized Marathon Training and Why It Works.
Gradually, and matched to what that tissue has actually adapted to, not a fixed timeline applied the same way to every runner. A common, sensible progression starts with shorter, flatter runs, builds frequency before distance, and adds hills and speed work last.
Runners who return to their old mileage and pace immediately, without a recalculated plan, are simply recreating the exact load mismatch that caused the injury in the first place. The tissue heals. The programming problem doesn’t, unless it’s actually addressed.
The same way it gets fixed once it happens: paces and volume calculated from current fitness, reassessed as that fitness improves. That’s Hard, Smart, and Consistent training, and it’s the entire prevention strategy, not a list of supplemental exercises.
Runners training inside a community are encouraged to hold their own calculated paces rather than match a group’s, which matters here specifically, since running someone else’s pace is a common, avoidable way to overuse a tissue that wasn’t ready for that load. That’s part of the philosophy behind the St. Pete Run Club.
What percentage of running injuries are IT band syndrome?
Roughly 10 to 12% of all running related injuries, making it one of the most common overuse injuries among runners.
Does stretching or foam rolling cure IT band syndrome?
Not on its own. These can ease pain temporarily, but a systematic review of conservative treatments found no clear consensus on which passive approach works best, largely because none of them address the training load that caused the injury.
Why does IT band syndrome keep coming back after treatment?
Because the underlying training error, usually progression that outpaced the runner’s actual fitness, was never corrected. Treating the pain without fixing the programming means the same load mismatch recreates the injury.