Key Takeaways
Make every message answer what the listener needs to do with it.
The listener is the point. As a baby, Sullivan’s son discovered that the loud sound he heard came from his own voice. The book’s deeper challenge is to move beyond that self-focused impulse: communication works when it connects your message to what another person needs. At work, people care less about your title or your expertise than about what either means for them. Instead of saying you are a real estate lawyer, explain that you help people build housing. The message changes with the audience, because relevance changes with the audience.
Choose what helps. Before speaking or writing, ask why this person is listening and what they should be able to do with the information. The answer helps determine what to include, how much detail to give, and what can be left out.
What's valuable here is the distinction between having something to say and having something useful to offer. Audience focus resembles good service design: first understand the person’s task, then shape the information around it. But attention to the audience is not the same as automatic agreement or flattery. A communicator still has a duty to be accurate, to surface inconvenient facts, and to say when a request cannot be met. Relevance gives the message a landing place; judgment determines whether it should land there.
State your conclusion first, then prove why the audience should care.
Give the audience a map. A senior banker once delivered complicated charts without explaining the conclusion. An attendee finally asked what the room was supposed to take away. The speaker then summarized his point in two sentences, giving the data a meaning it had lacked. Sullivan recommends making the core message short, plain, and easy to repeat. Industry jargon and elaborate vocabulary may feel impressive to the speaker, but they can leave everyone else guessing.
Match structure to purpose. For an update, state the main point, give supporting information, and briefly restate the point. For a recommendation, identify the problem, state the action, explain its benefits, provide evidence, and name next steps. Sullivan calls the audience’s practical concern WIIFM, or what the information does for them. Benefits often involve time, money, or how people feel about their work.
A clear conclusion gives listeners a mental frame for sorting incoming details, much as a map makes unfamiliar streets easier to navigate. It also respects the limits of attention in a meeting. The important qualification is that clarity must not become false certainty. A recommendation can lead with its conclusion while also stating what remains unknown, what evidence could change the view, or who bears the risk. A message is repeatable when it is simple, but credible when its simplicity does not conceal the trade-offs.
Make stories brief enough to remember, and explicit enough to teach.
Build toward a point. Sullivan recalls an uncle whose stories took so long to reach the event that relatives began looking for excuses to leave. The lesson is not to eliminate stories, but to give them direction. A useful business story establishes when or where it happened, shows the problem or tension, and ends by connecting the experience to the idea being discussed. The storyteller should know the opening and ending before speaking, then include only details that serve the point.
Choose a form that fits. A story is not mandatory. An analogy can make an abstract idea concrete, as when a communications professional compared media interviews to a baseball closer taking a risk for the team. Humor can add warmth, but a failed joke distracts, and jokes at someone else’s expense can damage trust. A straightforward delivery is always acceptable.
Stories are compact models of cause and consequence: they let an audience see what an abstract principle looks like in a real situation. That makes them memorable, but also persuasive in ways that can outrun the evidence. One vivid anecdote does not prove that an approach works generally. The strongest business storyteller uses a story to illuminate a claim, not to replace data or hide exceptions. The explicit ending matters because listeners can draw different lessons from the same event, especially when the storyteller leaves the interpretation unstated.
Turn a roomful of listeners into one-person conversations.
Give attention, not a scan. Sullivan advises speakers to look at one person through a complete thought, then move to someone else. Rapidly sweeping a room can make the speaker more aware of distractions and less settled. Individual focus can make a large audience feel like a series of manageable conversations. The book recounts Francis, a participant who stuttered during practice presentations but delivered one without stuttering after focusing his eyes on individual listeners. Sullivan stresses that eye contact is not a cure for stuttering; in this instance, the technique helped.
Keep delivery aligned. Speak at a pace listeners can absorb, pause between ideas, and vary volume and expression. Open posture and purposeful gestures can support the words. When using notes or slides, Sullivan’s method is to look at the material, remember the next point, then deliver it to a person rather than speaking toward the page or screen.
The practical insight is that presence is relational, not theatrical. A speaker does not need to dominate a room; the speaker needs to make each listener feel addressed. This also offers a useful way to manage performance anxiety by narrowing attention to the current exchange. Eye contact norms vary across people, cultures, and contexts, however, and sustained gaze can feel intrusive. The underlying principle is reciprocal attention, not a rigid number of seconds. A speaker should read the audience and adapt rather than mistake one delivery technique for a universal rule.
Ask open questions until you discover what neither side knew to ask.
Listen for the missing piece. Sullivan describes information as including what you know, what you suspect, what you know you lack, and what you have not realized you lack. Open questions can uncover that last category. Instead of asking whether a client has another concern, ask what else is worrying them. Closed questions are useful when confirming a fact or seeking a decision; open questions invite a fuller answer. In a workshop, one lawyer’s question about what would be most helpful ended weeks of stalemate with a business leader.
Show that the answer matters. Put distractions aside, take brief notes, and summarize what you believe the speaker means before responding. The book calls this a you statement: a short restatement followed by a check that the interpretation is accurate. In a survey of more than 1,800 professionals cited by Sullivan, listening ranked first among leadership communication skills.
Good questions are a form of epistemic humility: they acknowledge that another person’s priorities may not match the assumptions built into a plan. Restating an answer also gives the other person a chance to correct the record before decisions harden. But questions can become an interrogation if they are asked mechanically or without regard for privacy and power. Listening requires more than a sequence of prompts. It requires showing that the response can influence what happens next, even when the answer is inconvenient.
Edit until strong verbs, short sentences, and named actors carry the message.
Make each word earn its place. Sullivan asks writers to remove filler, replace long phrases with direct ones, and make the central action the sentence’s verb. For example, a manager who delayed a project is clearer than a sentence about a delay occurring at the manager’s insistence. Short sentences reduce the chance that a reader must backtrack to understand the point. The book recommends aiming for about 17 words per sentence, while varying sentence length so the result does not become choppy.
Choose accountability deliberately. Naming the actor before the action makes responsibility clear. Passive constructions can be useful when criticism needs tact, but they can also obscure who must act. A report can soften its description of a failure, then identify a specific person and task in its recommendations. Short paragraphs, informative headings, and a reader-focused use of personal pronouns make the document easier to navigate.
This approach treats editing as a design problem: reduce the effort required to find the action, its owner, and its rationale. Active verbs often expose responsibility that institutional language would otherwise blur. Yet directness is not always the same as fairness. In sensitive feedback, an aggressively active sentence can provoke defensiveness and close off learning. The useful question is not whether passive voice is bad, but whether the sentence’s level of explicitness serves its purpose. Clarity includes both accurate accountability and an appropriate tone.
Write emails that make the reader's next move unmistakable.
Supply the missing context. Email lacks facial expression, vocal tone, and the quick corrections of conversation. A useful subject line identifies the actual topic, not merely that the sender is following up. In the body, place answers beside the questions they address, state what response is needed, and give a clear deadline. Sullivan describes a workshop in which U.S. colleagues misread Indian coworkers’ group-based work practices and workplace hierarchy as unwillingness to take responsibility. Adding context and including the relevant manager improved the exchanges.
Know when to switch channels. If a thread keeps circling, a call may resolve it faster. Significant negative feedback and conversations meant to build a relationship are usually better handled directly. For sensitive messages, read the text aloud and check how emphasis might change its meaning. Names, courteous phrasing, and a realistic response window help make a terse medium feel more human.
Email is not simply speech in written form. It is an asynchronous record that readers interpret without many of the cues that normally repair misunderstanding. Clear requests and deadlines lower that ambiguity, while a well-chosen channel can preserve trust. The international example also points to a caution: cultural patterns can guide questions, but should not become stereotypes about individuals. The most reliable response is to clarify expectations with the people involved. When consequences are emotionally significant, efficiency alone is a poor reason to avoid a conversation.
Use client meetings to discover needs before presenting your prepared agenda.
Begin with curiosity. A client meeting can be more than a status report. Sullivan recommends adjusting to the client’s communication style, confirming the meeting’s purpose, and then asking what else is on the client’s mind before launching into prepared material. A client who repeatedly asks about one clause may have a concern the professional has not yet understood. Calling that concern an opportunity to sell more services centers the provider; asking about the client’s needs centers the client.
End with shared action. Explain information in terms of its benefit to the client, then agree on who will do what and by when. After the meeting, expand brief notes into complete thoughts before other work displaces the conversation. The measure of a successful meeting is not how much the professional presented, but whether it revealed useful information and produced clear follow-through.
Discovery-first meetings resemble collaborative diagnosis: the professional contributes expertise, while the client supplies context that cannot be inferred from technical knowledge alone. This makes the meeting more adaptive and can prevent excellent work on the wrong problem. Still, responsiveness does not mean surrendering all structure. Clients may benefit from a professional who flags an issue they have not noticed, or who protects time for a required decision. The strongest agenda is flexible about the route and explicit about the purpose.
Delegate with context, and give feedback that shows exactly how to improve.
Make the assignment workable. Effective delegation explains why the work matters, what the person must produce, who else is involved, why that person was selected, what happens next, and when progress will be checked. The conversation can take only a few minutes, but it prevents avoidable confusion about scope, support, and deadlines. Asking the recipient to summarize the assignment confirms shared understanding without relying on a vague nod.
Make feedback developmental. Identify the work under review, ask whether it is a good time to discuss it, and explain the overall result before addressing details. Name both specific strengths and specific problems, then work with the person on improvements and next steps. Sullivan’s example of a partner pointing angrily at a single mistake shows how correction can fix a sentence while damaging the working relationship. Receiving feedback well matters, too: reflexive defensiveness can discourage colleagues from offering useful observations.
Delegation and feedback are not separate management chores. Together, they create a learning loop: expectations define the task, observation identifies the gap, and a next attempt tests whether the gap has narrowed. Specificity makes that loop usable. A generic compliment or criticism gives little guidance. At the same time, a prescribed sequence can sound artificial if the manager treats it as a script. The aim is not procedural politeness for its own sake, but a real transfer of context, responsibility, and capability.
Give group conversations a structure that protects contribution and keeps attention on others.
Separate invention from judgment. In brainstorming, state the problem, appoint someone to record ideas where everyone can see them, and defer criticism until ideas have been generated. Numbering suggestions encourages volume, while visible notes let participants build on one another’s thinking. Sullivan recommends keeping the session to an hour because energy and idea quality can fall as people tire. Once the group has generated possibilities, organize related ideas and assess what is workable.
Honor the person, serve the room. Introductions should explain why a speaker matters to this audience, not recite a résumé. A toast is a personal message delivered publicly, so it should be genuine, brief, and focused on the person being celebrated. In either setting, insider references and forced humor can exclude listeners or steal attention from the subject.
The distinction between generating ideas and evaluating them protects a group from prematurely treating feasibility as the only measure of value. Public capture also makes participation visible and correctable, which can reduce the chance that a facilitator silently rewrites someone’s contribution. But a no-criticism phase should be bounded, not mistaken for a decision rule. Ideas still need scrutiny, resources, and ownership. The same design principle applies to introductions and toasts: a brief structure works best when it creates space for the person or idea being honored.
Lead with audience-valued purpose, consistent actions, and honest imperfection.
Give people a reason to follow. Sullivan frames leadership through values, vision, and a plan. Express values in terms of what others deserve, describe a concrete future they can work toward, and explain how the plan benefits the people expected to carry it out. A leader who says a department’s growth will create professional opportunities for its engineers connects organizational goals to individual stakes. Actions must support the message: a leader who demands attention while checking a phone teaches the opposite lesson.
Let the whole person show. Vulnerability means honest perspective, not repeated self-criticism or disclosure without purpose. Sullivan describes an insurance executive who replaced a flat speech with a personal family story about the consequences of lacking life insurance. The story carried emotional weight because it was genuinely his and helped the audience understand the stakes. A leader can admit uncertainty, mistakes, or the help received from others without abandoning confidence.
Leadership communication works through alignment: people compare stated values with the daily behavior they can observe. That makes small actions, such as giving a colleague full attention, part of the leader’s argument. Vulnerability can also reduce the distance created by status, especially when it connects a personal experience to a shared problem. The boundary matters. Leaders should not treat disclosure as a performance or expect employees to reciprocate. Honest imperfection is useful when it increases understanding and trust, not when it shifts emotional labor onto the audience.
Analysis
Simply Said is a practical business communication guide organized around one claim: messages become more effective when the speaker stops treating communication as self-expression and starts treating it as a service to the listener. Its examples range from a banker whose charts lacked a conclusion to an assistant who felt unheard, a junior colleague given humiliating feedback, and an executive whose personal story made a speech resonate. The book’s breadth is its advantage and its main compression challenge. It treats presentations, emails, listening, meetings, and leadership as different applications of the same stance, rather than as isolated techniques.
The most useful tension is between simplicity and reduction. A short message can be remembered and repeated, but shortness alone cannot make it true, fair, or complete. Sullivan’s best advice therefore pairs compression with audience analysis: state the point, then provide enough context and proof for the audience to evaluate it. His guidance on passive voice, questioning, and vulnerability also illustrates that communication is not merely transmission. It manages responsibility, status, and emotional safety. A manager’s wording can shape whether a colleague hears a task as meaningful development or as a threat.
The book’s examples are drawn largely from professional services and corporate settings, where meetings, clients, and presentations dominate. Its principles transfer broadly, but specific prescriptions require judgment. Eye contact, directness, humor, and disclosure are interpreted differently across cultures and individuals. The enduring contribution is less a universal script than a disciplined question: what does this person need from this exchange, and how can the message make that need easier to meet without distorting the truth? That question links the book’s tactical advice into a coherent practice of communication and leadership.
People Also Read
Glossary
WIIFM
Audience benefitAn abbreviation for What’s in it for me? It names the listener’s practical concern about how a proposal or piece of information affects their work, resources, or goals. In the book’s persuasive approach, a recommendation should be accompanied by benefits that matter to its audience, rather than relying only on what the speaker wants.
universal motivators
Common audience benefitsThe book’s shorthand for three broad kinds of benefit that often matter to people at work: saving or making money, saving time, and feeling better about their role or organization. The categories help a speaker test whether a recommendation has meaningful value for its audience. They are prompts for analysis, not a guarantee that every person values the same things.
See it. Save it. Say it.
A delivery sequenceA technique for speaking from notes or projected visuals while maintaining contact with listeners. The speaker looks at a short prompt, remembers the point, and then delivers it while looking toward an audience member. The process is designed to keep notes and slides as memory aids rather than turning them into the apparent focus of the presentation.
Arc of Silence
Silent glance between pointsThe quiet interval as a speaker shifts attention from an audience member to notes or a slide and back again. The speaker avoids talking while looking down or turning toward the screen, then delivers the next thought to a listener. The pause gives the audience time to process information and helps the speaker avoid filler words.
Spot Word outline
Sparse speaking notesA delivery outline containing only the words needed to prompt a speaker’s prepared knowledge. It uses a central column, ample white space, short cues, and grouped topics instead of dense prose. Its purpose is to make information easy to find at a glance, so the speaker can look up, speak naturally, and remain connected to the audience.
RIDE
A chart walkthroughA method for explaining a graph or chart before drawing a conclusion from it. The speaker identifies the visual, explains what its dimensions or categories represent, points out the significant data, and then explains why the audience should care. This sequence gives listeners time to orient themselves before they are asked to interpret the finding.
you statements
Understanding checksA listening technique for checking whether a speaker’s meaning has been understood. The listener introduces a restatement, summarizes or reframes the speaker’s point, and asks whether the interpretation is accurate. It helps catch assumptions before they turn into wasted work or disagreement, while signaling that the listener is trying to understand rather than take over the conversation.
Personal Communication Style
Individual interaction tendenciesThe book’s term for a person’s habitual way of communicating, including tendencies such as being abrupt, overly detailed, hesitant, or easily sidetracked. Recognizing these patterns helps someone adapt to a particular interaction. The goal is not to erase an individual style, but to notice when it may obstruct clarity, trust, or another person’s ability to contribute.
informative format
Structure for sharing informationA presentation or document structure for helping an audience understand information. It states the main point, supplies supporting material, and revisits the point at the end. The repetition gives listeners or readers a framework for sorting details and recalling the central idea. It is suited to conveying knowledge rather than securing a specific action.
persuasive format
Structure for winning supportA structure for asking an audience to take action. It begins by gaining attention and stating the recommendation, then explains the audience’s benefits and supports those benefits with evidence. It closes by briefly reinforcing the case and identifying next steps. The format shifts emphasis from the speaker’s preference to reasons the audience might have to agree.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.