How to review brand concepts without a taste vote

A brand concept review works best when everyone judges the same job. The question is whether the proposed identity supports the business, audience and applications in the brief. Personal preference matters, but it should not be the only information guiding the decision.

A room full of comments about colours and favourite logos can produce a long list of reactions without a clear direction. Focus the conversation on fit, recognition, language and use. Then distinguish a concern about the concept from a detail that can be refined within it.

Agree how the review will work before the presentation. This makes the feedback easier to interpret and helps the design team understand which decisions are approved, which need development and which still require evidence.

Read the brief together first

Begin with a short restatement of the business's offer, audience and intended direction. Include the applications that the identity needs to handle. A concept designed for a consumer product will be judged differently from one meant for a professional service firm.

Confirm what has changed since the brief was agreed. A new product category, audience or naming decision can affect the work substantially. If the business direction has moved, say so directly instead of reviewing the concepts as though the original criteria still apply.

Keep the review group small enough to make decisions, but include the people responsible for important applications. The operations person may notice a practical packaging issue that the campaign team does not. Give everyone the same context so that those contributions can be compared fairly.

Ask what the concept communicates

Look at the proposal before hearing the full explanation. Ask what it suggests about the business and how those associations relate to the brief. This is a useful test of the work's immediate impression, rather than a demand that a logo explain every service on its own.

Then listen to the design rationale. Good rationale explains choices and relationships. It should help the team understand why the type, colour, mark and imagery belong together. It should not require a long story to make an otherwise confusing application usable.

Record the difference between an unfamiliar direction and a direction that contradicts the brief. A new identity may need time to become familiar. That alone is not a reason to reject it. A proposal that signals the wrong category or cannot support the offer needs a more specific response.

Compare the same applications

Ask to see each direction in comparable situations. These could include a mobile header, a product pack, a bilingual sign and a simple social layout. Equal applications make the review more useful than comparing one polished mockup with another direction shown only as a flat logo.

Use realistic text and sizes. A small brand name in a profile image has a different job from a large sign. A longer Arabic service description may reveal a spacing issue that a short English placeholder conceals. These are practical tests of the system, not decoration around the concept.

You can explore Bricks' branding projects to see identities across different applications. The useful lesson is to look at the system in use, including the smaller supporting pieces, rather than choosing a concept from its most impressive hero image alone.

Separate direction changes from refinements

A direction change alters the central idea or structure of the identity. A refinement improves a particular application within that structure. Saying that the brand feels too formal may be a direction issue. Asking for more space around a line of copy is usually a refinement.

Be explicit about which kind of feedback you are giving. If a direction is approved subject to refinements, record that approval before listing the adjustments. Otherwise the design team may interpret every comment as a request to reconsider the entire concept.

Avoid combining favourite parts from several directions without testing the result as a complete system. A symbol from one proposal, type from another and colours from a third can lose the relationships that made each direction work. If a combination is worth exploring, treat it as a new proposal to review properly.

Give feedback with an observation and a consequence

Describe the issue you can see and explain why it matters. For example, a variant name may be difficult to distinguish at product-card size, which could confuse someone choosing between two products. That gives the team a problem to resolve without prescribing an arbitrary design solution.

• Name the application or decision being discussed.
• Describe the observation in concrete language.
• Connect it to the audience or business requirement.
• State whether the concern is essential or optional.
• Identify any test that would help settle the question.

Consolidate the feedback before sending it back. Several separate messages can contradict one another or give small comments equal weight with major decisions. A single response with priorities helps the next round address the important issues in the correct order.

Test the Kuwait applications before final approval

For an identity used in Arabic and English, review both language versions as part of the concept. Test the name, descriptor and layout together. Leave enough time for language corrections while the design remains flexible rather than treating translation as a last export task.

Consider where the identity will be seen locally. A shop sign, a delivery label, a product page and an event backdrop have different distances and information needs. A design does not need to work identically in each situation, but the important applications should be tested before production starts.

Close the review with a written decision. Name the direction, the approved elements, the remaining changes and the person responsible for the next approval. The team should leave knowing whether it is developing the chosen concept or beginning another round of exploration.

Turn a vague comment into useful feedback

A reviewer might initially say that a packaging direction feels too busy. Ask them to identify the application and what becomes difficult to understand. The useful observation may be that the variant name loses emphasis in the product grid, which matters because customers need to distinguish similar items.

The next action is then a focused test of hierarchy at the intended size. The designer can explore spacing, contrast or a simpler treatment while preserving the approved concept. That is more actionable than asking every application to become quieter without explaining why. Record the successful test beside the approval so the decision can guide later variants. The product detail shot-list guide applies the same principle of defining the information each image needs to communicate.

Frequently asked questions

Should everyone in the company vote on a logo?

A broad vote can reveal reactions but often lacks the brief and application context. Use a focused decision group, then test specific concerns with the people who represent the audience or will use the identity.

Is it useful to show competitor identities?

Yes, when the comparison explains category expectations and opportunities to be distinct. It is less useful as a request to copy a competitor's look or to judge concepts by resemblance to a popular brand.

What if the team likes different directions?

Return to the agreed criteria and identify the source of disagreement. The audience, tone or application priorities may still be unresolved. Settle that issue rather than averaging the concepts into an uncertain compromise.

Bricks' branding and strategy work is developed through decisions about meaning and use. A focused concept review helps those decisions become a system the business can apply with confidence.