Chaos and Order

💡 왼쪽 원문을 읽으면서 오른쪽에 따라 써보세요. Tab 키로 힌트를 받을 수 있습니다.

Introduction
1. Work Flows by Cost of Asking, Not by Skill
2. The Point Where the Reward Turns Into a Penalty
3. Saying No Fails at the Position, Not the Wording
4. The Three Parts of a Decline
5. Priority Is Not Your Call to Make
6. Saying No Has Three Layers
7. When Declining Is Not Available
8. One Thing You Can Do Today
Where This Advice Does Not Apply
Closing
Further Reading

Introduction

When work piles up on one person, the people around them tend to say the same thing. It is because you are good at it. It sounds like consolation, and it is meant as consolation, but the explanation is not accurate. And an inaccurate explanation produces the wrong response.

If you explain the pile-up with skill, only two options remain. Keep being good and keep getting buried, or pretend to be bad and receive less. Both are bad options. But if the reason is not skill but the structure of distribution, a different option appears.

This is not a collection of sentences for declining. Situation-by-situation wording is already gathered in Workplace Phrases That Work. What this post covers is why those sentences land in some positions and not in others — the structure underneath the sentence.

1. Work Flows by Cost of Asking, Not by Skill

Think from the requester's side and the structure becomes visible immediately. Something urgent has come up, and there are three people who could take it. What does the requester use to choose?

Not skill alone. Three things are actually being calculated: the probability that this person will get it done, the amount of persuasion the ask will take, and the probability of being turned down. The last two weigh as much as the first. Because the requester is short on time too.

So requests flow along the path with the highest chance of success and the least friction. Someone who is good and also receptive is that path. Less goes to the person who is good but asks questions back and attaches conditions every time. Nothing risky goes to the person who is receptive but not good.

One important conclusion falls out here. Work piling up is not the result of an assessment of you; it is the result of the path through you being the cheapest one. If it were an assessment, it would be something to be pleased about. If it is a route, it is something to adjust. And routes can be adjusted.

The reason this distinction actually matters is emotional. Read the pile-up as an assessment and declining feels like a betrayal. Read it as distribution and declining is just a route adjustment. The same action, and completely different to carry out.

2. The Point Where the Reward Turns Into a Penalty

Up to here it is bearable. The problem is what comes next.

Capacity has a limit; requests do not. So if you keep accepting, quality drops at some point without fail. And what drops is not the newly accepted work but usually the work you were already holding. New requests come attached to a deadline and a requester watching; the work you were already doing has neither, or has them weakly.

That produces this sequence. You are good, so it piles up. It piles up, so you take it all. You take it all, so the original work slips. It slips, so your rating drops. The reward for being capable eats away at exactly the evidence for that capability.

There is a more uncomfortable point. The person who accepts everything gets filed inside the organization as someone who does a lot of work, not as someone who does important work. These are different boxes, and promotions and assignments happen out of the second one.

The reason is simple. Throughput belongs to no one in particular, while important work leaves a record of who held it. Between a quarter spent handling twenty small requests and a quarter spent finishing one hard problem, the one you can still explain to someone six months later is the second. This is not because organizations are unfair; it is because of how the record gets written.

And finally, the organization has no way of knowing you have reached your limit. If you do not say so, your capacity is assumed to be infinite. This is not coldness; it is an information problem. What is visible from outside is only the output, and what got ground down while the output was being produced is not visible at all.

3. Saying No Fails at the Position, Not the Wording

Most people think the difficulty of declining is a matter of delivery. So they look for good sentences. But there is a reason polishing the sentence does not help much. The position the decline occupies inside the conversation is wrong.

Decline like this and it fails. I am too busy right now, I do not think I can do it. At a glance this looks like a statement of fact, but it actually reads as a statement about your ability and your diligence. The other person can naturally push back. It should not take long. This is more urgent than the other thing. And to counter that pushback you have to prove how busy you are. A conversation that starts with the burden of proof already on you is a conversation you generally lose.

Put the decline as a question of resource allocation and the position changes. I am currently holding A and B, and their deadlines are these. To do the new C this week, either A or B moves to next week. Which one should I push back?

There is nothing in that sentence to argue with, because it makes no claim about ability. And because the decision has been handed over, the conversation becomes an allocation discussion rather than a negotiation.

The core is this. You say what you will put down instead, not what you cannot do.

4. The Three Parts of a Decline

Build the actual sentence in three parts and it generally holds up.

First, confirmation that you received the request accurately. This is not politeness; it is a function. What the requester fears most is their request vanishing, and an acknowledgment removes that fear up front. Without the acknowledgment, every sentence after it reads as avoidance.

Second, present your current load as fact. No adjectives, just items and deadlines. Instead of saying you are busy, write down what you agreed to do by when. This is where most declines collapse. The facts are not prepared, so you end up speaking in emotions.

Third, propose a trade. There are three forms. Order trade (what gets pushed back), timing trade (when you could start), scope trade (you cannot do all of it, but you can do up to here). Any one of them is enough.

As a constructed example, it looks like this.

Got the request. What I am holding right now is two things: the report due Thursday and the release prep for next Tuesday. If the new item goes in this week, the report moves to next week. If pushing the report is fine, I will start now; if not, I can pick it up from Wednesday next week. Which would you prefer?

There is no I cannot do it in that message. But it is a decline in practice. And if the other person really is in a hurry, they will let the report slip or find someone else. Either way, my load gets adjusted.

One caution. This format only works when you know exactly what you are holding. If the list lives only in your head, you cannot pull it out on the spot, and if you cannot pull it out you fall back to saying you are busy. The raw material of a decline is not attitude but a list.

5. Priority Is Not Your Call to Make

There is a more fundamental reason the format above works well. In most organizations, deciding what comes first is not the individual contributor's authority.

This gets forgotten constantly. Three requests come in, and the individual sets the order alone and absorbs the consequences alone. It looks conscientious, but what is really happening is that a decision outside your authority is being made on someone else's behalf, and you are also carrying the blame for when that decision turns out wrong.

Handing priority back is the act of returning that decision to where it belongs. The format is simple. Put two things side by side and ask which comes first. What matters here is not extracting an answer but leaving the question on the record. Even if no answer comes, the question remains, and the remaining question shows later, when the ordering blows up, that the judgment was not yours alone.

This method passes more often than a flat decline because it does not take away the other person's role. A decline looks like an act of judging their request; a priority question looks like an act of returning authority to them. The actual outcome is similar, and the way it is received is not.

6. Saying No Has Three Layers

This is where a lot of effort gets wasted, because people fight only in the conversation with the requester.

The first layer is the requester. This is where the sentence structure above operates. But even winning here, the same thing repeats next week. The requester is a different person each time, and each time you explain from scratch.

The second layer is your manager. This is the layer that actually has to change. If your manager knows your load, requests get filtered before they reach you. If not, they do not get filtered. So the real work is not declining individual requests well; it is making sure your manager always knows what you are holding and how much of it.

This is different from venting. Venting conveys a feeling about a state; a load report conveys a list. From the manager's side, there is no way to act on the first and there is a way to act on the second. Designing the information flow with your boss is covered in more detail in the post on managing up.

The third layer is yourself. And this layer is the hardest. A large share of the people who accept everything do so not because they lack the technique but because they are afraid of what kind of person they will look like if they decline. That fear is not solved by sentences.

There is one honest thing to say about it. The cost of one decline is usually smaller than expected, and the cost of continuing to accept is usually larger than expected. The first is felt immediately and the second surfaces over months, so the perception is distorted. Which is why it is better to trust the list than the perception.

7. When Declining Is Not Available

There are positions where none of this works. Organizations where attaching a condition to an instruction from above is itself an incident. In Korean organizations, a request that came down the gyeoljae line — the formal approval chain a decision travels through — is a completely different animal from a request from a neighboring team, and using the previous section's sentences on the first one can escalate into a question of attitude regardless of the content of the conversation.

What you can do in that position is not decline but record. It goes like this. You accept. And you leave a note of both the acceptance and what slips because of it.

I will start on what you asked today. Adding this means A, which was due this week, moves to Tuesday next week. I will proceed on that basis.

This is a notification, not a decline. But you get half the effect. First, the fact that the slip is the result of allocation and not of your laziness goes on the record. Second, if the other person does not want A delayed, an adjustment comes right there. Third, once a few of these records accumulate, the allocation itself sometimes shifts a little.

The principle in one sentence. If you do not have the authority to decline, you hand over ownership of the outcome along with it. Accepting everything while also carrying the responsibility for the outcome alone is the worst combination, and, remarkably, the most common one.

One thing has to be said honestly, though. This method does not change the situation. It only changes the trace the situation leaves on you. There are positions where that is enough, and positions where it is not.

8. One Thing You Can Do Today

Make one page. Everything you are currently holding, each item's deadline, and who asked for each one. That is all. Fifteen minutes is enough.

With this list, when the next request arrives you can answer with items instead of adjectives. Without it, no matter how good a sentence you memorized, all that comes out on the spot is that you are busy.

And if, while making this list, you were surprised at how many items there were, that surprise is already the answer. If it surprises you, your manager has no idea at all.

Where This Advice Does Not Apply

The early days and the onboarding stretch are different. In that period, accepting in order to learn really is the right move. Your load list does not carry credibility yet, and you have no basis for judging what counts as important work. It helps to put a time limit on that stretch, though. If accepting everything with no end date goes on long enough, it hardens into your default. The ordering of the first quarter is handled separately in The First 90 Days After a Move.

The same sentence does not produce the same result in every position. On probation, on an unstable contract, with residency status tied to employment, or as the only person on the team who can do that work, the real cost of declining is far higher. The methods in this post assume a position with some room to negotiate. If there is no room, the work in front of you is not declining but creating room.

There are organizations where declining does not change the distribution. If you build the list, hand priority back, and leave records for several quarters and the incoming volume is unchanged, that is not a problem of declining technique. It is the result of a decision not to fill headcount that is short, and it is not the kind of thing an individual's delivery can reverse. What is needed at that point is the calculation about leaving or staying.

And even using all of these methods, some organizations will read you as uncooperative. That risk does not disappear. It only shrinks. What this post can promise is not that declining becomes safe, but that when the grounds for declining rest on a list rather than on feelings, there is less room for misunderstanding. Posts that promise more than that are usually not being honest.

Finally, there is a failure in the opposite direction. Once you know the structure, you want to turn every request into an allocation problem, and then you become hard to work with. A rule applied without exception stops being a rule and becomes a personality. There have to be times when you just take it because it is urgent, or your ordinary declines never earn trust.

Closing

The goal is not to become good at declining. The goal is a state where what you are holding is visible to you and to everyone else. In that state, declining is not a separate skill but an act of reading a list.

And the order, restated, is this. Build the list. Make it visible to your manager. When a request comes, talk about order rather than ability. Setting the order is not your authority, so hand it back. Where you cannot hand it back, accept, but pass the outcome along with it.

Not one of these steps requires a way with words.