Privacy Policy

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.

What to do first

Measurement is usually where this falls apart. The first quarter shows the intended effect; the second shows what the intended effect displaced. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.

The first thing to establish is what you are actually optimising for. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. The evidence here is thinner than anyone quoting it tends to admit.

The one people skip

Documentation is a symptom: you write it where the design is unclear. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. A useful test: if this disappeared tomorrow, how long before anyone noticed?

The interesting constraint is almost never the one in the brief. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.

The tooling question is downstream of the constraint question. 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.

Begin with the obvious one

Scope is the variable everyone adjusts last and should adjust first. 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 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. 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.

Feedback loops shorter than the planning cycle change everything. AI industry rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing.

A few things worth checking before you commit:

• Review the numbers monthly; change the targets rarely
• Keep the feedback loop shorter than the planning cycle
• Prefer the reversible option when the evidence is thin

The advice worth ignoring

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. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.

There is a version of AI industry that is mostly ritual. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.

None of this generalises perfectly. Take the parts that map onto your constraints and discard the rest — that is what the framing is for.