Earlier this week, Ragan.com posted a blog titled, “8 Foods PR Pros Should Avoid.” When I first saw it tweeted, I thought that it may have a few foods that aren’t good as we are working. Maybe I shouldn’t have that chicken finger sub for lunch; should I bypass the Starbucks breakfast sandwich. Heck, maybe I should be skipping Starbucks altogether (ok, that’s not happening).
As I clicked the link and actually read the blog, it was neither about foods we shouldn’t eat nor healthier options. The blog discussed how on the next visit to the store, we “consider which items not to buy. These products can rattle PR pros by planting negative subliminal messages in their psyches.”
Here are the first three:
1. Swiss cheese represents holes in our pitches.
2. Waffles remind us of a weak position on an angle and story credibility.
3. Fish triggers a sense of a foul smell. Translation: something stinks.
Upon finishing reading the post, I was flabbergasted. First, why would Ragan.com, a respected industry site, re-post this blog? Second, how did it pass the “smell” test (sorry for the pun)?
The blog was panned by the select few who anonymously commented. I’m not going to be anonymous. This blog is embarrassing and frankly, something I don’t expect from a seasoned pro. Imelda Dulcich, a fine PR pro near Seattle, Wash. told me on Twitter:
“It read like a required high school essay – trying to get the required number of words w/ no depth, matter.”
“No depth or matter” should never be words that are uttered when discussing advice from a PR/social media/marketing pro. We are expected to be knowledgeable with our guidance. We need to be better. We need to be smarter and think about what we say, write, and post everywhere.
Clients are looking to us and pay us a lot of money to give sound, smart advice. When I see blogs like this, I cringe because it is an example of taking the easy way out. It’s not something I’d want a potential or current client to read.
Set the bar high. It’s more than possible.
edCanvas = document.getElementById(‘content’);