Run a Review That Moves the Work

Before inviting comments, state the decision this review needs to produce. Early work may need agreement on an idea, audience or visual direction; later work may need a check of accuracy, legibility and delivery details. Show only the context necessary for that decision and explain which parts of the work are intentionally unfinished. This helps reviewers avoid spending the meeting correcting temporary copy when the concept itself is still open. Put the review question in the invitation and repeat it beside the work.

Prepare a short sequence of questions that moves from purpose to execution. Begin by asking whether the direction supports the agreed audience and message. Then ask about the specific choices that remain undecided. Reserve finishing details for a later pass if they cannot yet be assessed meaningfully. If someone raises an important issue outside the current scope, record it rather than dismissing it or immediately changing the whole meeting. Assign it a next step so the current decision can still be completed.

Practice: Write three review questions for an early concept and three different questions for its final export.

Break a reaction into an observation, its effect and a question about the intended outcome. The page feels crowded is a reaction. The pricing, feature list and primary action have equal visual weight is an observation that a designer can inspect. Explain why that matters, such as a reader not knowing where to begin, then ask how the hierarchy could become clearer. This structure preserves useful concern while avoiding an untested instruction about exactly which element must become larger or smaller.

Practice rewriting comments without removing the reviewer's uncertainty. Use phrases such as I am having trouble identifying the first step when the issue is your own reading experience, and distinguish that from evidence about a wider audience. Avoid turning one person's preference into a universal claim. Where the comment concerns a requirement, point to that requirement directly. Where it concerns taste, name the preference honestly. The creator can then decide whether to investigate, propose an alternative or ask the approving owner to resolve a tradeoff.

Practice: Rewrite five broad comments such as make it pop or feels too busy into specific review questions.

When two requests conflict, place them beside the same decision instead of sending them to the creator as separate tasks. Describe what each request is trying to achieve. One reviewer may want more explanation while another wants a shorter opening; the underlying question could be what the audience already knows. Return to the brief and identify which assumption needs to be confirmed. The conflict often becomes easier to discuss when it is framed as a choice about purpose rather than a disagreement between personalities.

Name the person authorized to make the decision and give them enough context to choose. Show the options, the benefit each preserves and the cost each introduces. Do not silently combine incompatible instructions into an awkward compromise just to appear responsive. Record the chosen direction and its reason in the review tracker, then update the affected actions. If the choice changes agreed scope or timing, make that effect visible before implementation. A resolved comment should tell the team what to do next and why.

Practice: Take two contradictory requests and write the question a decision owner needs to answer.

End the review with a concise record tied to a specific artifact version. Group accepted changes by the output they affect and give each action an owner. Separate open questions from approved work so uncertainty is not mistaken for a task already assigned. Include a brief explanation for a request that was declined or deferred, especially if it may return in the next round. The summary should be short enough that someone can check it against the reviewed work without reconstructing the entire conversation.

Before beginning revisions, confirm that the decision owner agrees with the summary. Then use it as a checklist for the next presentation: show what changed, what remained the same and which question still needs an answer. Avoid replacing the tracker with a fresh document that loses the previous reasoning. Carry decisions forward while closing completed actions. If new feedback reopens an earlier choice, record that explicitly as a new decision rather than erasing the history that explains how the work reached its current state.

Practice: Produce a one-page review summary with actions, owners and a named artifact version.