“That Might Be Difficult” — When a Soft No Sounds Like Maybe

Implementation planning. Jonas asks Samuel about a deadline. Samuel wants to decline without sounding blunt.

— Can we have it by Friday?
— Hmm… Friday might be difficult.

Samuel walks away convinced he said no. Jonas puts Friday in the plan because he heard “difficult,” not “impossible.”

What really happened

Samuel does not want to give a hard “no,” so he uses a softer phrase: “Friday might be difficult.” For him, the situation, tone, and context do the rest. Jonas hears the ordinary meaning of the words: difficult does not mean impossible. They therefore leave the same conversation with two different decisions. Samuel thinks he declined. Jonas thinks Samuel accepted a demanding deadline. It is a classic case of politeness hiding the most important operational information.

What the research says

Refusal is socially difficult because it can threaten the relationship, so people in many languages and contexts soften or phrase refusals indirectly (refusal strategies; Shishavan & Sharifian, 2016). Cross-cultural research also shows that the degree of directness in refusals can vary and create real misunderstandings (facework in refusals; Siebold & Busch, 2015). This does not mean an individual’s refusal style can be predicted from nationality. It means indirectness is a real communicative strategy and people may not share the same code for interpreting it.

How to handle it

For operational decisions, keep the courtesy but state the outcome explicitly: “We won’t make Friday. Tuesday is realistic.” If you hear “that might be difficult” and you need a decision, check: “Do you mean no, or is Friday still possible?” The general rule is: the more important the yes-or-no answer, the less safe it is to leave the “no” entirely in tone and implication.

How Empatyzer and Em can help

Empatyzer can show Samuel and Jonas in advance that the same soft refusal is two different messages to them. Cultural and personality assessment can surface differences in directness and literalness, while profile comparison lets Em warn Samuel that “Friday might be difficult” is unlikely to sound like a definite no to Jonas. Samuel does not need to change his whole style; he can simply add an explicit core to the softer delivery: “We won’t make Friday; Tuesday is realistic.” Jonas can develop the corresponding habit of checking whether “difficult” signals risk or a decision. If similar codes are common in the team, group-level insights help name them. Micro-lessons ensure that politeness stops hiding the decision the other person actually needs to know.