필사 모드: Asking and Saying No in Office English: Say It in Priorities, Not in "I Cannot"

Introduction: it is not that you lack the phrases

You know I can't. You know Sorry, I'm busy. And yet after refusing something in English there is a strange aftertaste. The other person does not seem convinced, and a few days later the same request comes back. Or the opposite happens: you set out to refuse, end up saying yes, and spend the weekend on it.

The cause is not vocabulary. It is that the grammar of refusal is different.

In Korean workplaces, refusal is mostly done in the language of relationships. You apologise, you say it is difficult, and the other person reads between the lines. In English-speaking workplaces, refusal is mostly done in the language of priorities. You say what is stopping you, when it would be possible instead, and whose decision this actually is.

Without that difference, no amount of politeness makes your refusal arrive as a refusal. With the structure in hand, a handful of phrases is enough to close things cleanly.

This article covers asking and refusing as one set, because in practice they are the front and back of the same structure.

The core: a sentence about the world instead of a sentence about me

Compare two refusals that land in completely different places.

The top three are all statements about me. Statements about me can be argued with. The other person may think you have misjudged it, so they try persuasion.

The bottom two are statements about the world. The migration slipping is not a matter of my willingness, it is a fact. It cannot be argued with. Instead, the other person has to make a choice — and that choice was theirs to begin with.

Someone who refuses well is not someone who refuses hard, but someone who hands the decision back to the person it belongs to.

There is an honesty condition attached. This works because you are naming a real constraint. Inventing a constraint because you do not feel like doing something is not a prettier refusal, it is a lie. Two or three times and you are found out, and after that nobody believes your real constraints either.

The three-part structure of a refusal

A good refusal almost always has three pieces.

Part 1, acknowledge. Briefly confirm that the request is legitimate. This is closer to an acknowledgement of receipt than to agreement.

Part 2, state the constraint as a fact. Say concretely what is in the way right now.

Part 3, give options. An alternative, a condition, or a request for a decision.

That's a fair ask, and I get why the demo needs it.    ← part 1: acknowledge
I've got the payments migration and on-call this week. ← part 2: constraint
I can either do a rough version Thursday,
or a proper one Tuesday. Which is more useful?         ← part 3: options

A bad refusal usually has only part 2. I'm busy this week on its own has no acknowledgement and no options, so from the other side there is no information beyond a closed door.

Conversely, parts 1 and 3 without part 2 is not a refusal at all — it is a vague yes. You need all three.

The four pieces of a request

It makes sense to sort out the asking side before the refusing side, because a well-built request also makes refusal easy.

First, what. It has to be a concrete action. Not help with payments but review the payments spec.

Second, by when. A request with no date is not a request, it is a wish. There is no way for the other person to prioritise it.

Third, why. One line is enough. With a reason, the other person can judge honestly, and you stop labelling non-urgent things urgent.

Fourth, an exit. One sentence that explicitly opens a route to refusal. With it, the other person does not force a yes, which is exactly why the promise holds.

Do you have bandwidth? is extremely common at American tech companies and asks whether someone has spare capacity. capacity is used the same way. Both are close to industry jargon, though, so outside tech or with colleagues who are not native speakers, Do you have time for this this week? is safer.

The exit sentences are worth collecting separately.

One honest warning. Attach No rush or whenever you get a chance and that task very probably will not happen. Use it only when it genuinely is not urgent. If you need it Friday, say Friday. Asking softly and then getting annoyed later is far worse than naming the date up front.

When you have to ask urgently

The last two are far stronger than the first four. The reason is simple. An adjective like urgent is information about my feelings; what is being blocked is information about the world. It's urgent can be argued with; the release is blocked cannot.

It is exactly the same principle as refusing. Asking or refusing, the strong sentence is not a sentence about me but a sentence about consequences.

The conditional yes: the most useful answer there is

What you most often need in practice is neither a full yes nor a full no.

The conditional yes is strong for two reasons. First, you remain someone who cooperates. Second, the other person gets a real choice. A rough Thursday version turns out to be enough more often than you would think.

The honesty condition applies here too. The condition has to be a real condition. Attach one you cannot keep just to soften the refusal, and when the other person meets it you have nowhere left to go.

When pushing a deadline, negotiate scope, not the date

This may be the most practical part of the article.

Deadline conversations usually go like this. "Friday is difficult." "Why?" "There is a lot on." "Could you not just push a bit harder?" You have already lost. Fight over the date and it becomes a contest of will, and in a contest of will the person asking wins.

Negotiate scope instead of the date. Talk about what you can deliver on that same Friday, and it stops being a contest of will and becomes a design conversation.

Ask Is this a hard deadline or a target? even once and you will often be surprised. A large share of deadlines are attached to nothing. Very often it is just a date somebody said in a meeting. Asking is not rude at all; if anything it reads as taking the schedule seriously.

Your call. is short and powerful. It means the decision is yours, and it is natural in both American and British usage. Put two options down and close with it, and the conversation resolves there.

When you have to refuse outright

I'm going to pass on this one is very common in American workplaces and is a neutral refusal with no feeling loaded into it. It is especially comfortable between peers.

I'm not the right person for this is a refusal and a help at the same time. Attach a name and the other person's problem is actually solved, so it costs the relationship almost nothing.

That's not going to work for me is strong, and use it knowing that. It is worth saving for when you really do need to draw a line.

And one point about apologising. Repeating apologies inside a refusal reads as a signal to reopen the negotiation. A run of I'm so sorry, I'm really sorry, I feel terrible tells the other person you are wavering, so they push once more. Acknowledge once, give the reason once, done. This is easier on them as well.

What changes when it is your manager

Everything so far assumed peers. Here is what changes when the other person is your manager.

First, what does not change. The principle of using the language of priorities is unchanged. If anything, managers respond to it better, because setting priorities is literally their job. Say I can't to a manager and an assessment of your ability starts; say "if I take this, that slips" and it becomes something for the manager to handle.

Two things do change. First, it is natural to reshape the refusal into a check-in. Rather than deciding yourself, you put the material for the judgement up and ask for the decision. Second, coming with a finished alternative is expected. Raise only the problem and it looks half done.

The first sentence is the heart of this table. What should I drop to make room? is a yes, not a refusal, and yet it functions as a perfect refusal. It keeps you cooperative while reminding everyone that the total is fixed.

The fourth is worth remembering too. It explicitly frames the act of raising bad news early, and most managers take it well. That said, the temperature varies by organisation. Some teams value early warnings highly; others want only confirmed facts brought upward. Watch your manager a few times and you will know which kind you have.

Escalation is not tattling

In Korean organisational culture, taking something upward is often read negatively. So when two people both demand this week, you end up carrying it alone and delivering both late.

In English-speaking workplaces the baseline definition of escalation is different. A priority conflict has to be resolved by whoever owns those priorities, and escalation is handing it back to that person. Making a decision that is outside your authority, by yourself, is the actual problem.

Can you two agree on the order and let me know? is especially good. It returns the conflict precisely to where the conflict arose, and leaves you as the person who executes.

One thing not to do is send complaints about people upward along with it. Send facts and options only. "A and B both want this week" is a fact; "A always makes unreasonable demands" is an evaluation. The moment you mix in the evaluation, this stops being a priority problem and becomes an interpersonal one, which is much harder to handle.

For what it is worth, the temperature of the word escalate itself varies by company. Some use it as a neutral process term; others hear it as "making a big thing of it." When in doubt, skip the word and describe the action: Can we get a decision on this?

When you are the one being refused

The last question is the most valuable in practice. A refusal is usually information about that person's schedule, not an answer to your problem, and the person refusing usually knows who could do it.

That's fair is a useful sentence you can use without being fully convinced. It carries the weight of "I can see it that way" rather than "you are right."

Things better left undone

Refusing with I will try. This is the most expensive mistake in this article. Korean "해볼게요" is, depending on context, a soft refusal, but English I'll try sounds like a promise to attempt it. The other person puts it in the plan, and if it does not happen you have broken a promise. Use it if you really intend to try; do not use it as a refusal.

Refusing with It's difficult. The same trap in another version. In Korean and Japanese business usage "어렵습니다" is a refusal, but English It's difficult means hard but possible. So an English-speaking counterpart hears it and starts looking for ways to help you. You get exactly the opposite result.

Refusing with silence or Maybe. No answer is mostly read as still under consideration. A refusal has to be spoken to arrive.

Using I'm busy as the reason. It is a sentence with no information in it. Everybody is busy. What is informative is what you are busy with, and therefore what would slip.

Saying yes for the sake of peace. The most expensive refusal there is. A yes given to buy five seconds of comfort now wrecks other people's schedules two weeks later. The trust lost at that point is not comparable to the cost of refusing at the start.

Using Sorry to bother you as the prefix to every request. Attach it every time and you define your own requests as an imposition. Use it only when the timing genuinely is an interruption.

Writing ASAP and no date. The same class of mistake, committed by the asking side. The recipient cannot prioritise it, and in the end everyone interprets it differently.

A worked example: a request that lands mid-sprint

PM:   Hey, could you build a quick dashboard for the board demo?
      We'd need it by Friday.

Me:   That makes sense for the demo — I get why you need it.
Me:   Right now I've got the payments migration and I'm on-call this week.
Me:   If I pick the dashboard up, the migration slips to next week.

PM:   Hmm. How long would the dashboard take?

Me:   Depends what's in it. Is Friday a hard deadline or a target?
PM:   Hard — the board meets Friday afternoon.

Me:   Okay. Two options.
Me:   I can do a rough one with the three main numbers by Thursday,
Me:   or a proper one with filters by Tuesday next week.
PM:   The three numbers would probably be enough.

Me:   Then yes, I can do that — as long as the migration moving to
Me:   next week is okay with you and Sujin.
PM:   Let me check with her.

Me:   I don't think this is my call to make, so that works.
Me:   Whichever you two decide, I'll start Wednesday morning.

Look at what actually happened: a refusal never appears, and the original schedule survives. All that happened was acknowledging, stating the constraint as a fact, checking what kind of deadline it was, negotiating scope, and handing the priority decision back to its owner.

Try this today

1. The base form of a refusal: If I pick this up, X slips to next week.
2. The deadline question: Is Friday a hard deadline or a target?
3. The conditional yes: I can do a rough version Thursday, or a proper one Tuesday.
4. Handing the decision over: I don't think this is my call to make.

Four sentences close most situations. Refusing well does not mean speaking forcefully; it means giving the other person enough information to decide.

Read next

• Speaking up in English meetings — the previous article. The signals for taking the floor and the four-step structure.
• Office English in email and chat — the next article. The same requests and refusals, in writing.
• Persuasion lab — trains the difference between a real objection and a clash of interests, through scenarios.
• Conversation practice — practises the gap between a refusal with an alternative and a vague yes.