Lifters have a single, well-worn dial for progress: more weight, more reps, or more sets, moved one at a time. Runners have a dial too, weekly distance, and it gets turned just as often. The problem shows up when both dials live in the same week and get turned together. Squat numbers start sliding for no obvious reason, and the honest explanation is usually a running block that quietly outgrew the recovery budget it was sharing with the lifting.

Two progression clocks running at once

A lifting plan and a running plan each have their own idea of what "more" should look like this week, and neither one knows what the other is asking of your legs. Progressive overload on the bar and a mileage build on your feet are the same kind of demand: a small, repeated increase that only works if the body gets enough recovery to absorb it before the next increase lands. Run both clocks forward in the same week and you are not doing two moderate builds, you are doing one large one, on the same set of leg muscles and the same recovery system.

That is easy to miss because a training plan usually gets built as two separate decisions: how much to add to the squat this month, and how much to add to weekly mileage this month. Nobody sits down and decides to increase total leg workload by both amounts at once, it just happens by not looking at the two decisions together.

Move one dial, not two

The fix borrows directly from how progressive overload already works inside a single lift: change one variable, hold the rest steady, and see what the log says before changing the next one. Applied across disciplines, that means picking which one is building this block and which one is holding.

A running-focused block might add a bit of weekly distance for three or four weeks straight, while lifting volume for the legs stays where it already was, useful accessory work, not a volume push. A lifting-focused block flips it: legs push for new weight or reps, and running holds at whatever distance has already proven sustainable, rather than also climbing. Trying to build both at once is the version of "everything gets harder every week" that interval progression already runs into when every variable moves at once, just spread across a longer timescale.

Small steps, not jumps

Within a running build, the increase itself should look boring: a modest addition to last week's distance, repeated for a few weeks, then held or eased before the next step up. A week that adds a long run, a second interval session, and extra easy mileage all at once isn't a progression, it's three progressions stacked into one week, and the body doesn't get to treat them as small. The same discipline that keeps a lifting program from adding weight, reps, and frequency simultaneously applies here: one increase, held long enough to see whether it stuck, before adding the next.

The muscles don't know which discipline trained them

This is the part that gets missed most often. A heavy squat day and a long run both load the quads and glutes, just through different movement patterns, and neither the muscle nor the recovery system cares which discipline gets credit for the fatigue. Counting weekly sets per muscle group already covers why running volume belongs in that same mental tally even though it never shows up as a labeled "leg day." A week where running mileage is climbing is a week where leg training volume is climbing too, whether or not the lifting log says anything changed.

That is the practical reason to hold lifting volume steady, not add to it, during a week that is also pushing running distance. The legs are already absorbing more work than the lifting plan alone suggests.

Reading it from the log instead of guessing

The reason this is hard to manage from memory is that a distance increase rarely announces itself. It shows up two weeks later as a squat session that felt heavier than the number on the bar, and by then it's hard to remember whether last Tuesday's run was the long one or a normal one. Zirv's training summary reports weekly running distance and session count as a rolling total, with a trend indicator showing whether this week's distance moved up, held flat, or came down against the week before, the same week-over-week comparison used for strength training volume. That turns "did my mileage actually go up this month" from a guess into something you can check in the time it takes to glance at a dashboard tile.

What it will not do is tell you the increase was too much. It reports the trend, not a verdict, the same honest limitation as any log: the number is real, the interpretation of whether it is sustainable is still on you, read against how the lifting numbers in the same weeks are actually behaving.

Build one, hold the other

A workable pattern for a hybrid week: pick a block, three to six weeks, and decide upfront whether running distance or lifting numbers get to be the thing that climbs. During a running-build block, treat leg lifting as maintenance, same weight, same reps, nothing new asked of it. During a lifting-build block, hold weekly mileage at whatever level has already been comfortable rather than adding to it. Switch which one is building when the current block's progress levels off or a normal easier week is due, similar to how a lifting program eventually calls for a lighter week once it has been pushing for a while.

The takeaway

Running volume and lifting volume compete for the same recovery, whether or not the plan on paper treats them as connected. Progress one at a time: build running distance for a block while lifting holds, then flip it, the same rule that already governs progressing a single lift applied across disciplines instead of within one. Running volume counts toward the leg training your muscles are absorbing even when it never appears in a lifting log, so the block that's adding mileage is not the week to also add lifting volume for the same muscles. Check the weekly distance trend against how the lifting numbers are moving in the same stretch, and let that comparison, not a feeling, decide which dial turns next.