U.S. flag

An official website of the United States government

Dot gov

The .gov means it’s official.
Federal government websites often end in .gov or .mil. Before sharing sensitive information, make sure you're on a federal government site.

Https

The site is secure.
The https:// ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.

Skip to page content

5 Tips for Communicating Technical Information: iPad Pilot

“The difference between the right word and the almost right word is the difference between lightning and the lightning bug.” — Mark Twain

It’s simple—you’re the technical expert; you know the topic inside out, so of course you can easily explain it to a captive audience. Right? Not always.

Communicators in every industry know that message development matters. External audiences, internal audiences and stakeholders of all kinds need clear information about your services, benefits and products.

However, government communicators can have an added challenge. Internal and external stakeholders with varying degrees of technical expertise often weigh in to review messages and provide input. It’s essential for you, as the professional communicator, to coach your team to focus on the value of the technology, rather than the technology itself, when it comes to messaging.

This summer, the Department of Veterans Affairs (VA) provided iPads to 1,000 family caregivers of post 9-11 veterans as part of the year-long VA Mobile Health Pilot that will test 10 mobile apps designed to help caregivers manage stress and the health and well-being of the veterans they assist.

A critical part of the pilot phase has been ensuring that all of the participants understand how to use the technologies they are helping to test. This can be a challenge as participants come from all walks of life—from individuals who have never used a mobile device to those who are tech-savvy.

As the communications lead on the project, I learned five valuable lessons in communicating technical information to a largely nontechnical audience:

  1. Be sure you can articulate your communications goals. We continuously go back to answer the question “What are we trying to accomplish?” It is a balancing act of trying to keep our internal team focused on the big picture communication goals while keeping the technical details in plain English to be understood by our nontechnical audiences. The critical piece is keeping conversations about communications focused on the big picture rather than getting stuck in the weeds regarding the technology’s functionality. Being comfortable with our communications end-goal allows us to keep everyone internally on the same page.

  2. Know your audience. We don’t mean identifying stakeholders. We mean…Know Them! What makes them tick! Understand their comfort level with technology. How do they prefer to receive news and information, when is the best time to communicate with them and why are they involved with your program? At VA, we work directly with our Caregiver Support team, which is responsible for knowing our caregivers and their needs. They have helped us identify tone, style and frequency of the messages being disseminated to our caregivers and other audiences.

  3. Structure your messages. Some communicators use message maps and others use message boxes. We structured messages in buckets so we could address our internal and external stakeholders. Our buckets include Vision, Value, Need to Know, and Calls to Action. This approach allows us to work from the same template and, as new apps are developed, think through—What is most valuable to veterans and their caregivers as well as health care teams.

  4. What’s in it for me. Sometimes it’s easy to lose sight of the larger goal amidst the arduous vetting and approvals of what we as communicators do in the federal government. Making sure that every message is associated with a value to veterans, caregivers or clinicians helped us focus on the essential components.

  5. Be responsive. Ours was a pilot program and issues pop up. As they do, we work with our IT team to minimize the impact. We inform our help desk, update our website and develop easy-to-understand communications translating the current IT challenges and providing solutions as they are available.

Originally published on the on the Federal Communicator’s Network Blog.

Tags: ,

GitHub LogoEdit
Top