“When You Get a Chance…” — When Politeness Hides a Deadline
Office, an ordinary workday. Tomasz is at his desk when Helena walks over with a report.
— Tomasz, could you maybe take a look at this report sometime when you get a chance?
— Sure, Helena. When I get a chance.
Helena walks away expecting the report to be ready later that day. Tomasz goes back to his work, assuming he can deal with it whenever he has time.
What do you get from Empatyzer?
When it’s time to close agreements, effective interpersonal communication at work becomes crucial for team results. Em provides ready-to-use conversation scenarios based on your employees’ unique collaboration styles, which significantly reduces friction. Always-on support lets leaders improve their craft in practice, without stress and without being judged by HR.
Watch the video on YouTubeWhat really happened
Helena was trying to be polite and avoid sounding pushy, so she used phrases like “maybe,” “sometime,” and “when you get a chance.” In her mind, however, the deadline was specific: today. Tomasz had no access to that unspoken deadline. He heard exactly what was said: there is a task to do, but no clear time attached to it. Both people behaved logically according to their own rules. Helena assumed a softer delivery did not make the task less urgent. Tomasz assumed that if timing mattered, it would be stated explicitly. The characters fit the situation well: Helena naturally softens requests, while Tomasz relies more heavily on the literal meaning of the words he hears.
What the research says
People often communicate part of their meaning indirectly and expect the other person to infer it from context. Many polite requests work this way. Trouble starts when two people do not use the same rules for interpreting what has only been implied (indirect speech acts and implicature; Blum-Kulka, 1987; Ruytenbeek, 2019). This does not mean that one person communicates “better” and the other “worse.” One person places important information in the context; the other looks for it in the words themselves. At work, the risk rises when what is left between the lines is not mood or nuance but something operational: a deadline, priority, responsibility, or decision.
How to handle it
Helena does not need to become blunt or cold. She can keep the polite tone and simply say the part that affects action out loud: “Tomasz, could you take a look? I need it by 4 p.m. today.” For important agreements, it also helps to confirm the shared understanding at the end: “So, today by 4, right?” This is a simple version of closed-loop communication, used in settings where misunderstanding can be costly. The general rule is straightforward: the delivery can be soft, but the deadline, priority, and responsibility should be clear.
How Empatyzer and Em can help
Empatyzer helps spot this kind of mismatch before the deadline disappears between the lines. The assessment can show that one person naturally softens requests while another relies more strongly on literal wording; comparing the two profiles gives Em a chance to flag that exact risk before the conversation. Helena does not need to become more forceful. Em can help her keep her style while making the operational point explicit: “Tomasz, could you take a look by 4 today?” Tomasz, in turn, can get a simple prompt to check the deadline when a task is phrased softly rather than filling in the gap himself. If the same pattern appears across a team, group-level insights can show that the issue is not “someone’s fault” but a recurring clash of communication styles. Micro-lessons then reinforce the small habit of making expectations explicit, so people can communicate more clearly without giving up their natural way of being.
Sources and research
- Shoshana Blum-Kulka (1987). Indirectness and politeness in requests: Same or different?. Journal of Pragmatics, 11(2), 131-146. https://doi.org/10.1016/0378-2166(87)90192-5 DOI: 10.1016/0378-2166(87)90192-5
- Nicolas Ruytenbeek (2019). Indirect requests, relevance, and politeness. Journal of Pragmatics, 142, 78-89. https://doi.org/10.1016/j.pragma.2019.01.007 DOI: 10.1016/j.pragma.2019.01.007
Author: Empatyzer
Published:
Updated: