Communication in the Workplace for IT Professionals: Why It’s On You to Get It Right

I opened the training on better communication in the workplace as I always have: “The responsibility for successful communication rests with the sender, not the receiver.” James, one of the attendees, raised his hand. “I disagree. You can’t tailor your communication style just to match everyone else’s preferences. That’s unrealistic. How can you be responsible for the crazy ways someone else might interpret what you say? If they need the information in your message, they just need to pay attention.” (I think he may have actually used the word mollycoddle.) James both made a good point and missed the point. Suppose you’re an IT manager or a supervisor. You need to make your team aware of a, say, new policy. Your team’s success depends on them getting the message. As a leader, you’re responsible for your team’s success or failure. Yes, they need to pay attention, but different people have different ways of processing what they hear and see. Sometimes, it’s a generational issue; sometimes, it’s something cultural; sometimes, it’s based on a person’s prior experience(s).

An obvious, although a bit extreme example is when you’re speaking to a group that speaks a different language than yours. It’s up to you to find a way to ensure the group understands your message, possibly by using an interpreter.

Here’s a relatable example of miscommunication between a manager and her team—perfect for illustrating how intent and interpretation can diverge:

🗣️ What the Manager Says:

“I’d like to see more initiative from the team.”

👂 What the Team Hears:

• “We’re not working hard enough.”
• “She’s unhappy with our performance.”
• “We need to stay late and take on more projects to prove ourselves.”

🧠 What the Manager Actually Meant:

She wanted team members to speak up with ideas during meetings and feel empowered to suggest improvements or take ownership of small process improvements—not work overtime or take on extra tasks without support.

This kind of miscommunication is common in technical environments, where people are task-focused and may not always pause to clarify intent. It’s a great example of why the sender—especially a leader—needs to be as specific and clear as possible:

“When I say I’d like to see more initiative, I mean I’d love for you to bring ideas forward during meetings or suggest ways we can improve our processes. It’s not about doing more work—it’s about feeling empowered to contribute your thinking, to say what’s on your mind.”

Even if you’re not in a leadership role, your communication with co-workers, customers, and everyone else must always be as specific and clear as possible.

If you’ve ever been on a project where something went sideways because of a miscommunication, you already know the importance of clear, intentional communication in the workplace. This is especially true in IT, where the stakes are often high and the work is complex, the ability to communicate effectively can make or break a team’s success. And yet, communication problems remain one of the most common sources of friction in technical environments.

In my book The Compassionate Geek: How Engineers, IT Pros, and Other Tech Specialists Can Master Human Relations Skills to Deliver Outstanding Customer Service, I talk a lot about human interactions in tech. One of the key themes throughout the book is the role of communication—how we speak, how we write, how we listen, and how we make sure our message gets across. What I’ve found over years of working with and training IT professionals is this: the responsibility for successful communication lies squarely with the person sending the message.

Let’s break that down.

---

What Is Successful Communication in the Workplace?

At its core, successful communication means that the message received is the same as the message intended. Sounds simple, but we all know it’s not. We filter everything through our own experiences, assumptions, and even our emotional states. What you think you said and what the other person actually heard can be two very different things.

Think about sending an email with a quick update to a project stakeholder. You might believe you’ve provided all the critical information, but if you’re using jargon, vague wording, or skipping over context, your message might leave them confused or even anxious. In that case, even though you technically “communicated,” you didn’t do it successfully.

Successful communication happens when the receiver understands your words and also grasps your intent. Successful communication means the receiver can act on your message with clarity and confidence.

---

Why It’s On the Sender

It might seem fair to say that both the sender and the receiver share responsibility for good communication. And while the receiver certainly plays a role, the bulk of the responsibility belongs to the sender.

Here’s why: the sender controls the message. You decide how to phrase it, when to send it, the tone you use, the format you choose (email, chat, voice, video, Zoom, Teams, Slack), and even whether to follow up. That’s a lot of control—and with that control comes responsibility.

“With great power comes great responsibility.” -Uncle Ben (Spiderman or perhaps Voltaire)

In technical environments, where the complexity of information can easily lead to confusion, it’s even more important for the sender to take the lead in ensuring clarity. If you’re explaining how to troubleshoot a network issue or outlining the steps for a software deployment, it’s not enough to say, “I told them.” The real question is, “Did they understand?”

---

Common Communication Pitfalls in IT

IT professionals often work in high-pressure environments where speed and precision matter. (No fooling!) That can lead to shortcuts in communication—technical jargon, overly brief messages, or assuming others have the same context we do. Here are a few common pitfalls:

• Tech-speak overload: Using acronyms or technical language without making sure the audience understands them.
• Assumed knowledge: Leaving out key context because you think the other person “should” already know it.
• Over-reliance on text: Sending emails or chat messages when a quick call or face-to-face conversation would be clearer.
• Tone mismatches: Writing in a way that sounds abrupt or harsh without meaning to.

These habits don’t usually come from a bad place. Often, they’re born of efficiency or habit. But they can cause misunderstandings, damage trust, and create friction within teams.

---

Taking Ownership of Your Message

So, if you’re the sender, how do you take full ownership of your communication? Here are a few strategies that make a big difference, especially in technical work:

1. Know Your Audience

Tailor your language, level of detail, and tone to your audience. If you’re explaining an issue to a non-technical stakeholder, ditch the jargon and focus on business impact. If you’re talking to a fellow tech, be as precise and technical as needed. Clarity means adjusting, not assuming. (Even when speaking with a fellow tech, make sure their technical level is where you think it is.)

2. Be Clear and Concise

Clarity doesn’t mean dumbing things down—it means structuring your message so it’s easy to follow. Use plain language where possible. Break up long paragraphs. Use bullet points. Highlight action items. Remove unnecessary detail unless it’s truly essential.

3. Check for Understanding

When possible, ask clarifying questions to confirm the message landed as intended. That might mean ending a message with, “Does that make sense to you?” or “Would you like me to walk through that again?” It might also mean watching facial expressions or tone of voice in real-time conversations. If you’re getting blank stares or one-word replies, it might be time to rephrase.

4. Use the Right Medium

Some messages are fine over email. Others—especially those involving nuance, emotion, or high stakes—are better delivered via voice or video. Asynchronous messages are efficient, but they lack tone and immediate feedback. Choose your channel thoughtfully. Depending on the nature of the message, consider asking the other person for their preferred medium.

5. Be Mindful of Your Tone

Tone isn’t just about what you say—it’s about how it comes across. Written messages, especially, are prone to being misinterpreted. A sentence you intend as neutral might come across as annoyed or sarcastic. Before hitting send, read your message aloud and ask yourself how you’d feel receiving it.

---

Communication in the Workplace and the 5 Principles of IT Customer Service

The five principles of IT customer service—technical competence, compassion, empathy, good listening skills, and treating others with dignity and respect—are directly tied to communication.

• Technical competence helps you explain complex issues accurately.
• Compassion and empathy help you frame your message in a way that supports the person receiving it, especially when the message involves frustration or bad news.
• Listening skills are crucial for understanding what the other person truly needs before you respond.
• Dignity and respect show up in your tone, word choice, and attitude.

These principles remind us that communication is not just a transfer of information—it’s an act of service. Whether you’re talking to a user, a teammate, or a vendor, how you communicate reflects your professionalism and your commitment to working well with others.

---

Communication Breakdowns: What Happens When We Drop the Ball

When communication fails, it creates a ripple effect. Projects get delayed, systems stay broken longer, teammates get frustrated, and customers lose confidence. In The Compassionate Geek, I discuss how technical work depends on relationships—between teams, between departments, and between providers and clients.

One unclear message can undo weeks of hard work. It’s not just about efficiency. Poor communication can damage morale, trust, and even career growth. On the flip side, being known as someone who communicates clearly, thoughtfully, and effectively is a huge professional asset. It builds credibility and strengthens every relationship you have on the job.

---

What About the Receiver?

Of course, the person receiving the message plays a role, too. They have to be open, attentive, and willing to ask questions if they’re unclear. But as the sender, you can’t assume that will always happen. People are busy, distracted, or afraid to admit they don’t understand. That’s why it’s so important for you to lead with clarity, empathy, and intentionality.

Put simply: if your message didn’t land, it’s on you to fix it.

---

Final Thoughts on Communication in the Workplace

If you work in IT, your technical skills are important. But your ability to communicate—clearly, respectfully, and thoughtfully—has just as much impact on your success. Whether you’re working with a user who’s locked out of their account or collaborating with a cross-functional team on a product launch, your words matter.

Own your message. Make it your job to ensure your audience understands what you’re saying. That’s what real communication is—and it’s what separates the good from the great in the tech world.

You don’t have to be a natural-born communicator to do this well. You just have to care enough to take responsibility.

🔑 5 Key Takeaways: Communication in the Workplace for IT Professionals

1. Successful communication means shared understanding.

It’s not enough to just deliver a message—you need to ensure the other person receives it the way you intended.

2. The sender owns the outcome.

As the communicator, it’s your job to be clear, choose the right medium, and confirm that your message landed. If there’s a misunderstanding, the responsibility starts with you.

3. Technical knowledge isn’t enough—people skills matter.

Your expertise is powerful, but how you explain and relate to others matters just as much. Communication is a core part of IT professionalism.

4. The 5 principles of IT customer service are also communication principles.

Use technical competence, compassion, empathy, good listening, and respect to guide every conversation—whether it’s with users, teammates, or leadership.

5. Every message is an opportunity to build trust.

Clear, respectful communication strengthens relationships, prevents confusion, and shows that you care—not just about the work, but about your fellow humans who are involved.

Next Level IT Customer Service Training

Enroll your team now in Compassionate Geek IT online customer service training so they can work together, get things done, and take care of customers.