So You Want Better Communication
Most people approach this completely backwards. They read books about speaking, join improv classes, and practice presentations alone in front of mirrors. Then they get in a room with actual stakeholders and their brain goes blank anyway. The disconnect comes from treating communication like a performance skill instead of a coordination tool. I learned this the hard way about eight years ago when I was leading a technical migration for a healthcare client. I spent two weeks preparing what I thought was a crystal-clear risk assessment document. The project manager called it "interesting" and we lost three months because she was still confused about the timeline. We were speaking the same language but using entirely different definitions for words like "risk" and "phase." The activities that matter fall into two buckets. The first is structured feedback loops where you learn what other people actually hear instead of what you meant. The second is constraint-based exercises that force you to communicate efficiently under pressure. Here is what I have seen genuinely move the needle. Start with the simplest one: the five-minute explain-back. You tell someone about a task or concept, then hand them the floor and ask them to explain it back to you in their own words. Not paraphrase. Explain it back. I do this with junior engineers when they are assigned a ticket, and it catches misunderstandings before they become six-hour debugging sessions. Most people think they understood something when they actually absorbed about sixty percent of it. The gap between what you said and what they heard will surprise you every single time.
Then there is the silence drill. Pick a topic you know well and give a three-minute explanation without using any of the following: filler words, jargon, or self-corrections. You can say what you mean but if you realize you used a term and decide not to rephrase it, you stop and restart. I know this sounds painful because it is painful. I remember running this exercise during a team meeting once and freezing at word one hundred and fourteen because I almost said "synergy" as a filler concept and caught myself. The room was dead silent. Nobody was taking notes. Nobody was looking at their phones. Just listening. It was the most uncomfortable thirty minutes I have ever done professionally and probably the most useful communication practice I have ever assigned anyone. Active listening training is another one people get wrong. They think it means nodding and saying "I see." It does not. It means repeating back the structure of what someone said before you respond with your own view. Here is the exact format that works: "So what you are saying is X, because of Y, and you are concerned about Z. Did I miss anything?" Say that before you offer a single counterpoint. Ninety percent of conflicts evaporate because the other person finally feels heard. The remaining ten percent are real disagreements that need to be worked through. For a more advanced exercise, try the stakeholder translation game. Take a technical decision your team made and write it three ways: one for executives, one for other engineers, and one for a complete outsider who has never used software in their life. Each version should be roughly one paragraph. This forces you to understand what the core message actually is versus what you assumed everyone already knew. I wrote an executive summary once that came out to twelve pages because I had no idea how to compress it. My manager edited it down to four sentences and the board approved the budget that afternoon. Twelve pages to four sentences. That was the lesson.
Role reversal is brutally effective. Have a colleague argue your position while you defend theirs, then switch. You need to genuinely understand the other side to communicate effectively across it. This is not groupthink. It is strategic empathy. I did this with a product manager who thought engineers were being stubborn about timelines, and an engineer who thought product managers were being reckless about scope. After twenty minutes of switching seats, both of them admitted something they had not realized: the product manager knew the engineering concern was valid but felt pressured by external deadlines, and the engineer knew the timeline was tight but felt nobody asked about technical debt anymore. The conversation that followed was normal. Productive. Done in an hour instead of three weeks of email threads. One thing nobody tells you about building communication skills is that written and spoken are almost entirely different competencies. The activities above help with both, but they do not automatically transfer. When I started doing these exercises, I was still writing ambiguous status updates that required three follow-up emails to clarify. The breakthrough came when I started treating written communication with the same constraint discipline. Every message I send now follows a simple template: what I need, what I am doing, what I need you to do, when I need it by. Four lines. That is it. It cut my internal meeting load by roughly forty percent over six months because most people do not need to talk about the work. They need to know what is happening and what they are responsible for. Here is a limitation that most guides ignore. These activities help you communicate better with people who are already cooperative and engaged. If you are dealing with someone who is actively resistant, hostile, or operating in bad faith, none of these techniques will reliably change the outcome. I ran into that exact scenario with a vendor who was deliberately vague about delivery dates for eighteen months. No amount of active listening, role reversal, or structured feedback loops helped. The workaround was to remove the communication entirely and shift to written contractual obligations with specific milestones and automatic penalties. Sometimes clear communication is realizing you need less of it and more documentation. There is no shame in that. There is efficiency in it.
Get the Full Details
Another counter-intuitive point: brevity is not a substitute for precision. People hear "be concise" and start stripping away necessary context. You might remove two paragraphs of background and end up causing confusion that takes three meetings to untangle. The difference is knowing what context the other person needs based on what they already know. A senior engineer needs different contextual framing than a junior one explaining the same system. Test this by asking a straightforward question before you launch into an explanation: "What do you already know about this?" The answer changes everything about how you communicate next. If you want a practical weekly routine, here is what I recommend and what has held up. Monday: one five-minute explain-back session with someone on your team. Wednesday: write one piece of communication (email, doc, post) and cut it in half without losing any actionable information. Friday: do a quick role reversal on whatever disagreement or friction point is alive that week. Twenty minutes total across the week. It sounds trivial. It is not. Consistency matters more than intensity for this kind of skill development. You are rewiring habits that probably took years to form. The broader point is that Activities To Develop Communication Skills is not about performing better in conversations. It is about reducing the gap between what you intend and what another person actually receives. That gap is where projects stall, budgets blow up, and good ideas die. Closing it is mostly unglamorous practice and occasional uncomfortable silence. The results show up quietly over time instead of all at once.
