Setting Boundaries and Saying No: Four Scripts

You didn't say yes. You just didn't say no.

Someone asks for something. There's a small pause where you're supposed to answer, and in that pause you can feel yourself not having a sentence ready.

So you say "yeah, sure, no worries" — and then spend the next four days resenting it.

The problem isn't that you lack the nerve. It's that "no" has no default form. "Yes" does — it's one word, it's socially frictionless, and it's already loaded. No has to be constructed on the spot, under mild social pressure, by someone who'd quite like to be liked. Nobody wins that.

The fix isn't confidence. It's having the sentence before you need it. Four of them, actually, because there are four different situations and using the wrong one is most of why saying no goes badly.

The structure: four scripts

1. The plain no — when the answer is no and you know it

Three parts, in this order, and no fourth part:

Warmth · No · Nothing.

"Ah, I'd love to — I can't this time."

That's the whole thing. The reason people fail here is the fourth part they add: the explanation.

Explaining converts your no into an argument, and arguments have counter-arguments. "I can't, I've got so much on this week" invites "it'd only take an hour." Now you're negotiating about your schedule instead of having declined.

One sentence of reason is a courtesy. Three is a negotiating position.

If they push, don't invent a new reason. Repeat the same one, in fewer words. That's the broken-record move, and it works because there's nothing to argue with.

2. The delayed no — when you're not sure and the pause is doing the damage

Most bad yeses happen because a decision got demanded at the speed of conversation.

"Let me check and come back to you tonight."

That's it. You have bought yourself the thing that was missing: time to answer as the version of you who isn't standing in front of them.

Two rules make this work rather than becoming avoidance:

• Name when. "Tonight", "by Thursday". Unbounded delay is just a slower yes.
• Actually come back. If you go quiet, next time they'll press for an answer on the spot — and they'll be right to.

3. The partial yes — when you want to help but not on those terms

The most useful of the four, and the least used. You're not choosing between yes and no; you're choosing what you're actually willing to do.

"I can't take the whole thing on. I could look at the first section on Sunday."

"I can't lend you that much. I can do fifty."

"I can't make Saturday. I could do an hour on Sunday morning."

The shape is always the same: decline the ask · offer the specific smaller thing you'd genuinely do.

The trap is over-offering to soften the no. If you don't actually want to do the smaller thing, this isn't a partial yes — it's a full yes with extra steps, and you'll resent it identically. Only offer what you'd be content to be held to.

4. The standing no — when it's a pattern, not a request

When it's the fourth time, you're not answering a request any more. You're changing a rule, and that needs different language: name the pattern, state the rule, once.

"I've covered the last three weekends. I'm not going to be able to keep doing that — I need to stop being the default for weekends."

Two things this does that a plain no can't: it makes the pattern visible (often they genuinely hadn't counted), and it sets an expectation forward rather than declining a single instance.

Expect this one to be uncomfortable and to need repeating. You're not turning down a request, you're renegotiating a norm — and norms have inertia. The first time you hold it is the only hard one.

Why this works

1. Prepared beats brave. The reason no fails isn't fear, it's the blank pause where a sentence should be. Having four ready removes the moment where you improvise badly.

2. Reasons invite negotiation; the decision doesn't. "I can't" is a decision. "I can't because X" is a claim about X, and X can be disputed. The less surface you offer, the less there is to argue with.

3. Matching the script to the situation is most of it. A plain no to a genuine emergency reads as cold. A partial yes to something you'll never do is a lie with a deadline. Most "I'm bad at boundaries" is actually using script 1 where script 3 belonged.

4. Standing nos change the future. Declining once resets nothing. Naming the pattern is the only version that stops you having the same conversation next month.

Patterns

The work no is worth memorising: "I can't take that on without dropping something else — which should it be?" It isn't a refusal, it's a prioritisation question, and it moves the decision to the person who owns the priorities. Very hard to argue with, and it makes your workload visible without complaint.

Delete these:

• "I'm so sorry, but…" — apologising frames your no as a wrong you're committing.
• "I'll try." — heard as yes, remembered as a promise, and it's how you end up doing it anyway.
• "Maybe next time?" offered reflexively — you've just scheduled the same conversation again.

When it doesn't work

• When you genuinely owe them. Sometimes the answer is yes because it's your turn. A boundary script isn't a tool for never being inconvenienced.
• When there's a real power gap. "No" to someone who controls your income has costs a script doesn't remove. Script 3 (partial yes) and the work prioritisation question are the usable ones there; the plain no often isn't.
• When you use it to avoid every discomfort. Boundaries protect capacity you then spend on something. If the no isn't in service of anything, it's just withdrawal.
• When the relationship needs the conversation, not the sentence. A single well-delivered no doesn't fix a friendship where the imbalance has been building for a year. That's SO-09.
• When someone frightens or coerces you. Not a scripts problem. Talk to someone you trust, or a professional.

The rehearsal protocol

Stage 1 — Written (10 min)

Write all four, in your own words, for requests you actually get:

PLAIN NO      : ..................................................
                (does it have more than one sentence of reason? cut it)

DELAYED NO    : ..................................................
                (does it name WHEN? if not, it's a slow yes)

PARTIAL YES   : ..................................................
                (would you be happy to be held to the smaller thing?)

STANDING NO   : ..................................................
                (does it name the pattern, or just this instance?)

Read each aloud. Anything that sounds like a customer-service reply gets rewritten.

Stage 2 — Rehearse against an AI (15 min)

Full setup: SO-22.

We're going to run a roleplay rehearsal.

YOU ARE: [who — e.g. "a friend who asks me to cover their shift most
weeks and is very likeable about it"]
THEIR SIDE: [why they think this is reasonable, in their voice]
I AM: saying no.

RULES
- Stay in character, dialogue only, no brackets, human-length replies.
- Difficulty 4/5: don't accept the first no. Push back twice — once
  with warmth ("go on, it'd really help me out"), once with a reason
  that makes it awkward to refuse.
- Don't be cruel. Persistent, not nasty.
- Stay in character until I type END REHEARSAL.

WHEN I TYPE "END REHEARSAL":
1. Quote my first no. How many reasons did I give?
2. Did I add a new reason when you pushed, or repeat the same one?
3. Did I apologise? Quote it.
4. Did I offer something I probably don't want to do?
5. Write a shorter version of my no.

Be blunt. Reply only "ready" and wait.

Watch for the new-reason move. Under pressure almost everyone invents a second justification — and each new reason is a fresh thing for them to solve. Holding one reason feels rude and isn't.

Stage 3 — Low-stakes real (this week)

Use the plain no on something trivial where the cost of a bad no is nearly zero: a free trial, a survey, an extra item at a counter, a group chat plan you don't want.

"No thanks" as a complete sentence, with nothing after it. That's the rep.

Exercise (30 min, verifiable output)

1. List the four requests you most often say yes to and regret. Real ones, with names.
2. Assign each the script that actually fits — most people discover they've been using script 1 where script 3 belonged.
3. Write all four scripts in your own words. Read them aloud; rewrite anything stilted.
4. Audit each: plain no under one reason? delayed no naming a time? partial yes you'd honour? standing no naming the pattern?
5. Run the SO-22 rehearsal at difficulty 4.
6. Use one for real this week and write two sentences on what happened.

✅ Finish check: four written scripts, a rehearsal transcript, and one real use with its outcome.

Summary card

• No has no default form — that's why it fails. Have the sentence before you need it.
• Plain no: warmth · no · nothing. One sentence of reason is a courtesy; three is a negotiating position.
• Delayed no: "let me check and come back to you tonight" — must name when, must actually return.
• Partial yes: decline the ask, offer the specific smaller thing — only if you'd honour it.
• Standing no: for patterns, not requests. Name the pattern, state the rule forward.
• When pushed, repeat the same reason — don't invent a new one. New reasons are new things to argue with.
• Work: "I can't take that on without dropping something else — which should it be?"
• Delete "I'm so sorry, but…", "I'll try", and reflexive "maybe next time?"
• Most boundary failures are using the wrong script, not lacking nerve.

Sources

1. Ury, W. — The Power of a Positive No, 2007
2. Smith, M. — When I Say No, I Feel Guilty, 1975 (broken-record technique)
3. Fisher, R. & Ury, W. — Getting to Yes, 1981

Next lesson: SO-09 — How to Open a Hard Conversation (L2) Related: SO-03 Active Listening · SO-13 The Anatomy of an Apology · SO-11 Negotiation · SO-22 Rehearsing with AI Path: Handling Conflict — 2/6 · Protecting Yourself — 4/6