The Super Shoe Arms Race Has Outrun the Rulebook

Sports 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

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. A useful test: if this disappeared tomorrow, how long before anyone noticed?

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. When we mapped it out, four of the seven steps existed only to compensate for the second one.

The expensive mistake

The compounding effects matter far more than the individual wins. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things.

The second-order effects arrive about a quarter after the first-order ones. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.

The one people skip

The tooling question is downstream of the constraint question. Sports industry — rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. 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.

What looks like a process problem is frequently an ownership problem. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.

The one that only matters at scale

A shared definition of "done" removes more friction than any tool. The first quarter shows the intended effect; the second shows what the intended effect displaced. It is worth saying that we have not run this long enough to be confident.

The interesting constraint is almost never the one in the brief. 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. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.

Simplicity is not the absence of work. It is the result of it.

— Overheard in a retrospective

What to do first

Consistency is worth more than any individual improvement to sports industry —. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive.

The default answer is right often enough to be dangerous. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. The clearest signal was that people stopped asking where things were.

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 checklist we ended up with:

1. Agree on what "done" means, in writing, before starting
2. Keep the feedback loop shorter than the planning cycle
3. Write the constraint down before choosing a tool
4. Name one person accountable — not a group

The habit that compounds

Measurement is usually where this falls apart. 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.

Nobody gets credit for the work that did not need doing. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted.

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. In practice the answer showed up in the calendar before it showed up in the dashboard.

The advice worth ignoring

Consider the failure mode rather than the success case. 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.

Feedback loops shorter than the planning cycle change everything. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. There are organisations where the opposite is true, and they are not obviously worse off.

Where to start on Monday

Scope is the variable everyone adjusts last and should adjust first. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. 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 sports industry — that is mostly ritual. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture.

It helps to separate the decision from the execution. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling.

Begin with the obvious one

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 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. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.

The quiet win

The default answer is right often enough to be dangerous. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen.

We will revisit this once we have another two quarters of data. The current answer feels right, which is exactly when it is worth checking.