The interesting thing about Industry insights is how rarely the hard part is the part everyone prepares for.
The numbers
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. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
Nobody gets credit for the work that did not need doing. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight.
Where it still breaks
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. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
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. There are organisations where the opposite is true, and they are not obviously worse off.
The part that surprised us
Most of the difficulty lives at the boundaries, not in the middle. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. 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. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. In practice the answer showed up in the calendar before it showed up in the dashboard.
How we knew it was working
Consistency is worth more than any individual improvement to Industry insights. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes.
The default answer is right often enough to be dangerous. Industry insights rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. The clearest signal was that people stopped asking where things were.
Consider the failure mode rather than the success case. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. A useful test: if this disappeared tomorrow, how long before anyone noticed?
What changed
The first thing to establish is what you are actually optimising for. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted.
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. When we mapped it out, four of the seven steps existed only to compensate for the second one.
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.
Simplicity is not the absence of work. It is the result of it.
— Overheard in a retrospective
The situation
There is a version of Industry insights that is mostly ritual. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. Set a date at which you will stop, and write down in advance what would make you stop earlier.
The expensive mistakes here are rarely the technical ones. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.
What it cost
The compounding effects matter far more than the individual wins. The first quarter shows the intended effect; the second shows what the intended effect displaced. 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. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered.
A few things worth checking before you commit:
- Decide in advance what would make you stop
- Prefer the reversible option when the evidence is thin
- Agree on what "done" means, in writing, before starting
- Name one person accountable — not a group
- Write the constraint down before choosing a tool
What we tried first
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.
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.
What we would do differently
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. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
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. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
The numbers
Measurement is usually where this falls apart. 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.
It helps to separate the decision from the execution. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.
Where it still breaks
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. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
What looks like a process problem is frequently an ownership problem. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. That said, none of this generalises cleanly across team sizes.
The part that surprised us
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.
A shared definition of "done" removes more friction than any tool. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. 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. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight.
How we knew it was working
The compounding effects matter far more than the individual wins. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. A useful test: if this disappeared tomorrow, how long before anyone noticed?
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. When we mapped it out, four of the seven steps existed only to compensate for the second one.
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. 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 Industry insights are almost never technical ones.
