Monday, August 4, 2014

Makeup of the Federal Communicators Network: Tap into a Wealth of Knowledge and Experience

Posted by: Debra Harris, FCN Leadership Team and Public Affairs Specialist at the Defense Finance and Accounting Service

Digital content management, that’s what 25% of FCN members do as their primary job function. Publishing website content, social media posts and email marketing are tasks that require members to stay abreast of the latest trends in the digital world. FCN regularly hosts training events and socials as a means to help individuals grow in these areas.

We also have members writing and editing, working with media and creating both internal and external communications for their agency. Earlier this year, 115 members answered survey questions aimed at providing the leadership team insight into the demographics of the group.

FCN is made up of employees from 54 federal agencies. Health and Human Services, General Services Administration, the US Geological Survey, Defense Department, Environmental Protection Agency, Department of Justice and the Department of Veterans Affairs to name a few.

We have members scattered throughout the United States in Seattle, Atlanta, Indianapolis and Louisville. But it’s no surprise that the majority of our members reside in the Washington, D.C., Maryland and Northern Virginia area.

Our listserv is the primary means for members to reach out and share knowledge, ask questions and engage in the community. 30% of our members have more than 20 years experience working in communications. Another 42% have between 10-20 years in the field. That’s a wealth of knowledge to tap into!

The leadership team learned that a majority of our members get FCN news from the weekly newsletter via the listserv. We have more than 1,500 Twitter followers and over 380 LinkedIn members getting our news also.

If you aren’t already reading our blog site, bookmark it to stay informed of upcoming events. There is never a cost to attend and membership is free. We’ll continue to bring training on social media, metrics, plain language and video producing as requested.

If you've missed our previous trainings, catch up with archived recordings and slides here.

Monday, July 14, 2014

Google Hangout Tech Tips

Posted by: Britt Ehrhardt, FCN Co-Chair and Technical Writer/Editor at the National Institutes of Health

The Federal Communicators Network held its first ever Google Hangout On Air last month. Members of the media joined experienced agency public affairs staffers for a candid panel discussion of relationships between the media and government communicators.

If you missed the event, find the recording on YouTube:

Here are a few technical lessons we learned from trying out Google Hangout:

1. Event Page design - You’ll need a photo/image with the right dimensions for the Event page. Google requires an image that is at least 1200 pixels wide and 300 pixels tall to serve as the banner, or “theme,” for the page. That banner should prominently include the time of the event and the name of your organization, as Event pages do not make this information as prominent as you might like. I made our banner in Paint with an image from the internet. (If you follow suit, be sure you use an image that is copyright-free or whose copyright allows this kind of use, as I did.)

2. Audio - Rather than use any of the in-Hangout apps to control audio, I simply asked our panel to mute themselves as they listened to others, unmuting only when they wanted to speak. (In Google Hangout, of course, the video features whoever is making noise, so coughs and other noises are a visual distraction, as well as an audial one.) We were happy with how this self-muting worked out. It had the advantage of allowing for free-flowing conversation. Our panel members could jump in and out of the discussion as they wanted, rather than waiting for a cue from a producer. Participants wore headphones, to avoid feedback.

3. Testing and prep - To test connections and lighting with participants in advance, I set up separate test Hangouts. This was a great opportunity for everyone to familiarize themselves with the technology, and to practice muting and unmuting. It also ensured that the necessary browser plugin was installed on everyone’s machine. When the tests were complete, we quickly deleted the Events and the YouTube video associated with the test. Google automatically generates a YouTube video for any Hangout On Air that goes live, so be sure you delete tests you don’t want public.

4. In-Hangout apps – I used both the Chat app and the Q&A app for our Hangout On Air, and we really liked both of them.

·         The Chat app is available within all Hangouts On Air, and it allows the panelists and producer to communicate privately with each other. “Hey, let’s answer that question next,” and that sort of thing. Gives participants a lifeline in case something goes wrong, as well.
·         The Q&A app needs to be enabled from the Event page, before you start the Google Hangout. It allows viewers to write in with questions throughout the event. Both panelists and viewers could see the questions as they came in on the side of the screen. (The producer can also delete questions, if necessary.) As our panelists addressed each question in turn, I marked the question we were currently answering so that it was highlighted toward the top of the screen. This data is added to the YouTube recording as well, to help people watching there understand what we were discussing, and when.

5. Internet connection - And finally, wireless connections really are not acceptable for video broadcast. (You might say, “well, duh!” But, we had to learn this for ourselves.) Even if the wireless at the location is great and fast, it just won’t work for Google Hangout. Insist that your participants connect on a hard-wired connection only.

There were plenty of other technical details and lessons learned—far too many to include in a blog post—but these are my quick highlights.
Did you watch our Google Hangout? Should we have another training event on Google Hangout in the future? Anything we could do better or different next time? Let me know by commenting below.