Research Brief

What They Studied

A 4% improvement in running economy from a single exercise sounds too clean. But this controlled study from Humboldt University tested exactly that: whether heavy isometric calf training changes how efficiently the soleus muscle operates during running.

Runners in the training group performed 5 sets of 4 isometric plantar flexion contractions (holding, not moving, like a wall sit for your calf) at 90% of their max strength, 3-4 times per week. Load was adjusted every 2 weeks. The control group kept running as usual.

Researchers measured plantar flexor strength, Achilles tendon stiffness, the energy cost of running at a fixed pace, and soleus muscle behavior using ultrasound imaging at 146 frames per second.

What They Found

• Running got cheaper: The training group used 4% less energy at the same pace. The control group didn't change. Absolute values (10.6 to 10.2 W/kg) pointed the same direction.

• The Achilles got stiffer: Tendon stiffness jumped roughly 31% in the training group. No change in controls. A stiffer tendon sounds like a bad thing? Not here. It's what allowed the soleus to work more efficiently.

• Calf strength climbed ~10%: Maximal plantar flexion force rose meaningfully across the training group. The effect was clear, not due to chance.

• The soleus got more efficient in early stance: During the phase where your Achilles tendon stretches and your soleus contracts, efficiency rose from 77% to 88% of the muscle's theoretical max. That's where your running economy was won.

• Late stance was already near ceiling: Efficiency during the shortening phase was already at 93-94% of max. No room to improve, and none did. The gains came from the phase that was lagging.

• Muscle activation dropped ~12%: The soleus needed less neural drive to do the same job. Think of it as your calf running the same pace on less effort. (That's efficiency, not just strength.)

What This Means for You

• Your stride didn't change. Your engine did. Cadence, contact time, flight time, and joint angles were all unchanged after training. The 4% economy improvement came entirely from how your calf muscle contracted, not from any visible change in your gait.

• This reframes what calf training does for you. Most runners target the calf for durability. This study suggests a stiffer Achilles tendon shifts how your soleus operates during each stride, allowing it to produce the same force at a lower metabolic cost.

• The efficiency gain was phase-specific. Your soleus already operates near peak efficiency during push-off. The improvement happened in early stance, when the tendon is loading and the muscle is doing its most metabolically expensive work.

• The effect was moderate to large by research standards. For a single training addition layered onto your existing program, that's a substantial signal. Could it be even bigger in faster runners with more room to improve? Possibly, but this study didn't test that.

• But this is one lab, one speed, one study. 13 runners in the training group. All recreational. All tested at a single treadmill pace (roughly 6.2 miles per hour (10 km/h)). Whether this holds at faster paces, in trained runners, or over longer time frames remains unknown.

How to Use This

• What this supports: Heavy isometric calf loading as a tool for improving running economy, not just Achilles tendon resilience. A stiffer tendon changes how efficiently your calf works during each step.

• What this does NOT support: Generic calf raises as a substitute for high-intensity isometric loading. The protocol used 90% of max voluntary contraction. Bodyweight calf raises on a step aren't in the same category. Load magnitude and specificity drove the tendon adaptation.

• How to apply this: Add the protocol from this study to your strength work 3-4 days per week. Use a leg press, Smith machine, or similar setup to hold a maximal isometric plantar flexion. Target 90% of your max. Reassess your max every 2 weeks and adjust.

• Big Picture: Running economy isn't just about form cues and shoe choice. The contractile efficiency of your calf musculature responds to targeted, heavy loading.

Sample 14-Week Isometric Calf Integration

How to layer this protocol into a typical training week. The study used 3-4 sessions per week on top of normal running.

The ramp-in phase is a practical addition, not from the study protocol. The study began at 90% MVC from week 1 in a supervised lab. If you don't have access to biofeedback, start conservative and build. Individual tolerance varies. The principle: load must be near-maximal and isometric to drive tendon adaptation.

What They Studied

19 recreational runners. Five speeds. Four gradients. Three cadences. One question: where does tissue damage actually accumulate?

Researchers used 3D motion capture and musculoskeletal modeling to estimate forces at three common injury sites: the kneecap (patellofemoral joint), the shinbone (tibia), and the Achilles tendon. They calculated two separate metrics for each site. First, cumulative load: total force multiplied by steps per kilometer. Second, cumulative damage: a weighted version that accounts for how tissues break down nonlinearly under repeated stress.

The distinction matters because bone and tendon don't fail in proportion to load. They fail on a power-law curve. Double the force per step, and you don't double the damage. You multiply it.

What They Found

• Load went down. Damage went up. Cumulative load decreased with speed for all three tissues (fewer steps per km). But cumulative damage increased, reaching significance at the kneecap (damage rose roughly 0.25 units for every 1 m/s increase in speed). Achilles tendon and shinbone trended the same direction.

• The kneecap took the biggest hit from speed. Patellofemoral cumulative damage rose from 11.5 at the slowest pace to 12.1 at 4.0 m/s. That's a modest absolute change, but it moved in the opposite direction from cumulative load, which dropped 30%.

• Uphill doesn't solve what you think it solves. Running uphill reduced kneecap damage (36% less compressive force at +6 degrees) but increased Achilles tendon damage more than it decreased kneecap damage. You're not reducing total tissue cost. You're shifting where it lands.

• Downhill is the mirror image. Steeper declines raised kneecap and shinbone damage while lowering Achilles tendon damage. Your trunk position changes which tissues absorb the load. Neither direction wins across all three sites.

• Cadence is the only lever that worked everywhere. Increasing cadence by 10 steps per minute reduced cumulative damage at all three injury sites simultaneously. Nothing else achieved that. Not speed. Not gradient.

• The nonlinearity is staggering. Lab testing on isolated tendon tissue shows that halving Achilles tendon strain (6% to 3%) extended fatigue life from ~1,400 cycles to ~93,000 cycles. That's a 6,600% increase in durability from a 50% reduction in strain.

What This Means for You

• Your watch is tracking the wrong number. If your app shows "lower load" after a fast interval session than after a slow long run, it may be right about load but wrong about tissue stress. The forces per step were higher. The damage per kilometer was likely higher too.

• Speed shifts don't reduce total tissue cost. You take fewer steps per kilometer when you run faster. That's real. But each step hits harder, and tissues don't absorb force linearly. A small increase in per-step force creates a disproportionate increase in damage.

• Hills are a trade, not a solution. Rehabbing a knee issue and switching to uphill running? You're reducing kneecap stress but increasing Achilles tendon and shinbone stress by a larger margin. The net tissue cost went up, not down.

• This is a modeling study, not a prospective injury trial. The researchers used validated biomechanical models, not direct tissue measurements. Absolute damage values may differ from in vivo. But relative comparisons across conditions are robust because the same model was applied to every runner in every condition.

• The sample was young and recreational. Mean age 23.6, all free of recent injuries. Your tissues may respond differently if you're older, carrying prior damage, or running higher weekly volume.

How to Use This

• What this supports: Cadence as a first-line load management tool. Adding 10 steps per minute to your preferred cadence reduced cumulative damage at the kneecap, shinbone, and Achilles tendon simultaneously. No other variable tested achieved this.

• What this does NOT support: Using hills to "protect" a single injury site. Uphill running reduced kneecap damage but increased Achilles and shinbone damage by more than the kneecap gained. Downhill did the reverse. Gradient is a tissue trade-off, not a tissue solution.

• How to apply this: Count your current cadence on an easy run. Add 5 steps per minute for two weeks. Then add another 5. Use a metronome app or your watch's cadence alert. Target your sessions where you're most concerned about tissue stress, not every run.

• Big Picture: Cumulative load and cumulative damage diverge at faster paces. Managing per-step forces through cadence is a more reliable strategy than managing total steps through speed or terrain.

Sample Cadence Adjustment Plan

A 4-week ramp from preferred cadence to +10 steps per minute, based on the study's tested intervention. Apply during easy and moderate runs first. Speed sessions can follow once the pattern feels natural.

Individual cadence varies. The principle: small, sustained increases reduce per-step force and cumulative damage across all three tissue sites. If a +10 change feels forced, hold at +5. The damage reduction scales with the change.

What They Studied

The science behind sodium bicarbonate is straightforward: it buffers acid in your blood, letting your muscles work harder before hydrogen ions shut them down. Prof. Lewis Gough calls the mechanism "about as clean as it gets in sports nutrition."

This is the first meta-analysis focused specifically on sodium bicarbonate and running performance. All 11 studies used crossover designs, meaning each runner tried both the supplement and a placebo. Doses ranged from 0.2 to 0.4 g/kg, with 9 of 11 studies using 0.3 g/kg. Performance tests lasted 1 to 30 minutes, with a median of 4 minutes. The population was 84% male, mostly competitive runners aged 20-31.

The companion source, Prof. Lewis Gough on Sigma Nutrition Radio (#580), provides the mechanism framework. Gough is an associate professor specializing in bicarbonate research at Birmingham City University.

What They Found

• The unadjusted number looks promising: A small, statistically significant benefit on running performance. But that number doesn't account for runners who dropped out due to stomach problems.

• Adjust for GI dropouts, and it shrinks: When researchers included the runners who withdrew because of GI distress, the effect dipped. Still significant, but smaller.

• Adjust for publication bias, and it disappears: Four estimated unpublished null-result studies were imputed. The final adjusted effect fell below the authors' own threshold for "negligible." Not statistically significant.

• Nearly 1 in 3 got GI symptoms: 29.5% of runners on bicarbonate reported GI issues versus 2.6% on placebo. Diarrhea (9%), nausea/vomiting (6.4%), and stomachache (5.1%) were the most common.

• One subgroup stood out: Males showed a small, significant benefit even after all adjustments. Higher body mass also predicted a bigger response. Why does bicarb work better in heavier males? Still unclear. (The female data barely exists. Only 16% of participants were women.)

• Nothing else predicted the effect: Training status, dose timing, capsule vs. powder, fasted vs. fed, test duration. None reached statistical significance.

What This Means for You

• The mechanism is solid. Gough explains that bicarbonate buffers hydrogen ions in your blood. This creates a steeper gradient that pulls acid out of working muscles faster. That's real physiology. The problem isn't whether it works in a test tube. It's whether it works in your gut.

• If you're a male runner with higher body mass doing short, hard efforts (1-10 minutes), this is the one population where the adjusted data still shows a meaningful effect. Think 800m to 3K specialists, not marathoners.

• For longer events, the evidence is thin. All 11 studies tested efforts under 30 minutes. No data exists on marathon or half-marathon performance. Your 5K might benefit. Your marathon fueling plan doesn't need bicarb.

• The 29.5% GI symptom rate is the number that should change your risk calculation. A 1-in-3 chance of GI distress during a race is a race-ending gamble, not a marginal supplement decision.

• Gough notes that 10-20% of people appear to be non-responders regardless of protocol. Hypothesized reason: individual differences in muscle fiber distribution. You won't know if you're a responder until you test it in training.

• The timing window varies more than most protocols suggest. Blood bicarbonate peaks anywhere from 40 minutes to 2.5 hours post-ingestion. The standard "90 minutes before" may miss your personal peak entirely.

How to Use This

• What this supports: Individual experimentation with bicarbonate for short, high-intensity running events (1-10 minutes). Testing in training before any competition use. Using the 0.2-0.3 g/kg dose range.

• What this does NOT support: Using bicarb for marathon or half-marathon performance (no data exists for efforts beyond 30 minutes). Assuming a universal benefit for all runners. Trusting unadjusted effect sizes from prior reviews that didn't account for GI dropouts or publication bias. Skipping GI tolerance testing because "the science says it works."

• How to apply this: If you race short events and want to test bicarb, start with 0.2 g/kg in capsule or enteric-coated form, 90 minutes before a hard training session. Test at least twice in training before considering race use. If you tolerate it, try 0.3 g/kg. If GI symptoms appear at any dose, bicarb isn't for you.

• Big Picture: Sodium bicarbonate has a clean mechanism and a messy track record. For most distance runners, the risk-benefit math doesn't favor it.

What They Studied

Seven studies. Thirteen elite Norwegian distance runners. Four decades of training data, from Grete Waitz in 1979 to the Ingebrigtsen brothers in 2019.

This systematic review compiled publicly available training logs from athletes racing 1500m through 10,000m. All data were classified using a 5-zone intensity scale based on lactate and heart rate thresholds.

The goal: document what "Norwegian training" actually looks like when you strip the social media away. If you've ever wondered whether the method is really just "run easy and do threshold work," the answer is more specific than that.

What They Found

• Easy running dominated everything: 75-80% of weekly volume sat in Zone 1 (below 2.0 mmol/L lactate, 62-82% max heart rate) for 12 of 13 athletes. Weekly totals ranged from 75 to 112 miles (120-180 km). The average was roughly 100 miles (160 km) per week.

• Threshold wasn't occasional. It was systematic: 15-20% of weekly mileage hit Zone 2 (2.0-4.0 mmol/L lactate, 82-92% max heart rate). That translates to roughly 18.5-25 miles (30-40 km) of threshold work per week.

• The "double threshold" day is the signature move: The Ingebrigtsen brothers ran two threshold sessions on the same day, twice per week. Morning: 5 x 6-minute efforts at marathon pace, lactate held below 2.5 mmol/L. Afternoon (5-6 hours later): shorter intervals at 5K-10K pace. Think 12 x 1000m or 25 x 400m, lactate below 3.5 mmol/L for most of session.

• High intensity was minimal: Zone 3 (4.0-8.0 mmol/L, 92-97% max heart rate) barely appeared during the base period. Zone 4 (above 97% max heart rate) was limited to 1-2 sessions per week. Think 20 x 200m hill runs, not 5K races.

• The pre-competition shift was specific: 6-10 weeks before racing, athletes added race-pace intervals at Zone 4 intensity while cutting Zone 2 threshold frequency. So what changed in your weekly split closer to race day? Henrik Ingebrigtsen's race-free weeks ran a 75:25 low-to-high ratio. Race weeks: 80:20. Less threshold, more race-specific speed.

• One outlier across 40 years: Grete Waitz (1979) spent just 52% of training at low intensity and 43% at threshold. Every other athlete in the review clustered at 75-80% low intensity. The authors don't fully explain this. (Different era, different event focus, or different classification methods could all contribute.)

What This Means for You

The "Norwegian method" has become shorthand for "do threshold work." That misses the point. The real method is 75-80% easy running with threshold sessions controlled by lactate, not pace.

Most runners who try double threshold days end up running them too hard. Without lactate monitoring, a "threshold" session drifts into Zone 3 or 4. You accumulate fatigue instead of aerobic adaptation.

The lactate targets are the operational detail that makes the volume sustainable. Morning sessions stayed below 2.5 mmol/L. Afternoon sessions stayed below 3.5 mmol/L. These aren't arbitrary numbers. They're the ceiling that keeps threshold work aerobic enough to recover from by the next day.

Your weekly volume matters more than your workout intensity. Norwegian juniors averaged 71.5-90 miles (115-145 km) per week while Spanish juniors of similar age ran 43.5 miles (70 km). The difference wasn't intensity. It was low-intensity volume.

These are elite athletes running 10-14 sessions per week. Generalizability to recreational runners wasn't addressed in any of the 7 studies. Applying elite protocols without scaling is a recipe for overtraining, not adaptation.

The review spans 1979 to 2019, so training environment, equipment, and support varied widely. Direct comparisons across eras aren't straightforward.

How to Use This

• What this supports: A polarized training distribution with 75-80% of your volume genuinely easy (conversational pace, below 2.0 mmol/L if you measure). Threshold work as a structured, repeatable part of your week rather than an occasional hard effort. Using lactate or heart rate to govern intensity rather than pace alone.

• What this does NOT support: Copying elite Norwegian sessions at elite Norwegian volumes without years of base building. Running "double threshold" days without monitoring intensity, which almost guarantees drifting too hard. Treating Zone 3 work (tempo runs at 92-97% max heart rate) as the foundation of your training. Assuming more threshold is always better, since even these elites reduced threshold frequency before competition.

• How to apply this: Audit your current intensity split. If more than 25% of your weekly mileage is above easy effort, you're likely in the moderate zone too often. For threshold sessions, cap intensity with a measurable target. Use heart rate at 82-92% of max, or lactate between 2.0-4.0 mmol/L if you have a monitor. Want to test a double threshold structure? Start with one double day per week. Keep the morning session at a pace that feels like controlled marathon effort, not tempo. Keep total weekly mileage appropriate for your experience level.

• Big Picture: Norwegian training works because it protects the easy days, not because it invented a harder workout.

Sample Double Threshold Week (Adapted from Kalle Berglund's 2018-2019 Preseason)

This is the actual week structure from Berglund's training log. Berglund averaged 84 miles (135 km) per week with a peak of 98 miles (158 km). Recreational runners should scale volume, not structure.

This is an elite training week from a 3:33 1500m runner averaging 10+ sessions per week. For recreational runners: preserve the principles (easy/threshold/easy rhythm, morning session easier than afternoon, one high-intensity day) but scale to your volume. A single threshold day with one session, not two, is the entry point.