When to back out
Not every project becomes a collaboration. And that’s okay but it still deserves a moment of reflection.
Sometimes, projects start with excitement, alignment, and the promise of a creative partnership. You invest time, you explore ideas, you prepare. The road to the shoot feels smooth. Everyone’s on board. You feel trusted, seen, respected. And then… the actual shoot happens.
And suddenly, that energy shifts.
Recently, I was involved in a project where the lead-up was incredibly positive. We had alignment on style, purpose, tone.
Or so I thought. To be honest, I had jumped into the project with double motivation: yes, it had a clear commercial angle, but for me, it was also an opportunity to bring more of myself into the work. A shared vision. A partnership. Something that could serve the client and let me creatively express a bit more of what I stand for.
I was partially compensated for the work, of course. But a lot of it I treated as my own passion project. I had already spent far more hours on it than initially budgeted. Because I cared. Because I was creatively engaged. Because I wanted this to be something we could both be proud of.
But once the camera started rolling and the first rough edit hit their inbox, the vibe flipped.
Instead of building forward from a shared base, I was met with a wall of micro-management. Detailed feedback, not on structure or intent, but on every cut, every transition, every breath. The kind of feedback that says: “I don’t trust your vision. I want it done my way.”
And then came the remark that really changed everything:
They compared my rough cut, my early, clearly communicated first preview, to a PowerPoint presentation. That one hit hard. Not because I believed it. Quite the opposite. I know what I deliver isn’t PowerPoint level. I know the quality and intent behind what I create.
The comment was about an animation that I used on a “lower third” that animates the name of an interviewed person.
But that comment didn’t just critique the work. It told me everything about how they viewed me, and this project and how they approach their work and team. That remark opened my eyes: this was never going to be our project. It was theirs and I was just expected to deliver on cue.
That comment wasn’t feedback. It was dismissal. It wasn’t a creative conversation. It was a put-down. It made me realize that they weren’t ready to collaborate, they weren’t open to creative dialogue, and they certainly weren’t seeing what I brought to the table. They were stuck in their own narrow framework of what creativity should look like. Anything outside of their mental blueprint? Discarded. Labeled. Shut down.
And that’s where I draw the line.
Here’s the thing:
I welcome feedback. I embrace collaboration. I love when a client’s vision challenges me and we build something better together. But collaboration means mutual trust. It means I bring my experience, style, and eye to the table, not just my hands to execute. When the tone shifts to pure execution, without space for interpretation, without curiosity or dialogue… well, then I’m not the right person for the job anymore.
In this case, it wasn’t about budget. It wasn’t about hours or revisions.
It was about tone. About respect. About feeling reduced to a pair of hands and a timeline instead of a creative partner.
I had entered this project with genuine enthusiasm, even doing extra work behind the scenes, on my own time, because I believed in it. Because I saw potential in the idea and wanted to bring something extra to it. But that requires shared ownership. A meeting in the middle. And when it turns into a one-sided process, I step back. Not out of ego, but out of principle. Creative work is not a vending machine. You don’t insert budget, press a button, and receive an edit with extra sauce. You work together. You share ideas, you challenge each other, you trust the person behind the camera.
And when that trust isn’t there, or disappears halfway through…
That’s not a collaboration anymore.
It’s production.
And I didn't sign up for just production in this project.


