We spent a quarter trying to get business right, and the useful lessons were not the ones we expected.
How we knew it was working
The compounding effects matter far more than the individual wins. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next.
Speed and reversibility are the trade-off worth naming out loud. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. The clearest signal was that people stopped asking where things were.
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 caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.
The part that surprised us
Most of the difficulty lives at the boundaries, not in the middle. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct.
The first thing to establish is what you are actually optimising for. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling.
The default answer is right often enough to be dangerous. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. There are organisations where the opposite is true, and they are not obviously worse off.
The situation
It helps to separate the decision from the execution. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened.
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. In practice the answer showed up in the calendar before it showed up in the dashboard.
What it cost
Scope is the variable everyone adjusts last and should adjust first. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. A useful test: if this disappeared tomorrow, how long before anyone noticed?
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.
What we tried first
Measurement is usually where this falls apart. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates.
The expensive mistakes here are rarely the technical ones. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort.
Consistency is worth more than any individual improvement to business. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. The version of this that works fits on an index card. The version that fails needs an onboarding session.
The numbers
There is a version of business that is mostly ritual. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. 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 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.
What looks like a process problem is frequently an ownership problem. Business rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. It is worth saying that we have not run this long enough to be confident.
What changed
Nobody gets credit for the work that did not need doing. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.
Feedback loops shorter than the planning cycle change everything. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes.
Consider the failure mode rather than the success case. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
Where it still breaks
Documentation is a symptom: you write it where the design is unclear. The first quarter shows the intended effect; the second shows what the intended effect displaced.
The tooling question is downstream of the constraint question. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort.
The expensive mistakes here are rarely the technical ones. 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.
Simplicity is not the absence of work. It is the result of it.
— Overheard in a retrospective
What we would do differently
Speed and reversibility are the trade-off worth naming out loud. 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 first thing to establish is what you are actually optimising for. Business 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. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. When we mapped it out, four of the seven steps existed only to compensate for the second one.
What we look for now:
- Prefer the reversible option when the evidence is thin
- Agree on what "done" means, in writing, before starting
- Review the numbers monthly; change the targets rarely
- Write the constraint down before choosing a tool
- Keep the feedback loop shorter than the planning cycle
How we knew it was working
A shared definition of "done" removes more friction than any tool. 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. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
Nobody gets credit for the work that did not need doing. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.
Measurement is usually where this falls apart. The first quarter shows the intended effect; the second shows what the intended effect displaced. The evidence here is thinner than anyone quoting it tends to admit.
The part that surprised us
The interesting constraint is almost never the one in the brief. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review.
What looks like a process problem is frequently an ownership problem. 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.
The situation
The second-order effects arrive about a quarter after the first-order ones. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. This is easier to write than to hold to when a deadline appears.
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.
The compounding effects matter far more than the individual wins. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix.
The short version: decide what you are optimising for, write it down, and revisit it when the answer stops feeling obvious.
