Feedback that gives the next revision a direction
By Gyata Tabiri · Revised October 30, 2026
Feedback helps when the person making the next revision can act on it. I want to make the concern specific enough to discuss, while leaving room for the designer or developer to contribute a better answer.
Describe the observation
Instead of starting with a proposed color or size, describe the difficulty: the main action is hard to find, the heading does not explain the offer, or the mobile reading order changes the message. That gives the team something to examine together.
Connect it to the task
A design decision should be reviewed against its audience and purpose. Ask what someone needs to notice or understand at this point. If the brief is uncertain, resolve that uncertainty before asking for another polished version.
Make the constraint visible
In email work, I have used screenshots, written explanations, and conversations to show layout, background, and button issues. Designers then revised the work. This keeps the conversation about a particular problem rather than an abstract disagreement about taste.
Agree on the next step
Say what needs to change, what is working, who owns the revision, and what will count as resolved. A short recap can prevent the next review from reopening decisions the team thought it had already made. That clarity helps both the person making the work and the person waiting for it.
The result of a useful review is a shared next step. A clear explanation of the problem and its priority can do more for the work than a long list of personal preferences.