The Hidden Cost of the Design-to-Dev Handoff (And How to Fix It)

The handoff is treated as a scheduling problem — get the file to the engineer sooner. It is a translation problem, and translation always loses something.

Why the handoff leaks

A design file describes an outcome. Code describes a mechanism. Between them sits an engineer inferring intent from pixels, and inference is where fidelity goes.

The cost is invisible in a sprint plan because it never appears as a task. It appears as review rounds — the same ticket returning three or four times over spacing nobody wrote down.

Fixing it structurally

Give both sides the same vocabulary. When a design references a spacing token rather than a measurement, there is nothing to infer — the value already exists in code.

@theme {
  --spacing-block: 4rem;
  --spacing-band: 7.5rem;
}

A section then writes py-block lg:py-band and the whole page rhythm moves from one place. Retuning stops being a ticket.

The library becomes the contract, and the handoff becomes a reference rather than a retelling.