I’m Known for Saying No at Work. That’s a Good Thing.

I have a reputation at work for saying no. I’d rather give you an answer you don’t like than say yes to everything and become completely unreliable.

I have a reputation at work for saying no.

People who work with me know it. Bring me a new idea or ask me to take something on and there is a decent chance I’m going to ask a few questions before I agree.

Why are we doing this?

Does it actually need to happen?

What are we already doing that this would compete with?

And, occasionally: what happens if we just don’t?

Sometimes the request holds up. Sometimes it doesn’t.

Apparently I do this often enough that saying no has become something of a personality trait.

I’m okay with that.

I’d rather be the person who occasionally gives you an answer you don’t like than the person who says yes to everything and becomes completely unreliable.

Yes is cheap when you say it

Most requests at work don’t sound especially expensive.

“Can you take a look at this?”

“Can we add one more thing?”

“Could you have this done by Friday?”

None of those sound like major decisions. You’re standing there talking to somebody who needs something, and saying yes ends the conversation nicely.

So: sure.

Then you go back to your desk and remember everything else you already agreed to do.

The meeting needs prep. The document somebody wanted you to “look at” needs an actual review. The small task is connected to three other tasks. Friday was technically possible until you remembered what Thursday already looks like.

The person asking may not know any of that. They aren’t doing anything wrong by asking.

But you know what you already have on your plate.

That makes it your job to think about the cost before you commit.

I don’t think being helpful means saying yes

There are people who are incredibly easy to get a yes from.

They mean well. They want to help. They take your thing, somebody else’s thing, and four other things they already had.

Then the deadline gets close.

“Sorry, this week got crazy. Can I get it to you next week?”

Compare that with somebody who tells you up front:

“I can’t have that Friday. I can have it Tuesday.”

Tuesday may be annoying. Maybe you really did need it Friday.

But now you know.

You can work with Tuesday. You can change the scope. You can ask somebody else. You can decide the request isn’t worth pursuing.

What you don’t have to do is spend four days believing something is coming Friday when it isn’t.

That matters more to me than being agreeable in the moment.

A lot of workplace stress comes from treating “Can I technically make this happen?” as the deciding question.

You probably can make a lot of things happen.

Stay late. Move something else. Rush one task so you can squeeze in another. Answer messages at night. Half-ass something that deserved more time.

That doesn’t make the commitment a good one.

The question I care about more is what the yes costs.

If I take this on, what moves?

If nothing moves, what gets less attention?

And if I’m about to miss an existing commitment because I’m making a new one, the person I originally committed to should probably have some say in that.

This is one of the biggest reasons I say no as often as I do. New work does not arrive in empty space.

Saying no doesn’t mean refusing everything

I should probably clarify this because “Default: No” can sound like a philosophy designed for becoming the most irritating person in your office.

That isn’t the point.

Sometimes yes is obviously the right answer. The work matters, you have room for it, and the tradeoff makes sense.

Sometimes the original request doesn’t work but another version does.

“I can’t finish the whole thing today, but I can review the first section.”

“I can’t make Tuesday. Wednesday works.”

“I can do this, but the other deadline will need to move.”

Those answers are useful because they describe what you can actually do.

The alternative is saying yes first and sorting out what you meant by yes later.

That’s where things get stupid.

If I agree to something, I want the person asking to be able to treat that agreement as real. I don’t want them mentally adding an asterisk:

He said yes, but check again Thursday.

That is not a good reputation, even if you earned it by trying very hard to be helpful.

A good yes should mean something

One thing I’ve noticed from saying no more readily is that yes becomes easier too.

There is less hedging.

If I have looked at the request, considered what else I’m responsible for, and decided I can take it on, then I can just say yes.

And I mean yes.

Before agreeing to something new, I try to understand three things: what I’m actually being asked to do, what it will compete with, and whether I’m willing to make that trade.

It doesn’t need to become a fifteen-minute negotiation every time somebody asks for help. Most of these decisions take a few seconds.

But a few seconds is different from a reflex.

That small pause has saved me from a lot of commitments I would have regretted twenty minutes later.

So yes, I’m known for saying no at work.

That’s fine.

What I care about more is this: when I tell somebody I’ll do something, I want them to be able to plan on it.

I’m writing a book about this called Default: No, on the simple practice of protecting your time, energy, and attention.