Why Communication Is the Real Career Skill
A McKinsey study found that workers spend 28% of their workweek reading and responding to email, and another 14% communicating internally. That's nearly half your job. Yet almost nobody receives formal training on how to do it well.
The result: most professionals default to habits that actively hold them back. They send emails that bury the point. They present to leadership the same way they talk to their teammates. They listen to respond instead of listening to understand. And they avoid giving honest feedback because they're afraid of conflict.
Here's the career math. If you're a strong individual contributor but a mediocre communicator, you'll plateau at the senior IC level. If you're a good IC and a great communicator, you'll be pulled into leadership. Organizations don't promote people who can't clearly convey ideas, influence stakeholders, or navigate difficult conversations.
Written Communication: Say More with Less
The average professional sends 40 emails per day, according to a Radicati Group study. Your emails are competing with 39 others in every recipient's inbox. The ones that get read, understood, and acted on share three traits: they're short, they're structured, and the ask is obvious.
The BLUF Method
The military uses a framework called BLUF: Bottom Line Up Front. Start every email with the conclusion or the request, then provide supporting detail below. Most people do the opposite -- they build up context for three paragraphs before revealing what they actually need.
Before (buried lead):
Hi team, as you know we've been working on the Q3 dashboard migration for the past few weeks. The team had a few discussions about the timeline, and after reviewing the dependencies with engineering, we realized there are some blockers related to the data pipeline refactor. Given these factors and the upcoming holiday schedule, I wanted to flag that we might need to adjust the launch date.
After (BLUF):
We need to push the Q3 dashboard launch from June 15 to June 29. The data pipeline refactor is blocking two key integrations, and the engineering team can't resolve them before the 15th. Details below.
The second version respects the reader's time and makes the decision point immediately clear.
Email Formatting That Gets Read
| Element | Best Practice |
|---|---|
| Subject line | Specific and action-oriented: "Decision needed: Q3 launch date" |
| Opening line | State the purpose or request immediately |
| Body | Use bullets or numbered lists for multiple points |
| Length | Under 5 sentences for routine emails |
| Call to action | Bold the specific ask and deadline |
| Attachments | Reference them in the body ("see attached proposal, page 3") |
When to Write vs. When to Talk
Not everything should be an email. Here's a quick decision framework:
- Email: Decisions that need a paper trail, updates to more than 3 people, anything requiring review before response
- Slack/chat: Quick questions, informal coordination, time-sensitive but low-stakes requests
- Meeting: Topics requiring real-time discussion, brainstorming, sensitive feedback, anything where tone matters
- Phone/video call: Conflict resolution, complex topics, anything where an email chain has gone past 4 replies without resolution
Presenting to Leadership: Think Pyramid, Not Narrative
Most people present information chronologically: here's the problem, here's what we explored, here's what we learned, here's our recommendation. This structure works for a documentary, not for a room full of VPs who have 15 minutes and three other meetings after yours.
Use the Pyramid Principle (developed by Barbara Minto at McKinsey):
- Lead with the recommendation. "We should invest $200K in a new CRM platform. Here's why."
- Follow with 2-3 supporting arguments. Each one should stand independently.
- Back each argument with data. But only the data that directly supports the point.
- Prepare the detail for Q&A. Don't present it unless asked.
This approach works because senior leaders think in decisions, not narratives. They want to know what you're proposing, then decide how deep they want to go. If your recommendation is strong, they might approve it after two slides. If you bury it on slide 14, you might never get there.
The Three Questions Every Executive Presentation Should Answer
Before you build a single slide, make sure you can answer these:
- What do you want them to decide or approve?
- What's the impact if they say yes vs. no?
- What's the risk, and how are you mitigating it?
If you can answer those three questions clearly, you have a presentation. Everything else is supporting material.
Active Listening: The Skill Nobody Thinks They Need to Practice
According to research cited by Harvard Business Review, most people retain only about 25-50% of what they hear. That means in any given conversation, you're missing at least half the information.
Active listening isn't just "being quiet while someone else talks." It's a set of concrete behaviors:
- Paraphrase before responding. "So what I'm hearing is [X]. Is that right?" This catches misunderstandings before they compound.
- Ask clarifying questions. "Can you give me an example of what you mean by 'more strategic'?"
- Resist the urge to formulate your response while they're still talking. This is the hardest one. Your brain wants to jump ahead. Don't let it.
- Watch for what's not being said. If someone says "the project is fine" but their body language says otherwise, acknowledge it: "You seem hesitant. What's your concern?"
- Take notes in meetings. Not transcription -- just key points and action items. It forces your brain to process rather than passively absorb.
Giving Feedback That Actually Changes Behavior
Most workplace feedback is either too vague to act on ("good job"), too harsh to hear ("this is wrong"), or too late to matter (the annual review). Effective feedback is specific, timely, and focused on behavior rather than character.
The SBI Framework
The Situation-Behavior-Impact model, widely used in leadership development and endorsed by the Center for Creative Leadership, gives feedback a clear structure:
- Situation: When and where did the behavior occur?
- Behavior: What specifically did the person do (observable actions, not your interpretation)?
- Impact: What was the result of that behavior?
Vague feedback: "Your presentation was confusing."
SBI feedback: "In yesterday's product review (situation), you jumped between the roadmap and the metrics slides several times (behavior), which made it hard for the leadership team to follow the narrative and they asked to reschedule the decision (impact)."
The SBI version gives the person something concrete to fix. The vague version just makes them feel bad.
Receiving Feedback Well
Feedback goes both directions. When you receive it:
- Don't defend immediately. Your first instinct is to explain or justify. Resist it. Just listen.
- Ask for specifics. If the feedback is vague, ask: "Can you give me an example?"
- Thank them. Even if you disagree. Giving honest feedback is hard, and punishing people for it ensures they'll never do it again.
- Follow up. After implementing changes, circle back: "I've been working on [X] since your feedback. Have you noticed a difference?"
Adapting Your Communication Style
Different audiences need different approaches. The message might be the same, but how you deliver it should change:
| Audience | What They Care About | How to Communicate |
|---|---|---|
| Your manager | Progress, risks, decisions needed | Concise updates, flag blockers early, propose solutions |
| Senior leadership | Business impact, strategic alignment | Lead with outcomes, use data, keep it high-level |
| Cross-functional peers | How your work affects theirs | Be collaborative, explain context, avoid jargon |
| Direct reports | Clarity, support, growth | Be specific about expectations, give regular feedback |
| External stakeholders | Results, timelines, reliability | Professional tone, manage expectations proactively |
The best communicators aren't the most eloquent speakers or the best writers. They're the people who consistently adapt their message to their audience, say what needs to be said clearly, and make the people around them more effective.
Sources
- Harvard Business Review: The Discipline of Listening -- Research on active listening and its impact on leadership effectiveness, including retention statistics
- McKinsey Global Institute: The Social Economy -- Data on how knowledge workers spend their time, including the finding that 28% of the workweek goes to email
- SHRM: The Cost of Poor Communication -- Analysis of how communication breakdowns affect productivity, retention, and organizational performance
Strong communication skills matter even before you get the job. Your resume is often the first example of your communication ability that a hiring manager sees. Superpower Resume helps you write clear, concise resume bullets that demonstrate impact -- the same BLUF approach that works in emails, applied to your career story.
