Progressive overload starts with remembering
Asking your body for a little more only works if you know what you asked for last time. What to write down after a set, and why memory is not enough.
Every strength program, whatever its name, rests on one idea: over time, you ask your body for a little more than it is used to. More weight, more reps, better control. That is progressive overload, and it is the least controversial thing in strength training.
What nobody tells you is that it has a prerequisite. To ask for a little more, you have to know exactly what you asked for last time.
The gap between two sessions
Two days pass, sometimes five. By the time you are back in front of the rack, the details of the last session have quietly gone: the load on the third set, whether the last two reps were clean or a struggle, how long you rested before the heaviest one.
You still remember the exercise. You rarely remember the number.
Memory rounds in the wrong direction
Estimating is not neutral. Left to memory, most people go back to a load they are comfortable with — the one they can picture themselves lifting, which is usually the one from two or three sessions ago, not the last one. Nothing feels wrong. The sessions go well. And six weeks later the numbers have not moved.
The opposite happens too: a good day, a load pulled out of nowhere, three sets that turn into a bad week. Both are the same problem — a decision taken without the previous line in front of you.
What is worth writing down
Less than you think:
- the load and the reps of each working set
- one word on how the last rep felt
- anything you changed on purpose: rest, tempo, order of exercises
That is enough to decide the next session. A training log is not an archive, and a set you write down after the fact, from memory, in the evening, is already a set you have estimated.
If you want a single number to follow over time, the 1RM calculator turns any working set into an estimated max: same set next week, one more rep, and the number moves.
The real constraint is time
The problem was never being convinced — everyone agrees a log is useful. The problem is that logging a set has to be faster than the rest between two sets, or it stops happening after a week.
That is the whole design brief of Basalt Lab: a set goes in with two taps, and the last time you did that exercise is already on screen when you start it. Not a diary to keep. A number to beat, put back in front of you at the moment you need it.