To communicate clearly, put the main point first, use specific words, explain what the other person needs to know or do, and check that you have been understood. Clear communication is not simply speaking slowly or choosing formal words. It is the work of connecting your intended meaning to another person’s situation, where the same phrase may suggest different things. Plain-language guidance likewise emphasizes writing for a specific audience and testing whether that audience understands. [1]
Name the point before the explanation
Start with the message’s purpose. If you need a decision, say what decision and by when. If you are sharing information, say what changed and what follows. A listener should not have to collect clues from a long preamble before discovering why you are speaking.
For example, instead of opening a team conversation with “There have been some things happening with the room,” try: “The meeting room is unavailable at 2 p.m.; can we move our review to 3?” The second version gives the relevant event and a next step. Add background only when it helps the listener decide or act.
Make abstract words concrete
Words are symbols, and the connection between a word and the thing a person imagines is not automatic. “Soon,” “finished,” “large,” and “ready” can point to different thresholds for different people. A useful repair is to replace a broad label with something observable: a date, an amount, a location, or a description of the result. [2]
Suppose a colleague asks you to send the “final” draft. You may mean a draft with all sections present; they may mean a file that has been proofread and approved. Ask what “final” means for this task, or specify your own: “I’ll send the complete draft with all sections by 4 p.m.; I haven’t checked the citations yet.” This prevents a difference in definition from turning into a disagreement about effort.
Separate what happened from what you infer
Clear messages distinguish direct observation from a conclusion or judgment. “You ignored my note” claims knowledge of another person’s attention and motive. “I sent the schedule on Tuesday and haven’t received a reply” describes what you can verify. You can then own the inference: “I’m not sure whether you saw it.” Communication guidance identifies the confusion of an inference with an observation as a common source of misunderstanding. [3]
This distinction does not require you to hide frustration. It gives the other person a more accurate account of what you know and what you feel. “I’m worried we may miss the booking deadline” states a feeling and the reason for it. “You never take deadlines seriously” turns one concern into a sweeping claim that is harder to discuss productively.
Build a complete request
A practical message often includes four parts: the situation, its effect, your need, and a specific request. Use only the parts the listener needs. For instance: “The event list still has two blank speaker bios. I need to send it to the printer tomorrow. Could you send those bios by noon today, or tell me when they’ll be ready?” The request leaves room for an honest answer and a workable alternative.
This is more useful than “Please handle the bios ASAP.” “ASAP” sounds urgent but gives no shared deadline. The concrete version also avoids implying that the listener should guess what “handle” means. Language that names your thoughts, feelings, and needs can help you own your message rather than casting the other person as its cause. [4]
Check the meaning, not just the words
After a consequential instruction, invite a short summary: “To make sure I explained this well, what will you send, and when?” This makes the check about the explanation rather than a test of the listener. In conversation, pause for questions and listen to the answer instead of treating silence as proof of agreement. People can hear a sentence while interpreting its purpose differently.
Try this five-minute exercise with a message you need to deliver. Write its main point in one sentence. Underline any vague word, such as “soon” or “appropriate,” and replace it with a detail the other person can verify. Add one action and a deadline if needed. Then ask a reader what they think is being requested. If their answer differs from yours, revise the message before sending it. Plain-language guidance includes testing content with its intended audience because clear design and wording are only useful when readers can understand them. [1]
