<?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: Just Say No?</title>
	<atom:link href="http://socialhoneycomb.com/just-say-no/feed" rel="self" type="application/rss+xml" />
	<link>http://socialhoneycomb.com/just-say-no</link>
	<description>somewhere between the sticky and the buzz</description>
	<lastBuildDate>Thu, 30 Sep 2010 14:21:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: CL</title>
		<link>http://socialhoneycomb.com/just-say-no/comment-page-1#comment-1645</link>
		<dc:creator>CL</dc:creator>
		<pubDate>Mon, 05 Oct 2009 23:36:09 +0000</pubDate>
		<guid isPermaLink="false">http://socialhoneycomb.com/?p=385#comment-1645</guid>
		<description>Here&#039;s a technology reporter&#039;s perspective: I don&#039;t have any trouble responding to a pitch with a &quot;Yes&quot; or &quot;No&quot; when I have a solid reason. (For instance, &quot;It&#039;s not by beat&quot; or &quot;It&#039;s not a timely topic.&quot;) But I struggle when I really don&#039;t have a good explanation, yet have to say &quot;No.&quot; The reason a topic doesn&#039;t get covered could be as dumb as &quot;I&#039;m not in the mood to cover data-management this month&quot; to &quot;I don&#039;t know enough about the topic.&quot; So, instead of providing what I know as an unacceptable answer, I chose to ignore the pitch. (Please don&#039;t hate me.)

But you&#039;re absolutely right: The PR person who has put in considerable time and energy deserves the courtesy of a response, at the very least. I promise to make a concerted effort to do that.</description>
		<content:encoded><![CDATA[<p>Here&#8217;s a technology reporter&#8217;s perspective: I don&#8217;t have any trouble responding to a pitch with a &#8220;Yes&#8221; or &#8220;No&#8221; when I have a solid reason. (For instance, &#8220;It&#8217;s not by beat&#8221; or &#8220;It&#8217;s not a timely topic.&#8221;) But I struggle when I really don&#8217;t have a good explanation, yet have to say &#8220;No.&#8221; The reason a topic doesn&#8217;t get covered could be as dumb as &#8220;I&#8217;m not in the mood to cover data-management this month&#8221; to &#8220;I don&#8217;t know enough about the topic.&#8221; So, instead of providing what I know as an unacceptable answer, I chose to ignore the pitch. (Please don&#8217;t hate me.)</p>
<p>But you&#8217;re absolutely right: The PR person who has put in considerable time and energy deserves the courtesy of a response, at the very least. I promise to make a concerted effort to do that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kenneth</title>
		<link>http://socialhoneycomb.com/just-say-no/comment-page-1#comment-1537</link>
		<dc:creator>Kenneth</dc:creator>
		<pubDate>Sat, 25 Apr 2009 20:23:33 +0000</pubDate>
		<guid isPermaLink="false">http://socialhoneycomb.com/?p=385#comment-1537</guid>
		<description>Here&#039;s a technology reporter&#039;s perspective: I don&#039;t have any trouble responding to a pitch with a &quot;Yes&quot; or &quot;No&quot; when I have a solid reason. (For instance, &quot;It&#039;s not by beat&quot; or &quot;It&#039;s not a timely topic.&quot;) But I struggle when I really don&#039;t have a good explanation, yet have to say &quot;No.&quot; The reason a topic doesn&#039;t get covered could be as dumb as &quot;I&#039;m not in the mood to cover data-management this month&quot; to &quot;I don&#039;t know enough about the topic.&quot; So, instead of providing what I know as an unacceptable answer, I chose to ignore the pitch. (Please don&#039;t hate me.)

But you&#039;re absolutely right: The PR person who has put in considerable time and energy deserves the courtesy of a response, at the very least. I promise to make a concerted effort to do that.</description>
		<content:encoded><![CDATA[<p>Here&#8217;s a technology reporter&#8217;s perspective: I don&#8217;t have any trouble responding to a pitch with a &#8220;Yes&#8221; or &#8220;No&#8221; when I have a solid reason. (For instance, &#8220;It&#8217;s not by beat&#8221; or &#8220;It&#8217;s not a timely topic.&#8221;) But I struggle when I really don&#8217;t have a good explanation, yet have to say &#8220;No.&#8221; The reason a topic doesn&#8217;t get covered could be as dumb as &#8220;I&#8217;m not in the mood to cover data-management this month&#8221; to &#8220;I don&#8217;t know enough about the topic.&#8221; So, instead of providing what I know as an unacceptable answer, I chose to ignore the pitch. (Please don&#8217;t hate me.)</p>
<p>But you&#8217;re absolutely right: The PR person who has put in considerable time and energy deserves the courtesy of a response, at the very least. I promise to make a concerted effort to do that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shiv</title>
		<link>http://socialhoneycomb.com/just-say-no/comment-page-1#comment-1536</link>
		<dc:creator>Shiv</dc:creator>
		<pubDate>Sat, 25 Apr 2009 04:40:03 +0000</pubDate>
		<guid isPermaLink="false">http://socialhoneycomb.com/?p=385#comment-1536</guid>
		<description>Oh Amanda, such a dreamer.</description>
		<content:encoded><![CDATA[<p>Oh Amanda, such a dreamer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Foster</title>
		<link>http://socialhoneycomb.com/just-say-no/comment-page-1#comment-1529</link>
		<dc:creator>Mike Foster</dc:creator>
		<pubDate>Fri, 10 Apr 2009 06:09:13 +0000</pubDate>
		<guid isPermaLink="false">http://socialhoneycomb.com/?p=385#comment-1529</guid>
		<description>Kill &#039;em with kindness, but still just say no...


peace,
mike
livelife365</description>
		<content:encoded><![CDATA[<p>Kill &#8216;em with kindness, but still just say no&#8230;</p>
<p>peace,<br />
mike<br />
livelife365</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick C</title>
		<link>http://socialhoneycomb.com/just-say-no/comment-page-1#comment-1528</link>
		<dc:creator>Patrick C</dc:creator>
		<pubDate>Wed, 08 Apr 2009 19:26:30 +0000</pubDate>
		<guid isPermaLink="false">http://socialhoneycomb.com/?p=385#comment-1528</guid>
		<description>Amanda - came across your blog the other night, a la one of your BFF&#039;s from back in the day (think oldest LeDoux - her and I are ... BFF++ and then some) - anyhow - great content, we&#039;re both in the same field ...

I came to realize a few years ago, that &quot;No&quot; is a perfectly acceptable answer, it&#039;s actually an answer.  Sure the client may not want to hear it right then and there, but it&#039;s a valid and sometimes very powerful answer.  Our job is to tell our clients what&#039;s right, wrong, strategic and out right ridiculous.  That&#039;s appropriate client or internally project team facing.  What I have seen is though, too many client teams trying to over-service a client by NOT saying no, which end up being a dis-service to our own resources, capacity, the program, and eventually our clients.  If we say no and back it up with the appropriate recommendations and responses, it&#039;s what the client needs.  We spend way too much time in this day and age chasing after land-grab activities with the advent of these social platforms, sometimes we forget, is this really appropriate for the program?</description>
		<content:encoded><![CDATA[<p>Amanda &#8211; came across your blog the other night, a la one of your BFF&#8217;s from back in the day (think oldest LeDoux &#8211; her and I are &#8230; BFF++ and then some) &#8211; anyhow &#8211; great content, we&#8217;re both in the same field &#8230;</p>
<p>I came to realize a few years ago, that &#8220;No&#8221; is a perfectly acceptable answer, it&#8217;s actually an answer.  Sure the client may not want to hear it right then and there, but it&#8217;s a valid and sometimes very powerful answer.  Our job is to tell our clients what&#8217;s right, wrong, strategic and out right ridiculous.  That&#8217;s appropriate client or internally project team facing.  What I have seen is though, too many client teams trying to over-service a client by NOT saying no, which end up being a dis-service to our own resources, capacity, the program, and eventually our clients.  If we say no and back it up with the appropriate recommendations and responses, it&#8217;s what the client needs.  We spend way too much time in this day and age chasing after land-grab activities with the advent of these social platforms, sometimes we forget, is this really appropriate for the program?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ANGirard</title>
		<link>http://socialhoneycomb.com/just-say-no/comment-page-1#comment-1527</link>
		<dc:creator>ANGirard</dc:creator>
		<pubDate>Tue, 07 Apr 2009 15:43:54 +0000</pubDate>
		<guid isPermaLink="false">http://socialhoneycomb.com/?p=385#comment-1527</guid>
		<description>I think this is a great point.  As much as I don&#039;t like to hear &quot;no&quot;... that simple two-letter word provides me with feedback to know that I shouldn&#039;t waste mine, or the reporter&#039;s time, with additional follow up.</description>
		<content:encoded><![CDATA[<p>I think this is a great point.  As much as I don&#8217;t like to hear &#8220;no&#8221;&#8230; that simple two-letter word provides me with feedback to know that I shouldn&#8217;t waste mine, or the reporter&#8217;s time, with additional follow up.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

