Communication Skills Examples: What They Look Like in Real Situations

Most articles about communication skills describe them in abstractions: "be a good listener," "use clear language," "adapt to your audience." None of that tells you what to actually do when your manager asks for a status update and you don't have good news, or when a colleague talks over you in a meeting and you need to address it without starting a fight.

Communication skills are only useful when they translate into specific behaviors. Here's what those behaviors look like in practice.

What "Good Communication Skills" Actually Means

In professional settings, strong communication skills come down to five core behaviors. They're not personality traits — they're techniques you can practice and get better at.

1. Specificity. Vague communication creates vague responses. "I've been working on it" is less useful than "I'm 70% through the data analysis section — I'll have a draft to you by Thursday at noon." The more precisely you describe a situation, request, or update, the less follow-up friction you create.

2. Active listening. This is the most overused phrase in communication advice and the least understood. Active listening doesn't mean nodding. It means periodically reflecting what you've heard to confirm you understood it: "So what you're saying is [X] — is that right?" and asking follow-up questions that could only be asked by someone who was paying attention.

3. Tone calibration. The same message lands differently depending on format and tone. "This needs to be redone" is one sentence. "This is heading in the right direction, but the data visualization in section three isn't quite telling the story we need — can we spend 15 minutes talking through what would work better?" is a different sentence with the same information. Neither is better in absolute terms — the right choice depends on context, urgency, and relationship.

4. Closing loops. Strong communicators confirm actions at the end of conversations. "So to summarize: you're going to [X], I'm going to [Y], and we'll reconnect on [date]. Does that match your understanding?" This prevents the dropped threads that create most workplace friction.

5. Managing upward. Keeping your manager appropriately informed without over-communicating is its own skill. Proactively flagging a problem before it becomes a crisis ("I wanted to loop you in early — I've hit a roadblock with [X], here's what I've tried, here are the options I see") is categorically different from waiting until the deadline and delivering bad news then.

Verbal Communication Skills Examples

Verbal communication — what you say in real-time conversations — is where most anxiety concentrates because there's no opportunity to revise.

Example: Raising a concern in a meeting Weak version: "I'm not sure about this approach." (No specificity, no alternative, no follow-through available for the listener.)

Strong version: "I have a concern about the timeline on this — specifically the gap between the design phase and the development handoff. Based on the last project, that transition typically takes two weeks but only one week is budgeted. Can we talk through how we'd handle that if the design runs long?"

The strong version identifies the specific concern, explains why it matters, and ends with a question that moves the conversation forward.

Example: Disagreeing with a manager Weak version: "I don't think that's going to work." (Adversarial framing, no data, no alternative.)

Strong version: "I want to make sure I'm thinking about this correctly. My concern is [specific concern]. The reason I'm flagging it is [specific consequence]. Am I missing something here, or would it make sense to consider [alternative]?"

This framing positions you as problem-solving, not opposing.

Example: Asking for clarification without sounding incompetent Weak version: "I don't understand." (No specificity about what's unclear.)

Strong version: "I want to make sure I do this right. I understand [part you understood]. I'm less clear on [specific part]. Is it [interpretation A] or [interpretation B]?"

Example: Speaking up when talked over In the moment: "I want to finish that thought — [complete your sentence]." After a meeting: "Hey, I noticed I got cut off a few times during that meeting — can we figure out a better flow so everyone gets airtime?"

Written Communication Skills Examples

Written communication is where Gen Z tends to be stronger (more comfortable in digital formats) but sometimes over-casual. The challenge is calibrating formality appropriately.

Email requesting something from a manager or senior colleague: Subject line: Clear and action-oriented. "Input needed: timeline for [project]" not "Quick question."

Body: One paragraph max. State the context in one sentence, the request in one sentence, the deadline in one sentence.

"Hi [Name] — I'm finalizing the [project] brief and need your input on [specific thing] before I share it with the team. Would you be able to review the draft by [date]? I've attached it here. Let me know if you need more context."

Responding to a message when you don't have the answer yet: "Thanks for flagging this. I need to look into it before I can give you a complete answer — I'll get back to you by [time/date]."

This is not a non-answer. It's a commitment, which is more useful than silence.

Slack vs. email: the rule Slack is for quick, informal, time-sensitive exchanges. Email is for anything formal, important, or that needs a record. If a Slack thread goes beyond three back-and-forth messages without resolution, move it to a call or a meeting. Complex conversations conducted entirely in text are a leading cause of misunderstandings.

Tone check for written communication: Read it once for content. Read it again imagining a person who is having a bad day receiving it. If it reads as cold, clipped, or dismissive at that second read, add one sentence of context or acknowledgment. "I know this comes at a busy time — here's what I need and by when."

Communication Skills Examples in High-Pressure Situations

When you don't know the answer to a question: "That's a good question — I want to give you an accurate answer rather than guess. Let me come back to you on that by [time]."

When you make a mistake: "I made an error in [specific thing]. Here's what happened: [brief, factual explanation without excessive self-flagellation]. Here's what I've already done to address it: [actions]. Here's what I'd suggest as the path forward: [plan]. Does that work?"

The structure is: name the error, explain it briefly, show the corrective action, and move forward with a plan. Excessive apology or self-blame doesn't add information and makes the listener uncomfortable.

When delivering bad news: Lead with the news, then the context. Don't bury the lead in a long setup.

"I have an update that's not what we'd hoped for: [the news]. Here's why it happened: [brief context]. Here's what I recommend we do next: [options or plan]."

This structure is more useful and more respectful of the listener's time than cushioning the bad news at the end of five paragraphs of preamble.

For a complete reference of professional scripts, verbal frameworks, and written communication templates, the Gen Z Social Skills Starter Kit at /gen-z-social-skills-guide/ covers the full range of workplace communication scenarios.