Clear Communication Skills

In my 14yrs career in engineering working for Big Tech companies such as Google and Uber, there is no other skill I used more than writing. And no, I don’t mean writing code. I mean English writing. Emails, Design Docs, Presentations, Feedback, Code Reviews, you name it. Here's how I make my written communication clear, effective, and punchy. 👇 Written communication can sometimes be daunting, especially for non-native speakers—like me. That’s why I wanted to share  the 6 questions that I use when writing anything. This helps me communicate more effectively and connect with my audience better. 1. Who is my target audience? Identify the specific group or individuals you are speaking to. Knowing your audience assists you in customizing your writing to meet their requirements and interests. 2. What is my main objective or purpose? Clarify the primary goal of your writing. Whether it's to inform, persuade, entertain, or educate, knowing your objective guides your content. 3. What key points do I want to convey? Identify the main idea or key points you want to communicate. This will help you stay focused and make sure your message is clear and logical. 4. Why should the reader care about this? Consider the value or benefit your writing offers to the reader. Highlight how it addresses their needs or solves a problem. 5. Is my writing clear, concise, and organized? Make sure your content is clear and easy to understand. Keep the flow logical and avoid using complex language or jargon that might confuse the reader. 6. Can I make my writing shorter? The answer is always yes. So make sure to edit edit edit. Brevity saves time for both the writer and the reader. What else would you add to this list? How does your writing process look like? ♻️ Please repost if you found this useful

The difference between a good design doc and a great one is usually clarity. Technical writing should be crisp and to the point. So, it is always better to treat every sentence like it has a cost. After writing, cut aggressively. Remove extra words. Then check if a line can go. Sometimes even a full paragraph is unnecessary. One thing I always do is to start the doc with the conclusion; this way, the reader/reviewer knows where we are heading. This is contrary to how most engineers write docs - listing every approach first and only concluding at the end. That slows readers down. I avoid this because long explanations make people lose track; most readers want the conclusion quickly. So, always start with the answer and why it matters. Then add details and alternatives below for those who want depth. A habit that helps is a quick editing pass like this: - Remove filler words and repeated ideas. - Break long sentences into smaller ones. - Prefer bullets when listing options or steps. - Check if the first section clearly states the outcome. - Add a link or short explanation where a reader may pause. Empathy matters more than most people realize. Try to read your document as someone new to the topic. Ask yourself what might confuse them. Add the missing context. Add the helpful link. Let the ideas evolve naturally from problem to solution. This skill develops over time. Use simple language and fewer buzzwords. The goal is to communicate, not impress. Simple documents get read more. More readers means better alignment and better visibility for the work. Finally, always provide enough context. A short setup about the problem, constraints, and prior decisions goes a long way. It helps readers understand why the decision exists, and, of course, it prevents unnecessary back and forth later. Hope this helps.

You can learn a company’s real values in one meeting. Not from the posters. Not from the mission statement. From the behavior leadership tolerates. I’ve seen leadership teams spend months rewriting company values… …while ignoring toxic meetings, defensive managers, and inconsistent accountability. That’s why culture is rarely built during offsites. It’s built in ordinary moments repeated every day. Here are 8 ways strong leaders reinforce culture consistently: 1️⃣ Start meetings with clarity. ↳ Confused teams create politics. ↳ Clear priorities create momentum. 2️⃣ Reward honesty early. ↳ If employees speak up and leadership becomes defensive, honesty disappears fast. 3️⃣ Address toxic behavior quickly. ↳ High performance should never buy someone permission to disrespect others. 4️⃣ Make listening visible. ↳ Repeat back feedback. ↳ Ask follow-up questions. ↳ Show employees they were actually heard. 5️⃣ Normalize disagreement. ↳ Strong cultures can handle tension without making people feel unsafe. 6️⃣ Model emotional consistency. ↳ Teams absorb the emotional habits of leadership faster than leaders realize. 7️⃣ Keep standards consistent. ↳ Trust disappears when accountability changes based on seniority or politics. 8️⃣ Audit your meetings regularly. ↳ Ask yourself: • Do people feel safe contributing? • Are quieter voices included? • Does leadership behavior match the stated values? Because culture is not what leadership says. Culture is what employees experience repeatedly. And over time… that becomes the company people either trust or quietly leave. ___________ ♻️ Repost to remind leaders that employees watch actions more than words. 👋 Follow me (Dr. Chris Mullen) for one practical idea each week to build better habits, strengthen your leadership, and live with more intention. Join 140K+ leaders who read my BETTER AT LIFE newsletter: https://lnkd.in/gJTcghKK

I used to believe that being assertive meant being aggressive. The reality is that you can both assert yourself and be kind. 5 proven tips to be more assertive (without being aggressive): 1/ Express your needs and wants clearly Why: Being direct and honest about your needs helps others understand your perspective and enables them to respond appropriately. It demonstrates self-respect and confidence in your own opinions and feelings. How: "I appreciate your input on this project, but I strongly believe we should take a different approach. Focusing on user experience will lead to better conversion. Can we discuss how we can incorporate both of our ideas?" 2/ Use "I" statements to communicate your perspective Why: "I" statements help you take ownership of your thoughts and feelings without placing blame or making accusations. They create a non-confrontational atmosphere that encourages open dialogue and mutual understanding. How: "I appreciate the effort you've put into this presentation, but I have some concerns about the accuracy of the data. I suggest we review the sources together and make any necessary updates to strengthen our case." 3/ Practice active listening and seek to understand others Why: Active listening demonstrates that you value others' perspectives and are willing to engage in a two-way conversation. It helps build trust and rapport, making it easier to find mutually beneficial outcomes. How: "I hear your concerns about the proposed changes to our team structure. Can you tell me more about how these changes will impact your work? I want to ensure that we address any potential issues." 4/ Offer solutions Why: Offering solutions rather than simply stating problems demonstrates your willingness to work collaboratively and find mutually beneficial outcomes. How: "I understand that you want to launch the new feature as soon as possible, but I have concerns about the current timeline. What if we break the launch into two phases? We can release the core functionality in the first phase and then add the additional enhancements in the second phase. This way, we can meet the initial deadline while ensuring the quality of the final product." 5/ Learn to say "No" when necessary Why: Saying "no" to unreasonable requests or demands demonstrates self-respect and helps you maintain control over your time and resources. It also helps prevent burnout and enables you to focus on your priorities. How: "I appreciate you considering me for this new project, but unfortunately, I don't have the capacity to take on additional work at the moment. I'm committed to delivering high-quality results on my current projects, and taking on more would compromise this. Can we revisit this opportunity in a few weeks when my workload is more manageable?" What’s one thing that helped you become more assertive? PS: Assertiveness is a form of self-care that also nurtures healthy, respectful relationships with others. Image Credit: Jenny Nurick

Communication isn't what you say. It's what everyone hears. And not just what they hear passively. But what action your words inspire in them. If you're leading a team, remember: • 90% of your team didn't hear you the first time • 50% didn't hear you the third time • 10% never will Clear communication requires repetition. When you're sick of saying it, they start to hear it. Here's the pattern the best communicators follow: 1. Create Systems Don't rely on one-off conversations. Build processes that reinforce the message consistently. Different formats for different learners. 2. Embrace Repetition Clarity requires persistence, not perfection. Say it again. Then say it differently. Then say it again. 3. Verify Understanding Check what was heard, not what was said. Ask: "What did you take away from that?" Create feedback loops that close the gap. Here's how the world's best leaders put these patterns into practice: Satya Nadella's "Model-Coach-Care" ↳ Shows the way personally first ↳ Coaches others through the change ↳ Demonstrates genuine care for outcomes "Don't be a Know-It-All. Be a Learn-It-All." Ray Dalio's "Radical Transparency" ↳ Records every meeting at Bridgewater ↳ Makes them available to all employees ↳ Uses real-time feedback tools "Lead discussions by being assertive AND open-minded. At the same time." Andy Grove's "Disagree and Commit" ↳ Encouraged vigorous debate before decisions ↳ Required full alignment after decisions ↳ Made dissent safe, but execution non-negotiable "Let chaos reign, then rein in chaos." Steve Jobs's "Three-Story Rule" ↳ Every product launch told three stories maximum ↳ Repeated the same core message relentlessly ↳ Made complex ideas simple and memorable "Simple can be harder than complex." Reed Hastings's "Context Over Control" ↳ Netflix's culture deck shared widely for transparency ↳ Attracts the right people before they even apply ↳ Replaces rules with shared understanding "Don't tolerate brilliant jerks. The cost to teamwork is too high." The best leaders aren't the best speakers. They're the best at being understood. And they never stop until they are. 🔔 Follow Dave Kline for more leadership insights. ♻️ Share to help other leaders communicate with impact.

I spent the first 5 years of my career thinking I was being polite. In reality, I was undermining my worth: "Sorry, can I just ask..." "I might be wrong, but..." "This is probably a dumb question..." Sound familiar? I was sabotaging my own authority — and didn't even realize it. 🥲 Your words tell people how to treat you. And the language that feels “polite” early in your career can quietly hold you back later. Here are 7 phrases that make you sound junior (and what leaders say instead): 1️⃣ "Sorry to bother you..." Say instead: "Do you have 5 minutes to discuss X?" Leaders value their time and yours. Be direct. 2️⃣ "I think maybe we should..." Say instead: "I recommend we..." Own your expertise. You were hired for your judgment. 3️⃣ "Does that make sense?" Say instead: "Happy to answer any questions." Assume clarity. Let others flag confusion if needed. 4️⃣ "I'm not sure if this is right..." Say instead: "Based on my analysis..." Make a confident recommendation based on the information you have. 5️⃣ "Just a quick thought..." Say instead: "I've been thinking about X and here's my take..." Take out unnecessary qualifiers. 6️⃣ "Ugh so sorry for the delay..." Say instead: "Thanks for your patience!" Turn apologies into appreciation. It changes the entire dynamic. 7️⃣ "I'll try to get it done..." Say instead: "I'll have it to you by [date]." Trying is hoping. Committing builds trust. Start speaking like the leader you want to be. ✨ Which phrase are you guilty of overusing? * * * * * * 👋 I'm Lorraine—keynote speaker and bestselling author. I help rising leaders build an unforgettable presence and stand out at work. Follow for more actionable career tips! ♻️ Reshare if this resonated with you! 📘 PS: Want more communication scripts that command respect? Check out my book, 𝙐𝙣𝙛𝙤𝙧𝙜𝙚𝙩𝙩𝙖𝙗𝙡𝙚 𝙋𝙧𝙚𝙨𝙚𝙣𝙘𝙚: https://amzn.to/3Hdv79r

🎨🖊️ "Draw two circles under a rectangle…" "Now, make the circles connect to the rectangle" - some of the instructions that were given to me by our Head of Architecture during a recent offsite. We engaged in an exercise that underscored the importance of clear and effective communication. Each participant paired up, with one partner facing a screen displaying an image and the other facing a blank wall with a pen and paper. The challenge? The partner facing the screen had to guide their teammate in drawing the image using only directional and descriptive language. This exercise was a powerful reminder of how crucial it is to be clear, descriptive and thoughtful when sharing requirements, feedback or instructions. In the world of technology, we often fall into the trap of using complex language, acronyms, and omitting details we assume are "obvious." This can lead to confusion, misunderstandings, rework, and ultimately, wasted time. The key takeaway? Being specific doesn't always mean being overly detailed or long-winded. There's a beautiful balance between being specific and descriptive. It's about conveying the right amount of information in a way that's easily understood. Here are some common pitfalls to avoid when striving for specificity in communication: - Overloading with Details: Focus on the most relevant information to avoid overwhelming your audience. - Using Jargon and Acronyms: Consider your audience and provide explanations when necessary. - Assuming Shared Knowledge: Provide necessary context to ensure understanding. - Being Vague: Use precise language to prevent misunderstandings. - Neglecting the Audience's Perspective: Tailor your communication to the needs and understanding of your audience. I am reminded of a quote by Mark Twain: "I apologize for such a long letter - I didn't have time to write a short one." Concise communication takes time and effort, but it's always worth it. In our fast-paced world, mastering the art of effective communication is essential. It not only enhances collaboration but also drives efficiency and innovation. #Communication #Leadership #EffectiveCommunication

Stop justifying your boundaries. “No” is not rude. It’s how you protect your time, energy, and sanity. I used to be available for everything: 6 PM “quick fixes” that turned into 90-minute tasks. Weekend messages that killed any chance of rest Not because I didn’t have boundaries, But because I didn’t know how to communicate them. Here are 12 boundary-setting phrases I wish I had used sooner: 10  Phrases That Say “I’m not available for that” - without burning bridges: "That doesn’t work for me—here’s what does." → Assertive, clear, and solution-focused. "I’m offline after 6 PM. Let’s revisit this in the morning." → You set the availability, not your inbox. "Let me check my schedule and get back to you." → Creates space to decide without pressure. "I’m happy to help. What should I deprioritize to take this on?" → Makes the tradeoff visible. "I’ve blocked 30 minutes for this call." → Time-caps your energy before others overrun it. "I can help with this part, but not the whole thing." → Protects your bandwidth while still being useful. "Let’s schedule this properly—I want to give it the attention it deserves." → Turn chaos into structure. "I’ve learned I don’t do well with last-minute requests." → Share the why without over-explaining. "Let me get back to you by [time] after I think it through." → You’re not obligated to answer instantly. "That’s outside my zone—but here’s someone who might be a better fit." → Say no, and still be a connector. You don’t need to be aggressive to be clear. You don’t need to explain your “no” to make it valid. Boundaries are a business skill. Use them like one. Save this. Read it again the next time someone tries to rush your yes.

I learned this one the hard way: leadership starts with clear communication. I remember a project where the problem started with me. I wasn’t clear enough upfront, and it led to confusion, misaligned expectations, and frustration. It didn’t stop there—it spiraled into extra emails, more meetings, and way too much time trying to sort it all out. Worst of all, it damaged relationships within the team. That experience was a wake-up call. I realized my communication needed structure, so I started using the “Why, What, How” framework to turn things around: 1️⃣ Why: Explain the purpose behind the project and why it matters. 2️⃣ What: Be clear about expectations and deliverables. 3️⃣ How: Give actionable steps and clarify roles. The shift was immediate. With clear communication, the team felt aligned, work flowed smoothly, and we rebuilt trust. Leadership communication isn’t just about saying the right things—it’s about giving your team the clarity they need to move forward confidently. How do you keep your communication clear and effective as a leader? #Leadership #Communication #TeamAlignment #IntentionalLeadership

Speaking Tech and Human: Why Every Team Needs a Communication Chameleon Ever been in a meeting where it feels like everyone's speaking a different language? Not in the literal sense, but in that "tech jargon vs. human speak" kind of way. It happens all the time, especially in cross-functional teams. Engineers, with our love of acronyms and complex terminology, can sometimes leave non-technical folks feeling lost in the weeds. I recently witnessed this firsthand. Picture a late-night meeting about an upcoming AI launch. The tension is high, the deadline is looming, and suddenly, someone asks a seemingly simple question: "So, what exactly is an IDE?" The engineer on the call launches into a detailed explanation, complete with references to command-line interfaces. It's like trying to explain astrophysics to someone who just learned the alphabet. This is where we TPMs (or anyone with a knack for both tech and "human speak") come in. We're the interpreters, the bridge-builders, ensuring everyone's on the same page. In that late-night meeting, I jumped in with a simple explanation: "An IDE is basically the tool where developers write and test their code. It's like a word processor for software." Problem solved! The question-asker got the gist, the engineer learned a valuable lesson about audience-focused communication, and we all got a little closer to hitting that launch button. Key takeaways for clearer tech communication: - Know your audience: Tailor your explanations to the listener's technical understanding. - Focus on the "why": Explain the impact and benefits, not just the technical details. - Keep it simple: Avoid jargon and acronyms whenever possible. - Use analogies (when appropriate): Relate complex concepts to everyday experiences. Effective communication isn't about showing off your technical expertise, it's about building a shared understanding and achieving goals together. And in a world where tech is increasingly intertwined with every aspect of our lives, the ability to translate "tech-speak" into "human-speak" is more important than ever. Have you ever witnessed a "lost in translation" moment in tech? Share your stories in the comments! 👇 #TPMlife #TechLeadership #Google #LifeAtGoogle