The useful question after a set
After a working set, the next training decision rarely needs a perfect scientific number. It needs a credible answer to a simpler question: how did that set actually feel?
Traditional effort scales can be valuable, especially for experienced lifters and coaches. They can also create friction for people who do not want to distinguish between many neighbouring scores while breathing hard.
Three states, three practical meanings
Easy
The target was completed with clear capacity left. The next session may be ready for more load, more reps or another progression step, depending on the exercise and the rest of the session.
Good
The set was challenging but controlled. This is the normal working zone: enough difficulty to matter without turning every set into a test.
Max
The set was at or near the user’s current limit. The system should be cautious about adding more and should preserve context such as missed reps, longer rest or poor readiness.
Why the user’s judgement matters
Sensors and formulas can estimate fatigue, but they do not replace the person who performed the set. A watch may observe heart rate. The app knows weight and reps. Only the user can confirm that technique broke down, a joint felt wrong or the set was easier than the numbers suggest.
User-confirmed reality should outrank an estimate.
One tap works because the plan is already visible
Easy, Good and Max are not meant to replace weight and reps. They work because the app already knows the planned target. The user is confirming the judgement that is missing from the numbers.
That lets one tap record a meaningful set, begin rest and prepare the next target. Edits remain available when reality differed, but the common path does not begin with a form.
What the three labels should not become
- A score used to shame the user for training lightly.
- A hidden requirement to tap Max for “better” progress.
- A substitute for pain, injury or technique controls.
- A fake promise that three buttons can understand the whole body.
The labels are a compact input, not an oracle. Their value comes from being combined with confirmed load, reps, completion, exercise type and the user’s recent history.
Simplicity in front, context underneath
The design goal is a calm surface with careful logic behind it. The user should not perform the calculation during the workout. They should make one human judgement and continue lifting.