Costs
Communication skills defined: purpose against audience, hearing against listening
Communication skills defined term by term: purpose against audience, hearing against listening, clear against short, and how the channel changes the message.
"Good communicator" is a label, not a skill. Underneath it are a dozen separate abilities, and most come in pairs that look alike from the outside: hearing and listening, feedback and criticism, clear and short. Someone strong on one side of a pair and weak on the other reads as inconsistent, and usually cannot say why.
This page takes the pairs in the order they show up in an ordinary working day: before you say anything, while the other person is talking, when you write it down, and when the exchange goes wrong.
What to take away
- Every act of communication has an intended outcome, and it is one of three: the reader knows something, the reader does something, or the reader agrees to something. Choose which before choosing the words.
- Listening is not the absence of speaking. It has its own moves, and they can be checked: can you restate what was said so the speaker accepts it?
- The channel is part of the message. A sentence that is fine spoken can be read as hostile written, and a decision announced in chat has not been announced.
Before you speak: purpose and audience
Inform, instruct and persuade are three different jobs. Informing succeeds when the other person now knows something they did not. Instructing succeeds when they can now do something. Persuading succeeds when they now agree, or act, on something they were not going to. A message that tries to do all three at once usually does none. The most common failure is an instruction written as information: a paragraph describing a situation, with the thing you need them to do buried in the last line.
Audience and recipient are also distinct. The recipient is whoever the message is addressed to. The audience is everyone who will read it, including the person it is forwarded to and the person who reads it in six months. Write for the audience. It is why a message that is perfectly clear to your colleague can be unusable to their manager, who lacks the context you both share.
Context is what the reader already knows; background is what you feel like telling them. The gap between the two is where messages get long. A quick test: cut every sentence the reader could have written themselves, and see what is left.
While listening
Hearing is receiving the sound. Listening is following the meaning.
Three Active Listening Moves
Paraphrase
- What you do
- Restate content in own words
- What it is for
- Checking you understood the facts
Reflection
- What you do
- Name what speaker feels or wants
- What it is for
- Checking you understood the point
Summary
- What you do
- Pull points into short list
- What it is for
- Checking you both agree what was covered
Active listening is the observable part: signaling that you are following, and checking that you are. Only the third can be practiced, and it has three moves that are easy to confuse.
| Move | What you do | What it is for |
|---|---|---|
| Paraphrase | Restate the content in your own words | Checking you understood the facts |
| Reflection | Name what the speaker seems to feel or want | Checking you understood the point |
| Summary | Pull several points into a short list | Checking you both agree what was covered |
The test for all three is the same: the speaker should be able to say, "yes, that is it." If they correct you, the move worked. You found the gap before acting on it.
What makes this hard is the curse of knowledge: once you know what a sentence means, you cannot easily hear it the way someone who does not would.
Two question types sit alongside these. An open question cannot be answered yes or no; it invites the other person to choose what matters. A closed question narrows to a fact. Neither is better.
Open questions come early, closed questions to confirm. The mistake is running them in reverse, so the person must confirm details of a picture they have not been allowed to describe.
Interrupting and interjecting differ by intent. An interruption takes the floor. An interjection ("go on", "and then?") returns it. The second is a listening tool; the first is not, even when the content is agreement.
When you write it down
Clear and short are separate targets, and they conflict more often than writing advice admits. A clear message contains everything the reader needs to act without asking. A short one contains little. When they collide, clear wins, because a short message that produces a reply asking for the missing piece has cost two messages instead of one.
Precise is a third thing again. A precise message could only be read one way. This is the property that federal plain language principles are built around, and it is a different target from brevity. "Soon", "the team", "the issue we discussed" are all clear enough to a reader who shares your context and unusable to one who does not. Precision is what survives forwarding.
Then the structure question. A message can lead with the conclusion and follow with the reasons, or lead with the reasoning and end with the conclusion.
The second is how the thinking happened, and it is the wrong order for almost every working message, because the reader wants to know what you are asking before deciding how much attention to give it. Put the ask, the decision, or the answer in the first line. The reasons are there for whoever wants them.
A request names what you want and by when; a suggestion offers it without asking. Many working messages are requests dressed as suggestions ("it might be worth looking at"), so the reader must guess whether they are being asked. If you want something done, ask.
The evasions that make an ask read as a musing are cataloged under corporate jargon; the short version: make sure a person and a verb are both present.
Choosing the channel
Channels differ on two axes, and both matter more than the words.
Choosing the Right Channel
Information the reader needs to find later -> Document or email
A decision that affects someone -> Conversation first, then written confirmation
A quick factual question -> A message
Synchronous channels (a conversation, a call, a meeting) let you correct in real time. Asynchronous channels (email, a document, a message left in a thread) let the reader choose when to engage and leave a record. A misread in the first is fixed in seconds; in the second it can run for days.
Rich channels carry tone, face and pace. Lean channels carry words. A lean channel is fine for information and bad for anything the reader might take personally, because they will supply the tone themselves, and the tone they supply is rarely generous.
Use
- Information the reader needs to find later
- A document or email
- A decision that affects someone
- A conversation first, then a written confirmation
- A quick factual question
- A message
- Disagreement
- Synchronous and rich
- Bad news
- In person or by voice, then in writing
Because
- Information the reader needs to find later
- It needs to be searchable and stable
- A decision that affects someone
- They deserve the chance to react, and both of you need the record
- A quick factual question
- The cost of an answer is low and no record is needed
- Disagreement
- Written disagreement escalates by default
- Bad news
- Tone is the message
A notification is not a communication. Posting a decision where people could see it is not the same as telling them, and the difference becomes clear the first time someone says "nobody told me" and is, by their own lights, correct.
When it goes wrong: feedback, disagreement, and repair
Feedback describes an effect: what happened as a result of what someone did. Criticism describes a judgment: what was wrong with it. Evaluation assigns a grade. The three are constantly run together, and the reason feedback is received badly is usually that it arrived as one of the other two. "The client asked me twice what the next step was" is feedback. "The email was unclear" is criticism. Only the first gives the person something to do.
Assertive, aggressive and passive are three stances toward disagreement. Assertive states your position and leaves the other person theirs. Aggressive states yours and attacks theirs. Passive withholds yours. There is a fourth, passive-aggressive, which withholds it and then acts on it anyway. Most people believe they are assertive; the check is whether the other person could repeat your position back accurately after the conversation.
Disagreement is about the content. Conflict is about the people. The first is productive and the second is not, and the transition between them is usually one sentence that was about a person rather than a claim. When you notice it, name the claim again.
Finally apology and explanation. An explanation says why something happened. An apology takes responsibility for its effect. They can be given together, but an explanation offered instead of an apology is heard as an excuse, and the person receiving it is not wrong.
Common questions
How do I get better at this quickly?
Pick one pair and work on it for a month. Most people's weakest is either the conclusion-first structure or the paraphrase check, and either can be practiced in every exchange with no one noticing.
Is being a good writer the same as being a good communicator?
No. Writing is one channel. Someone who writes well and cannot listen produces excellent documents that answer the wrong question. The skills that carry across channels are purpose, audience and the check that you were understood.
What about presenting?
A presentation is a persuading or informing job delivered synchronously to an audience that cannot easily interrupt. The rules are the same, with one addition: because they cannot interrupt, you have to build the paraphrase check in yourself, by stating what you think their question is before they ask it.
How does this relate to the rest of the site?
Communication is how every other skill here reaches other people.
The vocabulary pages, starting with business vocabulary, are about getting the word right; this page is about getting it received. The two fail differently, and both of them fail quietly. The habit of asking which quantity a sentence is really about, set out under business acumen, is the same habit applied to listening.
In this guide
- Communication skills mistakes seen from the repair sideNine communication skills mistakes, from a buried ask to a date agreed under pressure, each with the repair and what the writer was protecting themselves from.
- Communication skills examples separate a request from an instruction, cleanlyCommunication skills examples from the vocabulary of asking: request, instruction, reminder and escalation, with twelve real messages and the missing part named.
- Communication skills metrics: five states, proxies, and one direct checkCommunication skills metrics: five states from delivered to acted on, what evidence each needs, where proxies mislead, and one direct check for understanding.
- Communication skills glossary: plain against simple, brief against summary, approval against sign-offCommunication skills vocabulary defined: plain against simple, brief against summary, approval against sign-off, deadline against due date, voice and feedback words.
- Notes on communication skills questions from the field as of 2027Eight communication skills questions that cannot be answered usefully, why the easy answer costs nothing, and the specific request that replaces each one.
- Four axes of workplace communication: synchronous, durable, addressed, push or pullFour axes sort workplace messages: synchronous or asynchronous, durable or ephemeral, addressed or broadcast, push or pull, and a test for tool-born terms.
- A communication skills case study checklist: six hidden defects, one sentenceA communication skills walkthrough of one invented sentence carrying six named defects, from scope ambiguity to a deadline that is not one, each with its repair.
