CONTACT INFO BLOG SIGNUP

SCHWARTZ HOMEPAGE

CROSSROADS

SCHWARTZ CROSSROADS

Technology PR: 12 Terminal Media Relations Mistakes

iStock_000009964782XSmall.jpg

Most technology innovators are eager for positive, on-message media coverage to build their brands, drive sales leads or support other business goals. But unless you're already a tech industry behemoth, getting consistent, repeated media coverage across a variety of publications and channels takes some creativity, a fair amount of knowledge of what makes a good story and a ton of persistence.

When a technology company has before it an opportunity to work with a journalist, blogger or other influential individual, they're going to want to make that interaction as perfect as possible. Right?

You'd think so, but technology companies torpedo their chances of securing media coverage by doing, or by failing to do, some pretty elemental things. These mistakes have nothing to do with faulty communications strategy or going to the wrong journalist with the wrong story. They're more basic and they're pervasive in some companies' PR programs. Maybe the belief that the problems are small makes some people underappreciate their impact, but they kill coverage all the time.

The good news, then, is that they're fully within the tech company's control and doing this stuff right can make a huge difference in PR results. If the PR team detects these problems as they're occurring, they're remiss if they don't point them out, but ultimately only the tech company can fully correct these media relations errors.

1. Fail to provide a spokesperson. Your PR person has possibly just walked through walls to get a journalist to agree to talk with your company's expert. That reporter wants to hear from one of your smart people and if your industry is driven by breaking news, he needs to hear from that person minutes from now. In some cases, we may have the luxury of a couple of hours or days to provide an expert source. In either case, any small to mid-sized tech firm should be able to get an informed spokesperson on the phone quickly.

2. Neglect to prepare for the conversation. Your PR team will give you information about the blogger or journalist before your interview and tell you what she's been covering lately. You want to look at this information before, not during, the conversation. And there's no substitute for spending a little time reading the reporter's recent articles yourself. You'll feel more confident during the interview and be in a good position to give the journalist information that she'll find useful.

3. Miss scheduled briefings. Everyone's busy. Everyone also has a mobile device that allows them to contact their PR team before missing a briefing. Journalists are as stretched as anyone and we have to respect their time. Along those lines, we need to plan ahead to conduct the interview from an area with a decent cell connection and low background noise. Anything else will guarantee that the reporter will get off the phone with us at the earliest possible moment.

4. Respond on your own timetable. Media relations success is largely about being in the right place at the right time. A big part of that is understanding that reporters work on deadlines that are anything but leisurely; we have to conform to deadlines or forfeit coverage. It's hard for everyone involved, but if options are "I'm in the story" and "my competitor is in the story," priorities become a little clearer.

5. Decline to provide photos or graphics. Technology media are increasingly interested in telling stories that have a visual component. Your PR team should work with you to anticipate these needs, but when requests come for something we don't have on hand, know that providing it can mean the difference between coverage and exclusion from the story. Particularly when all that's required is a photo of the new executive, there's no reason for not being able to quickly provide one. Grab your camera and get it done.

6. Refuse to discuss pricing. Everyone who works in the B2B technology industry understands that there's no set price for anything and that stuff tends to be pretty expensive. And you didn't invent volume discounts--journalists understand the concept. So we need to have an answer to the elemental question, "how much does this cost?" Some journalists can't or won't cover our story without being able to say "pricing starts at ...."

7. Talk about confidential material and then ask the reporter not to use it. The #1 rule of media relations is "don't say anything you don't want to see in print." It's unfair to journalists to give them information that you later ask them not to use. They generally don't want to see you get into trouble, but you, in turn, should understand that it's a problem for them to not use material that they consider interesting. Don't put them or yourself into this painful position--if your PR team has asked you not to talk about how that big customer is using your product and about to toss the big vendor out on his ear, don't do it. 

8. Decline to discuss competitors. Maybe we truly don't have any, but most tech companies do. We don't need to offer up information about competitors, but if asked, we do need a coherent answer. Your PR team will work with you to think through how to answer this question, but flat-out refusing to address it makes it hard for the reporter to cover you because he needs to be able to place your company, particularly if it's small, into some larger context. Really, we should view questions about competitors as opportunities to talk about who we're challenging.

9. Ask to review the article prior to publication. Some journalists will allow you to take a peek at quotes, but most will not. And protests about having been misquoted in the past aren't that convincing, so the key here is to work with your PR team before the interview to think critically about the messages you want to convey and then take care not to go off on a tangent. Normally if we prepare for conversations and stay focused, we will come out of interviews feeling comfortable, not worried about what we said and how it might have been interpreted.

10. Speak in PowerPoint. Reporters and bloggers don't want a canned presentation--they want information that's tailored for them. Your PR people should tell you that using a PPT for media briefings is generally discouraged. Nothing says "I've had this conversation with all your competitors" like reliance on canned information.

11. Be boring, ramble, speak in monotone or otherwise fail to sell. Your PR team will help you understand what the journalist wants to learn about, how much time she has and what messages you need to deliver. It's then on the spokesperson to seal the deal by offering informed and timely conversation. Spokespeople from most companies should adopt the mindset, because it's nearly always true, that they need the journalist more than the journalist needs them and that the interview is not going to be an intellectual give and take. The spokesperson's job is to inform or educate the journalist and to convince her that this subject is worth her time. Make it interesting or expect to hear from your PR team that the reporter will "keep the information on file."

12. Assume the relationship is personal. Journalists value connections to people at tech companies if and only if those connections yield useful information. Perhaps they included us in an article or two, and that's great, but the challenge is to keep coming back with fresh info. If we cease to provide that, we should expect to be left off the short list of companies to include in stories going forward.

Your PR team, whether they're inside your company or with an agency, should be working to keep you on the straight and narrow in all these areas. You can help your technology company eke out every last bit of media coverage if you understand that these little mistakes can have a significant impact on your coverage.

Tags: media relations, PR agencies, public relations agencies, tech PR, technology PR

Posted by Laura Kempke on February 10, 2010 at 10:02 PM

Share |

blog comments powered by Disqus