We spent a quarter trying to get Industry insights right, and the useful lessons were not the ones we expected.
What it is not
The expensive mistakes here are rarely the technical ones. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. 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. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. It is worth saying that we have not run this long enough to be confident.
Speed and reversibility are the trade-off worth naming out loud. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.
How it works
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. Set a date at which you will stop, and write down in advance what would make you stop earlier.
Measurement is usually where this falls apart. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. The version of this that works fits on an index card. The version that fails needs an onboarding session.
The first thing to establish is what you are actually optimising for. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. The evidence here is thinner than anyone quoting it tends to admit.
Where to go deeper
Consistency is worth more than any individual improvement to Industry insights. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things.
Scope is the variable everyone adjusts last and should adjust first. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct.
There is a version of Industry insights that is mostly ritual. 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.
Why it is confusing
What looks like a process problem is frequently an ownership problem. The first quarter shows the intended effect; the second shows what the intended effect displaced. 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. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
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. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
The vocabulary problem
The default answer is right often enough to be dangerous. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. That said, none of this generalises cleanly across team sizes.
The compounding effects matter far more than the individual wins. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. 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. 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.
Putting it together
Feedback loops shorter than the planning cycle change everything. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. This is easier to write than to hold to when a deadline appears.
The second-order effects arrive about a quarter after the first-order ones. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling.
What we look for now:
- Agree on what "done" means, in writing, before starting
- Name one person accountable — not a group
- Write the constraint down before choosing a tool
- Prefer the reversible option when the evidence is thin
The short version
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.
It helps to separate the decision from the execution. Industry insights rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.
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 cost of a bad decision is rarely the decision. It is the six months of building on top of it.
— Overheard in a retrospective
A common misreading
The first thing to establish is what you are actually optimising for. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive.
Documentation is a symptom: you write it where the design is unclear. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling.
The compounding effects matter far more than the individual wins. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. When we mapped it out, four of the seven steps existed only to compensate for the second one.
The edge cases
Consistency is worth more than any individual improvement to Industry insights. Industry insights 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.
Nobody gets credit for the work that did not need doing. 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.
What it is not
Scope is the variable everyone adjusts last and should adjust first. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
The tooling question is downstream of the constraint question. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture.
There is a version of Industry insights that is mostly ritual. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. In practice the answer showed up in the calendar before it showed up in the dashboard.
How it works
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.
Measurement is usually where this falls apart. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. A useful test: if this disappeared tomorrow, how long before anyone noticed?
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.
Where to go deeper
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. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
We will revisit this once we have another two quarters of data. The current answer feels right, which is exactly when it is worth checking.
