Most branding problems do not begin in Figma. They begin in the meeting right before it.
A founder says, “I like it, but can we make it pop?”
A head of sales says, “Our customers want bolder.”
A board member says, “My spouse hates that color.”
Everyone is trying to help. The work starts to drift.
If you work with clients who hold strong opinions about design, you have already met the two futures of that situation:
You harness their conviction and end up with a sharper brand.
You accept every opinion as equal input and end up with a safe, generic compromise.
That second future has a name: design by committee. The term shows up often in product and brand work to describe what happens when too many voices carry equal weight and the result gets diluted.
This post is about keeping the first future alive. You can respect the client’s vision and still lead the process. You can invite input without handing over authorship. You can protect quality without turning the relationship adversarial.
The move is not to fight opinions. The move is to change what opinions are allowed to decide.
What “design by committee” really is
Design by committee is not “multiple people are involved.” Involving partner groups is normal. Usability practice even recommends planned engagement and interviews because it surfaces constraints and context early.
Design by committee happens when:
- decision rights are unclear
- feedback arrives late and unstructured
- personal preference carries the same weight as strategy
- the group aims for agreement instead of outcomes
The result tends to look polished and feel forgettable.
That is not because committees are useless. Committees can produce strong decisions when the process is designed for candor and dissent, not politeness and averaging.
Brand work fails when the group acts like a blender. Every opinion goes in. A little of each comes out. The original idea disappears.
Why smart, reasonable people create mediocre design together
When a concept gets watered down, it is rarely because someone is malicious. It is usually a predictable mix of incentives and psychology.
Shared decisions can reduce personal accountability
Research on collective decisions points out that people often choose group decision-making partly because it reduces the personal burden of responsibility if the outcome turns out badly.
That can be helpful for governance. It is deadly for creative clarity.
If no one owns the decision, no one protects the idea.
Responsibility diffuses as the room grows
Classic social psychology research on diffusion of responsibility shows that individuals feel less personal responsibility to act when others are present.
In a design review, diffusion shows up as:
- everyone feels entitled to tweak
- no one feels obligated to defend the strategy
- the loudest preference wins because it is the easiest path to closure
Groups often discuss the safest information, not the most useful
Group decision research notes a common pattern: groups focus discussion on shared information that is easy to agree on, while unique, decision-critical information can get ignored.
In branding, “shared information” is taste. It is easy to talk about colors. It is harder to talk about category conventions, positioning tradeoffs, and what the customer actually notices.
Critique collapses into criticism, or into silence
Good critique strengthens ideas. Bad critique turns into ego management.
HBR has argued that criticism can support creativity when it is aimed at the work and grounded in clear standards.
If the environment does not feel safe, people stop taking risks. Psychological safety, as defined in Edmondson’s research, supports learning behaviors like speaking up and experimenting.
The paradox is that clients who speak the loudest about taste often do so because the project feels risky. They are searching for control.
The real job: replace preference with criteria
Your client’s strong opinions are not the problem. The problem is when preference becomes the decision system.
You need a decision system that makes taste secondary. If you want a framework that puts strategy first, the 4Ps Method provides exactly that: Purpose, People, Positioning, and Proof working together as a complete brand system.
Here is the simplest version:
- Strategy defines the goal.
- Criteria define what success looks like.
- Evidence tests whether the work meets the criteria.
- One accountable person makes the call.
This is how you prevent a good concept from being negotiated into mush.
Step 1: Name one accountable decider
The fastest way to reduce design by committee is to clarify who decides.
If you have ever run a design sprint, you have seen this principle. Many sprint methods emphasize a “decider” role so the team can converge without endless debate.
In branding, the decider is often the founder, the CMO, or a product leader. The key is not the title. The key is that everyone agrees that the decider decides.
If you skip this step, you will spend the rest of the project negotiating process instead of building the brand.
Kickoff line you can use:
“Input is welcome from everyone. The final call needs one owner so we do not average the work into something no one believes in.”
Step 2: Put roles in writing with a RACI
A role map looks boring until it saves the project.
PMI describes responsibility assignment matrices, commonly known as RACI, as a way to clarify who is Responsible, Accountable, Consulted, and Informed.
You are not using RACI to limit voices. You are using it to prevent surprise vetoes at the end.
RACI snapshot for brand design decisions
When people know their lane, they still contribute. They just do not hijack the finish line.
Step 3: Run a criteria workshop before you show design
Most conflict arrives because the team never agreed on what success looks like.
A short criteria workshop creates shared language.
Agenda:
- Audience and moment: who is deciding and under what pressure?
- Brand promise: what change are we selling?
- Non-negotiables: what must be true in every direction?
- Guardrails: what is out of bounds?
- Evaluation criteria: the five checks we will use in every review
Sample criteria for identity work:
- recognizability at small sizes
- distinctiveness in the category
- clarity of meaning, not clever ambiguity
- capacity to expand across products and channels
- agreement with brand personality traits
Now when someone says, “I hate that,” you can ask a better question: “Which criterion does it fail?”
That small shift moves the conversation from personal taste to shared standards.
Step 4: Structure feedback like a design review, not a brainstorm
Many teams treat reviews like open-mic nights. Everyone speaks. The designer becomes a note-taker. The work becomes a poll.
Design review guidance from Atlassian emphasizes objectives, relevant participants, prep, and specific requests for feedback.
You want a review format that produces usable input.
A simple structure:
- Context: remind everyone of the goal and criteria
- Walkthrough: show the work and how it answers the brief
- Questions: ask for feedback tied to criteria
- Decisions: the decider chooses, or chooses what to test
- Next step: what changes, what stays, what needs evidence
Feedback prompts that keep people out of taste mode:
- “Where does this feel unclear to our buyer?”
- “What would make this more distinctive in our category?”
- “Which part reduces trust?”
- “What is the strongest argument for this direction?”
- “What is the strongest argument against it?”
This turns the room into a thinking partner, not an approval gauntlet.
Step 5: Use evidence to break deadlocks
When a client insists on a choice that conflicts with strategy, your job is not to win. Your job is to put the decision in contact with reality.
Evidence can be lightweight:
- 5-second comprehension checks on a homepage headline
- preference tests that compare distinctiveness and memorability
- interviews that focus on business constraints
- user testing with prototypes, even rough ones
Google’s re:Work guide on team effectiveness highlights psychological safety as a condition that lets teams take interpersonal risks, share concerns, and learn quickly.
When the team trusts the process, they can let evidence lead.
Also, groups can make better decisions when designed well. The goal is to borrow the benefits of group intelligence without the cost of compromise.
Two stories you can probably recognize
Story 1: The founder who wanted “premium,” and meant “safe”
A founder hired a studio after a big funding round. They wanted a brand that “looked like we belong with the big players.”
In the first review, they rejected the most distinctive direction and pointed to the safest one. Their language sounded like taste, but the real driver was fear: fear of being judged by investors, fear of looking small, fear of taking a swing that could be criticized.
We paused the review and ran a criteria workshop. The team wrote down what “premium” needed to signal in their market: reliability, precision, calm confidence, and a hint of speed. Then we listed what “premium” did not mean: copying competitors and erasing personality.
Once the founder saw their own criteria in writing, they could choose with more courage. The final identity still felt premium. It also felt like them. The work did not get safer. It got clearer.
Story 2: The committee that learned to disagree productively
A marketing team had eight people with equal influence. Every round ended with compromises. The designer stopped pitching bold options because they were tired of watching them die.
We changed one thing: a decider was appointed, and the review format shifted. Comments had to map to criteria. People could still disagree, but they had to argue for outcomes, not taste.
The surprising result was speed. Once the rules were clear, dissent increased, and that strengthened the work. The decider did not pick favorites. They picked the direction that best met the criteria and could be validated with evidence.
HBR’s guidance on committees points out that candid debate and dissent can strengthen decisions when the process supports it.
That team still had strong opinions. They just used them in service of the brand.
The client relationship move: assert expertise without disrespect
Clients with strong opinions are often highly invested. That is a good sign. They care.
Your job is to convert that care into clarity.
A few lines that protect the relationship while protecting the work:
- “Let’s separate preference from performance. What do we need this to achieve?”
- “If we aim for internal agreement, we may lose the customer. Let’s check the buyer criteria.”
- “I will take all input. I also need one decision owner so we can move forward with conviction.”
- “We can test this quickly. If the evidence disagrees with the direction, we adjust.”
This keeps you in the role of strategic partner, not pixel executor. For more on positioning yourself as a strategic partner, the key is establishing your expertise early and often.
A practical playbook you can run on your next project
- Kickoff with roles and decision rights
- Run a criteria workshop before visuals
- Write criteria at the top of every review deck
- Ask for feedback tied to criteria, not taste
- Capture decisions, not comments
- Use quick evidence to resolve conflict
- Protect psychological safety so people can disagree without politics
When you do this, you still get collaboration. You also get a brand that has a point of view. Design by committee becomes design by intention.
That is the outcome your client hired you for.
Closing: clarity, direction, action
Clarity: Design by committee is a process problem disguised as a taste problem.
Direction: The cure is a decision system built on criteria, roles, and evidence.
Action: On your next project, appoint a decider and run a criteria workshop before you show any design. Watch the entire review culture change.
If you need help or have any questions, please reach out.
References
- Nielsen Norman Group: Design by Committee
- Nielsen Norman Group: Stakeholder Interviews
- Harvard Business Review: Want Better Decisions? Appoint a Devil’s Advocate
- Harvard Business Review: Criticism and Creativity
- Harvard Business School Online: Psychological Safety Overview
- Edmondson (1999): Psychological Safety and Learning Behavior
- Google re:Work: Team Effectiveness Guide
- Darley & Latané (1968): Diffusion of Responsibility
- PMI: RACI and Responsibility Assignment Matrix
- Atlassian: Design Reviews and Feedback Structure