Every semester when it’s time to look at writing effective news releases, I relaunch my search for good examples. It’s not an easy task. Well-written releases seem to be a rarity, even though the World Wide Web gives me access to thousands of them.
Why is that? The chasm between the content of most releases and the information actually used by journalists is usually very wide. Year after year, nothing seems to change; news releases continue to be unclear, wordy, hyped-up missives littered with phony quotes.
It’s worth remembering that the move towards social media releases was not initially prompted by the allure of all the new multimedia tools in the digital world. It was prompted by the sad quality of most current releases. Check out Tom Foremski’s original diatribe that sparked the debate, and a great conversation by Brian Solis and Shel Holtz on the IABC Cafe2Go podcast for more about that.
Ultimately, tools and formats won’t help a poorly written release. Although I realize many releases suffer from endless rewrites and approvals that turn them into semantic mush, we need to do better.
Here are five reasons I think many releases stink:
1. Lengthy, tedious leads. The first paragraphs of most news releases are insufferably long. If published that way, they’d form daunting blocks of text designed to thwart eyeball-appeal. Which, of course, is why most publications have to rework them. In my introductory writing classes, students are not allowed to write lead paragraphs that exceed 30 words. I’ve seen nothing over the years to convince me to stop using that guideline.
2. Phony quotes. The use of quotations can add so much credibility to a news release. Journalists are hungry to have them. We punt this opportunity by inserting quotes that simply aren’t natural. They read like laboriously crafted written statements (that’s because they actually are laboriously crafted written statements). To literally quote from a recent release:
“… we have provided in these documents for a solid long-term framework for the further benefit of consumers, in which we will control rate increases; maintain reliability; introduce competition in generation; require performance standards; strongly encourage renewables; ensure proper regulatory oversight; enhance environmental protection; and encourage efficiency.”
People don’t talk this way (at least, they shouldn’t). Can’t we cut the journalists some slack here and give them something they might be able to use in a story?
3. Unsubstantiated hype. Somehow, we think that if our release says the event was a success (or the new product is the best on the market, or the revised service represents a dramatic improvement), the public and the media will accept these generalizations without any evidence to support the claim. Give your readers some credit; tell them the what and why of your story and let them decide if it’s a success, the best, or dramatically improved. For every newspaper that runs your promotional hyperbole, there are inevitably several others who wonder why you think they’ll run your thinly disguised advertisement for free.
4. Preoccupation with announcements. So many releases kick off with the fact that an announcement is being made, instead of telling readers what was announced. “Convoluted International announced yesterday that it has acquired Baffling Canada.” Why, exactly, are words three through six in this sentence? I’d wager announced is the most common first verb found in news releases. I’d wager that in most of those releases, making an announcement is not the actual story.
5. Gobbledygook. Sure, every field of endeavour has its terminology and jargon. It’s a not-so-subtle demonstration of expertise. But do we really have to lace our releases with it? Can’t we just tell the reader what a renewable is? Can’t we find a nice English translation for “The company will fully commercialize the intrinsic value of its intellectual property.”?
This is starting to sound uncomfortably like a lecture. That wasn’t my intent. I’m simply looking for some examples of well written news releases. Can you steer me in the right direction?