Communicate With Clarity and Confidence

Start with what you need the person to do

Think of a message you need to send. Finish this sentence: “After reading this, the other person should know, decide, or do ___.” If you cannot finish it, you may be trying to solve several problems in one message. Choose the main purpose first.

Now choose the channel. A brief coordination question may fit chat. An agreement may need an email record. An ambiguous or emotionally charged issue may benefit from a conversation, followed by a written summary of the decision. Use your organization’s approved channels for sensitive information. More formality does not automatically create more clarity.

Your turn: Write the purpose in one sentence, then name the channel that makes it easiest to respond.

Give the reader a clear path through the message

Use four parts: purpose, essential context, specific request, and next step. Put the purpose near the beginning. Add only the background the person needs to understand the request. Name a real deadline when one exists and explain what depends on it. If the timing is flexible, say so.

In chat, include your question with the context instead of stopping at “Can I ask something?” For example: “I am updating the event page. Is the registration link final, or should I wait for approval?” In a meeting, tell people whether you are sharing information, exploring options, or asking for a decision. Close by confirming who will do what.

Your turn: Check whether someone can find your request without reading the message twice.

Let’s rewrite a request together

A useful email subject could be “Decision requested: orientation sequence.” Adjust the greeting and detail to your relationship. Keep the clarity even when the tone is more casual.

Use clear language at any career stage

If you need to disagree, connect the concern to the work: “I see a risk in that approach because ___. Could we consider ___?” Clear communication does not require agreeing to every request.

Address the problem without guessing the motive

When a conversation is difficult, separate what you observed from the story you are telling yourself. “The file arrived after the review meeting” is an observation. “You do not care about the project” is an assumption about intent. Start with the observation, explain its effect, and invite the other person’s perspective.

Try: “When updates arrive after the meeting, I cannot include them in the decision brief. What would help us have a current version beforehand?” Listen for an unclear assignment, a different understanding of the deadline, or competing work. Then agree on a feasible next step. For safety concerns, harassment, or formal workplace issues, use the established reporting and support channels rather than treating a script as a substitute.

Review, send, and close the loop

Before sending, read from the recipient’s perspective. Can they tell what you need, why it matters, and how to respond? Check names, attachments, links, recipients, and commitments. If you used AI, ask it to identify ambiguity without inventing context or promises. Review every change yourself. Follow organizational rules for recordings and AI meeting summaries, and confirm decisions with the people involved.

After a conversation, a short record can prevent confusion: “We agreed that I will update the outline, and you will confirm the demonstration sequence.” Keep shared expectations for response times and channels explicit instead of assuming everyone works the same way.

Check your progress: Does the other person have enough information to take the next step without guessing?