Design By Committee Trap

What is this situation?

Design by Committee Trap — you start with a brief, a deck, a product flow, a campaign, a strategy doc, or a creative direction that actually has a shape, and for a moment the work feels movable. Then the invite list expands: a manager wants it safer, a stakeholder wants it bolder, a senior lead wants it aligned with last quarter, a client wants it more “premium,” someone in the comments asks if the whole thing can be reframed, and another person drops a late suggestion right before sign-off. The work no longer moves in a straight line; it gets passed through meetings, Slack threads, Figma pins, Google Doc comments, async reviews, and follow-up calls where every note sounds reasonable on its own but cancels out the note before it. You keep updating the file, renaming versions, softening edges, adding options, defending choices, and trying to remember what the original decision was supposed to solve. Authority is spread everywhere and owned by no one, so approval becomes a hallway with too many doors: each person can stop the work, but no one can clearly say when it is finished. Over time, the cost is not just the extra edits; it is the way your direct authorship gets pulled away from the thing you are making, until your hand pauses before the next move because you can already hear the next round of objections, much like the Three of Pentacles reversed, where the builder stands by the blueprint while the gathered reviewers become louder than the craft itself.

Why it's not you?

The issue is not that you are being difficult, precious, or unable to take feedback. A Design by Committee Trap is created when approval power is scattered across too many people without clear criteria, ownership, or a final decision point. That structure can make even solid work feel unfinished forever.