“No Worries If You Can’t” — Why Saying No Can Feel So Hard

Office, before a Friday client meeting. Maja is at her laptop when a message from Nia pops up.

— Maja, could you take over my demo on Friday? Totally fine if not — I have a plan B.
— I’m really sorry, but I genuinely can’t do Friday…

Nia switches to plan B without a problem. Maja keeps wondering whether saying no really was consequence-free.

What really happened

Nia genuinely gives Maja the option to decline. She has a backup plan and does not see “no” as a problem. Maja, however, is not evaluating only the words in the request. She is also thinking about the relationship: if Nia asked her specifically, perhaps she is really counting on her; if Maja says no, perhaps she will let Nia down or leave her with a problem. Nia therefore sees a simple question with two acceptable answers, while Maja sees a question in which one of the answers may carry a social cost. That distinction matters: freedom to refuse can exist formally without feeling equally available to everyone. Maja’s profile makes this reaction especially plausible, but the mechanism itself is very common.

What the research says

Research shows that people asking for help often underestimate how hard it can be for the other person to say no. A request triggers more than a calculation of time or effort; it can also raise concerns about awkwardness, disappointing someone, or appearing unhelpful. In experiments, requesters consistently underestimated how likely others were to comply because they did not fully appreciate the social cost of refusal (underestimating compliance with requests; Flynn & Lake, 2008). At work, relationship history and hierarchy can add even more pressure. That is why simply saying “of course you can say no” does not always remove it.

How to handle it

It helps not only to say that refusal is allowed, but to make clear that it will not create a problem: “I have a plan B, so if you can’t do it, it genuinely is fine.” It also helps not to demand a justification or start negotiating after the first no. When the person asking is a manager, the distinction between a request and an instruction should be even clearer. The person being asked can also test their own assumption: “Do I have evidence that saying no will be taken badly, or am I predicting that?” The general rule is: choice depends not only on the words used, but also on the cost a person believes they will pay for saying no.

How Empatyzer and Em can help

Empatyzer can show that “you can say no” may mean genuine freedom to one person while still feeling costly to another because of the relationship itself. The assessment and profile comparison help Em identify differences in need for approval, directness, and relationship-building, then turn them into a concrete suggestion. Nia can go beyond giving Maja permission to refuse and make the refusal feel genuinely low-cost: “I have a plan B, so you’re really not causing me a problem.” Maja, meanwhile, can be prompted not to guess how Nia will react but to check whether “no” really is a safe answer. At team level, Empatyzer can reveal that people may have very different definitions of what a voluntary request feels like. Micro-lessons reinforce a practical habit: it is not enough to give people a choice — you also need to communicate it in a way that lets them actually feel they have one.