On the subject in the title: Second pass at: Programming during a large energy deficit Working notes rather than a conclusion.
The question about Programming during a large energy that I actually want answered is the second one below. The first is context and I have kept it short.
Both are stated with units, and I have said what I already checked so that nobody repeats it.
Coming back to the opening post, because the follow-up matters more than the original answer.
Recovery capacity falls with energy availability, so a programme that worked at maintenance may be too much during a large deficit.
I have changed my mind on this once already, so take it as current rather than settled.
Frequency: three sessions per week of full-body training is easier to maintain than higher frequencies on an energy deficit. Consistency beats intensity when recovery capacity is limited.
This follows post #2 rather than contradicting it.
The confident answers on Programming during a large energy and the well-sourced answers are not the same answers, which is the most useful thing I have learned reading this category.
Where I have landed on Programming during a large energy, having got it wrong once in public: the direction is clear, the magnitude is not, and anyone quoting a precise magnitude has borrowed it from somewhere that did not measure it.
Seconded. It reads as careful rather than confident, which is the right register.
Worth separating two things that post #4 runs together.
Maintenance phases are where most people report training going best, which is unsurprising and is worth saying to anybody struggling during loss.
Take the reasoning and check the arithmetic; I do not always get it right.
Machine-based work is often better tolerated when energy is low and is not inferior for this purpose.
Reduced appetite makes fuelling a session harder, and that is a practical problem with practical solutions rather than a reason to stop.
On post #8 — agreed on the reasoning, with one qualification.
Where training is new, the early gains are largely neural, which is why they can appear even during a deficit and do not indicate tissue change.
The confident version of this sentence would be wrong, so here is the hedged one.
Post #11 answers the question as asked. The question underneath it is different.
The reports here that state the programme, the load and the timeframe are useful. The ones that state an outcome are not.
Worth reading the earlier posts in this thread before acting on mine.
Recovery: heavier training on a energy deficit and on a compound that slows gastric emptying requires attention to recovery (sleep, nutrition, stress). Recovery capacity declines with deficit, so training volume might need adjustment.
A single observation, in a thread that deserves better than single observations.
Reading rather than contributing, but this is the most useful thread I have found on it.
Performance usually declines somewhat during a substantial deficit, and expecting it to improve is the most common source of disappointment reported here.
Post #15 is right about the mechanism and I think understates the practical bit.
Adaptation and plateau: if strength does not change for weeks, that is stability, not backsliding. Expecting continuous progress during weight loss is unrealistic.
Useful. I have added it to my own notes with the date on it.
Maintenance is the goal: preserving lean mass and strength during weight loss is the goal of resistance training in this context, not building new muscle. That goal is usually achievable with consistent, moderate training.
Post-weight-loss training: once weight loss is complete and energy deficit ends, training can shift to building again. The transition from preservation mode to building mode is real and worth planning.
The right answer here may simply be that it has not been measured.
Programming during a large energy would be much easier to settle if anyone reported the denominator. Almost nobody reports the denominator.
This follows post #20 rather than contradicting it.
Distinguishing three things in the Programming during a large energy discussion that keep getting used interchangeably: the observation, the proposed mechanism, and the recommendation that gets attached to both.
Right — I had this wrong and I am glad to have read it before it mattered.
That is a fair summary of where the discussion has got to.
Trying to state the Programming during a large energy position in a way that someone who disagrees would recognise as fair, because I do not think the version in this thread passes that test.
Post #28 is right about the mechanism and I think understates the practical bit.
Maintaining load with reduced volume is a reasonable strategy during a deficit and appears in the published literature more than the reverse.
It is the kind of thing that is obvious once and never again.
Helpful, and easy to find again, which is half of what a good reply is.