| By Loraine Antrim | Article Rating: |
|
| August 12, 2009 06:15 AM EDT | Reads: |
3,278 |
As an IT professional, you talk about IT issues all the time. But when you speak to a business crowd, well… it can sometimes be very challenging, to say the least.
Welcome to the communication dead zone (CDZ for acronym aficionados). Your non-technical listeners don't have a clue what you're talking about. You've forced them to tune out and shut down, and once they fall into the CDZ, it's very very hard to pull them back.
CDZ Causes
In most cases, we put listeners in the CDZ by merely communicating like IT folks. We just forget that when we say, "networking" our audience automatically imagines chatting with colleagues over wine and cheese, or if we say, "AJAX" our listeners think of an abrasive bathroom cleanser.
What else do IT professionals do to put up communication barriers?
1. We use acronyms like CRM, SaaS, SOA, ERP, Five nines, ADSL, TAPI, BAPI and API. Whew! We just assume the audience knows what we are talking about. We say SMB and think, "Server Message Block" but our audience is thinking, "Small to Medium Sized Business."
2. We'll explain complex ideas with other complex ideas: "Cloud computing is a pool of abstracted, highly scalable, and managed compute infrastructure capable of hosting end-customer applications and billed by consumption." No wonder eyes glaze over!
3. We'll talk about cause and effect without an adequate explanation. We assume the listener gets the association and everyone has an IT background. "As you are all aware, the packet loss can cause considerable performance issues." That might compute for CCIEs, but your business listener is thinking, "What kind of performance issues? Will I still get my email"?
So what are some communication best practices we can put in place to keep listeners in their seats and out of the CDZ?
CDZ Remedies
1. Use simple analogies and explanations. What if you were trying to explain digital video and how data must travel in a continuous stream in order to avoid losing frames during the video capture and playback process?
Why not try: "Think of your video capture card as throwing lots of baseballs and your hard drive is the catcher that must catch them all. If the video card starts throwing more balls than your catcher can catch -- then balls are going to be dropped. That's what's happening as data is pumped into your system and your drive must have enough "hands and catcher's mitts" to avoid dropping frames and data." Simple analogies like this can make all the difference between comprehension vs. confusion.
2. Kill the Acronyms. Never assume your audience understands your acronym. You can use an occasional acronym, but play it safe and right away parenthetically explain it.
3. Provide background or context. Especially for business listeners, give a short history of the project you're talking about. And when describing a technical situation, frame it with a bit of background to help anchor your ideas in some common ground. Think about talking to your mom. She's a very bright woman (after all, she has a brilliant kid in IT!) but does she really "get" Virtualization? Without talking down to the audience, provide the background, history or context so even your mom can understand it.
4. Never make assumptions. Your audience is bright and eager to hear what you have to say, but don't assume they have a level of understanding on technical issues. One of the best practices is to entertain a dialogue rather than a monologue. Whether you're communicating to a small group internally or a large crowd at a conference, periodically take the pulse of the audience: simply ask a question. "How many of you think of coffee when I say, 'JAVA'?" That way you'll always stay on the same plane.
5. Examples, examples, examples! You can't underestimate the power of examples. Throughout our schooling, we had teachers who were really good at explaining obtuse concepts, and they used examples to bridge the learning gap. Take a page out of their teaching manual and offer up real-world examples of what your technology can DO for the clerk at his desk or the administrator in her meeting. "For example" are he two most powerful words in your communication arsenal.
Ultimately, the Communication Dead Zone exists in almost every profession. But for IT, it can be a real dilemma. Shut the Zone down by keeping your audience in mind, respecting their intelligence and guiding them through your concepts. Then you won't be asking, "Can they hear me NOW?" You'll be stating, "Now they CAN hear me!"
Published August 12, 2009 Reads 3,278
Copyright © 2009 SYS-CON Media, Inc. — All Rights Reserved.
Syndicated stories and blog feeds, all rights reserved by the author.
More Stories By Loraine Antrim
Loraine Antrim is co-founder of Core Ideas Communication, a communications consulting agency focused on presentation development and media training for C-suite executives. Core Ideas enables executives to package and communicate relevant and compelling messages in their presentations and interviews. Loraine's expertise is killing butterflies. You know, butterflies: the feeling in your stomach before you have to present or speak in public. Loraine works with executives to create a powerful story, memorable messages and an authentic delivery style. Confidence kicks in, and butterflies scatter. Nice work killing butterflies! You can contact Loraine at: manager at coreideas.com
- It's the Java vs. C++ Shootout Revisited!
- Patterns for Building High Performance Applications
- Asynchronous Logging Using Spring
- Java for Programmers (2nd Edition)
- Cross-Platform Mobile Website Development – a Tool Comparison
- Three Buzzwords That Every CIO Hears but One They Should Listen To
- Write Once Run Anywhere or Cross Platform Mobile Development Tools
- Immersing into JavaScript Frameworks
- Workday Reportedly Prepping to Go Public
- Cloud Expo New York: The Java EE 7 Platform - Developing for the Cloud
- Book Review: Sams Teach Yourself Java in 24 Hours
- OpenOffice.com Lives
- Book Excerpt: Introducing HTML5
- Adobe Sends Flex to the Apache Foundation
- Five Years Waiting for JRE 7: Is It Justified? (Part 1)
- Book Excerpt: Java Application Profiling Tips and Tricks
- i-Technology in 2012: Five Industry Predictions
- It's the Java vs. C++ Shootout Revisited!
- Patterns for Building High Performance Applications
- OpenXava 4.3: Rapid Java Web Development
- The Next Web Architecture
- Asynchronous Logging Using Spring
- Java for Programmers (2nd Edition)
- Is Write Once Run Anywhere Ever Going to Be a Reality?
- A Cup of AJAX? Nay, Just Regular Java Please
- Java Developer's Journal Exclusive: 2006 "JDJ Editors' Choice" Awards
- JavaServer Faces (JSF) vs Struts
- The i-Technology Right Stuff
- Rich Internet Applications with Adobe Flex 2 and Java
- Java vs C++ "Shootout" Revisited
- Bean-Managed Persistence Using a Proxy List
- Reporting Made Easy with JasperReports and Hibernate
- Creating a Pet Store Application with JavaServer Faces, Spring, and Hibernate
- Why Do 'Cool Kids' Choose Ruby or PHP to Build Websites Instead of Java?
- What's New in Eclipse?
- i-Technology Predictions for 2007: Where's It All Headed?


















