> ## Content Index > Fetch the complete content index at: https://bastian.ghost.preview.themeanax.com/llms.txt > Use this file to discover other available public pages before exploring further. # The Case for Training Fewer Lifts, Better - URL: https://bastian.ghost.preview.themeanax.com/the-case-for-training-fewer-lifts-better/ - Published: 2026-08-03T05:43:14.000Z - Updated: 2026-09-07T12:47:00.000Z - Description: The interesting thing about strength training is how rarely the hard part is the part everyone prepares for. - Author: Bastian Team - Tags: #themeseed, Strength training, Practice, Strength Strength training is one of those topics where the obvious answer is right about sixty per cent of the time, which is exactly often enough to be dangerous. ## The numbers Consistency is worth more than any individual improvement to strength training. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison. ![black adjustable-weight barbell](https://bastian.ghost.preview.themeanax.com/content/images/2026/09/photo-1534368270820-9de3d8053204-1.jpg) Photo by Alora Griffiths on Unsplash It helps to separate the decision from the execution. Strength training rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. Measurement is usually where this falls apart. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it. ## How we knew it was working Most of the difficulty lives at the boundaries, not in the middle. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem. ![woman doing weight lifting](https://bastian.ghost.preview.themeanax.com/content/images/2026/09/photo-1541534741688-6078c6bfb5c5.jpg) ![a man and woman exercising](https://bastian.ghost.preview.themeanax.com/content/images/2026/09/photo-1648542036561-e1d66a5ae2b1.jpg) ![two person inside gym exercising](https://bastian.ghost.preview.themeanax.com/content/images/2026/09/photo-1534258936925-c58bed479fcb.jpg) Strength training in practice Speed and reversibility are the trade-off worth naming out loud. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. The second-order effects arrive about a quarter after the first-order ones. The things that are easy to count are rarely the things that matter, and once a number reaches a dashboard it starts shaping behaviour whether or not it deserves to. There are organisations where the opposite is true, and they are not obviously worse off. ## What we tried first Nobody gets credit for the work that did not need doing. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. Documentation is a symptom: you write it where the design is unclear. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. That said, none of this generalises cleanly across team sizes. ## The situation The default answer is right often enough to be dangerous. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. This is easier to write than to hold to when a deadline appears. The interesting constraint is almost never the one in the brief. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer. The expensive mistakes here are rarely the technical ones. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. ## What it cost There is a version of strength training that is mostly ritual. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests. Consider the failure mode rather than the success case. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound. Scope is the variable everyone adjusts last and should adjust first. The first quarter shows the intended effect; the second shows what the intended effect displaced. When we mapped it out, four of the seven steps existed only to compensate for the second one. > You can have it fast, or you can have it reversible. Pick before you start, not after. — Overheard in a retrospective ## The part that surprised us The compounding effects matter far more than the individual wins. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. What looks like a process problem is frequently an ownership problem. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. It is worth saying that we have not run this long enough to be confident. The first thing to establish is what you are actually optimising for. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. The checklist we ended up with: - Decide in advance what would make you stop - Name one person accountable — not a group - Prefer the reversible option when the evidence is thin - Agree on what "done" means, in writing, before starting - Keep the feedback loop shorter than the planning cycle ## What changed A shared definition of "done" removes more friction than any tool. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. A useful test: if this disappeared tomorrow, how long before anyone noticed? Feedback loops shorter than the planning cycle change everything. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. The evidence here is thinner than anyone quoting it tends to admit. The tooling question is downstream of the constraint question. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests. ## Where it still breaks A shared definition of "done" removes more friction than any tool. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. The first thing to establish is what you are actually optimising for. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. ## What we would do differently It helps to separate the decision from the execution. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. Measurement is usually where this falls apart. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. The evidence here is thinner than anyone quoting it tends to admit. The expensive mistakes here are rarely the technical ones. The first quarter shows the intended effect; the second shows what the intended effect displaced. ## The numbers There is a version of strength training that is mostly ritual. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. This is easier to write than to hold to when a deadline appears. The interesting constraint is almost never the one in the brief. Strength training rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. ## How we knew it was working Nobody gets credit for the work that did not need doing. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem. Most of the difficulty lives at the boundaries, not in the middle. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. In practice the answer showed up in the calendar before it showed up in the dashboard. ## What we tried first Scope is the variable everyone adjusts last and should adjust first. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. Feedback loops shorter than the planning cycle change everything. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound. Documentation is a symptom: you write it where the design is unclear. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. The version of this that works fits on an index card. The version that fails needs an onboarding session. If there is one thing worth carrying away, it is that the expensive mistakes in strength training are almost never technical ones.