What couture can teach us about restraint

The interesting thing about luxury design is how rarely the hard part is the part everyone prepares for.

When to change course

There is a version of luxury design that is mostly ritual. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted.

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.

Start with the constraints

The interesting constraint is almost never the one in the brief. The first quarter shows the intended effect; the second shows what the intended effect displaced. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.

The first thing to establish is what you are actually optimising for. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. When we mapped it out, four of the seven steps existed only to compensate for the second one.

Measurement is usually where this falls apart. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered.

Handing it over

Speed and reversibility are the trade-off worth naming out loud. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.

Consistency is worth more than any individual improvement to luxury design. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.

Consider the failure mode rather than the success case. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight.

The first month

A shared definition of "done" removes more friction than any tool. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix.

Nobody gets credit for the work that did not need doing. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. The clearest signal was that people stopped asking where things were.

The setup

The second-order effects arrive about a quarter after the first-order ones. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. The evidence here is thinner than anyone quoting it tends to admit.

Most of the difficulty lives at the boundaries, not in the middle. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. In practice the answer showed up in the calendar before it showed up in the dashboard.

A worked example

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.

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

You can have it fast, or you can have it reversible. Pick before you start, not after.

— Overheard in a retrospective

Choosing what to measure

What looks like a process problem is frequently an ownership problem. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. It is worth saying that we have not run this long enough to be confident.

It helps to separate the decision from the execution. 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. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.

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. The version of this that works fits on an index card. The version that fails needs an onboarding session.

Making it stick

The expensive mistakes here are rarely the technical ones. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.

The default answer is right often enough to be dangerous. Luxury design 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.

Documentation is a symptom: you write it where the design is unclear. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.

A few things worth checking before you commit:

• Decide in advance what would make you stop
• Write the constraint down before choosing a tool
• Agree on what "done" means, in writing, before starting

Where teams go wrong

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?

The expensive mistakes here are rarely the technical ones. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. That said, none of this generalises cleanly across team sizes.

When to change course

The tooling question is downstream of the constraint question. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted.

The default answer is right often enough to be dangerous. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. When we mapped it out, four of the seven steps existed only to compensate for the second one.

If there is one thing worth carrying away, it is that the expensive mistakes in luxury design are almost never technical ones.