Start with the decision you actually need to make
Imagine you have three directions for a visual identity. One has a refined logo mockup, another is a sheet of rough sketches, and the third is a written idea with a few reference images. Asking “Which one is best?” invites a quick reaction to how they look today. A more useful question is: “Which direction is most promising for the work we need to do?”
Write down the decision before reviewing anything. Are you selecting one direction to develop, deciding which two deserve a test, or choosing a final design? These decisions require different levels of evidence. An early selection can be provisional; a final choice needs closer attention to how the concept performs across its intended uses.
Keep the brief visible and reduce it to a few concrete needs. For example, an identity for a neighbourhood workshop might need to feel welcoming, work on a small sign and be simple enough for volunteers to apply. This gives the group something more useful to discuss than personal taste alone.
Give every concept a comparable introduction
Presentation quality can distort a comparison. A concept shown on a realistic poster may appear more convincing than one shown as a thumbnail, even if the thumbnail contains the stronger idea. Before the review, give each option a similar amount of space and a similar set of examples. You do not need to polish everything; simple, consistent presentations are often better for an early decision.
For each concept, prepare a short statement of its central idea, one representative image or sketch, and an example of how it might work in a real setting. If one direction is mostly verbal, make a quick visual study for it. If another has an elaborate mockup, include its plain version too. The aim is not to erase meaningful differences, but to avoid mistaking extra production time for better thinking.
Name each concept neutrally, such as A, B and C. Labels like “safe option” or “bold option” can steer reactions before anyone has considered the work. Give reviewers a moment to look at all the directions before discussion begins.
Use a small set of criteria, not a complicated scorecard
Choose three to five criteria that reflect the brief. Useful questions might include: Does the concept communicate the intended character? Can it work in the formats we need? Does it offer enough room to develop? Is it practical for the people who will use it? Define each criterion in ordinary language so everyone is evaluating the same thing.
Ask reviewers to note one strength, one concern and one unanswered question for each direction. This produces more useful feedback than a single score. A number may suggest precision that the team does not have at an early stage. If you do use ratings to spot patterns, treat them as prompts for conversation rather than a verdict.
Separate problems with the underlying idea from problems with its current execution. “The lettering is hard to read at small sizes” may be fixable. “The direction relies on a tone that conflicts with the brief” is a more fundamental concern. That distinction helps protect promising concepts from being discarded because an early draft needs work.
Discuss differences, then choose a test
Let people record their first impressions independently before opening the conversation. This gives quieter participants room to form an opinion and reduces the chance that the first confident comment frames the whole review. During discussion, ask for observations tied to the criteria: “What in the concept makes it feel welcoming?” is more productive than “Do we like it?”
Look for disagreements that can be tested. If the group is unsure whether a symbol will remain clear at small sizes, print it at its intended size. If a concept may be difficult to extend, make two quick applications, such as an event notice and a social image. Keep the test small enough that it informs the decision without turning every direction into a full project.
End by choosing a next action, not merely a favourite. You might develop one direction, combine a useful feature from two, or test the two strongest options. Record why you made that choice and what would cause you to reconsider it. A brief decision note prevents the team from repeating the same debate later and makes the next round of work more focused.
