Skip to content

Instantly share code, notes, and snippets.

@melodykramer
Created October 8, 2015 12:40
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save melodykramer/e54f38f992c27e21ac97 to your computer and use it in GitHub Desktop.
Save melodykramer/e54f38f992c27e21ac97 to your computer and use it in GitHub Desktop.
The Comms team provides an extra set of eyeballs to make sure the products you're shipping are easily understood by other agencies and the public. We've developed this checklist for project teams to ensure that your products have a strong communications strategy and that you're able to talk, write, and speak easily about your subject area.
Early in the process:
[ ] Designate a lead on your team to communicate with the Comms team
[ ] Brainstorm three potential blog posts that relate to your project (success stories, things you've learned, launches)
[ ] Ask the Comms team for editing assistance for any Pages or Guides you're writing about your project area.
Midway through your project
[ ] One-hour meeting with the comms team to develop a communications strategy for your product
[ ] Media training to go over commonly-asked questions about your product
[ ] Send your comms lead to the weekly blog huddle to plan blog posts
[ ] Collect testimonials from client if appropriate.
Before you ship:
[ ] Tell the comms team your launch date
[ ] Pass along any testimonials you've collected.
[ ] Go over communications and social strategy for launch day.
After you ship:
[ ] Pass along any feedback from public
[ ] Go through media training if you have any interviews coming up
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment