The Problem With Logo Design by Committee

Design by Committee Is a Real Problem

The research on group decision-making in creative contexts is pretty clear: committees regress to the mean. The most distinctive, surprising, and potentially excellent options get eliminated because they make at least one person uncomfortable. What survives is the option that offends nobody — which is the same as saying it excites nobody.

Logo design is particularly vulnerable to this dynamic. Everyone has aesthetic opinions. Everyone feels qualified to evaluate visual work because they live in the visual world. And in a committee setting, the social pressure to reach consensus overrides the strategic discipline to choose the option that best serves the brief.

How I Structure Stakeholder Input

I don't present logo concepts to large groups. I present to one or two decision-makers who have the authority and strategic understanding to evaluate the work against the brief.

If there are multiple stakeholders whose input matters, I gather that input before the presentation through a structured intake process. Each stakeholder answers the same questions independently: What qualities should the new identity communicate? What existing elements should be preserved? What visual directions would feel wrong for this brand? I synthesize these inputs before the design phase and present the synthesis back to the group for alignment.

By the time I present concepts, the group has already agreed on the evaluative criteria. The presentation becomes a check against agreed standards rather than a free-form opinion exchange.

One Evaluator, Clear Authority

The single most important structural decision in any brand project is establishing who has final approval authority. Not who has input. Not who needs to be consulted. Who has the final say.

I establish this in writing at the start of every project. When the approval chain is ambiguous, I ask for it to be clarified. This protects the project from the situation where a concept is approved at one level and then revised out of recognition at a higher level.

The Feedback Filter

When I do receive committee feedback, I filter it before acting on it. Feedback falls into three categories: strategic concerns (this doesn't serve the brand's goals), functional concerns (this won't reproduce correctly in our main use case), and preference statements (I personally don't like this aesthetic).

Strategic and functional concerns get addressed. Preference statements get explored — "what specifically about this direction isn't right for the brand?" If the preference can be grounded in a strategic or functional concern, I address it. If it can't, I explain why the design choice serves the brief and recommend proceeding.

This filtering process occasionally frustrates stakeholders who feel their preferences are being dismissed. I address this directly: my job isn't to design something everyone likes. It's to design something that serves the brand's strategic goals. The brief is the standard, not personal taste.

When to Accommodate Preference

That said, I'm not rigidly inflexible. Client relationships require trust, and sometimes a preference accommodation — when it doesn't compromise the design's strategic effectiveness — is the right call for the relationship.

The line I draw: I'll accommodate preferences that don't compromise the brief. I won't accommodate preferences that do. And I'll always explain which side of that line a requested change falls on.

The Long Game

The best logos I've produced came from clear briefs, decisive clients, and a disciplined process that kept strategic alignment at the center of every decision. The worst came from unclear briefs, diffuse authority, and design-by-committee dynamics that optimized for internal consensus rather than external effectiveness.

Brief discipline and decision-making structure are the designer's responsibility to establish, not just the client's to provide.