Give feedback someone can actually work with
Turn a vague reaction into a clear conversation about audience, purpose and choices.
Return to the brief
Before reviewing a concept, restate the audience and intended outcome. This gives everyone a shared reference point. Personal taste can be discussed, but it should not silently replace the agreed objective. If the objective has changed, acknowledge that as a change to the project.
Describe the observation
Instead of saying the design feels wrong, point to what is happening. Is the main action hard to find? Does a heading suggest a different audience? Does an image make the product difficult to understand? Specific observations make it easier to diagnose the issue without prescribing a premature fix.
Explain the effect
Connect the observation to the reader or user. For example, a dense introductory paragraph may make it difficult to understand the service quickly. This leaves room for the designer to solve the underlying problem through structure, type, imagery or copy rather than simply following a cosmetic instruction.
Consolidate and prioritise
Send one agreed set of feedback. Mark essential corrections separately from questions and optional refinements. Resolve contradictory stakeholder comments internally where possible. A short review conversation can help, but retain a written record of the agreed changes afterwards.
Recognise what works
Identify the elements that already serve the brief. Otherwise a collaborator may change a successful part while trying to address an unrelated concern. Feedback should make the next iteration clearer, including what to preserve.
An original planning framework. Examples are illustrative. No visit, interview or product test is claimed. Our editorial standards.
Put the ideas to work.
A useful brief gives a collaborator enough context to ask better questions. Start yours here.
Open creative project brief ↗