Start by defining the decision
A disagreement about creative direction can sound personal: one collaborator prefers a restrained identity, while another wants something expressive. Before asking anyone to defend a concept, name the decision the group needs to make. Is the team choosing a final direction, selecting two ideas to develop, or deciding what to show a client? Those are different conversations. A facilitator can open with a simple question: “What must we decide by the end of this meeting?”
Write down the decision, the intended audience and any practical constraints everyone already accepts. For a visual identity, these might include where the work must appear, what it needs to communicate and who has final approval. Separate firm constraints from assumptions that can be tested. This gives collaborators a shared frame without asking them to abandon their points of view.
Give each idea a fair hearing
Ask each person to present their idea in the same short format: the problem it addresses, the audience response it aims for and the choices that make it work. Set a time limit and hold questions until each presentation is finished. Equal space does not mean every proposal will be selected; it means the group can understand each one before judging it.
Then invite participants to describe what they heard before offering criticism. Someone might say, “The bold colour system is meant to help people recognise the project quickly across posters and social posts.” The proposer can correct any misunderstanding. This step is especially useful when a team has begun arguing about surface details while disagreeing about the purpose of the work.
Turn preferences into criteria
“I like this one” is an honest reaction, but it is not enough to guide a group decision. Ask what sits behind the preference. Is the concept easier to read, more adaptable, more distinctive within the project’s context, or more appropriate for its audience? Record a short list of criteria in plain language. For a workshop series identity, the list might include legibility at small sizes, flexibility for changing event themes and a tone that feels welcoming rather than formal.
Use the criteria to discuss specific strengths and risks of each proposal. Avoid treating a quick score as an objective verdict: criteria can pull in different directions, and the team may not agree on their relative importance. A useful facilitator question is, “What would we give up if we chose this direction?” It makes trade-offs visible and gives quieter participants a concrete way to contribute.
Test the uncertainty, not the people
When discussion circles around an unproven claim, design a small test instead of extending the debate. If one collaborator thinks a detailed illustration will be difficult to use in a narrow newsletter banner, place it in a rough banner. If another worries that a minimal concept lacks warmth, try it with a sample photograph and a short piece of copy. A test should answer a named question; it does not need to become a polished presentation.
Agree in advance what the group will look for, then review the results together. Ask what improved, what failed and what remains unknown. This keeps feedback focused on the work rather than on who proposed it. It can also reveal a useful combination: one direction may have the stronger layout system, while another suggests a better approach to imagery. Combining ideas works best when the elements serve a coherent goal, not when it is used to avoid making a choice.
Close with a decision and a record
Before the meeting ends, state who will decide and how. Some teams can reach agreement; others need a project lead or client to choose after hearing the evidence. Either approach can be fair if the decision process is clear from the start. If a choice cannot be made yet, assign a specific test, an owner and a point at which the team will return to it. “We will keep exploring” is less useful than naming what needs to be learned.
Finish by recording the chosen direction, the reasons for it and any concerns that still need attention. For example: “Develop the flexible type-led system because it works across event formats; test whether the imagery adds enough warmth.” Share the note with everyone involved. It prevents the same debate from restarting and shows that an idea can be set aside without its contributor being dismissed. Good facilitation does not remove disagreement; it helps a team use it to make a more considered piece of work.
