<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: No more press releases!!</title>
	<atom:link href="http://www.chipdesignmag.com/bailey/2009/08/05/no-more-press-releases/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.chipdesignmag.com/bailey/2009/08/05/no-more-press-releases/</link>
	<description>ESL Design and Verification</description>
	<lastBuildDate>Tue, 06 Sep 2011 02:23:02 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Alan Smith</title>
		<link>http://www.chipdesignmag.com/bailey/2009/08/05/no-more-press-releases/comment-page-1/#comment-1635</link>
		<dc:creator>Alan Smith</dc:creator>
		<pubDate>Thu, 13 Aug 2009 09:13:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.chipdesignmag.com/bailey/?p=43#comment-1635</guid>
		<description>Hi.

Disclosure, so as not to protect the guilty: I&#039;m the head of communications at Altium. And we&#039;ve been tussling (struggling) with these opportunities for some time. I don&#039;t think we&#039;re there yet, and your blog, Brian, really brought into focus what we need to do - so thanks for that. And, to the points raised by others, the future is all about having relevant conversations with people. In communications, that means creating value in what you have to say. And, only the reader knows what &#039;value&#039; is, so those of us on the vendor side have to get it right, and not just hope for the best.</description>
		<content:encoded><![CDATA[<p>Hi.</p>
<p>Disclosure, so as not to protect the guilty: I&#8217;m the head of communications at Altium. And we&#8217;ve been tussling (struggling) with these opportunities for some time. I don&#8217;t think we&#8217;re there yet, and your blog, Brian, really brought into focus what we need to do &#8211; so thanks for that. And, to the points raised by others, the future is all about having relevant conversations with people. In communications, that means creating value in what you have to say. And, only the reader knows what &#8216;value&#8217; is, so those of us on the vendor side have to get it right, and not just hope for the best.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Bailey</title>
		<link>http://www.chipdesignmag.com/bailey/2009/08/05/no-more-press-releases/comment-page-1/#comment-1632</link>
		<dc:creator>Brian Bailey</dc:creator>
		<pubDate>Wed, 12 Aug 2009 14:50:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.chipdesignmag.com/bailey/?p=43#comment-1632</guid>
		<description>Hi Susan. I think you have hit the nail on the head, now we just have to work out the right terms. By &quot;traditional&quot; press, I mean the place where press releases go - almost verbatim. They are a conduit of information between a company and the user community via some print or on-line publication. It allows the company to reach not only their existing customers but also their non-customers. There is value there and I am not saying it should stop.

In your example, you cite what I believe is the real purpose of editors and bloggers alike. To find something that they believe has value to people - a level of understanding that does not come from raw information. In your case, a press release triggered that, but I would suggest that there are better ways to encourage that form of dialog.

Most good articles (in my opinion) have an educational purpose. The reader should understand something at the end of it that was not clear or evident before. This could come from an aggregation of information from several sources, or the impact that a particular development could have on the way a technology is used etc. What I need is access to information that can allow me to do this in an efficient and effective manner. This kind of information is deeper than would be contained in a press release, so I either need a more detailed source of information that I can access (without NDA), or access to the people who can provide it (as was the case with your client).

As you can see, I don&#039;t have all of the answers, but I do know that sending a press release to me is very unlikely to get the desired response. I have tried to write up many potential solutions to this and so far at the end of each of them I reach a conclusion that they suffer from many of the same problems. I agree that at the end of the day I may need some kind of trigger that a company has something important to say, but most of the time I just want access to information from which I can extract what I think is interesting. So I also need the ability to pull information.</description>
		<content:encoded><![CDATA[<p>Hi Susan. I think you have hit the nail on the head, now we just have to work out the right terms. By &#8220;traditional&#8221; press, I mean the place where press releases go &#8211; almost verbatim. They are a conduit of information between a company and the user community via some print or on-line publication. It allows the company to reach not only their existing customers but also their non-customers. There is value there and I am not saying it should stop.</p>
<p>In your example, you cite what I believe is the real purpose of editors and bloggers alike. To find something that they believe has value to people &#8211; a level of understanding that does not come from raw information. In your case, a press release triggered that, but I would suggest that there are better ways to encourage that form of dialog.</p>
<p>Most good articles (in my opinion) have an educational purpose. The reader should understand something at the end of it that was not clear or evident before. This could come from an aggregation of information from several sources, or the impact that a particular development could have on the way a technology is used etc. What I need is access to information that can allow me to do this in an efficient and effective manner. This kind of information is deeper than would be contained in a press release, so I either need a more detailed source of information that I can access (without NDA), or access to the people who can provide it (as was the case with your client).</p>
<p>As you can see, I don&#8217;t have all of the answers, but I do know that sending a press release to me is very unlikely to get the desired response. I have tried to write up many potential solutions to this and so far at the end of each of them I reach a conclusion that they suffer from many of the same problems. I agree that at the end of the day I may need some kind of trigger that a company has something important to say, but most of the time I just want access to information from which I can extract what I think is interesting. So I also need the ability to pull information.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Susan Cain</title>
		<link>http://www.chipdesignmag.com/bailey/2009/08/05/no-more-press-releases/comment-page-1/#comment-1631</link>
		<dc:creator>Susan Cain</dc:creator>
		<pubDate>Tue, 11 Aug 2009 22:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.chipdesignmag.com/bailey/?p=43#comment-1631</guid>
		<description>So just who is &quot;traditional&quot; press anymore?  I don&#039;t know anyone who fits into that category.  While many of the editors I know may write what you consider to be &quot;traditional&quot; stories (who hired whom, who bought whom, faster than fast newest, coolest chip), they also are looking for the &quot;interesting bits&quot; and when they find it, it may appear in a traditional article (whatever that is) or a blog with a teaser tweet.  I was recently in an interview with a traditional editor and he accepted the meeting based on the press release and the not so exciting topic discussed in the release.  What he wrote about was something he began poking at during the interview and had little to do with the topic of the call.  And then this traditional editor blogged the story.  There are no traditonal editors nor skillsets exclusive to one group over another.  Not if they are good at their job.  While some editors may not take a story to a deeper level, some well-known bloggers write to enjoy their own writing.  But you aren&#039;t one of them Brian.  You always bring something to the table to get people going!</description>
		<content:encoded><![CDATA[<p>So just who is &#8220;traditional&#8221; press anymore?  I don&#8217;t know anyone who fits into that category.  While many of the editors I know may write what you consider to be &#8220;traditional&#8221; stories (who hired whom, who bought whom, faster than fast newest, coolest chip), they also are looking for the &#8220;interesting bits&#8221; and when they find it, it may appear in a traditional article (whatever that is) or a blog with a teaser tweet.  I was recently in an interview with a traditional editor and he accepted the meeting based on the press release and the not so exciting topic discussed in the release.  What he wrote about was something he began poking at during the interview and had little to do with the topic of the call.  And then this traditional editor blogged the story.  There are no traditonal editors nor skillsets exclusive to one group over another.  Not if they are good at their job.  While some editors may not take a story to a deeper level, some well-known bloggers write to enjoy their own writing.  But you aren&#8217;t one of them Brian.  You always bring something to the table to get people going!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Bailey</title>
		<link>http://www.chipdesignmag.com/bailey/2009/08/05/no-more-press-releases/comment-page-1/#comment-1628</link>
		<dc:creator>Brian Bailey</dc:creator>
		<pubDate>Tue, 11 Aug 2009 16:29:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.chipdesignmag.com/bailey/?p=43#comment-1628</guid>
		<description>Hi Paul,
Thanks for your thoughtful comments. I am not against PR agencies in any ways - so I agree with you there; they are as you say just the messenger. However, they are also the messengers back into the companies and I think it is important to try and give them some guidance about how to reach the Blogosphere. If we don&#039;t tell them what is not working, then how are they going to change and respond. So I hope the article did not sound too negative - I just want to see some changes happening.</description>
		<content:encoded><![CDATA[<p>Hi Paul,<br />
Thanks for your thoughtful comments. I am not against PR agencies in any ways &#8211; so I agree with you there; they are as you say just the messenger. However, they are also the messengers back into the companies and I think it is important to try and give them some guidance about how to reach the Blogosphere. If we don&#8217;t tell them what is not working, then how are they going to change and respond. So I hope the article did not sound too negative &#8211; I just want to see some changes happening.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Dempsey</title>
		<link>http://www.chipdesignmag.com/bailey/2009/08/05/no-more-press-releases/comment-page-1/#comment-1627</link>
		<dc:creator>Paul Dempsey</dc:creator>
		<pubDate>Tue, 11 Aug 2009 16:08:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.chipdesignmag.com/bailey/?p=43#comment-1627</guid>
		<description>Hey Brian,

The old joke about &#039;delete&#039; being the first key to get worn blank on a journo&#039;s keyboard is not actually a joke. We just take solace in the fact that fewer trees are being toppled to pay for the &#039;incrementals&#039; these days. The old Electronics Times could receive several hundred pieces of mail a day in the run-up to an event like Electronica, and 99.9% of it was binned even then.

As for NDAs, they simply have no place in the communications industry. Embargos, yes, but NDAs that limit what you can say publicly in any way beyond when you can say it should simply be rebuffed.

And slagging PRs over a lot of this smacks somewhat of killing the messenger. The problem is not necessarily there but sited among the people who direct them and have outdated expectations and an outdated sense of how things work. It&#039;s hard for PRs to talk about their internal and external masters publicly, but just about everyone I&#039;ve ever met in tha business can tell you plenty of horror stories about releases they have been forced to issue after warning that they were more likely to irritate than inform or even mildly interest the community.

Welcome to the club. ;-)

Paul</description>
		<content:encoded><![CDATA[<p>Hey Brian,</p>
<p>The old joke about &#8216;delete&#8217; being the first key to get worn blank on a journo&#8217;s keyboard is not actually a joke. We just take solace in the fact that fewer trees are being toppled to pay for the &#8216;incrementals&#8217; these days. The old Electronics Times could receive several hundred pieces of mail a day in the run-up to an event like Electronica, and 99.9% of it was binned even then.</p>
<p>As for NDAs, they simply have no place in the communications industry. Embargos, yes, but NDAs that limit what you can say publicly in any way beyond when you can say it should simply be rebuffed.</p>
<p>And slagging PRs over a lot of this smacks somewhat of killing the messenger. The problem is not necessarily there but sited among the people who direct them and have outdated expectations and an outdated sense of how things work. It&#8217;s hard for PRs to talk about their internal and external masters publicly, but just about everyone I&#8217;ve ever met in tha business can tell you plenty of horror stories about releases they have been forced to issue after warning that they were more likely to irritate than inform or even mildly interest the community.</p>
<p>Welcome to the club. <img src='http://www.chipdesignmag.com/bailey/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>Paul</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harry Gries</title>
		<link>http://www.chipdesignmag.com/bailey/2009/08/05/no-more-press-releases/comment-page-1/#comment-1621</link>
		<dc:creator>Harry Gries</dc:creator>
		<pubDate>Sat, 08 Aug 2009 01:51:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.chipdesignmag.com/bailey/?p=43#comment-1621</guid>
		<description>Brian,

This is the blog post I wish I had written :-)

I had a similar conversation with a fellow blogger earlier this week, one who is more in the sales and marketing side, about the waning value of press releases and PR people in general. I&#039;m more new to blogging that you are, so the PR attention is new to me. But as far as DAC was concerned, PR people added little value beyond what a good admin would have done in trying to set up meetings. The ones that sat in my meetings with me said nary a word.

As for NDAs, I know they are needed in some cases, but they are certainly overused. Most companies would get more benefit from the positive coverage resulting from releasing the &quot;family jewels&quot; than any competitive harm.

Harry</description>
		<content:encoded><![CDATA[<p>Brian,</p>
<p>This is the blog post I wish I had written <img src='http://www.chipdesignmag.com/bailey/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>I had a similar conversation with a fellow blogger earlier this week, one who is more in the sales and marketing side, about the waning value of press releases and PR people in general. I&#8217;m more new to blogging that you are, so the PR attention is new to me. But as far as DAC was concerned, PR people added little value beyond what a good admin would have done in trying to set up meetings. The ones that sat in my meetings with me said nary a word.</p>
<p>As for NDAs, I know they are needed in some cases, but they are certainly overused. Most companies would get more benefit from the positive coverage resulting from releasing the &#8220;family jewels&#8221; than any competitive harm.</p>
<p>Harry</p>
]]></content:encoded>
	</item>
</channel>
</rss>

