The homepage is in its fourth review. There are fifteen comments in the file, three of them contradict each other, and the headline now carries two "and"s it didn't have last week. Nobody did anything wrong: everyone was asked for input, and everyone gave it.
That's design by committee, and in a rebrand it comes from decisions nobody owns. The fix is one owner for every decision, a short list of people who advise, and a date when the decision closes.
Key takeaways
- Design by committee is an ownership problem. When nobody owns a decision, every comment carries the same weight, and the work ends up averaging them.
- The Decision Table names one owner per decision. Each rebrand call gets the person who decides, the few who advise, the people who hear about it, and a closing date. Two owners means none.
- Alignment isn't consensus. Everyone has to understand the direction and support it; nobody has to prefer it.
- A committee reviews only the one-way doors. The name, the trademark filing, the domain and any regulated claim get a wider review; what you can change after launch goes to one owner.
What design by committee looks like in rebrands
Design by committee is what a design becomes when a group approves it and nobody in the group has the final say. Each reviewer's comment goes in, none comes out, and the result carries a piece of everyone's preference and the full intent of no one.
In a rebrand it has a recognizable rhythm:
- A direction is proposed, then someone disagrees
- Next second option gets created…
- Then a third
- Finally, someone who wasn't involved before wants to revisit the first option!
Suddenly, what should have taken a few days turns into weeks, because nobody owns the decision. Talent isn't the problem here.
Rebrands breed it for two reasons. A brand belongs to everyone: the CEO sees the vision, sales sees the pipeline, product sees the features. And nobody wants to own taste. Collecting opinions feels safer than making a visual call that someone senior might dislike, so the decision stays open and the reviews keep coming.
At first, it feels collaborative. Then it gets heavy, and feedback becomes fragmented. Direction starts shifting mid-way. Work gets approved, then questioned, and then adjusted again. And slowly, without anyone explicitly choosing it, responsibility drifts downward. How? Execution teams start filling the gaps:
- Designers interpret strategy
- Developers make product decisions
- Marketing rewrites positioning on the fly
Because someone has to, not should.
On a homepage, giving every offer equal weight can take two shapes. Either every offer takes a turn: a financial technology provider's hero rotates three slides, each with its own headline and button, from fleet management software to outsourcing for Asia Pacific fund managers.
Or every offer shares the line: a managed IT provider's hero reads "Managed IT. AI. Cybersecurity. One partner for it all." Neither page shows how it was decided, and either layout can be a deliberate choice. What a first-time visitor gets is the same in both: several offers at equal weight. On your own homepage, the same shape with nobody able to say who chose it is an open decision showing through.
Pick any open item in the latest review deck and ask who can close it today. If the honest answer is "the next meeting", it's a committee decision.
The cause is decision rights nobody assigned
Too many opinions is the symptom. The cause is that nobody holds the decision rights: the explicit say over who closes which call. Paul Rogers and Marcia Blenko, who set out the RAPID decision model in Harvard Business Review, describe both ways it fails. When more than one person thinks the decision is theirs, it "will get caught up in a tug-of-war"; on the flip side, "No one is accountable for crucial decisions, and the business suffers."
Netflix wrote the rule into its culture memo: "We avoid decision-making by committee, which tends to slow companies down and undermine accountability." Each significant decision gets an informed captain, "responsible for making a judgment call", who is expected to "seek out different opinions". The input stays, and one person answers for the call.
In a rebrand, the decision that needs an owner above all others is the one execution can't make:
At some point, someone has to decide what the company is becoming, who it's for, and what it's not. That doesn't sit with designers. Or developers. Or external partners. That sits with leadership.
Write down every decision your rebrand has open right now and put one name next to each. Every blank, and every line with two names, is where design by committee will start.
The Decision Table gives every decision one owner
The Decision Table is one row per decision, with four columns beside it: who decides, who advises, who hears about it, and the date it closes. Everyone wants input. Few want accountability. The table gives everyone the first and puts the second on one name.
In effective teams, roles are defined early:
- Who contributes perspective
- Who challenges assumptions
- Who makes final decisions
This isn't about limiting collaboration. It's about protecting direction. The table puts names against those roles. Advisers contribute and challenge; the owner decides; everyone else hears about it.
Four rules keep it honest:
- One name in Decides. A named leader, never a group. If a decision has two owners, it has none.
- Advises is short and has a deadline. Advisers' input arrives by a date, in writing, against the direction rather than their taste.
- Hears about it means informed, not consulted. These people get the decision and the reason, not a vote.
- The closing date is real. After it, the decision reopens only through its owner, and the reopening has a cost on paper.
And everyone has a perspective, but not everyone should have a vote. That's an uncomfortable distinction, but a crucial one.
Here's the table filled in for a hypothetical mid-market B2B website rebrand. The roles and dates are examples; the shape is the point.
| Decision | Decides | Advises | Hears about it | Closes by |
|---|---|---|---|---|
| Positioning: what the company claims, and for whom | CEO | VP Marketing, Head of Sales, Head of Product | Leadership team, board | End of week 2 |
| Audience ranking: who the site persuades first | VP Marketing | Head of Sales, Customer Success lead | Leadership team | End of week 2 |
| Message: the headline claims and their proof | VP Marketing | Head of Sales, Head of Product | Whole company | End of week 3 |
| Site structure: which pages exist and why | VP Marketing | Head of Sales, SEO lead | Design and build team | End of week 4 |
| Visual identity direction | Head of Brand | Design partner, CEO | Whole company | Before page design starts |
| Company name, if it changes | CEO | Legal counsel, VP Marketing, board | Whole company, then customers | Before design starts |
| Launch announcement | VP Marketing | Head of Sales, Support lead | Whole company, then customers | Two weeks before launch |
Copy the table into your kickoff document before the first review, and send review comments to the owner of the decision they touch, not to the designer. That one routing rule takes the designer out of the negotiation: every comment reaches the person who can act on it.
Stakeholder alignment, buy-in and consensus are different
Consensus means everyone agrees. Alignment, in turn, means everyone understands the direction and supports moving forward, even if it wasn't their preferred option. Trying to achieve consensus on every decision creates friction.
Amazon's 2016 letter to shareholders has a phrase for that kind of support: "disagree and commit". When you have conviction on a direction and there's no consensus, the letter suggests asking the people who disagree whether they'll gamble on it with you.
The IETF's RFC 7282, an informational document on how its working groups reach decisions, counts support for a choice you didn't prefer as consensus: a participant who says "That's not my favorite solution, but I can live with it" is part of the consensus, not the rough part of it. The IETF can even close a question with objections still standing: "Rough consensus is achieved when all issues are addressed, but not necessarily accommodated".
| Term | What it asks of people | When you need it |
|---|---|---|
| Consensus | That everyone agrees on the chosen option | Not as a working rule: it gives every reviewer a veto |
| Stakeholder alignment | That everyone understands the direction and supports it, preferred or not | Before design starts, from everyone in Decides and Advises |
| Stakeholder buy-in | That the people who carry it out commit to it in their own work | Before launch, from sales, support and product |
A quick test of alignment comes from why rebrands fail inside leadership teams: ask each leader, separately, who your primary competitor is. If the answers differ, the team isn't aligned yet.
Stakeholder management in a rebrand comes down to this sequence: alignment from the table, buy-in from the people who carry the brand, and consensus as a bonus, never a requirement.
Run the alignment conversation before anyone designs
The alignment conversation is a working session with the people in Decides and Advises, before any visual exists. It goes well when the room argues about the business, not the look:
A rebrand is not a creative exercise. It's a business decision tied to growth, market perception, and marketing alignment.
When that shift happens, the tone of discussions changes. Opinions become hypotheses. Preferences become secondary to strategy.
On the table:
- The business change in one sentence
- The decision being closed and its owner
- The options
- The direction they're judged against
Off the table:
- Taste ("I don't like blue")
- Wordsmithing headlines in the room
- Choices that belong to the design partner
- Anything already closed
Before you close, ask for objections the way RFC 7282 suggests to working-group chairs: "Is everyone OK with choice A?" draws objections, while "Can anyone not live with choice A?" is more likely to hear only from people who think choice A can't work. The RFC calls the follow-up essential: "What are the reasons you object to choice A?" Each reason gets a written answer, even when the answer is no.
The people left out of this session don't stay out:
When stakeholders are not brought into the process early, they re-enter late with stronger opinions and less context. That's when resistance and delays show up. Not because they disagree, but because they weren't aligned.
That includes the CEO. A CEO who overrides the design in the final review is reopening a decision that was supposed to be closed, so treat it as one: route it to the decision's owner, and price it. The Variance Map runs a plan at ×1 when decisions close before design and ×2 to 3 when they're reopened after it.
If the CEO wasn't in the Decision Table, the table was wrong. Anyone who can stop the launch takes part from the first session, as the B2B rebrand checklist asks, and sits in Decides or Advises.
When a committee should review the work
A committee can earn a place in a rebrand's review, never in its decision. Which calls get the wider review depends on whether the decision can be undone, and Amazon's 2015 letter to shareholders draws its line between a heavy and a light decision process in the same place.
Decisions that are "consequential and irreversible or nearly irreversible", the one-way doors, "must be made methodically, carefully, slowly, with great deliberation and consultation." Reversible ones should be made "quickly by high judgment individuals or small groups", and running the heavy process on them ends, the letter says, in "slowness, unthoughtful risk aversion, failure to experiment sufficiently".
In a rebrand, the one-way doors are the company name, the trademark filing, the domain and any claim your industry regulates. They get a wider review: legal counsel, the CEO and, where it applies, the board. Everything you can change after launch, such as the homepage copy, the imagery and the page layout, goes to one owner with advisers and a date. Either way, one person signs.
Mark each row of your Decision Table as one-way or two-way. Only the one-way rows get a review meeting.
How fifteen reviewers became three owners
On one project of mine, it went like this:
One of the hardest alignment challenges was simply reducing the number of decision-makers. Imagine 15 people giving feedback? I.e. 15 slightly different perspectives of what the company is, or should be.
Honestly, nothing moves like that. At some point, the shift had to happen; decision ownership was reduced to 3 people… max. Didn't others matter? Yes, but clarity simply doesn't survive committees.
And something interesting happens when that shift is made. Decisions get faster, not rushed, just clearer. Conversations stop getting pulled in different directions. Now there's an actual owner.
The filled table above holds seven decisions with three owners, one name on each row, and everyone else in Advises or Hears about it. Count the people who can stop any decision on your project today. If it's more than three, move the rest to Advises.
Final thoughts
The Decision Table won't make a decision good, and it doesn't replace legal review of a name or a claim. It also can't fix a leadership team that disagrees about what the company is; that's a positioning problem first. What the table does is make every open question someone's job, with a date, so review rounds argue about the work instead of about who decides. Execution without direction shows where a busy team's decisions went missing.
If you want the table filled in and the first decisions closed in a fixed engagement before your build partner starts, that's the work I do as a B2B website strategy consultant.
Frequently asked questions
What is design by committee?
Design by committee is what happens when a group approves a design and nobody in it has the final say. Every reviewer's comment goes in, and the result averages them. In a rebrand it starts when decisions have no named owner, so review rounds turn into negotiations.
How do you avoid design by committee?
Give every decision one owner, a short list of advisers with a deadline for input, and a closing date: the Decision Table. Send review comments to the decision's owner instead of the designer, and keep wider review for the decisions you can't undo after launch, such as the company name, the trademark filing, the domain and any claim your industry regulates.
What does it mean to align stakeholders?
It means everyone involved understands the direction and supports moving forward, even when it wasn't their preferred option. A quick check: ask each leader, separately, who your primary competitor is. If the answers differ, the team isn't aligned yet, and design reviews will turn into positioning debates.
What is the difference between stakeholder alignment and buy-in?
Alignment is a shared understanding of the direction and support for it, even from people who preferred another option, and you need it from the people who decide and advise before design starts. Buy-in is the commitment to carry the direction out, and you need it from sales, support and product before launch.
Who should make the final call in a rebrand?
One named person with the authority to close the decision: the CEO, or someone the CEO explicitly backs. For positioning that's the CEO or the VP of Marketing; for the message and the site, the VP of Marketing. Never the agency or the designer: they execute a direction, they shouldn't have to invent it.
