Working Surfacelink · 28 Sep · 03
03
Two figures seen from behind, the backs of their heads showing, sit at a workbench where a small robot turns a sideways card in a hand-cranked clamp, one figure pointing at the clamp while the other holds an open notebook, and a filing drawer stands open beside the workbench, the whole scene drawn with wide empty margins on every side.
Design Outcomes

Good Isn't Great

Leonardo De La Rocha · 26 September 2026

How-to · critique & review · roles · Human approval

Read the original
Takeaway

A designer fixed a billing problem for clinicians in an afternoon with an AI coding agent, and his design lead used the review to take it from good to great.

Summary

Clinicians at a mental-health practice had to rotate patients' sideways insurance-card photos by hand before they could use them. A designer who works on billing at the company that makes their software fixed this in one afternoon with an AI coding agent. His design lead, Leonardo De La Rocha, then reviewed the fix with him and explains what separates a good fix from a great one.

Key points
  • The designer left the small thumbnail unrotated until the rotation can be saved, so that nobody walks away believing an unsaved change was stored.
  • He offered rotation to the left only, as Apple Photos does, and kept the control in the larger preview that clinicians already open. He disagreed when De La Rocha suggested moving it.
  • De La Rocha argues that reaching good was an achievement when a fix took a sprint. When a fix takes an afternoon, good is a first draft.
  • The designer added a caution of his own: a feature that can overwrite someone's files deserves closer review as a result.
Implication

A team whose fixes now take an afternoon can spend its review time on the step from good to great. The application beyond De La Rocha's team is an inference and is not the author's claim.

Source issue

28 September 2026: when agents build, people keep the first screen, the review, the files agents read and the whole product.