“Ideally Tomorrow Morning” — Suggestion or Hidden Deadline?

Company messenger, the day before a client delivery. Maja needs data from Marek in the morning but does not want to sound as though she is managing his work.

— If you can, ideally I’d have this tomorrow morning.
— Sure.

Maja believes she has given a deadline politely. Marek hears a preference that can move behind more urgent tasks.

What really happened

Maja genuinely needs the data in the morning, but she does not want to sound like someone assigning Marek’s priorities. So instead of stating the deadline directly, she writes: “if you can, ideally I’d have this tomorrow morning.” To her, the softer form shows respect to an older and more experienced colleague. Marek takes the words at face value: “ideally” sounds like a preference, and “if you can” sounds like a real option to say no. He postpones the task behind more urgent work. In the morning both are surprised. Maja believed she had communicated urgency politely. Marek believed he had received a preference, not a hard dependency.

What the research says

Requests are a special kind of communication because the speaker is trying to get another person to act while often preserving that person’s sense of choice and avoiding sounding overly commanding. That is why people soften requests with phrases such as “maybe,” “if you can,” “ideally,” or “it would be great if…” (indirectness and politeness in requests; Blum-Kulka, 1987; Ruytenbeek, 2019). Research on workplace email also suggests that request strategies vary with the size of the request, the parties’ rights and obligations, and their working relationship (Jung & Lee, 2025). The key point is that politeness and precision are not opposites. Maja’s problem is not that she was too nice; it is that she softened information that the other person needed in order to plan their work.

How to handle it

You can respect someone’s autonomy while making the dependency explicit: “I need the data by 9:30 because I’m sending the client material at 10. Can you make that?” The message says three things: what is needed, why the deadline is real, and that you need to know whether it is feasible. If Marek cannot do it, Maja learns immediately and can change the plan. The general rule is: the more another person’s work blocks your deadline, the less useful it is to hide that fact under polite softeners; politeness should soften the delivery, not blur the information.

How Empatyzer and Em can help

Empatyzer can show Maja in advance that her natural politeness and tendency to soften requests may lead Marek to treat a real deadline as a loose preference. Comparing their profiles can show that nobody lacks goodwill: Maja wants to respect autonomy and the relationship, while Marek organizes work around explicitly stated priorities. Before she sends the message, Em can suggest wording that keeps her style while removing the risk: “I need the data tomorrow by 9:30 because I’m sending the client material at 10. Can you make that?” At team level, Empatyzer can show whether some people regularly encode urgency between the lines while others expect it to be explicit. Micro-lessons reinforce a simple habit: courtesy can stay soft, but the deadline and dependency should be unmistakably visible.