Speaking So People Act

Writing That Actually Gets Read was about words on a page — words the reader controls, can reread, and can skim at their own pace. Speaking is different. When you talk, the listener can’t rewind. They hear your words once, in order, at your speed, while also reading your face and tone. If you lose them for ten seconds, those seconds are gone. So spoken communication needs its own discipline.

This page is about talking so that people move — so a stand-up, a hallway chat, or a five-minute update ends with the room genuinely knowing what happens next, not just nodding politely. The goal isn’t to sound impressive. It’s to produce action.

Speak in points, not streams

In writing, we called it BLUF — Bottom Line Up Front. The same discipline applies out loud, and it’s even more important, because a listener can’t skim ahead to find your point. If you bury it under three minutes of background, they spend those three minutes wondering where you’re going instead of listening.

A stream is talking in the order the thoughts arrive in your head: “So I was looking at the numbers, and then I noticed the Tuesday batch, and I remembered we had that issue last month, and anyway I think maybe we should…” A point leads with the takeaway and then supports it: “I think we should re-run the Tuesday batch. Here’s why.”

The listener now has a hook to hang everything on. Every detail you add lands as support for a conclusion they already understand, instead of as clues to a conclusion they’re still guessing at.

STREAM (point arrives last — listener guessing the whole time):
  "The vendor emailed, and I checked the contract, and it turns out
   the renewal date moved, so... I think we need to decide this week."

POINT (takeaway first — listener oriented immediately):
  "We need to decide on the vendor renewal this week. The date moved.
   Here's the short version of what changed."

The fix is small: before you open your mouth for anything that matters, know your one sentence. If you can’t say it in one sentence, you’re not ready to say it in twenty.

In practice — the update that starts with the answer

A nurse hands off a patient at shift change. The stream version: “So they came in around two, we did the bloods, the doctor saw them, then we moved them…” The point version: “Bed 4 is stable and waiting on a scan; the one thing you need to watch is their blood pressure — it’s been dropping.” The second version means the incoming nurse knows the priority in five seconds, even if the phone rings mid-sentence.

Be concrete, not abstract

Abstract words feel safe because they’re hard to argue with. Nobody objects to “let’s improve reliability” or “we should communicate better” or “we need to be more customer-focused.” But that’s exactly the problem: nothing you can’t argue with is anything you can act on. Vague words produce vague action, or no action at all.

Concrete language names a thing, a person, and often a time:

ABSTRACT (feels good, changes nothing):
  "Let's improve reliability."
  "We should tighten up communication."
  "Someone needs to look at the returns problem."

CONCRETE (someone can start Monday):
  "Ship the login fix by Thursday."
  "Post a status update in the team channel by 9am each day."
  "Priya, review last month's returns and bring three causes to Friday's meeting."

Notice what concreteness forces you to do: decide. “Improve reliability” lets you avoid choosing what and by when. “Ship the login fix by Thursday” makes the commitment visible — which is uncomfortable, and that discomfort is precisely why abstract language is so tempting. Speaking concretely is partly a communication skill and partly the courage to be pinned down.

A quick test: after you say something, ask yourself, could a reasonable person walk away and do the wrong thing while believing they did what I asked? If yes, you were abstract. Add the missing noun, the missing owner, or the missing date.

The common trap — mistaking agreement for understanding

The room nods. Everyone says “yep, sounds good.” You conclude the message landed. But nodding is cheap — people nod to be polite, to move the meeting along, or because they grasped the topic without grasping the ask. Agreement is not evidence of understanding. The way out is in the next section: don’t infer understanding from nods; confirm it out loud.

Close the loop out loud

The single most common failure in spoken communication is the silent assumption: you believe the meeting produced a decision and clear owners; three people in the room believe something slightly different; nobody says so, because it all felt clear at the time. A week later the work hasn’t happened, and everyone is surprised.

Closing the loop means making the shared understanding explicit before people leave. It takes thirty seconds and it is almost never wasted:

Before ending any conversation that's supposed to produce action, say:

  "So to confirm — [decision]. [Name] is doing [thing] by [when].
   [Other name] is doing [other thing]. Anything I've got wrong?"

Two things make this work. First, saying it out loud forces vagueness into the open — the moment you try to name who owns what, you discover the gaps (“wait, I thought you were sending that”). Second, the closing question — “anything I’ve got wrong?” — invites correction, which nodding never does.

You don’t have to be the leader to do this. Anyone in the room can close the loop, and doing it as the most junior person present is one of the fastest ways to become known as someone who makes meetings work.

Case study — NASA’s Challenger launch, January 1986

The night before the January 1986 Challenger launch, engineers had serious concerns about the shuttle’s O-ring seals in cold weather. The concern existed — it was raised on a call — but it never crossed the line into a clear, confirmed, acted-upon decision by the people with authority to stop the launch. Accounts of the disaster point to a communication breakdown as much as an engineering one: a grave doubt that was voiced but never landed, never closed into “we are not flying tomorrow.” The lesson isn’t that people should have talked more; it’s that a critical concern must be confirmed and owned out loud, not left as an uneasy feeling in the room. Closing the loop is how doubts become decisions.

Adjust for the medium

The same content needs different compression depending on where you’re saying it. A hallway aside, a stand-up update, and a presentation are three different instruments, and using one where another is needed is a classic mistake — the person who delivers a ten-minute monologue at a stand-up, or a one-line mumble in a presentation that needed real explanation.

HALLWAY ASIDE (seconds, one idea):
  "Quick one — the client moved the demo to Thursday. That work for you?"

STAND-UP UPDATE (30–60 seconds, status + blocker):
  "Done: finished the returns report. Doing: the vendor comparison.
   Blocked: I need finance to approve the budget before I can go further."

PRESENTATION (minutes, argument + context):
  Lead with the point, then build the case, then land on the ask.
  The audience can't interrupt to ask, so you must anticipate their
  questions and answer them in order.

The rule underneath all three: match the compression to the time you have and the listener’s need. A hallway aside should never expand into a meeting nobody scheduled. A presentation should never assume the audience will fill in the context you skipped. Before you speak, ask what medium am I in, and how much does this person actually need right now?

The evidence — meetings are expensive time

Studies of workplace time generally find that professionals, and managers especially, spend a large share of their week in meetings, and that a meaningful fraction of that time is widely reported as unproductive. Whatever the exact figures, the direction is clear and worth internalizing: every minute you speak in a group is multiplied by the number of people listening. A rambling five-minute update to eight people isn’t five minutes — it’s most of an hour of human attention. Compression isn’t just politeness; it’s respect for a genuinely scarce resource.

Delivery carries meaning, not just words

Here’s the uncomfortable truth: the same words land completely differently depending on how you say them. “I think we should ship Thursday” delivered with a steady voice and a clear ask sounds like a plan. The same sentence delivered fast, quietly, with a rising, questioning tone sounds like you’re hoping someone will talk you out of it — and someone will.

Three things you control:

• Pace. Rushing signals anxiety and makes you hard to follow; the listener spends effort keeping up instead of thinking. Slowing down, especially before the important sentence, tells people this part matters.
• Confidence in the ask. There’s a difference between “Could we maybe possibly look at the login thing at some point?” and “I’d like the login fix shipped by Thursday.” The second isn’t rude — it’s clear. A vague, hedged ask gives people permission to do nothing.
• Pauses. A short silence after your main point does more work than another sentence. It lets the point land and signals you’re done and waiting for a response.

None of this means performing or faking authority. It means noticing that delivery is part of the message, and that a good point delivered as an apology often gets treated as one. If the ask is real, say it like it’s real.

In practice — the same request, two ways

A café manager needs the closing checklist followed properly. Version one, muttered while walking away: “Um, if you could try to remember the checklist stuff, that’d be great, thanks.” Nothing changes. Version two, said while making eye contact, then pausing: “Before you go — I need the closing checklist done fully every night. It’s the one thing I’m asking. Can you own that?” Same manager, same shift, same words nearly. The second one gets done, because the delivery told the staff it wasn’t optional.

Try this

For one week, before every meeting or update where you need people to do something, prepare a single closing sentence and actually say it out loud: “So to confirm — [decision]; [name] does [thing] by [when]; anything I’ve got wrong?” Notice how often the act of saying it surfaces a gap nobody had spotted — a missing owner, a fuzzy date, two people who thought different things. That surfaced gap is the whole payoff.

Reflect

1. Think of the last time you explained something out loud and lost the room. Were you streaming or leading with the point?
2. Where in your recent conversations did you reach for a safe abstract phrase (“improve,” “tighten up,” “focus on”) instead of a concrete ask with a noun, an owner, and a date?
3. When a meeting you were in ended with nods but no confirmed owners, what happened afterward? Who could have closed the loop?
4. Do you use the same compression everywhere, or do you adjust between a hallway aside, a stand-up, and a presentation? Which one do you tend to get wrong?
5. Recall an ask of yours that got ignored. Was it the words that failed, or the delivery — the pace, the hedging, the missing pause?

Show reflections

1. If you lost them early, you were almost certainly streaming — making them guess your destination. The fix is to know your one sentence before you speak and lead with it, so every detail after it lands as support.
2. Abstract phrases feel safe because they commit to nothing. The useful move is to catch one and rewrite it on the spot into “who does what by when” — and notice the small flinch of commitment that comes with it. That flinch is the point.
3. Nods are not understanding. If the work didn’t happen, the loop was never closed. The good realization is that anyone in the room could have said “so to confirm…” — including you, regardless of seniority.
4. Most people have one default setting. If you tend to over-explain, watch your hallway asides and stand-ups; if you tend to under-explain, watch your presentations, where nobody can interrupt to ask what you skipped.
5. Often the words were fine and the delivery leaked doubt — a hedge, a rush, a rising question-tone on a statement. A real ask, said like it’s real and followed by a pause, gets treated as real. This connects to listening: to deliver well you also have to read whether it landed.