Restate the decision you need
Begin a concept review by naming the assignment, intended adult reader and stage of work. Are you choosing a layout direction, checking factual copy or confirming a handoff? A meeting can become unproductive when one person judges a rough concept as finished while another is still discussing the communication problem.
The Design Council’s process separates defining a challenge from developing and delivering responses. Use the brief to keep the current question clear. If the problem has changed, record that change openly rather than asking a designer to reconcile incompatible feedback while the original brief remains on the page.
Look for evidence in the actual work
Ask the reviewer to point to a particular element and explain its effect on the task. “The main heading is difficult to distinguish from the introduction at phone size” identifies an observable issue. “It needs more energy” may express a preference, but it does not yet explain what the reader needs to do differently.
Try the relevant format with realistic content. Check whether the reader can identify the main message and find necessary supporting information without guidance. Record observations before proposing solutions. That leaves the collaborator room to solve the actual issue instead of treating every suggestion as an instruction to add a particular colour or image.
Use specific checks for specific concerns
For a text-contrast question on the web, use W3C’s explanation of the relevant WCAG criterion and check the actual foreground/background combination. Do not settle a measurable concern with a show of hands. Equally, a contrast result cannot decide whether the message is accurate or the page satisfies every accessibility requirement.
For a factual or implied health-claim question, involve the responsible reviewer and provide the complete creative. The U.S. FTC’s health-products guidance explains why overall impression matters. A team’s preference for an attractive concept is not evidence for the claims it may communicate, nor does a review meeting establish legal clearance.
Separate decisions from open questions
Write down what has been chosen, the reason linked to the brief and who owns the next action. Keep unresolved matters in a separate list with a responsible person. “Use this heading hierarchy; replace the unlicensed reference image before release” is more useful than a broad approval that hides a rights question.
Resolve conflicting feedback through the agreed decision owner. A request to add more detail may conflict with a requirement for a short preview. Describe the tradeoff and decide which requirement takes priority, rather than combining every request into a crowded design. Update the brief if the scope or audience genuinely changes.
Review the changed version deliberately
When the next version arrives, check the recorded issues and any new consequences of the edits. Confirm that changed wording, imagery or format has reached the right reviewers. Close the discussion with a clear status: another exploration, a review-ready draft or an agreed handoff. None of those labels alone promises publication permission or campaign results.