"I don't really feel like it" is not a no

At work I have been able to say no for years. My boss asks whether I can still take that on by Monday, and I say what will be left lying around if I do. In private I am a specialist in the opposite. Someone suggests something, and I say: I don’t really feel like it. The second time: no, I genuinely don’t enjoy that. The third time I say, all right, let me see whether we can make it work somehow. That is not friendliness. That is a no I broke myself in the first sentence.

Last week I worked with a communication trainer who has spent years practising difficult conversations with managers. Her point landed with me: people rarely react to the word no. They react to what they suspect sits behind it. And if you offer them a loophole, they take it. Don’t be surprised when the other person turns your no into a yes, she says. You handed them the invitation.

The most common hedges

Hedges are words that soften the core of a statement without you noticing. You mean them as courtesy; they arrive as negotiating room. The tricky part is the asymmetry: you remember your sentence, the other person remembers the word that suited them.

What you say	What arrives	What actually carries
I don’t really have time	So there is an exception	I have no capacity for that this week
I’ll try	He has agreed	I won’t get that done by Friday
I’ll do my best	He has agreed and he is motivated	I’ll take the analysis, the proposal stays where it is
Maybe I can manage it	He didn’t say no	No, I’m not taking that on
I’ll see what I can do	He is on it	I’ll come back to you Thursday with an answer

The most expensive sentence in that table is “I’ll try”. It sounds like a commitment and is not one. Whoever hears it plans around you. Whoever says it has committed to nothing. Two people leave the same conversation with two different pictures, and when it goes wrong, formally nobody lied.

The conditional is not politeness

“I would suggest.” “I’d like to invite you.” “Could you maybe take a look at some point.” In our speech culture that counts as considerate. She disagrees: the conditional is not a form of politeness, it is a form of indecision. “I’d like to invite you” becomes “I’m inviting you”, and the sentence loses none of its warmth.

There is one exception. The conditional is right when it describes a real condition rather than your uncertainty. “If we push the proposal to next week, the analysis is doable by Friday” is a clean sentence. It names a trade. Nothing is watered down.

Hedging is rarely a courage problem

Here I see it differently. Her diagnosis is that many people have too little commitment and too little courage for a clear no. In coaching I rarely saw it that way. What is missing is usually not the courage, but the cover.

Look at the replacement sentence she uses instead of a bare no: “I can’t take that on this week, because I have already committed to three other things.” The sentence only works if you can name those three other things on the spot. If you can’t, you lose the conversation at the first follow-up question. That is exactly where “actually” comes from: it is the linguistic form of “I didn’t have the overview just now”.

That is why saying no is easy for me at work and hard at home. At work I have a project list, context lists and a calendar that holds only what genuinely has to happen on that day. In private, a lot of it runs past all of that. Cut the hedges without the overview behind them and you don’t get a better no, only a harder one that holds just as poorly.

In practice that means: before you answer, thirty seconds on the project list. Then you don’t say “I have a lot on”, a sentence nobody can hear any more, you name two commitments and a date. That is checkable, and checkability is the difference between a boundary and an excuse. How to defend your own day against exactly these requests is in your plan for the day survives until quarter past ten.

Separate fact from interpretation

“You keep giving me extra work” is an invitation to disagree. The other person will defend themselves, and from then on the two of you are talking about your relationship instead of the work. Priorities are never decided on the relationship level.

The fact-based version: “Over the past week I received three additional tasks on top of what was planned. How do you want to handle it? What can I take, what do we move?” That cannot be disputed, because nothing is being interpreted. Complaint mode (“more again, how am I supposed to manage all this”) reliably produces resistance, even when the complaint is justified.

When your no is not accepted

The sentence that follows is almost always: but it still has to work somehow. At that point don’t cave, and don’t get harder either — ask. What makes Monday so important? The nicest example of this comes from her own practice: the answer was “because I’m on holiday from Tuesday”. A piece of information you did not have before, and it changes the entire conversation. Suddenly it is no longer about everything by Monday, but about the part he needs before he leaves.

A no does not need a counter-offer. It needs a continuation. Whoever says “let’s talk about the order of things” has created an open loop, and open loops without a date die. That sentence belongs on your waiting-for list or in your day as a next action while you are still in the conversation, otherwise your no is a yes again in three days, only this time without the negotiation.

The rescuer reflex

“Could you take the difficult client call for me, you’re so much better at those.” You feel flattered, you say yes, and the work has been rerouted. She suggests three steps: show understanding (“I understand that the conversation feels unpleasant”), set the boundary (“I won’t take it over for you”), offer development (“sit in on one of my calls, and afterwards we’ll talk about it if you’re interested in my view”).

That offer has a useful side effect: it separates two requests that sound the same. Whoever genuinely wants support takes it. Whoever wanted to offload suddenly has no time to learn. A quick yes would have prevented that distinction and taught the colleague that it works again next time.

Where this typically fails

You cut the words without having the list. The no sounds firm until someone asks what is actually on your plate. Without nameable commitments it collapses at exactly that point.

You say no too quickly and don’t ask. Clarity without curiosity is defensiveness. Asking why costs two sentences and often delivers the information that dissolves the problem.

You transfer spoken sentences one to one into writing. In an email the tone is missing that keeps your no friendly in person. One line of appreciation, one sentence of fact, one question. No justification spiral that leaves the recipient looking for leverage.

You negotiate and write nothing down. “We’ll talk about prioritisation again” with no date and no entry has vanished into the universe.

You teach the other person that pushing works. Whoever gets a yes on the fourth attempt has learned that asking four times is enough. That is no longer a communication problem, it is a pattern you installed yourself.

Common questions

What is hedging language?

Hedges are words that weaken a clear statement without changing its content. Typical examples are “actually”, “maybe”, “I’ll try” and “I’ll do my best”. They are meant as courtesy, but they arrive as negotiating room and reliably turn a no into a maybe.

How do I say no without sounding rude?

In three movements: acknowledge the other person’s request, state your position without hedges, keep the conversation open. “I understand this is pressing. I have no capacity for it this week, because the analysis and the proposal are already committed. If one of those can wait, let’s talk about the order.” The friendliness sits in the acknowledgement and the offer, not in the softness of the wording.

What do I do when my no is not accepted?

Don’t repeat it and don’t cave — ask what makes the deadline so important for the other person. The answer usually contains information you did not have before and turns a demand into a solvable problem. You are not giving up your boundary, you are only moving the conversation from the commitment to the priorities.

Isn’t the conditional simply polite?

No, in most cases it signals indecision rather than respect. “I’d like to invite you” and “I’m inviting you” are equally polite; only the second one is a decision. The conditional is justified when it expresses a real condition, for instance which trade would make a commitment possible.

How do I turn down a colleague who wants to hand me their task?

Say clearly that you are not taking the task on, and offer support with doing it themselves instead — sitting in on a conversation, and a debrief afterwards. That combination separates the two requests that sound alike: whoever really wants to get better takes the offer, whoever only wanted to hand it off has no time for it.

---

An observation task for the next seven days: open your sent folder and search for “actually”, “maybe”, “I’ll try” and “I’ll see”. In Gmail that is in:sent actually, in Outlook the search box in “Sent Items”. Go through the hits from the last four weeks and mark the ones where you really meant no. At the end you will know whether you have a wording problem or a list problem.

The words are one thing, the overview behind them another. If you want to go through both against your real commitments, sparring is the place for it. Write to me.