Every article on communication skills for managers says the same thing. Listen more. Be clear. Show empathy. Then it stops there, as if naming the skill is the same as building it.
That advice isn’t wrong. It’s just useless without context. A manager who’s told to “listen better” doesn’t know what that looks like when a direct report is venting about workload at 4:45 on a Friday. A manager told to “communicate clearly” doesn’t know how to recover when a stakeholder interrupts their update thirty seconds in.
Communication skills aren’t abstract virtues. They’re specific behaviors that show up in specific moments. The 9 skills below are the ones that separate managers who get buy-in from those who get ignored. Each one comes with a scenario you can practice this week.
1. Active Listening
Active listening means processing what someone is actually saying, not waiting for your turn to respond. Most managers think they’re good at this. Most aren’t.
The common mistake is solving too early. A team member starts explaining a problem and you jump to a fix before they’ve finished the second sentence. You meant to be helpful. They heard “I don’t need the full picture from you.” Over time, they stop bringing you the full picture. Then you’re managing with partial information and wondering why things slip.
Practice scenario: In your next 1:1, try this. When your direct report raises a problem, respond only with a clarifying question. Not a suggestion. Not “have you tried…” Just a question that helps them go deeper. “What’s the part that’s most stuck?” or “When did you first notice this?” Count to three after they finish before you speak. Notice how much more information you get when you stop racing to the answer.
One technique: After someone finishes speaking, paraphrase what you heard before responding. “So the blocker is X, and you’ve already tried Y.” If they correct you, you just avoided a miscommunication. If they confirm, they know they were heard.
Take Risely’s active listening self-assessment to see where your blind spots are.
2. Giving Constructive Feedback
Feedback isn’t a monologue you deliver. It’s a conversation about observed behavior, its impact, and what to do differently. Most managers either avoid it entirely or dump it in a way that makes the other person defensive.
The most common failure mode: sandwiching. Positive-negative-positive. Everyone knows the pattern. The moment you say something nice, the other person braces for the criticism. The compliments lose credibility, and the actual feedback gets diluted.
Practice scenario: You notice a team member’s last two project updates missed key risk items that surfaced later as surprises. Instead of “your updates are great, but you need to include risks, and overall you’re doing well,” try this: “In the last two sprint updates, the deployment risks weren’t flagged. The team found out about the database migration issue in the standup instead of the written update. Can we talk about what goes into the risk section going forward?”
That version names the behavior, describes the impact, and opens a conversation. No sandwich. No vague “you need to improve.”
One technique: Separate observation from interpretation. “I noticed you didn’t speak in the last three meetings” is an observation. “You seem disengaged” is an interpretation. Start with observations. Let them provide the interpretation.
Risely’s constructive feedback assessment helps you identify which part of the feedback loop you’re weakest at.
3. Receiving Feedback
Giving feedback gets all the attention. Receiving it is harder and matters just as much. When a direct report tells you that your last-minute scope changes are stressful, what you do in the next ten seconds determines whether they’ll ever tell you anything honest again.
Managers who receive feedback poorly don’t usually get angry. They explain. They contextualize. They say things like “well, the reason I changed the scope was…” And the person who gave the feedback walks away thinking: noted, won’t bother next time.
Practice scenario: Ask one of your direct reports this week: “What’s one thing I do that makes your job harder?” When they answer, say “thank you, that’s useful” and write it down. Don’t explain. Don’t defend. Don’t fix it in the meeting. Come back in the next 1:1 with what you changed or why you couldn’t. That follow-through is what makes people trust the feedback loop.
One technique: Buy yourself processing time with honest language. “I need to sit with that for a day before I respond. I want to take it seriously.” This works much better than a knee-jerk reaction dressed up as engagement.
Receiving feedback well uses many of the same muscles as giving it. Risely’s constructive feedback assessment covers both directions of the feedback loop.
4. Setting Clear Expectations
Unclear expectations are the root cause of most performance problems that get mislabeled as “motivation issues” or “skill gaps.” When a manager says “I need this by end of week” and the team member delivers a rough draft on Friday afternoon while the manager expected a polished final version on Thursday, neither person is wrong. The expectation was never specific enough to be met.
The failure pattern is assuming shared context. You’ve been thinking about a project for three weeks. Your direct report heard about it for the first time in a ten-minute meeting. The gap between your mental model and theirs is enormous, and you can’t see it because you’re standing inside your own context.
Practice scenario: The next time you assign a task, cover these four things explicitly: what done looks like (specific output, not “a good job”), when it’s due (day and time, not “soon”), what resources or authority they have, and what to do if they get stuck (come to you, make a judgment call, escalate to someone else). Write it in a message after the conversation so both of you have the same reference point.
One technique: End every assignment conversation with “tell me back what you’re going to do.” Not to test them. To test your own clarity. If their version doesn’t match yours, the gap is in your communication, not their comprehension.
Risely’s expectation setting assessment shows you where the gap between your intent and your team’s understanding is widest.
5. Running Effective Meetings
Bad meetings aren’t just annoying. They’re a signal to your team about how you value their time. A manager who calls a 60-minute meeting with no agenda, lets two people dominate the conversation, and ends without decisions has just told eight people that their hour wasn’t worth protecting.
Most meeting problems come from a single root cause: the meeting doesn’t have a clear purpose. “Sync” isn’t a purpose. “Decide whether to ship feature X this sprint or next” is a purpose.
Practice scenario: Pick your recurring team meeting. Before the next one, write down the single decision or outcome that meeting needs to produce. Share the agenda 24 hours in advance. At the end, read back the decisions made and who owns each action item. If no decisions were made, ask yourself whether the meeting needed to happen at all.
One technique: Assign a “silent start.” For the first three minutes, everyone reads the pre-read or agenda silently. This levels the playing field between people who process verbally and people who need time to read and think. You’ll get higher-quality input from the full room instead of just the loudest voices.
Most meeting friction comes down to one-on-one dynamics. Assess how well yours are working.
6. Difficult Conversations
Difficult conversations aren’t difficult because of the topic. They’re difficult because managers wait too long to have them. A performance issue that could have been a five-minute check-in after week one becomes a 45-minute confrontation after month three, with accumulated resentment on both sides.
The mistake managers make most often is rehearsing a script. They plan exactly what to say, then deliver it as a monologue. The other person feels talked at, not talked with. The conversation becomes a sentencing hearing instead of a problem-solving session.
Practice scenario: You have a team member who’s been consistently late to morning standups. Instead of building a case with timestamps and policies, start with curiosity. “I’ve noticed you’ve been joining standups 10-15 minutes late the last couple of weeks. What’s going on?” Then listen. Maybe they’re dealing with a daycare situation. Maybe they think standup is pointless. Both are useful data that changes your next move.
One technique: Prepare your opening sentence and your first question. Nothing else. The opening sentence names the topic without judgment: “I want to talk about the timeline on Project X.” The question invites their perspective: “What’s your read on where things stand?” Everything after that should be a response to what they actually say, not a script you wrote at your desk.
Difficult conversations are a subset of conflict resolution. Assess your default style to understand why some conversations feel harder than they should.
7. Written Communication
Managers underestimate how much of their communication happens in writing. Slack messages, emails, project briefs, status updates, performance reviews. Written words get re-read, forwarded, screenshot-ted, and interpreted without the benefit of your tone of voice or facial expression. A message that made sense in your head can read as passive-aggressive, confusing, or dismissive on someone else’s screen.
The most common written communication failure is length. Long messages don’t get read carefully. They get skimmed, and the reader picks up whatever their eyes land on, which is usually not the part you considered most important.
Practice scenario: Find the last email or Slack message you sent that was longer than three paragraphs. Rewrite it. Put the ask or decision at the top. Cut any sentence that doesn’t change the reader’s understanding or action. See if you can get it under half the original length without losing the point.
One technique: Structure matters more than prose quality. Use this pattern for any written update: (1) what’s the situation, (2) what do I need from you, (3) by when. Put the “what I need from you” in bold or on its own line. Most people scan for “what do I have to do” and ignore everything else.
Risely’s written communication assessment shows where your writing lands: too long, too vague, or too blunt.
8. Presenting to Stakeholders
Presenting to stakeholders is a different skill than presenting to your team. Your team has context. Stakeholders don’t. Your team cares about the how. Stakeholders care about the so-what. Most managers present to leadership the same way they’d present to their peers and lose the room within two minutes because they started with background instead of the conclusion.
The failure pattern is burying the lead. Managers build up to their recommendation through five slides of context, and by slide three the VP has already formed their own opinion and is waiting to voice it. You’ve lost control of your own narrative.
Practice scenario: You’re presenting a quarterly review to your skip-level. Open with the outcome: “We hit 94% of target. The gap was in Q3 onboarding delays, and we’ve already changed the process for next quarter.” Then stop. Let them ask questions. Their questions tell you what they care about, which is better data than guessing what to cover.
One technique: For any presentation above your level, apply the newspaper test. If a journalist had to write one sentence about your update, what would it be? That sentence is your opening line. Everything else is supporting evidence you deploy only when asked.
Presenting is oral communication under pressure. Risely’s oral communication assessment pinpoints whether your gap is structure, delivery, or audience adaptation.
9. Cross-Functional Communication
Working across teams is where most communication breakdowns compound. Your team has its own vocabulary, priorities, and definition of “urgent.” The team you’re collaborating with has different ones. Neither side is wrong. They’re operating from different context, and nobody pauses long enough to translate.
The common mistake is assuming your priorities are shared. When you tell the engineering team that your marketing launch is “critical for Q2,” they hear urgency. But they have six other teams also calling things critical for Q2. Without specifics about deadlines, dependencies, and trade-offs, your request enters a queue and gets prioritized by someone who doesn’t have your context.
Practice scenario: You need the design team to prioritize a landing page for a campaign launching in three weeks. Instead of “this is high priority, can you get it done ASAP,” try: “We’re launching on June 5th. The page needs to be in staging by May 28th for QA. If that timeline doesn’t work, the fallback is using the existing template, but we’d lose the custom header. Can we look at what’s feasible?”
That version gives the other team a deadline, a dependency, and an alternative. It treats them as collaborators, not a service desk.
Cross-functional communication is really collaboration under a different name. Assess where your collaborative instincts are strong and where they break down.
One technique: When you’re working across teams, ask early: “What does your team need from mine to make this work?” People who feel like partners give you better work and more honest timelines than people who feel like they’re being handed a task. Cross-functional communication is a negotiation, not a handoff.
How to Actually Improve (Not Just “Be More Aware”)
Reading about communication skills doesn’t build them. Neither does self-awareness alone. Knowing you interrupt people in meetings is useful. Knowing it and still interrupting is the more common reality.
Communication skills improve through structured practice with feedback. That means three things:
Pick one skill, not nine. Look at the list above and identify the skill that causes you the most friction right now. Maybe it’s feedback conversations. Maybe it’s written communication. Practice that one deliberately for 4 weeks before adding another.
Practice in real situations, not simulations. The scenario attached to each skill above is meant for your actual work this week. Use your real 1:1, your real meeting, your real stakeholder update. Simulations build comfort. Real conversations build skill.
Get feedback on the skill you’re practicing. Ask a trusted peer or direct report: “I’m working on how I give feedback. After our next conversation where I share feedback, can you tell me what landed and what didn’t?” This closes the loop between intention and impact.
If you want a structured approach, Risely’s AI coach Merlin helps you prepare for specific conversations before they happen and debrief afterward. Across 4,000+ users, Risely sees an average 26% improvement in communication-related skills within 12 weeks of coaching. That improvement comes from practice, not theory.
Your MBTI type also shapes how you communicate and where your natural blind spots sit. Understanding your type preferences alongside these 9 skills gives you a more precise development target than generic advice ever could.
Communication isn’t a talent. It’s a practice. Start with one skill, one scenario, this week.