Ask ten people to define yoga practice and you will get ten answers, most of them describing a symptom rather than the thing itself.
The edge cases
Speed and reversibility are the trade-off worth naming out loud. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive.
Nobody gets credit for the work that did not need doing. 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.
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 short version
The default answer is right often enough to be dangerous. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.
The first thing to establish is what you are actually optimising for. 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.
There is a version of yoga practice that is mostly ritual. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix.
Where to go deeper
Measurement is usually where this falls apart. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. It is worth saying that we have not run this long enough to be confident.
Consistency is worth more than any individual improvement to yoga practice. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered.
The tooling question is downstream of the constraint question. 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.
How it works
Consider the failure mode rather than the success case. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes.
Feedback loops shorter than the planning cycle change everything. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted.
The compounding effects matter far more than the individual wins. 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. Set a date at which you will stop, and write down in advance what would make you stop earlier.
Every process is perfectly designed to get the results it gets.
— Overheard in a retrospective
A common misreading
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.
What looks like a process problem is frequently an ownership problem. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review.
Most of the difficulty lives at the boundaries, not in the middle. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. There are organisations where the opposite is true, and they are not obviously worse off.
What it is not
The expensive mistakes here are rarely the technical ones. Yoga practice rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.
The interesting constraint is almost never the one in the brief. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. The evidence here is thinner than anyone quoting it tends to admit.
A few things worth checking before you commit:
- Write the constraint down before choosing a tool
- Name one person accountable — not a group
- Keep the feedback loop shorter than the planning cycle
- Decide in advance what would make you stop
- Prefer the reversible option when the evidence is thin
Putting it together
The second-order effects arrive about a quarter after the first-order ones. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen.
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. This is easier to write than to hold to when a deadline appears.
Scope is the variable everyone adjusts last and should adjust first. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.
Why it is confusing
A shared definition of "done" removes more friction than any tool. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
Consider the failure mode rather than the success case. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. That said, none of this generalises cleanly across team sizes.
Scope is the variable everyone adjusts last and should adjust first. 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. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
The vocabulary problem
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.
Measurement is usually where this falls apart. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. There are organisations where the opposite is true, and they are not obviously worse off.
The edge cases
The first thing to establish is what you are actually optimising for. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. The clearest signal was that people stopped asking where things were.
What looks like a process problem is frequently an ownership problem. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
Consistency is worth more than any individual improvement to yoga practice. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture.
The short version
Speed and reversibility are the trade-off worth naming out loud. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. A useful test: if this disappeared tomorrow, how long before anyone noticed?
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. This is easier to write than to hold to when a deadline appears.
Where to go deeper
The interesting constraint is almost never the one in the brief. 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.
If there is one thing worth carrying away, it is that the expensive mistakes in yoga practice are almost never technical ones.
