Should last-mile design feedback be fed back into the design system?

THE SHORT ANSWER

Not as it arrives. Luke Wroblewski reported on November 3, 2026 that his coding agents, steered by the design system and agent instructions, get a screen about 90% right on the first pass, up from 50 to 60% with earlier models, and that the last 10% is closed by annotating the screen, which is why Intent now turns the macOS notch into a feedback surface. His proposed next step is feeding that feedback back into the design system, held back because models over-document instead of simplifying. The over-documenting is not a model gap; it is what any system does when every fix becomes an entry, which is why the Design Operating Model's kill list retires the component library as monument in favor of a constraint layer and a much smaller set of primitives. The rule: log every last-mile fix against the surface and the component it touched, promote a fix into a constraint only when it recurs on a third surface, and measure the systems team on the time from a quality complaint to a rule change, the third health number in Team Shape, rather than on the size of the system. A designer signs the weekly diff, and with a threshold of three the diff fits on a screen.

SOURCES

THE LONG VERSION

RELATED ANSWERS

Last reviewed 2026-11-03 · 1 min read