> ## 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. # Ashtanga's Second Series Is a Patience Test, Not a Flexibility One - URL: https://bastian.ghost.preview.themeanax.com/ashtanga-s-second-series-is-a-patience-test-not-a-flexibility-one/ - Published: 2026-09-07T12:46:12.000Z - Updated: 2026-09-07T12:46:22.000Z - Description: We spent a quarter trying to get yoga practice right, and the useful lessons were not the ones we expected. - Author: Bastian Team - Tags: #themeseed, Yoga practice, Notes, Practice, Most teams arrive at yoga practice the same way: something breaks, and the fix becomes a habit. ## What the data actually shows Nobody gets credit for the work that did not need doing. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. ![a person posing for the camera](https://bastian.ghost.preview.themeanax.com/content/images/2026/09/photo-1655712779546-a1c0ea613cd8.jpg) Photo by Kaspars Eglitis on Unsplash It helps to separate the decision from the execution. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison. ## Where this leaves us What looks like a process problem is frequently an ownership problem. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. The default answer is right often enough to be dangerous. 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. ## The objection worth taking seriously Consistency is worth more than any individual improvement to yoga practice. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound. Measurement is usually where this falls apart. Yoga practice rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. Feedback loops shorter than the planning cycle change everything. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. The evidence here is thinner than anyone quoting it tends to admit. ## A more modest claim The compounding effects matter far more than the individual wins. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. The tooling question is downstream of the constraint question. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. ## The incentive problem The first thing to establish is what you are actually optimising for. The first quarter shows the intended effect; the second shows what the intended effect displaced. There are organisations where the opposite is true, and they are not obviously worse off. Most of the difficulty lives at the boundaries, not in the middle. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem. Consider the failure mode rather than the success case. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. That said, none of this generalises cleanly across team sizes. > Every process is perfectly designed to get the results it gets. — Overheard in a retrospective ## How we got here The second-order effects arrive about a quarter after the first-order ones. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. There is a version of yoga practice that is mostly ritual. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. Scope is the variable everyone adjusts last and should adjust first. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. ## The received wisdom The expensive mistakes here are rarely the technical ones. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. The version of this that works fits on an index card. The version that fails needs an onboarding session. A shared definition of "done" removes more friction than any tool. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests. Documentation is a symptom: you write it where the design is unclear. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. This is easier to write than to hold to when a deadline appears. ## A different reading Speed and reversibility are the trade-off worth naming out loud. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. Set a date at which you will stop, and write down in advance what would make you stop earlier. The interesting constraint is almost never the one in the brief. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. The expensive mistakes here are rarely the technical ones. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. In practice the answer showed up in the calendar before it showed up in the dashboard. ## What would change our mind 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. 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. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. The clearest signal was that people stopped asking where things were. The default answer is right often enough to be dangerous. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not. What we look for now: 1. Prefer the reversible option when the evidence is thin 2. Keep the feedback loop shorter than the planning cycle 3. Write the constraint down before choosing a tool 4. Decide in advance what would make you stop ## What the data actually shows Documentation is a symptom: you write it where the design is unclear. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests. It helps to separate the decision from the execution. 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. ## Where this leaves us The interesting constraint is almost never the one in the brief. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. The tooling question is downstream of the constraint question. 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. This is easier to write than to hold to when a deadline appears. ## The objection worth taking seriously Measurement is usually where this falls apart. 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. What looks like a process problem is frequently an ownership problem. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. ## A more modest claim A shared definition of "done" removes more friction than any tool. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem. Nobody gets credit for the work that did not need doing. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. A useful test: if this disappeared tomorrow, how long before anyone noticed? The short version: decide what you are optimising for, write it down, and revisit it when the answer stops feeling obvious.