#31 Do people understand you when you speak about the technical details of your work?
A lot can go wrong when you use technical terms with team members who don't have the same technical depth. Here's what to consider.
Photo by Mimi Thian on Unsplash
Imagine you're an engineer. You need to talk to designers about technical limitations that prevent you from implementing their new design ideas. Or perhaps you need to discuss unclear use cases with the product manager to better understand the goals. Sometimes, you might even have to give status updates to the C-suite.
In these scenarios, you might use technical terms and dive deep into complex issues that others may not understand. Translating what’s common knowledge for us to those who aren’t specialists in the same field is tough.
And this isn’t just a problem for engineers.
Product Managers: You need to share relevant information about product evolution in a clear, actionable way for everyone involved.
Data Analysts: You need to present experiment results without jargon, so non-data specialists can understand and use your findings in UX research, marketing, business, etc.
UX Researchers: You need to explain your research methodology clearly, ensuring that everyone understands why certain sample sizes or unbiased questions are crucial for high-quality user feedback.
Here are some questions to consider when communicating with someone outside your specialty:
1. What’s the ONE Thing You Want the Non-Technical People to Understand?
Maybe all those technical details you’re about to share aren’t necessary for the other person to understand your message and give their input. When reviewing your communication, identify what technical information is essential for context and what might be confusing or irrelevant.
2. How Can You Simplify the Necessary Technical Information?
Writing simply is challenging, especially when your background is different from those whose work is interdependent. Here's a tip: Use examples. Explaining technical concepts with simple language and relevant examples helps others grasp the scope of your conversation.
3. How Can You Explain the Why Behind Decisions to Non-Technical People?
Your technical expertise helps you do your work, but it’s not the only reason for your decisions. Subjectivity, like taking calculated risks or following intuition, also plays a role. Being transparent about your reasons in non-technical terms can help your collaborators understand and appreciate your decisions.
What are your thoughts? I’d love to hear your perspective. Feel free to ping me!
👋🏽 I’m Mel...
I coach tech professionals and help them take meaningful actions based on self-awareness. Say hi on LinkedIn to find out more and join the waitlist.