We spent a quarter trying to get Industry insights right, and the useful lessons were not the ones we expected.
The objection worth taking seriously
The second-order effects arrive about a quarter after the first-order ones. 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.
Feedback loops shorter than the planning cycle change everything. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered.
What would change our mind
Scope is the variable everyone adjusts last and should adjust first. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates.
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 counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.
What the data actually shows
There is a version of Industry insights that is mostly ritual. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct.
Most of the difficulty lives at the boundaries, not in the middle. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. 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. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted.
The incentive problem
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. 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. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. In practice the answer showed up in the calendar before it showed up in the dashboard.
Where this leaves us
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. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.
Consider the failure mode rather than the success case. Industry insights rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing.
Measurement is usually where this falls apart. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive.
A different reading
It helps to separate the decision from the execution. 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.
Consistency is worth more than any individual improvement to Industry insights. 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.
Simplicity is not the absence of work. It is the result of it.
— Overheard in a retrospective
A more modest claim
Speed and reversibility are the trade-off worth naming out loud. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. A useful test: if this disappeared tomorrow, how long before anyone noticed?
Documentation is a symptom: you write it where the design is unclear. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort.
The received wisdom
The compounding effects matter far more than the individual wins. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
The default answer is right often enough to be dangerous. The first quarter shows the intended effect; the second shows what the intended effect displaced.
Nobody gets credit for the work that did not need doing. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. That said, none of this generalises cleanly across team sizes.
How we got here
What looks like a process problem is frequently an ownership problem. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened.
It helps to separate the decision from the execution. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things.
The checklist we ended up with:
- Review the numbers monthly; change the targets rarely
- Name one person accountable — not a group
- Keep the feedback loop shorter than the planning cycle
- Agree on what "done" means, in writing, before starting
The objection worth taking seriously
Measurement is usually where this falls apart. 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. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. This is easier to write than to hold to when a deadline appears.
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. When we mapped it out, four of the seven steps existed only to compensate for the second one.
What would change our mind
The default answer is right often enough to be dangerous. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix.
Speed and reversibility are the trade-off worth naming out loud. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes.
What the data actually shows
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. There are organisations where the opposite is true, and they are not obviously worse off.
Consider the failure mode rather than the success case. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. The clearest signal was that people stopped asking where things were.
Most of the difficulty lives at the boundaries, not in the middle. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.
The incentive problem
What looks like a process problem is frequently an ownership problem. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. The version of this that works fits on an index card. The version that fails needs an onboarding session.
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. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
Feedback loops shorter than the planning cycle change everything. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
The short version: decide what you are optimising for, write it down, and revisit it when the answer stops feeling obvious.
