Over-polishing steers discussion toward visuals
Aliases: polish steers critique · visual hijack of review
What it is
When structure or flow has not yet been asked, but type, color, illustration, and shadow are already finished, talk in reviews and tests slides onto the visual: this screen is too plain, that icon is off-brand, the radii do not match. The harm of over-polishing here is not wasted hours; it is swapping the object of discussion from “does this path hold” to “does this picture look good.” Comments look plentiful and do not answer the current question. It is the meeting-room face of raising visual fidelity: polish supplies the easiest target to point at.
Why it happens
People comment first on the attribute that is easiest to name. Pixels are more pointable than information architecture, have a shared vocabulary (looks good / looks bad), and challenge power less—saying the color is wrong is safer than saying the business flow is wrong. Polished visuals also trigger a sense of completion; structural problems feel “too late to change.” If the facilitator leads with visual decisions, the room’s agenda is set. Structural objections run out of time, visual preferences are logged as “feedback,” and the next round iterates on the wrong dimension. The more complete the polish, the stronger the gravity: it adds surface detail to comment on and raises the social cost of opposing structure.
Studying it
Send the same flow into review as a low-look deck and as a polished deck, and code comment objects: structure, content, visual, implementation. Track the visual share of comments against polish time. Snyder and later prototyping practice treat “forty minutes in and nobody has mentioned a failed task” as a signal of over-polish. You can also leave one uncolored structural change on the board and see whether it still gets discussed. Do not use comment count as engagement—counts can be filled with visual detail.
Where it stops holding
When the current question is visual design, brand, or illustrated narrative, polish is the material, not a mislead. Expert reviews explicitly told to judge structure first can partly hold the gravity down. Asynchronous document review follows an outline more easily than a conference room, so visual hijack is weaker. For participants with visual impairments the shift will not run along “looks good”; it may run along contrast and type size—and is still surface attributes capturing the agenda.
Applying it
- For structure rounds, use wireframes or paper, and take visual decisions out of the filename and the agenda.
- Put the structural questions that must be answered first on the review outline; park visual items last or in another meeting.
- File visual comments separately; they do not write the structural conclusion.
- If visuals are more than half the comments and structural questions were never touched, declare the material a failure, strip polish, and reopen—do not “absorb the feedback.”