Depth Over Velocity

There is no shortage of advice about AI industry. There is a shortage of advice that survives contact with a real week.

What to do first

Feedback loops shorter than the planning cycle change everything. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates.

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. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.

The expensive mistakes here are rarely the technical ones. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing.

The advice worth ignoring

The tooling question is downstream of the constraint question. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.

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.

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 quiet win

A shared definition of "done" removes more friction than any tool. 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.

Consistency is worth more than any individual improvement to AI industry. AI industry rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. A useful test: if this disappeared tomorrow, how long before anyone noticed?

The habit that compounds

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.

Documentation is a symptom: you write it where the design is unclear. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix.

The expensive mistake

The first thing to establish is what you are actually optimising for. 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. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.

Consider the failure mode rather than the success case. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. The version of this that works fits on an index card. The version that fails needs an onboarding session.

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