Make the context and purpose visible

Some messages rely on shared background: everyone is expected to know which draft is current, who can decide, and what a phrase such as “soon” means. Other messages spell out the request and its context. Neither approach is inherently more respectful or intelligent. Difficulty arises when people do not share the same background but the message assumes they do.

When a request matters, make its purpose, needed response, timing, and decision authority visible. This does not require eliminating warmth or writing a long instruction. A brief sentence can state why you are asking and what the person can influence. Explain whether you are inviting ideas, checking a fact, requesting approval, or communicating a settled requirement. People may otherwise spend energy interpreting the relationship instead of answering the question.

Clarity is a shared responsibility. The receiver can ask questions, but the person with more institutional knowledge often has more ability to explain hidden context. Do not treat repeated clarification requests as evidence that someone lacks competence. Examine whether different versions of a document, unexplained abbreviations, or an unstated decision process created the confusion. In an intercultural exchange, clearer context can reduce the need to guess how hierarchy and disagreement operate in the setting. Necessary boundaries should remain clear; politeness should not obscure whether an action is optional or required.

Fictional case: A coordinator emails, “Can you take a look at this when you get a chance?” The attachment is a policy summary due that afternoon, but the recipient has never worked with the team. The coordinator expects a factual review; the recipient edits the wording and returns it next week. The problem is not adequately explained as a cultural mismatch. The request omitted the purpose, deadline, and scope. A revised message can ask for factual corrections by a stated time and explain what to do if that timing is not feasible.

Rewrite the coordinator’s request in four sentences: why the review matters, what to examine, when a response is needed, and how to raise a timing concern. Ask a reader unfamiliar with the project to tell you what action they would take. Use their interpretation to revise the request rather than grading their understanding.

What does your team assume a new person already knows? Which familiar phrase could carry several different expectations?