Thursday 30 January 2014

A common PR mistake & some obvious advice

Just a small piece of 'PR learning' to share.

After laying out a very clear Response Source yesterday asking for a rather technical set of opinions on the use of...

... open source configuration and automation management tools (such as Puppet, Ansible, SmartFrog, Juju, OpenQRM, CFEngine & Chef)...

...I did invite the likes of IBM, EMC, HP, CA etc.. to also comment.

BUT - and here's the common mistake... (focus on point #2)

But the kids from the big boys who do not need to be named (big agency name, big client, none of the ones listed above) sent me:

1. Emails asking for an interview when I had clearly specified that I was out all afternoon and open to canned comment if it was properly written

2. Suggestions that EMC (it wasn't EMC) could talk about EMC's products when I specifically asked for opinions on Puppet, Ansible, SmartFrog, Juju, OpenQRM, CFEngine & Chef.

LEARNING OPPORTUNITY  --- this was a chance for vendors to talk about the industry and gain credibility in a wider sphere, there will be plenty more stories to focus on the client itself, this IS NOT THAT TIME ... this is a chance to earn wider kudos with the readers and (if I may be so bold as to suggest) also the journalist too.

3. Questions about when my deadline was when it was clearly stated in the Response Source.

WHY WHY WHY is it that PR people are so lazy and slapdash when it comes to detail?

Is it the 'excitement' of thinking they might have a hit?

Does this cloud their ability to read the full brief?

 I worked in PR for 7-years (mainly for Brodeur) and would have been shot for this kind of shoddy approach given that the PR person is spending the client's money out of what is no doubt a meaty monthly retainer.

Exasperated as always --

Adrian ---------- AdrĂ­an Bridgwater

Technology Journalist
http://twitter.com/Abridgwater

2 comments:

  1. I was going to leave a comment to the effect that, despite the headline of the piece (and the title of the blog itself) there wasn't any actual advice here. But I can see you've edited it and there's more detail appearing by the minute.

    Anyone who has worked in PR will know the way these things work ... junior staff get told to *do stuff* by more senior staff.

    This not a new phenomenon. I entered journalism in the early 90s.

    I will, however, applaud your openness on the use of canned comment.

    I'm not for one minute suggesting this is something you do, but the practice of pasting together a series of PR-written responses into features and articles is something that really irks me.

    When I exited full-time journalism (more than a decade ago) and started working in PR it was such an eye-opener to see the extent to which so-called journalists were, in effect, getting PR agencies to write their work for them.

    There are many problems with the relationship between hacks and flacks. Sloppy and unprofessional approaches to work are to be found on both sides of the line.

    ReplyDelete
  2. It is VERY specific and highly technical canned comment Sean... you get it right, some of it gets used, you don't, it doesn't.

    ReplyDelete