Give a creative review a clear job
By Gyata Tabiri · Revised October 30, 2026
A review works better when everyone knows what decision it needs to produce. Choosing a direction, checking a build, and approving a final version call for different kinds of attention.
Set the stage
Share the audience, intended action, constraints, and the decision needed. Explain which parts are ready for review and which are still being explored. People can contribute more usefully when they know what kind of response will help.
Let the work be explained
Give the person presenting room to describe the reasoning. Then ask questions about the problem rather than guessing at their intention. A concern about legibility, for example, deserves a different response from a preference for another visual style.
Resolve competing feedback
Identify who makes the final decision and consolidate comments before sending the work back. If two requests conflict, name the tradeoff and settle it. The person making the revision should not have to negotiate contradictory instructions alone.
End with a decision record
Record what was approved, what changes, what remains open, and who owns the next action. For a technical review, include the tested version and accepted differences. This makes the review useful after the meeting ends, when someone has to act on it.
When a review has a clear purpose and decision owner, the person doing the next revision receives something usable. That is especially important when an outside contributor or a new team member is joining the work.