<?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: Stories&#8230;Impact	</title>
	<atom:link href="https://claxon-communication.com/2011/06/01/stories-impact/feed/" rel="self" type="application/rss+xml" />
	<link>https://claxon-communication.com/2011/06/01/stories-impact/</link>
	<description>Claxon creates powerful messaging for purpose-driven clients.</description>
	<lastBuildDate>Wed, 08 Jun 2011 18:19:48 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.7.2</generator>
	<item>
		<title>
		By: Erica		</title>
		<link>https://claxon-communication.com/2011/06/01/stories-impact/#comment-86</link>

		<dc:creator><![CDATA[Erica]]></dc:creator>
		<pubDate>Wed, 08 Jun 2011 18:19:48 +0000</pubDate>
		<guid isPermaLink="false">https://claxon-communication.com/?p=1824#comment-86</guid>

					<description><![CDATA[Great question, Carolyn! How you decide to handle this comes back to brand and authenticity, i.e. is your organization&#039;s personality approachable and friendly, or more serious and practical. If it&#039;s the former, using &#039;John&#039; or &#039;Kate&#039; and leaving it at that, without the asterisks, is a common approach. If it&#039;s the latter, your readers will not be thrown by the asterisks. They will actually expect it. 

So no hard and fast rule, sorry! But if you answer the question: &quot;if our organization were a movie star, who would it be?&quot;, will get you a long way to answering your question...plus many others!]]></description>
			<content:encoded><![CDATA[<p>Great question, Carolyn! How you decide to handle this comes back to brand and authenticity, i.e. is your organization&#8217;s personality approachable and friendly, or more serious and practical. If it&#8217;s the former, using &#8216;John&#8217; or &#8216;Kate&#8217; and leaving it at that, without the asterisks, is a common approach. If it&#8217;s the latter, your readers will not be thrown by the asterisks. They will actually expect it. </p>
<p>So no hard and fast rule, sorry! But if you answer the question: &#8220;if our organization were a movie star, who would it be?&#8221;, will get you a long way to answering your question&#8230;plus many others!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Carolyn Hamilton		</title>
		<link>https://claxon-communication.com/2011/06/01/stories-impact/#comment-85</link>

		<dc:creator><![CDATA[Carolyn Hamilton]]></dc:creator>
		<pubDate>Wed, 08 Jun 2011 17:21:52 +0000</pubDate>
		<guid isPermaLink="false">https://claxon-communication.com/?p=1824#comment-85</guid>

					<description><![CDATA[Thank you for reinforcing my belief in the power of stories!

At DESC, we are first and foremost concerned with client confidentiality. I&#039;d like to see you address the best way to identify the person in the story. Some examples I&#039;ve seen:  John W, or &quot;John&quot; (in quotes to imply it&#039;s not his real name). 

I hate to add an asterisk and &quot;not his real name&quot; because I think it dilutes the power of the story, implying that because the name isn&#039;t real, the story might not be, either.

Thoughts?
Carolyn]]></description>
			<content:encoded><![CDATA[<p>Thank you for reinforcing my belief in the power of stories!</p>
<p>At DESC, we are first and foremost concerned with client confidentiality. I&#8217;d like to see you address the best way to identify the person in the story. Some examples I&#8217;ve seen:  John W, or &#8220;John&#8221; (in quotes to imply it&#8217;s not his real name). </p>
<p>I hate to add an asterisk and &#8220;not his real name&#8221; because I think it dilutes the power of the story, implying that because the name isn&#8217;t real, the story might not be, either.</p>
<p>Thoughts?<br />
Carolyn</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
