Avoiding PR "Gotchas" -- a list of don'ts to learn from
I don't know about you, but I'm always a sucker for lists of do's and don'ts. A recent email to me from a magazine I subscribe to included the "top 25 beauty mistakes" and, of course, I clicked on it. I learned a few things, so it was worth the investment of time. It inspired me to ask our PR experts to help me assemble a list of the biggest PR mistakes they have seen recently that we all can learn from:
-
Telling a business press reporter after an interview that if he writes about your company it will raise interest in it, which would be a good thing. Get ready for a major eye roll from the reporter on that one -- unless he is a stockholder.
-
Capitalizing on a tragedy, especially with the words "if they had used XX product/service, this wouldn't have happened." This is one time you have to pass up a newsworthy angle.
-
Speaking for quotation to the media on behalf of a partner or a customer. It's always better to direct them to the customer or partner for their own quotes rather than risk souring your relationship by saying something they would not want to see in print.
-
Being unwilling to comment on industry trends or issues during an interview. Reporters are happy to hear about your company, if you are relevant in your market, but they'd also like to hear broader perspectives. It makes you more valuable as a source too.
-
Answering the reporter's end-of-interview question, "Do you have anything to add?" with a smile and a quick "No." You just missed a great opportunity to briefly summarize the key points you hope the reporter got from your interview.
-
Telling a reporter "don't write what I just told you." Only a red flag in front of a bull is a more visible symbol to "charge" and get that scoop.
-
Keeping your PR team in the dark on corporate events. This sometimes happens to internal and agency people when a senior team's style is close-to-the-vest. It really blunts the effectiveness of the entire PR team to not have all the nuances of what is happening and why to shape their programs.
-
Starting a call with a journalist with the statement, "I think you are very wrong." An interview is a conversation and this, ladies and gentlemen, is a conversation killer.
-
Suggesting a headline for the article you want them to write and asking when it will run. This type of behavior makes for good stories at internal editorial meetings at publications, but it doesn't work.
-
Promising a customer by name to a journalist before clearing it with them. If you aren't sure the customer will clear it, tell them you'll check into it and get back to them with a name.
-
Agreeing to author a blog if you don't have the time to post. No one will take you seriously as a blogger if your content isn't fresh. Assign someone else or wait until you're really ready to provide regular postings.
-
Sending a reply on Twitter (which goes to everyone who follows you) instead of a direct message (which goes just to the person you want to engage with). Always think before you "tweet."
-
Insisting that PR take the toughest question out of the FAQ preparation document for a major announcement. Removing the question will not guarantee no one asks it and you will be much less prepared when it is asked.
-
Being so anxious to "tweet" that you reveal some news or comments from a partner, customer or company leader before a planned announcement. This is what social media policy guidelines are written to prevent.
-
Not respecting a journalist's deadline. If you offer the best customer contact, but it is right on top of or after the reporter's deadline, you not only won't be included in the article, but you also will hurt your chances of her calling you for the next story she is writing.
-
Assuming too much knowledge on behalf of reporters. These days, with publications being smaller, reporters are asked to cover a wide range of "beats" and they aren't always experts in all of them. It always helps to provide context and spell out acronyms or at least do temperature reads to give them a chance to ask for a backdrop on a technology or market segment, if they need it.


