For twenty years, reviewers read fidelity as a proxy for conviction, and it was a good proxy. A grayscale wireframe meant early thinking, so you challenged the concept. A pixel-perfect mock with real copy and real photography meant someone had already lived with the problem for two weeks, so you moved to spacing, states, and edge cases. Nobody taught you that rule. You absorbed it by sitting in enough rooms.
That rule is dead. The cost of looking finished collapsed. The cost of being right did not move at all.
The failure mode this creates
Reviews now break in one direction, and it is the expensive one: the work that looks most done gets the shallowest critique. Everyone in the room is still running a twenty-year-old heuristic on a signal that stopped carrying information. The polished screen gets a spacing note. The rough one gets a real conversation about whether the problem is even the problem.
The same collapse hits the brief. When generation was expensive, a weak brief showed up as a thin deck and everybody could see it. Now a weak brief produces a beautiful, confident, wrong artifact that survives a whole review because it photographs well.
The fix, and it is cheap
Move the signal off the artifact and into the room.
Before anyone presents, they say one sentence: where they are, and what they want from the room. "Third direction, I don't believe it yet, attack the concept." Or "I've been on this two weeks, I'm committed, find the failure modes." Ten seconds. It decides what the next twenty minutes are worth.
Then review the choice instead of the output. The question that separates the two is what did you kill, and why. If someone can't name what they rejected and the reason it lost, they didn't choose a direction, they picked one.
The four things I put on a review agenda
- A stated confidence level from whoever presents, before the screen share.
- The brief and the constraint first, the pixels second.
- A two-minute "how I made this" slot: the prompt, the tool, the eval, the thing that failed twice before it worked. This is how capability stops being individual and starts being the team's.
- One person assigned each week to the confident work specifically. Rotate it. Their job is to take the piece nobody is worried about and try to break it.
I have been running product and design reviews for two decades, at Adobe, at Salesforce, and in every CPO seat I have held since. The ones that mattered had almost nothing to do with the quality of feedback in the room. They worked because they were the only recurring event where taste got calibrated across people who otherwise never saw each other's raw work. That was true before any of us had a model in the loop. It is more true now, because every designer on your team is quietly building a different private toolkit and the bars are drifting apart faster than they used to.
At your next review, ask everyone to state their confidence level before they present. Watch what happens to the conversation about the work that looked finished.