Open Comms: Difference between revisions

Jump to navigation Jump to search

Open Comms (view source)

Revision as of 18:03, 18 May 2016

4,939 bytes removed ,  18 May 2016
→‎Media Relations Guidelines: deleted section - moved to subpage
(→‎Communication Guidelines: deleted section)
(→‎Media Relations Guidelines: deleted section - moved to subpage)
Line 10: Line 10:


Currently, you can find a collection of basic guidelines and tutorials for the different kinds of communication you might engage in. But ultimately our goal is to create frameworks and processes that enable you, amazing Mozillian, to see, hear and participate in Mozilla’s marketing communications. In other words, we want Open Comms to be more than a program, but to become the natural way we do things around here.
Currently, you can find a collection of basic guidelines and tutorials for the different kinds of communication you might engage in. But ultimately our goal is to create frameworks and processes that enable you, amazing Mozillian, to see, hear and participate in Mozilla’s marketing communications. In other words, we want Open Comms to be more than a program, but to become the natural way we do things around here.
== Media Relations Guidelines ==
Don’t panic! In this section you will find tips to help you identify and work with press, who can be a highly influential audience for our Mozilla story and amplify it even more.
You may meet press and media:
* At Mozilla events <br>
* At partner events <br>
* At non work events <br>
* Through invitations from individual reporters, directly or via the Mozilla PR team
'''Reactive work'''
You may be approached by media who have read about your work and see a story in there that they want to tell.
'''Proactive work'''
You may choose to reach out directly to reporters whose reporting could raise awareness of your work with relevant audiences. If you have signed up to be part of CommSquared you will have access to the tools to help build a media list, analyze the media landscape, and PR training and mentoring. If you are an employee or Mozillian who is *not* in the CommSquared program, but are interested in communicating with a reporter proactively or reactively, feel free to get in touch with the PR team.
'''How to build relationships with media'''
* Read, watch and/or listen to as much of relevant media’s work as you can. You should be equally informed on their work as reporters are by researching you. <br>
* Think about how what you’re doing may be perceived by media, without input from you. Is it easy to misinterpret what you do, without more context? <br>
* Think about which media cover your work well and which you’d like to build a relationship with. What do you know about their audiences, do they include people you want to reach? <br>
* Think about the media who seem not to understand your work. Are these people you still want to speak to, and take an opportunity to change their mind? How realistic is that?  What do you know about their audiences, do they include people you want to reach?
'''What to do in interviews'''
* If you’re not sure if you are talking to a journalist, ask them. And remember bloggers count too, including developers who just update a blog occasionally. <br>
* Ask basic questions to help decide whether this is a good opportunity, i.e. what publication does the reporter represent, what’s the topic, when’s the deadline? <br>
* Do your research around each specific opportunity. <br>
* If you agree to speak with media, always honor your commitment and give them as much notice as possible if you have to postpone or delay. <br>
* Set realistic time limits on an interview, half an hour is ample, sometimes you only need to offer 15 minutes. <br>
* Be familiar with high level Mozilla and product messaging and talking points (below). <br>
* Stick to your area(s) of expertise. <br>
* If you are asked for a comment that goes beyond your area of expertise, explain that it does and think about who else might be able to help the reporter. But don’t commit other Mozillians to speak without asking them first! <br>
* If the reporter just doesn’t understand how something works, you can ‘give them the background’. You’re not giving them anything newsworthy, just educating them. <br>
* If a reporter states something you know absolutely to be untrue, politely correct them.
* Use analogies that make your subject more relatable. <br>
* Use statistics, sparingly, when they support your points and you can clearly source them.
* Be excited, be friendly, be responsive within your boundaries. <br>
* Take some notes right after so you can revisit anything that needs to be corrected later or which offers you the chance to build a bigger story with that reporter or another.
'''What not to do interviews'''
* Don’t let anyone talk you into doing an interview. <br>
* Don’t bluff. <br>
* Don’t make jokes <br>
* Don’t comment on non Mozillian companies/individuals unless you’re prepared for the reporter to take your words right to that company/individual for a response. <br>
* Don’t fall for a request to have an ‘off the record’ conversation. If you say something newsworthy it becomes very hard for the reporter to keep it off the record.
'''What do if you are wrongly quoted'''
* Be sure! Reporters take complaints very seriously. Was the story actually inaccurate or just an interpretation of what you said that you don’t agree with? If you aren’t 100% convinced it’s inaccurate, your complaint can produce another even less positive story. <br>
* If it’s inaccurate, provide the reporter with the source for the correct information. <br>
* If you feel you need support from the Mozilla PR team, share the story with them at press@mozilla.com and ask if we have contacts or insight that may help secure a correction. <br>
* If it’s an interpretation you don’t agree with, decide whether this is something you have to live with as part of working with media or something you can reach out to the reporter about and discuss, even if it doesn’t immediately change what they wrote.


== How to write an effective blog post ==
== How to write an effective blog post ==
Ehull
69

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/1133165"

Navigation menu