<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: The shape of press releases to come</title>
	<atom:link href="http://commons.iabc.com/media/2006/05/23/the-shape-of-press-releases-to-come/feed/" rel="self" type="application/rss+xml" />
	<link>http://commons.iabc.com/media/2006/05/23/the-shape-of-press-releases-to-come/</link>
	<description>A Blog Community for Business Communicators</description>
	<pubDate>Tue, 14 Oct 2008 12:27:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Mark McLaughlin</title>
		<link>http://commons.iabc.com/media/2006/05/23/the-shape-of-press-releases-to-come/#comment-254</link>
		<dc:creator>Mark McLaughlin</dc:creator>
		<pubDate>Wed, 27 Sep 2006 06:08:00 +0000</pubDate>
		<guid isPermaLink="false">http://commons.iabc.com/media/2006/05/23/the-shape-of-press-releases-to-come/#comment-254</guid>
		<description>As usual, Mr. Holtz is correct.
The News Release is not dead.
It's just being presented, delivered and filed in a new way.
The technical methods of disseminating the old tried 'n true News Release are changing dramatically.  There's no question of that. 
When I was in News and on the Assignment Desk, I was appalled by the same criticisms Mr. Holtz mentions.  That's the problem of the writer of the news release - not the release itself.  If a release is sent to inappropriate editors and reporters, the release is not at fault.  It's the human element that's to blame (and it always will be).
The bottom line here is that the "release" is not dead - it's just evolving.</description>
		<content:encoded><![CDATA[<p>As usual, Mr. Holtz is correct.<br />
The News Release is not dead.<br />
It&#8217;s just being presented, delivered and filed in a new way.<br />
The technical methods of disseminating the old tried &#8216;n true News Release are changing dramatically.  There&#8217;s no question of that.<br />
When I was in News and on the Assignment Desk, I was appalled by the same criticisms Mr. Holtz mentions.  That&#8217;s the problem of the writer of the news release - not the release itself.  If a release is sent to inappropriate editors and reporters, the release is not at fault.  It&#8217;s the human element that&#8217;s to blame (and it always will be).<br />
The bottom line here is that the &#8220;release&#8221; is not dead - it&#8217;s just evolving.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Pincus</title>
		<link>http://commons.iabc.com/media/2006/05/23/the-shape-of-press-releases-to-come/#comment-60</link>
		<dc:creator>David Pincus</dc:creator>
		<pubDate>Thu, 08 Jun 2006 20:17:52 +0000</pubDate>
		<guid isPermaLink="false">http://commons.iabc.com/media/2006/05/23/the-shape-of-press-releases-to-come/#comment-60</guid>
		<description>After reading Shel's thoughtful post, and the responses thus far, I have to say I'm more than a little encouraged by the apparent direction -- and merger -- of the traditional news release and the many new technology forms.  My feeling of optimism comes from what I perceive as a blurring of boundaries and differences between the old and new forms of preparing and distributing the so-called news release.  The major benefit of this melding process underway is, I believe, the shifting of emphasis from management's message to constituencies' perceptions/needs. 

Of course, I guess I should admit my long-held bias, which I espoused regularly in the classes I taught in the realm of public relations, that the news release, as we have long known it, is a relic and should be abandoned.  Replacement forms, whatever shape they take and whatever label given them, should -- again, my view -- dispense with the formalities and archaic structure of top-down, organization-heavy news releases and go with forms that highlight data, information, and viewpoints that are designed to tweak the primary interests of the media BECAUSE they would unquestionably do the same of the media's readership/viewership.  A simple fact sheet, for instance, perhaps presented in descending order of importance with an accompanying clarifying "pitch" note, is no doubt perceived more positively by media than anything resembling a pat, one-sided presentation of the organization's prime interests.  Heck, nobody likes to be told what they should consider important, much less how they ought to say it, right?  Certainly that's true of journalists, in my experience.

It's all about perceptions . . . So, what's new?</description>
		<content:encoded><![CDATA[<p>After reading Shel&#8217;s thoughtful post, and the responses thus far, I have to say I&#8217;m more than a little encouraged by the apparent direction &#8212; and merger &#8212; of the traditional news release and the many new technology forms.  My feeling of optimism comes from what I perceive as a blurring of boundaries and differences between the old and new forms of preparing and distributing the so-called news release.  The major benefit of this melding process underway is, I believe, the shifting of emphasis from management&#8217;s message to constituencies&#8217; perceptions/needs. </p>
<p>Of course, I guess I should admit my long-held bias, which I espoused regularly in the classes I taught in the realm of public relations, that the news release, as we have long known it, is a relic and should be abandoned.  Replacement forms, whatever shape they take and whatever label given them, should &#8212; again, my view &#8212; dispense with the formalities and archaic structure of top-down, organization-heavy news releases and go with forms that highlight data, information, and viewpoints that are designed to tweak the primary interests of the media BECAUSE they would unquestionably do the same of the media&#8217;s readership/viewership.  A simple fact sheet, for instance, perhaps presented in descending order of importance with an accompanying clarifying &#8220;pitch&#8221; note, is no doubt perceived more positively by media than anything resembling a pat, one-sided presentation of the organization&#8217;s prime interests.  Heck, nobody likes to be told what they should consider important, much less how they ought to say it, right?  Certainly that&#8217;s true of journalists, in my experience.</p>
<p>It&#8217;s all about perceptions . . . So, what&#8217;s new?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wilma Mathews</title>
		<link>http://commons.iabc.com/media/2006/05/23/the-shape-of-press-releases-to-come/#comment-40</link>
		<dc:creator>Wilma Mathews</dc:creator>
		<pubDate>Wed, 31 May 2006 18:23:59 +0000</pubDate>
		<guid isPermaLink="false">http://commons.iabc.com/media/2006/05/23/the-shape-of-press-releases-to-come/#comment-40</guid>
		<description>Ease-of-use is wonderful. To echo others: if there is not news, it doesn't matter what the format is.
Remember: you can put a tutu and a tiara on a pig and maybe even teach it to dance but it's still a pig.

Thanks.</description>
		<content:encoded><![CDATA[<p>Ease-of-use is wonderful. To echo others: if there is not news, it doesn&#8217;t matter what the format is.<br />
Remember: you can put a tutu and a tiara on a pig and maybe even teach it to dance but it&#8217;s still a pig.</p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich Barger, ABC, APR</title>
		<link>http://commons.iabc.com/media/2006/05/23/the-shape-of-press-releases-to-come/#comment-30</link>
		<dc:creator>Rich Barger, ABC, APR</dc:creator>
		<pubDate>Mon, 29 May 2006 14:49:25 +0000</pubDate>
		<guid isPermaLink="false">http://commons.iabc.com/media/2006/05/23/the-shape-of-press-releases-to-come/#comment-30</guid>
		<description>You're right, Shel.  Before we spend lots of time figuring whether this or that format or template or delivery mechanism is best, we oughta have something to say.

On &lt;a href="http://pr-squared.blogspot.com/2006/05/social-media-press-release-debuts.html" rel="nofollow"&gt;PR Squared&lt;/a&gt;, a blogger identified as PR Minority echoed your earlier comments:

&lt;blockquote&gt;The challenge in my opinion is not getting clients to try the new format...it is in getting them to stop issuing releases without news. Poorly written news releases with little to no news value are what brought the format under fire in the first place.&lt;/blockquote&gt;

I first saw the &lt;a href="http://www.shiftcomm.com/"&gt;SHIFT Communications&lt;/a&gt; &lt;a href="http://www.shiftcomm.com/downloads/smprtemplate.pdf"&gt;Social Media Press Release&lt;/a&gt; last week.  SHIFT says: 

&lt;blockquote&gt;This radically different format is more à la carte menu than standard press release. In a non-linear fashion, it ties together narrative, quotes and various multimedia (RSS, social bookmarking, photos, etc.) on one page. Journalists &#038; bloggers can "re-mix" the elements into the story THEY want to write.&lt;/blockquote&gt;

I'll talk a bit more about formatting separately.</description>
		<content:encoded><![CDATA[<p>You&#8217;re right, Shel.  Before we spend lots of time figuring whether this or that format or template or delivery mechanism is best, we oughta have something to say.</p>
<p>On <a href="http://pr-squared.blogspot.com/2006/05/social-media-press-release-debuts.html" rel="nofollow">PR Squared</a>, a blogger identified as PR Minority echoed your earlier comments:</p>
<blockquote><p>The challenge in my opinion is not getting clients to try the new format&#8230;it is in getting them to stop issuing releases without news. Poorly written news releases with little to no news value are what brought the format under fire in the first place.</p></blockquote>
<p>I first saw the <a href="http://www.shiftcomm.com/">SHIFT Communications</a> <a href="http://www.shiftcomm.com/downloads/smprtemplate.pdf">Social Media Press Release</a> last week.  SHIFT says: </p>
<blockquote><p>This radically different format is more à la carte menu than standard press release. In a non-linear fashion, it ties together narrative, quotes and various multimedia (RSS, social bookmarking, photos, etc.) on one page. Journalists &#038; bloggers can &#8220;re-mix&#8221; the elements into the story THEY want to write.</p></blockquote>
<p>I&#8217;ll talk a bit more about formatting separately.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kelsey Mullen</title>
		<link>http://commons.iabc.com/media/2006/05/23/the-shape-of-press-releases-to-come/#comment-20</link>
		<dc:creator>Kelsey Mullen</dc:creator>
		<pubDate>Thu, 25 May 2006 16:09:37 +0000</pubDate>
		<guid isPermaLink="false">http://commons.iabc.com/media/2006/05/23/the-shape-of-press-releases-to-come/#comment-20</guid>
		<description>Wow. I am a public relations major based out of Calgary, Alberta, Canada. I am currently on my first work term, set up by the college.

Working for this organization and following the standard procedure for press releases has made me see the need for adaptation in today's world of media relations.

I printed off your template, and really agreed with the things that you said. I doubt that I have the clout around here to actually implement something like this, but I am certainly going to share this with my graduating class, and keep it with me as I venture on.

Thanks.</description>
		<content:encoded><![CDATA[<p>Wow. I am a public relations major based out of Calgary, Alberta, Canada. I am currently on my first work term, set up by the college.</p>
<p>Working for this organization and following the standard procedure for press releases has made me see the need for adaptation in today&#8217;s world of media relations.</p>
<p>I printed off your template, and really agreed with the things that you said. I doubt that I have the clout around here to actually implement something like this, but I am certainly going to share this with my graduating class, and keep it with me as I venture on.</p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Bergman, ABC, APR</title>
		<link>http://commons.iabc.com/media/2006/05/23/the-shape-of-press-releases-to-come/#comment-18</link>
		<dc:creator>Eric Bergman, ABC, APR</dc:creator>
		<pubDate>Wed, 24 May 2006 20:40:16 +0000</pubDate>
		<guid isPermaLink="false">http://commons.iabc.com/media/2006/05/23/the-shape-of-press-releases-to-come/#comment-18</guid>
		<description>Shel,

As always ... thoughtful and articulate.

I followed the links in your post (and the links in theirs ... and so on ... and so on) and took at look at the SHIFT template.  

We used to send the same thing out by courier: relevant written information to the journalist(s) we hoped to attract (with emphasis on relevance to those journalists); a photo; some form of corporate identity; audiotaped sound bites (which we used to refer to as "actualities"); and B-roll.  

Back then, if I remember, journalists complained that we didn't do our homework on them (and I read at least three links following your thread from bloggers with the same complaint), and PR people tended to ignore that complaint.  

The house above the ground may look at little different with technology.  But the foundation on which success rests is exactly the same.</description>
		<content:encoded><![CDATA[<p>Shel,</p>
<p>As always &#8230; thoughtful and articulate.</p>
<p>I followed the links in your post (and the links in theirs &#8230; and so on &#8230; and so on) and took at look at the SHIFT template.  </p>
<p>We used to send the same thing out by courier: relevant written information to the journalist(s) we hoped to attract (with emphasis on relevance to those journalists); a photo; some form of corporate identity; audiotaped sound bites (which we used to refer to as &#8220;actualities&#8221;); and B-roll.  </p>
<p>Back then, if I remember, journalists complained that we didn&#8217;t do our homework on them (and I read at least three links following your thread from bloggers with the same complaint), and PR people tended to ignore that complaint.  </p>
<p>The house above the ground may look at little different with technology.  But the foundation on which success rests is exactly the same.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
