Wearables Finally Learned to Say Rest

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.

What we would do differently

Consider the failure mode rather than the success case. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. The clearest signal was that people stopped asking where things were.

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. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.

There is a version of sports 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. Set a date at which you will stop, and write down in advance what would make you stop earlier.

Where it still breaks

The interesting constraint is almost never the one in the brief. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.

What looks like a process problem is frequently an ownership problem. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. It is worth saying that we have not run this long enough to be confident.

The situation

The default answer is right often enough to be dangerous. Sports industry — rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. 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.

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

What changed

Consistency is worth more than any individual improvement to sports industry —. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.

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.

How we knew it was working

Speed and reversibility are the trade-off worth naming out loud. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. A useful test: if this disappeared tomorrow, how long before anyone noticed?

Feedback loops shorter than the planning cycle change everything. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. In practice the answer showed up in the calendar before it showed up in the dashboard.

Nobody gets credit for the work that did not need doing. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. This is easier to write than to hold to when a deadline appears.

A few things worth checking before you commit:

1. Decide in advance what would make you stop
2. Keep the feedback loop shorter than the planning cycle
3. Review the numbers monthly; change the targets rarely
4. Agree on what "done" means, in writing, before starting
5. Name one person accountable — not a group

The numbers

Documentation is a symptom: you write it where the design is unclear. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes.

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. There are organisations where the opposite is true, and they are not obviously worse off.

What it cost

It helps to separate the decision from the execution. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered.

The expensive mistakes here are rarely the technical ones. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. When we mapped it out, four of the seven steps existed only to compensate for the second one.

The part that surprised us

The tooling question is downstream of the constraint question. 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 evidence here is thinner than anyone quoting it tends to admit.

The first thing to establish is what you are actually optimising for. The first quarter shows the intended effect; the second shows what the intended effect displaced. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.

The second-order effects arrive about a quarter after the first-order ones. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix.

What we tried first

The compounding effects matter far more than the individual wins. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling.

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. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.

What we would do differently

Feedback loops shorter than the planning cycle change everything. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort.

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