Lrnon

Lesson 7 of 8 · 8 min read · last verified 2026-08-26

Learning to refuse

In this lesson you will:

  • Refuse a request in terms that do not invite negotiation
  • Recognise the pressures that make lines collapse

E6·L8 asked you to write down what you would refuse. This lesson is the part that actually decides whether that document matters: saying it, to a person, who wants something else.

Most lines do not fail because somebody forgot them. They fail because refusing was awkward at the moment it was needed.

How the request actually arrives

Not as a proposal to do something wrong. If it arrived that way it would be easy.

It arrives small — just this once, just a draft. Urgent — the deadline is tomorrow. From someone reasonable, who is not asking you to do anything they think is wrong. With the difficult part already assumed — “obviously we’d check it first” — where the checking is precisely the thing there is no time for. And framed as pragmatism, so objecting makes you the person slowing things down.

Under those conditions “no” feels disproportionate. That is what the framing is for, whether or not anyone intended it.

What a refusal that holds looks like

Refuse the act, not the person. “I’m not able to do that” rather than anything implying the asker is behaving badly. They usually have not thought it through, and giving them room to reconsider makes agreement far more likely.

Be specific. “I can’t put unverified figures in a document going to the board” beats “I’m not comfortable with this.” Comfort is negotiable and sounds like a preference. A specific reason is a fact about the work.

Offer the nearest thing you can do. “I can have the checked version by Thursday, or an unchecked draft clearly marked as unchecked.” This is what separates a refusal from an obstruction, and it usually resolves the situation entirely — most requests want the outcome, not the shortcut.

Do not over-explain. One reason. Several reasons sound like you are searching for one that will be accepted, and it invites the other person to argue with the weakest.

Write it down

If it matters, put it in a channel that persists. A short message confirming what was asked, what you said, and what you offered.

Not aggression — a record. A refusal in a searchable channel is a fact. A refusal in a corridor is a disagreement about what was said, six weeks later, when it matters.

This protects the other person as much as you. Frequently they are relaying pressure from somewhere else, and a written note is what they need to push back with.

When it does not stop there

Sometimes you refuse and it is asked again, or over your head.

Escalate on the substance. Not “X is asking me to do something wrong”, but “we have a request that needs a decision above me: unverified figures in board papers.” That is a question about process, which organisations can answer.

Find who owns it. Compliance, legal, a data protection officer, a safeguarding lead. Their job is to hold the line so it is not only you.

Know your own floor. Some things you decline regardless of the answer that comes back. E6·L8’s list. Deciding where that is beforehand is the entire reason for writing it down while nothing was at stake.

Refusing is a skill, and it improves

Worth saying, because the first one is genuinely hard and people conclude they are bad at it.

The first refusal is uncomfortable. The third is a normal conversation. People learn quickly what you will and will not do, and stop asking — which means most of the difficulty is concentrated at the start and then disappears.

The reputational effect is also the opposite of what people fear. Someone who occasionally says “not that one” is more trusted on everything else, precisely because their yes carries information.

Try it now (5 minutes)

Take one item from the rules you wrote in E6·L8. Write the actual sentence you would say — the act, the specific reason, the alternative.

Say it out loud once. That is not a silly exercise; it is the difference between having a position and being able to state one.

Check your understanding

1. Why do clear lines collapse in practice?
2. Which refusal is strongest?
3. Putting a refusal in writing is primarily:

Recap

Requests that cross your line arrive small, urgent and reasonable, which is why refusing feels excessive. Refuse the act rather than the person, give one specific reason, offer the nearest thing you can do, and put it in writing. Escalate on substance, know which items you decline regardless — and expect it to get much easier after the first time.

🗂 3 flashcards from this lesson join your daily review.

Previous: Automation and the people around you · Next: Your code of conduct