AI industry is one of those topics where the obvious answer is right about sixty per cent of the time, which is exactly often enough to be dangerous.
The quiet win
Measurement is usually where this falls apart. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
The default answer is right often enough to be dangerous. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. The evidence here is thinner than anyone quoting it tends to admit.
Feedback loops shorter than the planning cycle change everything. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive.
Where to start on Monday
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.
The second-order effects arrive about a quarter after the first-order ones. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
Begin with the obvious one
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.
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. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.
The one people skip
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. This is easier to write than to hold to when a deadline appears.
There is a version of AI industry 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.
The interesting constraint is almost never the one in the brief. 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 habit that compounds
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. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.
The tooling question is downstream of the constraint question. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. A useful test: if this disappeared tomorrow, how long before anyone noticed?
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
The checklist we ended up with:
- 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 advice worth ignoring
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.
It helps to separate the decision from the execution. The first quarter shows the intended effect; the second shows what the intended effect displaced. In practice the answer showed up in the calendar before it showed up in the dashboard.
The first thing to establish is what you are actually optimising for. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things.
The expensive mistake
Most of the difficulty lives at the boundaries, not in the middle. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen.
Documentation is a symptom: you write it where the design is unclear. AI industry rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing.
What to do first
Nobody gets credit for the work that did not need doing. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. That said, none of this generalises cleanly across team sizes.
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.
If there is one thing worth carrying away, it is that the expensive mistakes in AI industry are almost never technical ones.
Enjoying this story from Daily Insight?
“Get new deep dives delivered quietly to your inbox.”
Insight Daily Desk
Insight Daily Desk writes about AI industry.
