The One Where I Said No

I’m sitting in Martin’s office on a Tuesday at 2:47 p.m., and I can feel the yes forming in my chest like a muscle memory, like my body remembers how to say it before my brain catches up.

Martin is the VP of Product. He’s two levels above me. He’s leaning back in his chair the way people do when they’re about to ask you something they’ve already decided you’re going to do, and he’s talking about how much he values my “can-do mentality” and how he knows “if anyone can handle this, it’s you.”

The thing he’s asking me to handle is: absorb the entire backlog of the Analytics team, who just lost both their senior engineers to a startup that sells cryptocurrency to people who definitely should not own cryptocurrency. “Just until we backfill,” he says. “Probably three months, maybe four. Your team’s crushing it right now anyway.”

My team is not crushing it. My team is exactly at capacity. Dex is still on sprint four of the “almost done” refactor. Marcus submitted a PR yesterday with an apology in every single comment, like he was sorry for the oxygen he was using. Priya has already texted me twice about considering her options.

But here’s what happens in my head in the three seconds between Martin finishing his pitch and me opening my mouth: I think about how saying yes has always worked out. I think about how refusing might make me look like I’m not a team player. I think about how this is a vote of confidence, and votes of confidence are currency. And then, and this is the part where I actually feel something shift, I remember Saturday.

Last Saturday I was supposed to have eight hours to myself. Eight hours I’d blocked off a month in advance, physical blocks on my calendar with little notes like “MINE” and several bass-related emojis because The Merge Conflicts had finally—finally—scheduled an actual rehearsal. We were going to finish the arrangement on “Recursive Blue” that we’ve been workshopping for eighteen months. And at 9 a.m. I got a message from Martin asking if I could jump on a quick call about a “small deployment issue.”

(For context: “Recursive Blue” is a song we have been “finishing” since a presidential administration ago. At this point it is less a song and more a long-term group therapy project that occasionally has a bassline.)

The small deployment issue became three hours. By noon, that eight-hour window was a four-hour window. By 2 p.m., I texted the band and said I’d be late. By 5 p.m., I didn’t go at all.

That was a yes I shouldn’t have given. And the thing that kills me is that the deployment issue? It would have waited. Martin would have figured it out, or someone else would have, or it would have held until Monday. I’d actually told him four times before the call that we could handle it Monday morning. But I said yes anyway because saying yes is the path of least resistance, and I’ve been walking that path so long I don’t even notice the ground anymore.

So I’m looking at Martin, and I’m feeling the yes rising, and instead of letting it out, I do something I don’t normally do: I pause.

“That’s a big ask,” I say. “Let me do some math.”

Martin looks surprised. He’s probably not used to being paused on. “Sure. Take your time.”

I don’t actually take my time. I just do the math right there in his office, out loud, the way I should have done on Saturday or a month ago when Yusuf wanted to rewrite the entire stack because he’d read a conference talk.

“We’ve got the core roadmap—that’s twelve weeks of committed work for twenty people. The analytics backlog is, what, maybe thirty tickets? If I pull four devs off the roadmap to handle that—” I’m watching myself do this, like I’m standing next to myself watching someone I know finally get something obvious—”we miss the Q2 release by six weeks minimum.”

Martin nods slowly. He’s not defensive. He’s listening.

“But here’s what we could do,” I say, and this is the part I’m surprised to hear coming out of my own mouth. “If the roadmap timeline moved—if we compressed the Q2 release by two weeks and moved some lower-priority work to Q3—I could have three people on the analytics backlog without drowning the core work. Or, if the timeline stays locked, I could absorb maybe fifteen of the analytics tickets now, the ones that are blocking other things, and handle the rest when you hire the replacement engineers.”

“Okay,” Martin says. He’s not angry. He’s not even disappointed. He’s just nodding. “Let me check with Product on the timeline. I’ll get back to you.”

That’s it. No argument. No “well, I was really hoping” or passive-aggressive follow-up email. He said okay.

The next day he emails me and says we’re going with option two: we’ll take the fifteen high-priority analytics tickets, and the executive team is going to accelerate the backfill search because apparently they have to if they want the core roadmap done.

And here’s the thing that actually matters: nothing explodes. The company doesn’t collapse. Martin doesn’t ice me out. I just got the thing I actually wanted—which was not to absorb the entire analytics backlog while still shipping the roadmap—and I got it by doing something my anxiety told me would be catastrophic.

At 4:30 p.m., I open our band chat, and before my brain can suggest a backup plan or a maybe-we-could-do-Sunday instead, I write and send it.

I’m closing Cyberpunk on Saturday. We’re finishing “Recursive Blue.”

My mistake wasn’t that I said no. My mistake was that I almost didn’t. I almost did what I’ve done a hundred times: opened my mouth, felt the path of least resistance, and walked it straight off a cliff. The difference this time was pausing for thirty seconds and doing the actual math out loud, which made it impossible to pretend the yes wouldn’t cost something. And once I couldn’t pretend anymore, I realized that a specific no with a concrete alternative isn’t rude—it’s professional.

If you freelance, you’ve had my exact conversation, just with a client instead of a VP. They email and ask if you can “squeeze in” one more project, or expand the scope, or start earlier, and you feel that same reflex: say yes, be the person who doesn’t cause problems, eat the lunch break or the Saturday. But here’s what I learned: a client who’s worth keeping respects a clear no more than a resentful yes. They don’t want you burned out and cutting corners on their work. They want to know where they actually stand with you. And a no that comes with a specific alternative—”I can’t do the full scope by then, but I could do X by Y date, or do everything but Z”—reads as professional, not difficult. It reads like you’ve thought about it.

“A client who’s worth keeping respects a clear no more than a resentful yes.”

This week, I want you to find one place where you’ve been saying yes automatically. Not a place where you need to say no forever—just one thing. And instead of saying yes on the spot, pause. Do the quick math. Say something like “let me look at my current work and get back to you tomorrow.” Then figure out what you can actually deliver, what the trade-off is, and come back with a specific offer. “I can’t take this on before X date, but I could start then” or “I can do this but not that” or “yes to the core work, but the extra features would need to be phase two.” You’ll be amazed how often the person on the other end just says okay.