{"id":212,"date":"2009-11-10T16:19:00","date_gmt":"2009-11-10T16:19:00","guid":{"rendered":"https:\/\/anne.myupcomingsite.com\/jargon-buster-6-ways-to-get-past-techno-speak\/"},"modified":"2013-08-06T15:45:57","modified_gmt":"2013-08-06T15:45:57","slug":"jargon-buster-6-ways-to-get-past-techno-speak","status":"publish","type":"post","link":"https:\/\/anne.myupcomingsite.com\/?p=212","title":{"rendered":"Jargon Buster: 6 Ways to Get Past Techno-Speak"},"content":{"rendered":"<p>Ever tried to get an engineer to explain a company\u2019s newest product or solution to a lay audience?<\/p>\n<p>It can be frustrating. A lot of technical people have difficulty stepping back and speaking clearly outside their universe \u2013 whether it is the latest gadget for in-flight connectivity or software for supply chain logistics. But, as high-tech communicators, we serve as a bridge between the no-man\u2019s land of nanotech speak, and the company\u2019s mainstream audience of business decision makers, investors and non-technical staff.<\/p>\n<p>How do you pull the necessary detail from a technical source and still get the big picture across? Geek speak is confusing to both casual online perusers and the more targeted business readers.<\/p>\n<p>Here are six tips for minimizing techno-speak in news releases, marketing materials and website copy &#8212; mastered in 17 years crafting copy in the high-tech world:<\/p>\n<p>1. Get more than one viewpoint. Ideally, sit down with both the technology and marketing sources so you can ask questions a different way and get varying perspectives.<br \/>\n2. Always bring it back to the customer \u2013 what customer problem does our technology, service or product solve? Tell a story.<br \/>\n3. Bring in the competition &#8211; ask what differentiates our breakthrough, product, solution or service from what is already out there. You may be pleasantly surprised by what you learn.<br \/>\n4. Resist using in-house techno-speak &#8212; especially acronyms that are only known to IEEE members. Your job is to grab readers with a simple, succinct description that they can understand without scratching their head. Ask your expert (and yourself): \u201cIs there a simpler way to say this?\u201d<br \/>\n5. Use numbers and other comparison language &#8212; for example, when talking about the speed or throughput of a data product,instead of stating the megabits per second, try a reference that your readers will understand: &#8220;DSL-like speeds two times faster than the current product.&#8221;<br \/>\n6. Seek third-party credibility \u2013 can you get a customer or an industry expert to comment on the solution? Including their perspective can carry a lot more weight than relying just on company sources.<\/p>\n<p>A final thought &#8212; if you face a stumbling block as you de-jargon and simplify the message, seek inspiration and advice from other wordsmiths. Visit the Visual Thesarus, a handy resource that provides word associations in a cool visual format that encourages out-of-box thinking:<br \/>\nhttp:\/\/www.visualthesaurus.com\/. The blog commentary on the site alone is worth a look, including a guest Writers Talk About Writing column. Check out a post on Nov. 5 called &#8220;Microspeaking&#8221; by Mike Pope, a technical editor at Microsoft, who discusses some of the quirky jargon that has emerged at the software behemoth: http:\/\/www.visualthesaurus.com\/cm\/wc\/2058\/.<\/p>\n ","protected":false},"excerpt":{"rendered":"<p>Ever tried to get an engineer to explain a company\u2019s newest product or solution to a lay audience? It can be frustrating. A lot of technical people have difficulty stepping<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[659,658],"class_list":["post-212","post","type-post","status-publish","format-standard","hentry","category-writing-tips","tag-eliminating-jargon-in-writing","tag-simplifying-your-writing"],"_links":{"self":[{"href":"https:\/\/anne.myupcomingsite.com\/index.php?rest_route=\/wp\/v2\/posts\/212","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/anne.myupcomingsite.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/anne.myupcomingsite.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/anne.myupcomingsite.com\/index.php?rest_route=\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/anne.myupcomingsite.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=212"}],"version-history":[{"count":1,"href":"https:\/\/anne.myupcomingsite.com\/index.php?rest_route=\/wp\/v2\/posts\/212\/revisions"}],"predecessor-version":[{"id":835,"href":"https:\/\/anne.myupcomingsite.com\/index.php?rest_route=\/wp\/v2\/posts\/212\/revisions\/835"}],"wp:attachment":[{"href":"https:\/\/anne.myupcomingsite.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=212"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/anne.myupcomingsite.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=212"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/anne.myupcomingsite.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=212"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}