<?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: Note to Startups - Work on your Briefings</title>
	<atom:link href="http://www.chipdesignmag.com/blyler/2008/04/30/note-to-startups-work-on-your-briefings/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.chipdesignmag.com/blyler/2008/04/30/note-to-startups-work-on-your-briefings/</link>
	<description>Just another engineering physicist turned editor</description>
	<pubDate>Thu, 28 Aug 2008 00:37:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Virtue IMC</title>
		<link>http://www.chipdesignmag.com/blyler/2008/04/30/note-to-startups-work-on-your-briefings/#comment-4927</link>
		<dc:creator>Virtue IMC</dc:creator>
		<pubDate>Tue, 12 Aug 2008 21:34:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.chipdesignmag.com/blyler/?p=95#comment-4927</guid>
		<description>John,

Part of the problem that start-ups have is that they completely overlook the necessity of a knowledgeable, reputable, well-connected PR practitioner - and the investment in such a person is worth 100 times their salary/fee when it comes to advancing their brand and product/services.

As a former tech PR practitioner, I have to say that it can be a bit daunting to know what each editor wants to hear - every editor has their own agenda and can be a bit insistent that you, as the one providing the info, know what they want. Many who are not wise to the ways of Public Relations conduct briefings can be cookie cutter clones - with no regard as to what the editor wants or needs from the company. But my job was to make sure that I did the research on each publication and editor, so that each editor receives the briefing that meets their needs and the needs of their readers (their customers - ultimately).

As to the comment of the "untechnical" people using briefings as a platform - in my position, I made certain that we facilitated access to those that had the knowledge base to address the questions that cold possible spring forth during the discussion process with an editor. 

I won't take too much umbrage with the press release comment - the releases that I was responsible for were crafted to get as much technical information out to the editors for them to communicate to their readers without spec overload (trust me trying to reign in the engineers can be a merciless job).

Thank you gentlemen for reinforcing that we PR folks can be useful in business - not just a pain-in-the-rump when product folks want to toot their horns!

Charity</description>
		<content:encoded><![CDATA[<p>John,</p>
<p>Part of the problem that start-ups have is that they completely overlook the necessity of a knowledgeable, reputable, well-connected PR practitioner - and the investment in such a person is worth 100 times their salary/fee when it comes to advancing their brand and product/services.</p>
<p>As a former tech PR practitioner, I have to say that it can be a bit daunting to know what each editor wants to hear - every editor has their own agenda and can be a bit insistent that you, as the one providing the info, know what they want. Many who are not wise to the ways of Public Relations conduct briefings can be cookie cutter clones - with no regard as to what the editor wants or needs from the company. But my job was to make sure that I did the research on each publication and editor, so that each editor receives the briefing that meets their needs and the needs of their readers (their customers - ultimately).</p>
<p>As to the comment of the &#8220;untechnical&#8221; people using briefings as a platform - in my position, I made certain that we facilitated access to those that had the knowledge base to address the questions that cold possible spring forth during the discussion process with an editor. </p>
<p>I won&#8217;t take too much umbrage with the press release comment - the releases that I was responsible for were crafted to get as much technical information out to the editors for them to communicate to their readers without spec overload (trust me trying to reign in the engineers can be a merciless job).</p>
<p>Thank you gentlemen for reinforcing that we PR folks can be useful in business - not just a pain-in-the-rump when product folks want to toot their horns!</p>
<p>Charity</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Fuller</title>
		<link>http://www.chipdesignmag.com/blyler/2008/04/30/note-to-startups-work-on-your-briefings/#comment-4924</link>
		<dc:creator>Brian Fuller</dc:creator>
		<pubDate>Mon, 11 Aug 2008 22:52:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.chipdesignmag.com/blyler/?p=95#comment-4924</guid>
		<description>John, nice post. 
I wonder whether time, industry maturity and publication shrinkage has changed the dynamics. In other words, have the number of b.s. briefings fallen because it's harder to get time and attention from editors? In my early days at EET we used to get inundated because there were a bunch of editors and companies tried to play the field to get multiple coverage pieces.</description>
		<content:encoded><![CDATA[<p>John, nice post.<br />
I wonder whether time, industry maturity and publication shrinkage has changed the dynamics. In other words, have the number of b.s. briefings fallen because it&#8217;s harder to get time and attention from editors? In my early days at EET we used to get inundated because there were a bunch of editors and companies tried to play the field to get multiple coverage pieces.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Blyler</title>
		<link>http://www.chipdesignmag.com/blyler/2008/04/30/note-to-startups-work-on-your-briefings/#comment-4457</link>
		<dc:creator>John Blyler</dc:creator>
		<pubDate>Mon, 12 May 2008 14:58:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.chipdesignmag.com/blyler/?p=95#comment-4457</guid>
		<description>Hi Gary. Sorry, I glanced at your website and noticed the reference to an EETimes article. Thought that you must have had a press interview, but instead the interview seems to have been with your partner at Semifore.

I made one of the worst mistakes an editor can do, namely, jumping to a conclusion. Haste makes waste, as they say. Cheers!</description>
		<content:encoded><![CDATA[<p>Hi Gary. Sorry, I glanced at your website and noticed the reference to an EETimes article. Thought that you must have had a press interview, but instead the interview seems to have been with your partner at Semifore.</p>
<p>I made one of the worst mistakes an editor can do, namely, jumping to a conclusion. Haste makes waste, as they say. Cheers!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: New Startup</title>
		<link>http://www.chipdesignmag.com/blyler/2008/04/30/note-to-startups-work-on-your-briefings/#comment-4456</link>
		<dc:creator>New Startup</dc:creator>
		<pubDate>Mon, 12 May 2008 13:45:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.chipdesignmag.com/blyler/?p=95#comment-4456</guid>
		<description>John,

Are you playing the devil’s advocate?

No I'm not. You said that from &lt;a href="http://www.garystringham.com" rel="nofollow"&gt;my website&lt;/a&gt;, it looks like I had had press briefings before. What I have on my website is a press release but I have never been in a face to face meeting with the press about my company and/or product. So that is why I erroneously equated briefing to press release.
As you pointed out in your reponse to Gene, I know the technology "in painful detail" but very little about anything else, like "engaging the press."
Thanks for your clarification.</description>
		<content:encoded><![CDATA[<p>John,</p>
<p>Are you playing the devil’s advocate?</p>
<p>No I&#8217;m not. You said that from <a href="http://www.garystringham.com" rel="nofollow">my website</a>, it looks like I had had press briefings before. What I have on my website is a press release but I have never been in a face to face meeting with the press about my company and/or product. So that is why I erroneously equated briefing to press release.<br />
As you pointed out in your reponse to Gene, I know the technology &#8220;in painful detail&#8221; but very little about anything else, like &#8220;engaging the press.&#8221;<br />
Thanks for your clarification.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Blyler</title>
		<link>http://www.chipdesignmag.com/blyler/2008/04/30/note-to-startups-work-on-your-briefings/#comment-4451</link>
		<dc:creator>John Blyler</dc:creator>
		<pubDate>Sun, 11 May 2008 20:44:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.chipdesignmag.com/blyler/?p=95#comment-4451</guid>
		<description>Hi Gene. Couldn't agree more, i.e., briefings are often used only to keep a company's name in the press, regardless of whether that company has a real product or technology to offer. Sales folks that lack a technical understanding of the product/technology can often make the briefing worse.

NEVERTHELESS, briefings can be a very useful way to get the attention of editor(s) or investor(s). The problem is that many start-ups are understandably headed by someone who understands the technology in painful detail, but knows very little about anything else (like actually creating a product, engaging the press or creating useful PR/marketing material). Which is why many of us seasoned editors have such great tales about briefings with startups. &lt;grin&gt; 

I really do like to cover startup companies, having worked as an engineer or program manager in several startups myself. I'm sure that Chris Edwards (see my original post) likes to cover startup, too. It's just the unproductive briefings that I (and Chris) try to avoid.</description>
		<content:encoded><![CDATA[<p>Hi Gene. Couldn&#8217;t agree more, i.e., briefings are often used only to keep a company&#8217;s name in the press, regardless of whether that company has a real product or technology to offer. Sales folks that lack a technical understanding of the product/technology can often make the briefing worse.</p>
<p>NEVERTHELESS, briefings can be a very useful way to get the attention of editor(s) or investor(s). The problem is that many start-ups are understandably headed by someone who understands the technology in painful detail, but knows very little about anything else (like actually creating a product, engaging the press or creating useful PR/marketing material). Which is why many of us seasoned editors have such great tales about briefings with startups. <grin> </p>
<p>I really do like to cover startup companies, having worked as an engineer or program manager in several startups myself. I&#8217;m sure that Chris Edwards (see my original post) likes to cover startup, too. It&#8217;s just the unproductive briefings that I (and Chris) try to avoid.</grin></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Blyler</title>
		<link>http://www.chipdesignmag.com/blyler/2008/04/30/note-to-startups-work-on-your-briefings/#comment-4450</link>
		<dc:creator>John Blyler</dc:creator>
		<pubDate>Sun, 11 May 2008 20:32:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.chipdesignmag.com/blyler/?p=95#comment-4450</guid>
		<description>Gary: Are you playing the devil's advocate? &lt;grin&gt; No - Briefings are those events were you meet face to face with an editor to talk about your self/product/technology. At a minimum, briefings serve as an information gather activity. At best (from the perspective of many individuals/companies), briefing may convince the editor to cover the person/product/technology in some kind of content vehicle (print, online, blog, etc).

Press releases are another matter. They all follow a certain template, which is good because editors can quickly pick out the main features that the PR person is trying to convey. Of course, press releases are not to be taken seriously, at least by those writers who are trying to cover technology in an independent and meaningful way.</description>
		<content:encoded><![CDATA[<p>Gary: Are you playing the devil&#8217;s advocate? <grin> No - Briefings are those events were you meet face to face with an editor to talk about your self/product/technology. At a minimum, briefings serve as an information gather activity. At best (from the perspective of many individuals/companies), briefing may convince the editor to cover the person/product/technology in some kind of content vehicle (print, online, blog, etc).</p>
<p>Press releases are another matter. They all follow a certain template, which is good because editors can quickly pick out the main features that the PR person is trying to convey. Of course, press releases are not to be taken seriously, at least by those writers who are trying to cover technology in an independent and meaningful way.</grin></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: New Startup</title>
		<link>http://www.chipdesignmag.com/blyler/2008/04/30/note-to-startups-work-on-your-briefings/#comment-4445</link>
		<dc:creator>New Startup</dc:creator>
		<pubDate>Sat, 10 May 2008 15:57:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.chipdesignmag.com/blyler/?p=95#comment-4445</guid>
		<description>Ah, so a briefing is the same thing as a press release. I have heard before from others that editors have complained about the lack of substance in the press releases they've recieved.</description>
		<content:encoded><![CDATA[<p>Ah, so a briefing is the same thing as a press release. I have heard before from others that editors have complained about the lack of substance in the press releases they&#8217;ve recieved.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gene Bushuyev</title>
		<link>http://www.chipdesignmag.com/blyler/2008/04/30/note-to-startups-work-on-your-briefings/#comment-4430</link>
		<dc:creator>Gene Bushuyev</dc:creator>
		<pubDate>Sat, 10 May 2008 00:56:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.chipdesignmag.com/blyler/?p=95#comment-4430</guid>
		<description>Briefings are very often used to create a noise following the principle: any publicity is a good publicity. Lack of content of such briefings is often the result of the absense of the real product and progress on one hand and non-technical (lets call them sales) people, who know not what they are talking about on the other.</description>
		<content:encoded><![CDATA[<p>Briefings are very often used to create a noise following the principle: any publicity is a good publicity. Lack of content of such briefings is often the result of the absense of the real product and progress on one hand and non-technical (lets call them sales) people, who know not what they are talking about on the other.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Blyler</title>
		<link>http://www.chipdesignmag.com/blyler/2008/04/30/note-to-startups-work-on-your-briefings/#comment-4427</link>
		<dc:creator>John Blyler</dc:creator>
		<pubDate>Fri, 09 May 2008 21:51:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.chipdesignmag.com/blyler/?p=95#comment-4427</guid>
		<description>Hi Gary. I'm referring to press briefings, i.e., discussion with the technical press. Judging from the "News" section of your business homepage page, I'd say you've had press briefings before. Cheers. -- John</description>
		<content:encoded><![CDATA[<p>Hi Gary. I&#8217;m referring to press briefings, i.e., discussion with the technical press. Judging from the &#8220;News&#8221; section of your business homepage page, I&#8217;d say you&#8217;ve had press briefings before. Cheers. &#8212; John</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: New Startup</title>
		<link>http://www.chipdesignmag.com/blyler/2008/04/30/note-to-startups-work-on-your-briefings/#comment-4426</link>
		<dc:creator>New Startup</dc:creator>
		<pubDate>Fri, 09 May 2008 21:33:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.chipdesignmag.com/blyler/?p=95#comment-4426</guid>
		<description>I'm a start up but I don't know what you mean by a briefing.</description>
		<content:encoded><![CDATA[<p>I&#8217;m a start up but I don&#8217;t know what you mean by a briefing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
