Shindo Two constraints, both of them refusals#
Most self-coached endurance athletes do not fail from lack of effort. They fail from two specific, well-documented patterns:
- Running the easy days too hard, which leaves nothing for the hard days.
- Increasing load faster than connective tissue can adapt to it.
Both are prevented by constraints, and constraints are unpopular because they take the form of a plan saying no. That is what this piece is about.
The 80/20 rule#
The finding, replicated across sports and across decades of observing elite endurance athletes: roughly 80% of training time at low intensity, and the remainder genuinely hard, outperforms distributions with more moderate work — including at equal total load.
Note that this describes time, not sessions. Eighty per cent of your minutes, not eighty per cent of your workouts.
Why the middle is the problem#
The temptation is to think the enemy is laziness. It is not. The enemy is the moderate zone — that comfortable, satisfying tempo effort that feels like real training.
Moderate work has an unfortunate profile: it generates substantial fatigue, comparable to genuinely hard work, while providing much less of the specific adaptive stimulus that hard work does, and much less of the aerobic base-building that easy work does. It is the worst of both.
The practical consequence for an athlete stuck there: easy days are too hard to allow recovery, so hard days cannot be hard enough to drive adaptation, and everything converges on one grey medium intensity. Progress stalls, the athlete concludes they need to train harder, and it gets worse.
The hard part is the easy part#
Almost everybody who tries 80/20 discovers that their easy pace needs to be substantially slower than they had been running. This is genuinely uncomfortable — it feels like you are not training — and it is where most attempts fail.
The test is conversational: you should be able to speak in full sentences. If you cannot, you are not in the easy zone, however easy it feels.
The ramp cap#
The second constraint. Weekly training load should grow by no more than about 8–10% week over week, with recovery weeks interrupting the progression regularly.
Why a cap, rather than trusting how you feel#
Because the systems in your body adapt at different speeds, and the one that limits you is not the one you can perceive.
Cardiovascular fitness responds within weeks. Tendon, ligament and bone remodel over months. So an athlete increasing volume aggressively develops the aerobic capacity to run further, well before the structural capacity to survive it. They feel fine right up to the moment they do not, and the perceived signal — “I can handle this” — is accurate about the cardiovascular system and blind to the tissue that actually fails.
Eight per cent works out to roughly 3–5 points of fitness a week. That is meaningful progression: over a 16-week block it is a substantial rise. It simply is not the 25% jump that feels available in week three of a block when motivation is high.
Why recovery weeks are scheduled, not earned#
The common cadence is 3:1 — three loading weeks, then a recovery week. The important word is planned. A recovery week taken in advance costs a small amount of fitness and prevents a large problem. A recovery week taken when you finally break costs weeks.
Adaptation happens during recovery, not during the work. A block with no recovery weeks is not a harder block; it is an incomplete one, in which the stimulus is applied and never converted.
Why a plan should refuse you#
Here is the part that matters, and the reason both of these belong in software rather than in an article you read once.
Every athlete, on a good week, wants more. Motivation is highest exactly when you are freshest, which is exactly when adding load is most tempting and least wise. Every athlete also, on a bad week, wants to make up what they missed — which stacks a missed week’s load onto the following one, producing precisely the spike the cap exists to prevent.
A plan that simply reflects what you ask for is not a plan. It is a calendar.
The useful behaviour is a plan that declines: that will not schedule a 25% jump because you feel good, will not let you repay a missed week by doubling the next one, will not put threshold intervals in a taper, and will not let every day of the week be a medium day. And that says so, out loud, rather than quietly building something smaller and letting you wonder.
This is uncomfortable software to use for about three weeks, and then it is the reason you are still training in month six.
The numbers, together#
If you take nothing else:
| Constraint | Value | What it prevents |
|---|---|---|
| Easy intensity share | At least 80% of training time | The moderate trap |
| Weekly load growth | Under about 8% | Overuse injury from outpacing tissue adaptation |
| Recovery cadence | Every fourth week | Accumulated fatigue that never converts to adaptation |
| Acute-to-chronic load ratio | 0.8 to 1.3 | Both spikes and detraining |
| Monotony | Under about 1.5 | Weeks with no real hard days and no real rest |
None of these are exotic. They are all in the published literature, they are all implemented across the better training platforms, and following them puts you ahead of most self-coached athletes — not because they are secret, but because they require saying no to yourself consistently, which is the one thing people are worst at.
Shindo enforces all five. Planned weekly load cannot grow more than 8%, plans are built to the 80% low-intensity threshold, recovery weeks land every fourth week, and workload ratio and monotony are checked continuously — including against any week the AI proposes. The methodology documents each constant.
Read next