Too Many Cooks: How I Learned to Protect My Creative Vision Without Shutting Everyone Out

There's a song that lives in my archives that I will never release. Not because it's bad, exactly, but because it stopped being mine somewhere around the fourth round of notes. By the time everyone who loved me had weighed in — the producer, the collaborator, the well-meaning friend who once took a music theory class in college — the thing I'd started with had been sanded down into something smooth and unrecognizable. Safe. Palatable. Completely hollow.

I pulled it. Started over. And I learned something I wish someone had told me years earlier: collaboration is a gift, but it has a threshold. Cross it, and you're not making art anymore. You're making a committee report.

The Moment You Realize You're No Longer Driving

It doesn't happen all at once. That's the sneaky part. It starts with one reasonable suggestion — what if the chorus came in earlier? — and you think, okay, sure, that's a fair point. Then there's another note, also reasonable. Then someone else chimes in. Each individual piece of feedback sounds logical in isolation. But somewhere along the way, you look up and realize you've been slowly steered into a ditch.

I've had this happen with music, with visual work, with written pieces. The first sign is usually that I stop feeling excited about the project. That low-grade enthusiasm I normally carry around — the thing that makes me want to wake up early and get back to the work — just goes quiet. That silence is a warning signal I've learned not to ignore.

The second sign is when I start explaining my original choices in the past tense. Well, I had wanted it to feel more raw, but... The moment "I had wanted" replaces "I want," something's already been lost.

Not All Feedback Is Created Equal

Here's where I have to be honest with myself and with you: sometimes the feedback is right. Sometimes someone outside the project sees something I genuinely can't, because I'm too close to it. I've had collaborators catch structural problems in songs that I'd been circling around without naming. I've had a friend read a draft and point to a paragraph that I secretly knew was weak but kept hoping nobody would notice.

The difference between that kind of feedback and the diluting kind comes down to one question: Is this note asking me to make the work more fully itself, or is it asking me to make the work more comfortable for someone else?

Feedback that sharpens your vision — even when it stings — feels like someone handing you a better tool. Feedback that dilutes it feels like someone asking you to work with your non-dominant hand because it makes them less nervous.

I've started literally writing this question down when I'm sorting through notes. It slows me down enough to actually think instead of just react.

The Times I Pushed Back (And What It Cost Me)

Pushing back isn't free. I want to be clear about that. There have been professional relationships that got awkward when I said, "I hear you, and I'm going to keep it the way it is." There have been collaborators who took it personally. There was one situation — I won't get into specifics — where holding my ground on a creative choice meant losing a partnership I'd genuinely valued.

And I'd do it again.

Because the alternative is a body of work that doesn't actually reflect who I am. And what's the point of that? If I wanted to make things by consensus, I'd go into marketing.

That said, I've also been wrong. There was a visual project where I dug in on a color palette that, in retrospect, really wasn't working. I was so defensive of the original concept that I couldn't hear a note that was completely valid. The piece suffered for it. So this isn't about being stubborn for stubbornness's sake — it's about being discerning.

A Framework I Actually Use

Over time I've built a loose system for processing outside input, and it's kept me from going off the rails in either direction.

Wait 24 hours before responding to notes. This is the single most useful thing I do. My first reaction to feedback is almost never my most accurate one. Sometimes I need to be annoyed before I can be clear-eyed.

Separate the note from the solution. When someone gives feedback, they often bundle the problem they're identifying with the fix they'd suggest. The problem might be real; the fix might be wrong for your project. Try to hear only the former and ignore the latter until you've sat with it.

Ask yourself who the work is for. Some projects are genuinely collaborative — they're supposed to carry multiple voices. Others are solo expressions, and treating them like group projects is a category error. Know which kind you're making before you open the floor.

Check your gut, not your ego. There's a difference between defending your work because it's right and defending it because you're attached. I try to ask: if a stranger had made this exact choice, would I still defend it? If yes, hold the line. If no, maybe listen harder.

Staying Open Without Getting Lost

The goal isn't to become someone who never takes notes. That's just a different kind of creative failure — the kind that stops growing, stops surprising itself, stops making anything worth talking about.

The goal is to stay porous enough to let in what's useful and solid enough to keep out what isn't. It's a balance I'm still calibrating. Honestly, I think I always will be.

But I know this much: the work I'm most proud of — the stuff that actually feels like me — came from moments where I stayed in the driver's seat even when it would've been easier to slide over. And the work I regret, or that never saw the light of day? Almost always came from letting someone else grab the wheel.

Your vision is the whole point. Protect it like it matters — because it does.