One Kinase, Two Answers
Why you cannot train for everything at once — the interference effect at the level of the molecule that causes it.
"Do both" is the standard advice, and it's mostly right. But there's a real molecular conflict underneath it, and knowing where it lives is the difference between scheduling around it and wondering why nothing is moving.
The switch
Prolonged endurance work depletes ATP relative to AMP. That ratio is sensed by AMP-activated protein kinase — AMPK — which is activated by LKB1 when energy runs short.
AMPK then does two things that directly oppose muscle growth:
It phosphorylates TSC2, activating it. Active TSC2 switches off Rheb, and Rheb is the direct upstream activator of mTORC1. No Rheb, no mTORC1.
It phosphorylates Raptor, inhibiting mTORC1 assembly directly — a second, independent route to the same off-switch.
And simultaneously, AMPK drives PGC-1α, the master regulator of mitochondrial biogenesis. That's the thing you want from endurance training.
So it isn't a metaphor or a resource-allocation argument. It is one kinase with two opposing downstream consequences: the same switch that builds an aerobic engine suppresses the anabolic signal you lift for.
How big is it, actually
Smaller than the mechanism makes it sound, and this matters — people read "interference effect" and abandon cardio entirely, which trades a large mortality benefit for a modest hypertrophy one.
What the magnitude scales with:
- Endurance volume, far more than intensity. Long steady-state work interferes substantially more than short hard intervals, because AMPK activation tracks cumulative energy depletion.
- Proximity in time to the lifting session. Same-session, same-muscle is the worst case.
- Modality. Running interferes with lower-body hypertrophy considerably more than cycling, because the eccentric loading of running adds a muscle-damage cost that cycling largely avoids. If you must do both and legs matter, bike.
Upper-body hypertrophy is barely affected by running at all. The interference is substantially local.
The scheduling that follows
Separate conflicting sessions by six hours or more. The AMPK signal is transient; mTORC1 sensitivity recovers.
Put the priority quality first in the day, when the nervous system is fresh and neither signal is competing with accumulated fatigue.
Bias endurance toward intensity, not volume. One hard interval session captures most of the VO₂max benefit — which is the largest single mortality lever available — at a fraction of the AMPK exposure of several long easy sessions. This is the single highest-leverage adjustment on the page.
Run one primary quality per block, 8–16 weeks, and hold the others at maintenance. Maintenance is remarkably cheap: roughly a third of the volume that built a quality will hold it.
What doesn't conflict
Worth knowing, because the interference framing gets over-applied:
- Sprint speed and vertical jump are compatible with each other and with strength work. They're all rate-of-force-development qualities and they train the same machinery.
- Mobility conflicts with nothing.
- Heat exposure carries no anabolic conflict. Cold does — cold immersion near lifting blunts the acute inflammatory and satellite-cell response, attenuating the very signal the session generated. Keep cold hours away from lifting, or on other days.
The honest limit of the argument
The molecular pathway above is well characterised. The inference from it to the human interference effect is less clean than it appears — training studies show interference that is real but consistently smaller than the mechanism predicts, and the gap between "AMPK inhibits mTORC1 in a cell" and "you gained less muscle over ten weeks" contains a lot of unaccounted biology.
Take the scheduling advice. Hold the magnitude loosely. And don't drop cardio over it — the mortality data on cardiorespiratory fitness is far stronger than the interference data working against it.
This comes out of an ongoing protocol. The research behind it — every mechanism, every source tier, and an append-only record of everything it has gotten wrong — is at /protocol.
More writing
Measurement Without a Decision Is a Hobby
More data makes the signal-to-noise problem worse, not better, unless the analysis accounts for it. A counterweight to my own tracking article, and the rule that decides whether a metric earns its place.
What a Blood Panel Actually Tells You
A lab reference range describes the population that walked into the lab, and that population is not healthy. Here's how to read a standard panel, which numbers matter, and the one test you only need once in your life that almost nobody gets.