Design systems

The inconsistency tax

Thirty minutes on a cost you can name this week.

Christoph Hellmuth ยท Design Engineering Studio

The point

You are paying twice for the same button.

The second invoice is the one nobody puts in the sprint.

Compositors working at type cases in a printing shop at Hampton Institute, 1899.

Every letter has a slot.

This room

You are past the size where everyone knows everyone.

The system used to be a person. That person is now in four meetings.

Thirty minutes

Four parts. Then questions.

  1. 05
    Name the tax

    Four places the money actually goes.

  2. 12
    Where it leaks

    The symptoms you can see in a sprint.

  3. 18
    What a system is

    A slot, a name, an owner, a door.

  4. 24
    Ninety days

    A sequence that does not wait for a rebrand.

Part one

Name the tax

If you cannot point at it, you cannot fund it.

The invoice

Four places the money goes.

  1. 01
    Rebuild

    The same pattern, built again, because the first one could not be found or trusted.

  2. 02
    Review

    Design and code review spent re-deciding spacing, color, and states.

  3. 03
    Support

    Tickets and refunds caused by UI that lies, or flows that do not match.

  4. 04
    Onboarding

    Weeks before a new designer or engineer knows which pattern is real.

Rebuild

The second build is not a new idea.

It is the first idea, with the name filed off.

Review

Critique spent on settled questions is waste.

Taste belongs on the undecided. The rest should be a check.

Support

Customers pay the tax in confidence.

When the interface disagrees with itself, people stop trusting the action.

Onboarding

Every new hire pays tuition to the old mess.

Tribal knowledge feels fast until the person who holds it is out.

Architects at drafting tables in the Treasury Department Building, drawings stacked at each desk.

Same drawing. Many tables.

A number you can use

About 90 percent fewer reclamations.

One systematic fix at Flyeralarm. Not a mood board. A correction the product could repeat.

The choice

Both compound. Pick one.

HackFaster this week

A local copy. A one-off hex. A note in chat. It ships, and next month it has a cousin.

SystemFaster next quarter

A named slot, used twice, with an owner. The third use is cheaper than the first.

A 1910 sample board with hand-made filet lace labeled above machine-made filet.

Hand-made and machine-made, both named.

Part two

Where it leaks

Four symptoms. If you have two, you are paying.

Symptoms

You can see these in a sprint.

  1. 01
    Every squad, a different UI

    No shared tokens, components, or docs. Every screen is a one-off.

  2. 02
    The file and production drift

    Engineers rebuild patterns, or ship a variant the design never had.

  3. 03
    Onboarding is a chat thread

    How we build UI here lives in people, not in a place you can open.

  4. 04
    The system keeps losing to features

    Everyone agrees. Priorities, governance, and adoption stall.

The leak I would pick

You do not have to ship four buttons.

One of them is the product. The other three are the tax, still in the interface.

Two Linotype machines at Anthony Hordern and Sons, Sydney, around 1935.

Two machines. One measure.

Part three

What a system is

Small enough to fund. Strict enough to help.

A definition

A slot, a name, an owner, a door.

  1. Slot
    One place it lives

    The component in the repo, and the component in the library, are the same idea.

  2. Name
    The decision, not the hue

    Action, not blue-500. The name says what it is for.

  3. Owner
    A person who can say no

    Not a committee. Someone who accepts the change or sends it back.

  4. Door
    A way in that is faster than a fork

    Contribution, a checklist, a review. Otherwise people copy.

A chart from the 1915 Atlas of the Munsell Color System, with named branches of color.

Name the color, then use it.

A side effect

Lighthouse 34 to 77 was not a trick.

Fewer one-offs. Less CSS that only one screen understood.

Part four

Ninety days

Beside the roadmap. One path, then the next.

A sequence

What I would do in ninety days.

  1. 01
    This week: name the leaks

    One squad, one month, four buckets. A range, not a fantasy.

  2. 30
    Day 30: one path, one button

    The flow you rebuilt. States included. The cousins get a deprecation date.

  3. 60
    Day 60: the file and the repo agree

    Same names. A check for drift. Not a new source nobody opens.

  4. 90
    Day 90: a door

    An owner, a checklist, and a way for the next squad to add without forking.

What I would not fund

Do not start with a museum.

A library nobody imports is a folder with good taste.

A library card catalog in a central search room, drawers labeled and in reach.

Find it by the name, not the pile.

Honest next steps

Estimate one month. Then fix one path.

If you want a second pair of eyes, the consult is thirty minutes and it is free.

Design Engineering Studio

Pick which compounding you want.

Quick hacks compound. So do systems.

christophhellmuth.com

Questions

What are you paying for twice?

Bring a pattern, a squad, or a number. Leave the theory.