If you work in an engineering or sales driven culture (see blog posting about Focus in marketing http://credibilitybranding.typepad.com/blog/2007/01/focus_the_missi_1.html) then you have often been pushed to create a press release that matches that culture. There are thousands if not hundreds of thousands of press releases that are serving internal constituents and not the editorial communities, or even customers. Most of us know that a press release is just another marketing tactic that contributes to expanding brand awareness through messaging. A press release is one big messaging document and a key ingredient to messaging are benefit statements. Most releases miss this point.
I have literally seen thousands of releases that are a big ball of jargon especially technology releases… but this can happen in any industry. Here is a rule of thumb if a friend or relative who is not in your industry can get the general gist of the release and understand what the news is, who it will benefit and how, then it is a good release.
Following is an example of an extremely well written release but it has zero benefit statements and for anyone but an engineer it is incomprehensible. Remember even though an editor at an engineering focused publication may understand a lot of technology, he can’t understand it all. The purpose of the release to ensure that these editors can glance through it and understand the news of the release, have a handle on how your product is benefiting customers and know the main messaging of the company.
NO BENEFITS JARGON FILLED RELEASE EXAMPLE:
New Converged Wireless Voice/Data Solution Results From Technology Partnership Combining COMPANY NAME2 With COMPANY NAME1's PRODUCT NAME1
COMPANY NAME1, Inc. (COMPANY NAME1), developers of the award-winning PRODUCT NAME1 solution for wireless terminal environments, today announced a new technology partnership with COMPANY NAME2. The partnership is a result of the two companies recently successfully testing and validating the flawless interoperability of COMPANY NAME1's PRODUCT NAME1 thin-client wireless terminal emulation software and COMPANY NAME2's new VoIP push-to-talk software -- running together at the same time, on the same device, using the same RF/wireless network connection. HERE IS THE FIRST CHANCE TO OFFER A BENEFIT STATEMENT. WHY IS OFFERING IT ON THE SAME DEVICE AT THE SAME TIME IMPORTANT? WHAT DOES IT DO FOR THE END-USER? WHO IS THE END-USER AUDIENCE?
"The ability for a user to have a flawless experience with voice and terminal emulation running on the same device makes the COMPANY NAME2 and PRODUCT NAME1 combination unique and a must-have next-generation solution stack for enterprises deploying Windows Mobile RF/wireless terminal devices," said xxxxx. "Most handheld wireless devices sold by MANUFACTURER NAME and other manufacturers are still being used as terminals for accessing host-based applications, so this technology partnership and resulting validated solution stack is a strategic win for both our companies and the markets we serve."
COMPANY NAME2, like PRODUCT NAME1, is a MANUFACTURER NAME +PLUS Validated software solution that is reliable, affordable and user-friendly, allowing workers to instantly talk with others using MANUFACTURER NAME mobile computers. Users need only click on the name of the person they want to speak to, and they are instantly connected together in either hands-free, full- or half-duplex voice modes. The software is cross-compatible with various operating systems, including Windows CE.NET 4.2, Pocket PC 2003, Windows Mobile 5.0 and CE 5.0.
PRODUCT NAME1 -- the market leader in host-based, thin-client wireless terminal emulation -- provides centralized, secure, high-performance wireless access to 5250/3270, VT100/220 and SSHv2 host-based screen applications, with support for a wide range of wireless terminal devices that, in addition to MANUFACTURER NAME, also includes those from Intermec, AML, PSC, HHP, LXE, and Psion-Teklogix. With PRODUCT NAME1, all terminal emulation and client device/session control runs natively on the same host system as the Telnet or SSH server, with only a thin-client software component loaded on each device being used.
Unlike legacy, device-side Telnet/SSH terminal emulation that uses TCP/IP, PRODUCT NAME1 thin-client terminal emulation features a unique UDP/IP-based host-communication scheme that is proving to be inherently compatible with VoIP applications, according to XXXXX.
"We anticipate that a solution stack comprising two MANUFACTURER NAME +PLUS Validated software solutions, authored by two innovative MANUFACTURER NAME ISV partners, that offers this type of compelling added-value for MANUFACTURER NAME mobile computers will be extremely well-received by our channel of solution-oriented PRODUCT NAME1 Certified Partner wireless technology resellers and their customers," said xxxx.
-----------------------------------------------------------------------------------
This release while well written has no benefit statements, just technology statements. It is a typical engineering driven release that is frustrating to editors and customers alike. I usually apply the “who cares” test; who would care about the news or content of this release… I suspect just the engineer that wrote it.
Exercise: get your last twenty releases and put them in a pile in front of you. Now pretend you are an editor… these twenty release represent about two hours worth of what an editor would receive in any given day. Your time limit is five minutes, now read through these releases in that five minute time frame. How did you do? Did the lead have a benefit statement that drew you into to read more? Did the first paragraph explain in a nutshell the real news or meat of the release? Now having reviewed these all at once, is there an underlying message that you can succinctly state from this grouping of releases?
If you would like your press release critiqued send me an email.
Digg this page
Recent Comments