A camel is a horse designed by committee.

There’s an old, sardonic saying in the design and business worlds: “A camel is a horse designed by a committee.”

It’s a pithy, powerful image. We all know what a horse is: a creature of elegance, speed, and singular purpose. A camel, while wonderfully adapted for the desert, is by comparison a awkward-looking hodgepodge of features—a hump, long eyelashes, wide feet—all bolted on to solve a series of disconnected problems, with little regard for a cohesive whole.

This metaphor is more than just a witty quip; it’s a stark warning for anyone involved in creating products, services, or experiences. It perfectly encapsulates the pitfalls of design by committee, a process where the pursuit of consensus and the incorporation of too many conflicting opinions dilute a strong vision into a compromised, ineffective mess.

How the “Camel” Gets Designed

The journey from sleek horse to clumsy camel is rarely intentional. It happens gradually, in conference rooms and Slack channels, through a series of well-meaning but misguided steps:

1. The Death of the Visionary: A designer or product manager starts with a clear, user-centric vision—the “horse.” This vision is based on research, a core user need, and a strong aesthetic principle.
2. Too Many Cooks: The prototype is presented to a group of stakeholders. The VP of Marketing suggests adding a feature because a competitor has it. The Lead Engineer proposes a change to simplify the backend, complicating the user flow. The CEO wants the company logo to be bigger.
3. The Compromise Cascade: Instead of evaluating these suggestions against the core vision and user needs, the team seeks consensus. To avoid conflict and make everyone feel heard, a little bit of everything gets added. The elegant solution is burdened with exceptions, additions, and redundant features.
4. The Launch: What ships is no longer a horse. It’s a camel. It technically has all the requested features (it even has a hump for storing water!), but it’s slow, confusing, and fails to delight anyone. It satisfies internal politics but fails the user.

The Antidote: Designing the Racehorse

So how do you avoid designing the proverbial camel and instead create a thoroughbred product that wins? It requires intentionality and discipline.

• Empower a Decisive Leader: Every great product needs a single, accountable product owner or design lead who holds the vision. This isn’t about being a dictator; it’s about being a curator. Their job is to listen to all input but filter it ruthlessly through the lens of the user and the core product goal. Their question should always be: “Does this make the product better for the user, or does it just satisfy an internal stakeholder?”
• Define and Defend the User: The user’s needs are the ultimate shield against feature creep. Ground every decision in user research and data. When a suggestion arises, ask: “Is this what our user actually needs, or is it what we think they want?” A deep, shared understanding of the user persona is the best tool for building consensus around the right decisions.
• Embrace a “No” Culture: Saying “no” is not negative; it is a essential design skill. Saying “no” to a superfluous feature is saying “yes” to clarity, usability, and a focused value proposition. Frame this positively: “We’re not doing that because it conflicts with our primary goal of making the onboarding process seamless.”
• Prototype and Test Early: Don’t wait until the product is fully built to get feedback. Use low-fidelity prototypes and user testing sessions to validate ideas early and often. Often, seeing a real user struggle with a “committee feature” is the most powerful argument for cutting it.

The Takeaway: Celebrate the Camel, But Don’t Design One

Let’s be clear: the camel is a marvel of evolution, perfectly suited for its environment. But it wasn’t designed by a committee with conflicting agendas; it was adapted by the relentless pressure of a singular environment—the desert.