UCD methodsEstablishedDiscovery

Critiquing AI drafts needs old-school rigor

Published 12 September 2026 · Source dated 18 August 2026

When an AI tool hands you three layout options, eyeballing them and picking the one that feels right skips the review step. Heuristic evaluation is decades old, and it still catches problems a vibe-check misses.

**Heuristic evaluation didn't stop being useful just because AI writes the first draft.** When an AI tool hands you three layout options, the temptation is to eyeball them and pick the one that 'feels right'. That's the same trap as shipping your own first draft without review. Running a quick heuristic pass — visibility of system status, consistency, error prevention, and so on — on each AI-generated option before you commit takes minutes and catches problems a vibe-check misses. This is genuinely established practice, just applied to a newer kind of first draft. The rigor doesn't change; only the author of the draft does.

Coach

next time an AI tool gives you multiple UI options, spend 10 minutes running a heuristic pass on each and write down which heuristic each option breaks before you pick one.

Today's digest

Surf this topic: UCD methods (opens in a new tab)

Source: nngroup.com (opens in a new tab) ·