Start with the decision the presentation needs to support
Before arranging slides or boards, decide what you need from the people viewing them. Are they choosing a direction, checking whether a direction fits the brief, or reviewing details of an already selected system? These are different conversations. A presentation that asks for a final choice while important questions remain unresolved can lead to premature approval or a long list of contradictory edits.
Write a short decision statement for yourself, such as: “We need to decide which direction best expresses a confident but approachable studio.” Then identify who will give feedback and what each person can reasonably assess. A team member who writes customer communications may notice whether the tone feels usable; a person responsible for production may spot practical constraints. You do not need everyone to comment on every detail.
Give every concept the same clear structure
Begin with a brief reminder of the audience, communication goals and practical needs. Keep this concise: the presentation is not a repeat of the entire discovery process. For each concept, explain its central idea in plain language, then show how that idea informs the typography, color, imagery and layout. Avoid describing one direction with a polished story while leaving another to speak for itself. Uneven explanations can make the comparison unfair.
Use the same sequence of examples for each direction. A small creative team might show a website header, a social post, a simple document cover and a one-color treatment. When viewers see each concept in comparable situations, they can discuss how the systems work rather than reacting to whichever mockup looks most impressive. Label unfinished elements as explorations so they are not mistaken for final specifications.
Show the identity working, not just looking attractive
A visual identity is more than a logo on a large, empty page. Include enough everyday material to reveal how its parts behave together. For a workshop business, that might mean showing a session announcement with a long title, a registration confirmation and a handout with dense instructions. These applications put useful pressure on the system: Can people find the important information? Does the identity still feel coherent when the content changes?
Choose examples that reflect likely use, not just ideal conditions. Show a short and a long headline, a photograph that is less than perfect, or a layout with more text than a promotional image would need. You can also include one deliberately simple example, such as a text-only notice. If a direction only works when every image, phrase and format is carefully curated, that limitation is worth discussing before it becomes part of the team's routine.
Ask questions that produce actionable feedback
“Which one do you like?” is easy to answer but hard to design from. Ask questions tied to the original goals instead: Which direction makes the work easiest to understand? Where does the tone feel too formal or too casual? Which elements would be difficult to use consistently? Invite viewers to point to a specific example and explain their reaction. This separates an observable concern, such as a hard-to-read heading, from a general preference for blue.
Consider collecting initial responses individually before opening a group discussion. That gives quieter participants a chance to form their own views and reduces the chance that the first opinion becomes the group position. During discussion, record comments as questions or problems to investigate rather than immediate instructions to change the design. “The event date is easy to miss” is more useful than “Make the date red,” because it leaves room to test several solutions.
Close with a decision and a testable next step
At the end, summarize what appears settled, what remains uncertain and who will make the next decision. If one direction is preferred, name the reasons that connect it to the brief. If the group is divided, avoid merging every favorite feature into a single concept by default. First check whether the disagreement concerns the core idea, a particular application or a detail that can be refined later.
Turn unresolved concerns into a small set of tests. For example, try the preferred direction on a text-heavy handout, check a compact version in a narrow space, or compare two treatments for event information. Assign a person to review each test and agree on what would count as improvement. A useful presentation does not have to end with universal enthusiasm; it should leave the team knowing what to keep, what to examine and how to move forward.
