The psychology of colour in high-end brand identity

We spent a quarter trying to get luxury design right, and the useful lessons were not the ones we expected.

A worked example

Most of the difficulty lives at the boundaries, not in the middle. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. Set a date at which you will stop, and write down in advance what would make you stop earlier.

Feedback loops shorter than the planning cycle change everything. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.

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. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.

Choosing what to measure

The compounding effects matter far more than the individual wins. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct.

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 first month

Scope is the variable everyone adjusts last and should adjust first. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.

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.

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

When to change course

The expensive mistakes here are rarely the technical ones. Luxury design rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing.

The interesting constraint is almost never the one in the brief. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.

Consistency is worth more than any individual improvement to luxury design. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. When we mapped it out, four of the seven steps existed only to compensate for the second one.

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

— Overheard in a retrospective

Start with the constraints

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

Measurement is usually where this falls apart. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted.

Making it stick

The default answer is right often enough to be dangerous. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture.

Consider the failure mode rather than the success case. The first quarter shows the intended effect; the second shows what the intended effect displaced. There are organisations where the opposite is true, and they are not obviously worse off.

The checklist we ended up with:

1. Name one person accountable — not a group
2. Prefer the reversible option when the evidence is thin
3. Decide in advance what would make you stop
4. Keep the feedback loop shorter than the planning cycle

The setup

Documentation is a symptom: you write it where the design is unclear. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling.

There is a version of luxury design that is mostly ritual. 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.

The first thing to establish is what you are actually optimising for. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered.

Where teams go wrong

It helps to separate the decision from the execution. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen.

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. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.

Handing it over

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.

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

A worked example

The first thing to establish is what you are actually optimising for. 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 second-order effects arrive about a quarter after the first-order ones. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. That said, none of this generalises cleanly across team sizes.

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

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