Agree on the decision before judging the ideas
A concept review is easier when everyone knows what the meeting must decide. Are you selecting one direction for development, choosing elements to test, or approving a finished proposal? Those are different decisions. State the purpose at the start, along with who will make the final call and what input the rest of the group can provide. This prevents a useful discussion from ending with several people believing they have approved different things.
Give each concept the same basic presentation: the problem it addresses, the idea behind it, a few relevant examples and any known constraints. Avoid showing one direction as a polished mock-up while another remains a rough sketch unless that difference is itself under review. If possible, allow a moment for individual notes before group discussion. People can then record their first observations without having to respond immediately to the most confident voice in the room.
Turn the brief into a small set of criteria
Criteria should describe what a successful solution needs to do, not what it should look like. For a visual identity project, a team might ask whether a concept expresses the intended character, is understandable to its audience, works across required formats and can be produced with available resources. These questions are more useful than criteria such as “feels fresh” unless the team has discussed what fresh means in this particular brief.
Keep the list short enough to remember during the review; four to six criteria are often manageable. Write each one as a question and add a brief description of what would count as evidence. For example, “Works across formats” might mean that the core idea remains recognisable on a small digital image, a presentation slide and a printed sign. If some criteria matter more than others, agree on that before seeing reactions to the concepts. A practical production constraint may be essential, while a stylistic preference may be negotiable.
Ask the group to identify any non-negotiable requirements separately. A concept that cannot meet a required format needs a plan to resolve that problem, even if it performs well in other respects. Separating requirements from preferences keeps the team from treating every point as equally decisive.
Compare concepts with evidence, not just scores
A simple comparison table can help: place concepts across the top, criteria down the side, and leave room for observations. For each concept, ask, “What in the work supports this criterion?” and “What remains unproven?” Consider a workshop series with two visual directions. One may be immediately welcoming but difficult to reproduce in low-cost handouts. The other may adapt well to every format but need clearer cues about the workshops’ purpose. Those observations offer a path forward that a vote alone would miss.
Scores can be useful for revealing where opinions differ, but they are not a substitute for discussion. If one person rates audience clarity highly and another rates it poorly, ask what each noticed. They may be imagining different audiences or judging different parts of the concept. Record the reason for the difference rather than averaging it away. When evidence is thin, mark the point as uncertain instead of forcing a confident rating.
Keep feedback tied to the agreed questions. “I dislike yellow” is hard to act on; “the pale text may be difficult to read on the proposed background” identifies a concern the team can examine. Personal responses still matter, especially in creative work, but they become more useful when someone can explain what prompted them and how that response relates to the brief.
Make trade-offs visible before choosing
Few concepts lead on every criterion. Summarise each direction in a sentence or two: its strongest contribution, its main weakness and what would need to change next. This helps the group distinguish a promising concept with a fixable problem from one whose central idea conflicts with the brief. Be cautious about combining the most popular feature of every proposal; the resulting direction may lose the coherence that made each original idea work.
When the choice depends on an unanswered question, define a small test rather than continuing the same debate. You might place two identity concepts into the same set of sample applications or ask a few intended users what they think each communication is about. Specify what the test needs to clarify before running it. The goal is not to make a creative decision automatic, but to give the decision-maker better information.
Record the decision and the next step
End the review by naming the selected direction, the reasons it was chosen and any reservations that still need attention. If no direction is selected, state exactly what must be revised or tested and when the group will reconvene. Assign an owner to each next step so that “develop the idea further” becomes an actionable brief.
A short decision record protects the work as it moves beyond the meeting. It can say, for example, that the team chose the adaptable direction because it communicates the project clearly across required formats, while asking for a warmer treatment of its introductory materials. This gives the designer room to work without reopening every earlier preference. Agreed criteria do not remove judgement from creative decisions; they give that judgement a shared purpose and a clear explanation.
