Too Many Cooks Is Not a Metaphor — It's Your Project Right Now

There is a particular kind of exhaustion that doesn't come from working too hard. It comes from working in circles. From explaining your vision in a kickoff meeting, then re-explaining it in a check-in, then defending it in a feedback session, then softening it in response to notes, then watching it arrive in the world as something technically functional and completely inert.

You know this feeling. If you've spent any time in a creative field in the last ten years — agency work, content production, editorial, brand strategy, film, any of it — you have felt the specific demoralization of watching a good idea get sanded down by process until it no longer has edges.

We did this to ourselves. And we called it collaboration.

How We Got Here

The pivot toward radical collaboration in creative industries wasn't random. It came from a few converging forces, all of them reasonable on their own terms.

First, there was a legitimate reckoning with the damage done by unchecked creative egos — the auteur model that produced brilliant work sometimes and disasters just as often, often while treating everyone around the primary creative as expendable. Getting more voices in the room was, in many cases, a genuine corrective.

Second, remote work and digital project management tools made collaboration easier and more trackable. Suddenly you could have twelve people commenting on a document simultaneously, and that felt like efficiency. It felt like inclusion. It felt like good process.

Third, the risk-aversion that's been creeping through every corner of the media and entertainment industry created a business incentive for consensus-building. If twelve people signed off on it, twelve people share the blame if it fails. Collaboration became, in many organizations, a liability management strategy wearing the costume of creative culture.

The result is an industry full of people who are technically collaborating constantly and producing work that is profoundly, structurally safe.

The Real Cost of Consensus

Here's what the collaboration-is-always-good framework gets wrong: it treats creative work like a problem-solving exercise where more data points improve the output. More perspectives, better result. More feedback, sharper product.

But creative work isn't just problem-solving. It's also perspective-having. And a perspective that has been averaged across fifteen stakeholders isn't a perspective anymore. It's a compromise. Compromises can be well-executed. They are rarely interesting.

Think about the work that actually got to you — the piece of writing, the campaign, the film, the design — that hit you somewhere real. I'd bet serious money it came from a point of view specific enough to feel like it was made by an actual human being with actual opinions. That kind of specificity almost never survives a full feedback loop. It gets flagged as "too niche" or "potentially alienating" or "a bit much" and it gets filed down.

The irony is that the thing that made it powerful — its particularity — is exactly what the consensus process is designed to eliminate.

Distinguishing Collaboration from Diffusion

I want to be careful here, because the alternative to "collaborate on everything" is not "work in complete isolation and refuse all input." That's its own trap, and a well-documented one.

The distinction worth making is between collaboration that sharpens your work and collaboration that diffuses it.

Sharpening collaboration looks like: a trusted editor who understands what you're trying to do and helps you do it more effectively. A creative partner who challenges your assumptions early, before you've committed to a direction. A director of photography who brings technical solutions to a visual problem you've identified. A co-writer who fills genuine gaps in your own skill set.

Diffusing collaboration looks like: a committee review that requires sign-off from people who have no creative stake in the outcome. A feedback round that collects opinions from people whose taste conflicts with the project's intent. A revision process that incorporates every note regardless of whether it reflects the project's actual goals.

The difference isn't really about the number of collaborators. It's about whether the people in the room are helping you make your thing better, or whether they're gradually making it into everyone's thing — which is to say, nobody's thing.

When to Actually Protect Your Work

So when do you close the door? A few situations where protecting the work from more input is the right call:

When the vision is still forming. Early-stage creative work is fragile. Bringing it into a group process before it has structural integrity is how you end up building something that satisfies the feedback rather than the original intent. Let ideas develop in private long enough to know what they actually are.

When the feedback is coming from the wrong people. Not all input is created equal, and the most well-intentioned note from someone who isn't your audience can still steer you wrong. A 55-year-old brand executive's discomfort with a piece aimed at 25-year-olds is data about the executive, not about the work.

When you've already made the decision. There is a version of collaborative process that is actually just delayed decision-making dressed up as inclusion. If you already know what the right call is, running it through another round of feedback doesn't improve the outcome — it just delays it and introduces the risk that someone else's uncertainty becomes your problem.

When the work is almost done. Late-stage notes on a nearly-finished project are almost always destructive. They introduce changes that haven't been tested against the full piece, and they cost more to implement than they're worth. Learn to recognize when a project is done and stop asking people what they think.

The Skill Nobody Talks About

We spend a lot of time in this industry talking about how to give feedback, how to receive feedback, how to build collaborative cultures, how to make space for everyone's voice. These are real skills and they matter.

But there's a complementary skill that gets almost no attention: knowing when to stop. Knowing when your work has absorbed enough external input and needs to be protected from more. Knowing when the next round of notes will cost more than it contributes. Knowing when the collaborative process has done its job and it's time to make a decision and live with it.

That skill is harder to talk about because it sounds like arrogance. It sounds like you're claiming your judgment is better than the group's. Sometimes that's exactly what you're claiming — and sometimes you're right.

Collaboration is a tool. Like any tool, it can be overused. The work that lasts usually came from someone who knew when to put it down.