07 · Foundational Communication Skills¶
Everything covered so far — listening, empathy, trust, delegation — has to travel through actual communication to have any effect. This module covers the foundational mechanics: being clear rather than vague, adjusting your message to your audience, and communicating in a way that invites dialogue rather than shutting it down. These are deliberately basic, general-purpose skills — Modules 2.6 and 2.9 (difficult conversations, meetings) build more advanced applications on top of them later in the track.
1. Clarity over cleverness¶
The single most common communication failure in leadership isn't saying something offensive or wrong — it's being vague enough that people fill in the gap with their own (often worse) assumption. Compare:
| Vague | Clear |
|---|---|
| "Let's try to get this done soon" | "I need this by Thursday at 5pm" |
| "There were some concerns about the approach" | "Two specific concerns: the timeline assumes no code review delays, and it doesn't account for the holiday week" |
| "Good job on this, just a few tweaks needed" | "The structure and logic are solid — the two things to fix before this ships are X and Y" |
Vague language often comes from a desire to soften bad news or avoid sounding harsh — but it usually backfires, because the listener either under-reacts (missing the real urgency) or over-reacts (imagining a worse problem than what's actually there) and either way spends energy decoding intent instead of acting on clear information.
2. The message-audience-medium check¶
Before an important message, three quick questions:
- Message — what's the one thing I actually need this person to walk away understanding or doing? (If you can't state it in one sentence, it's not ready to send.)
- Audience — what does this specific person already know, and what do they need explained that someone else wouldn't? (The same update sounds different told to your manager vs. told to a new hire.)
- Medium — does this need a real-time conversation (anything with emotional weight, ambiguity, or where you need to read a reaction), or is it simple enough for async text (a status update, a scheduling question)? A common mistake is sending emotionally loaded messages over text/chat because it's easier for the sender, at the cost of being harder and more ambiguous for the receiver.
3. Framing that invites dialogue vs. framing that shuts it down¶
| Shuts down dialogue | Invites dialogue |
|---|---|
| "This isn't working." | "I'm seeing X — what's your read on it?" |
| "Just do it this way." | "Here's the outcome I need — what's your plan to get there?" |
| "Why didn't you tell me?" | "Help me understand what happened here." |
| "That's not what I meant." | "Let me try that again — what I meant was..." |
The pattern: framing as a statement of judgment ("this isn't working") puts the other person on the defensive and ends the conversation before it starts. Framing as an open question or an invitation to explain keeps the conversation live and gives you more accurate information before you react — which is the same active-listening discipline from Module 3 applied to how you initiate a conversation, not just how you receive one.
4. A worked example¶
A project lead, Carla, needs to tell a stakeholder that a launch date will slip by two weeks.
- Weak version: "There have been some challenges and we might need a little more time" — vague on the amount, vague on the reason, and invites the stakeholder to imagine the worst (or push back hard because the ask feels unclear and untrustworthy).
- Strong version: "The launch is moving from the 15th to the 29th. The cause is a vendor integration that's taking longer to test than planned — here's specifically what's left, and here's what I need from your team to hit the new date." This states the message clearly first, gives the real reason instead of a vague gesture at "challenges," and ends with a specific ask rather than leaving the stakeholder to guess what happens next.
How It Actually Works¶
Clarity beats cleverness because of a hard limit on working memory, not because of taste. Working memory can hold roughly 4 (Cowan's revised estimate, down from Miller's classic "7±2") independent chunks at once before older ones get displaced. A cleverly layered message — a metaphor wrapped around a caveat wrapped around the actual ask — forces the listener to hold the outer structure in working memory while decoding the inner content, competing for the same limited slots the actual message needs. Plain, front-loaded statements ("here's the decision, here's why, here's what I need from you") consume fewer working-memory slots for structure, leaving more capacity for the listener to actually engage with the content — which is why dense, "smart-sounding" messages are frequently misunderstood by smart audiences, not because the audience is unable to follow but because parsing effort has crowded out comprehension.
Why the message-audience-medium mismatch produces predictable failure. Communication requires the sender's mental model to survive encoding into a channel and decoding by a receiver whose prior context differs from the sender's. A message calibrated for someone with full context, sent to someone without it, forces the receiver to either silently fill gaps with guesses (introducing errors that don't surface until later) or to ask clarifying questions (which a busy sender often reads as the receiver being slow, when it's actually the channel mismatch working as intended — the gap was real, and asking closed it early instead of late).
Why framing changes what people are willing to say next, not just how they feel about what was said. Framing that starts with a fixed conclusion ("we're doing X") triggers a different conversational move structure than framing that opens with a shared problem ("we're trying to solve X — thoughts?") — the first invites compliance or silent disagreement (there's no structurally available slot for a counter-proposal without it reading as opposition), while the second creates an explicit slot for information the leader doesn't have yet. This is a known result in conversation-analysis research: the opening move of an exchange mechanically constrains what a "fitting" response can be, independent of either party's intent — a leader who wants dialogue but opens with a decision-framed statement is fighting the structure of their own sentence.
Exercise¶
Think of a message you need to send this week that currently feels vague or uncomfortable to state clearly (a deadline, a piece of feedback, a decision you need to explain). Run it through the message-audience-medium check: write the one-sentence core message, note what this specific audience already knows vs. needs explained, and decide the right medium. Then rewrite the message itself using the vague-vs-clear and shuts-down-vs-invites-dialogue tables as a guide, and send the clear version instead of the vague one you started with.