A big barrier to communication is using language that you are familiar with but may not mean anything to your intended audience. It’s easy to fall into this trap, whether it’s the dreaded TLA’s (three letter acronyms) or technical IT terminology. Whatever the source, it makes for a one-directional conversation and often one that ultimately causes the receivers to shut down and tune out. It makes communications complicated, can leave the receiver feeling foolish because they don’t understand and may be afraid to ask for clarification. All this leads to a “threat” response – not at all the purpose of communication.
A client called today to discuss how to move a business transformation forward. They were challenged with reaching their stakeholders and getting adoption. Given it was a technical implementation it was loaded with jargon and acronyms. There was a big “AHA” here – on both our parts! Sometimes for me it takes an interaction to realize there is a nugget of value in there, so thought I would share.
So what can you do? Here are a few tips:
- Jargon check your communication. Look for acronyms and technical language that you may be comfortable with, but your receiver may not. Try it out on someone you trust who will give you feedback.
- Step back. Rather than telling your recipient about what you are going to do, start the conversation with what are their challenges? Create a conversation hook from the start. Let them lead and answer their questions.
- Frame your conversation from the business outcome perspective. How can what you will be doing help them achieve their goals and address their challenges? And…do you even know what those challenges are?
And…the definition of jargon is “gobbledygook” and “nonsense” – so it merits taking time to either remove it or get your concept across in plain, understandable language.
What other tips do you have? How do you “jargon check” your communications? Love to hear from you.
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.