You know the moment.
A stakeholder pings you at 4:47pm on a Friday. They need “a quick deck” by Monday. Your team is already underwater. Two people are out. One is on their honeymoon. The brief hasn’t been written. The deck doesn’t exist. The data they want in the deck? Also doesn’t exist. The audience for the deck? Unclear. The deck’s purpose in the universe? A mystery rivaled only by Stonehenge.
And somehow, you’re the one who’s supposed to figure it out.
If you say yes, your team pays for it. If you say no, you become the person who “isn’t a team player” — which, in corporate speak, is one performance review away from “not a culture fit,” which is two performance reviews away from a very awkward calendar invite titled “Quick Chat.”
So you do what most creative ops leaders do. You type “let me see what I can do!” — exclamation point, because we’re being pleasant about it — and spend the weekend solving a problem you didn’t create, with a glass of wine in one hand and resentment in the other.
I’ve been there. More times than I want to admit. I’ve also been the person who responded at 11pm on a Sunday with a fully built deck just to prove a point. The point, by the way, was never received. Nobody noticed. Nobody said thank you. Monday morning the same stakeholder asked if I could “take another quick look.” Don’t be me.
Here’s what I’ve learned after 20 years of being the person in the middle: pushing back isn’t the problem. How you push back is.
Why “no” feels so loaded for ops people
Creative operations exists in the squishy space between strategy and execution. We don’t own the work, but we own the throughput. When something slips, we get asked why. When we ask why something is slipping, we’re told we’re being negative. When we flag risk early, we’re “blocking.” When we don’t flag it, we “should have seen this coming.” It’s a fun little trap. The walls are made of Slack messages.
That tension is the job. But it also means most of us learn — early — to absorb pressure instead of redirect it. We say yes to keep the peace, then quietly burn our teams out to keep the promise. Then we wonder why everyone keeps “exploring new opportunities” on LinkedIn at 9:14am on a Tuesday.
The trick isn’t getting better at saying no. It’s getting better at making the trade-offs visible so the no isn’t yours to carry alone.
Three moves that actually work
1. Replace “no” with “what would you like to deprioritize?”
This single reframe has saved me more late nights than I can count. When someone adds work, you’re not refusing — you’re asking them to choose. Most stakeholders genuinely don’t know what’s already on the team’s plate. They think we’re back here sipping lattes between Slack messages, doing crafts, vibing. We are not. We are holding fourteen plates and a Gantt chart.
Try this: “Happy to slot this in. We’re currently in flight on the Q4 launch and the partner decks. Which of those should we pause to make room?”
You’d be amazed how often the answer is “oh, never mind, next week is fine.” Funny how the urgency evaporates when there’s a price tag attached, isn’t it? Almost like it was never that urgent. Almost like we’ve been training people to throw work at us with no consequences. Almost.
2. Say yes to the goal, no to the timeline
A lot of “no” pushback isn’t about the work — it’s about the math. The work is fine. The timeline is fantasy. Specifically, the kind of fantasy that involves three people doing six people’s jobs, nobody sleeping, and a designer named Marcus quietly losing his will to live.
Separate them out loud: “We can absolutely do this. Monday isn’t realistic given current load, but we can deliver Wednesday EOD with the team you’ve got.”
Now you’re not blocking the request. You’re protecting the quality. You’re also being the only adult in the meeting, which — if we’re honest — is a part-time job none of us applied for but all of us got promoted into.
3. Put the receipts in writing
If a stakeholder is going to push you to commit to something risky, get it on paper. Not as a CYA move — as a clarity move. (Okay, fine, also as a CYA move. We’re grown. We’re allowed to have layers. Beyoncé has layers. So do we.)
A short follow-up email that says “confirming we’re moving X to fit in Y, with the risk that Z” forces everyone to look at the actual decision. This isn’t passive aggression. It’s good ops hygiene with a light spritz of self-preservation. Half the time, when people see the trade-off written out, they revise the ask. The other half, you have a paper trail and the moral high ground, which is honestly the best ground.
The bigger thing
The leaders I most admire aren’t the ones who say no the most. They’re the ones who make decisions easier for everyone around them. They surface trade-offs early. They name reality without drama. They protect their team without making the stakeholder feel like an enemy. They do all of this while drinking lukewarm coffee and pretending they’re not exhausted.
That’s the real skill. Not the no — the clarity underneath it.
You don’t need to be more assertive. You need to be more honest about what’s actually possible. And maybe stop ending every email with an exclamation point. (We’re working on it. Together. It’s a journey.)
Try this week →
The next time a request lands that you know is going to break something, don’t reach for “no.” Reach for one of these instead:
- “Happy to take it on — what should we deprioritize?”
- “Yes to the work. Can we revisit the timeline?”
- “Just confirming what I heard so we’re aligned…”
Use it once. See what happens. I promise the response will be better than the one you’re bracing for. And if it’s not? You’ve got receipts. And Marcus gets to go home on time. Marcus deserves that.