<?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: How long should your story be?</title>
	<atom:link href="http://www.mcwade.com/DesignTalk/2010/03/how-long-should-your-story-be/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mcwade.com/DesignTalk/2010/03/how-long-should-your-story-be/</link>
	<description>Before &#38; After&#039;s creative director John McWade&#039;s conversations with subscribers</description>
	<lastBuildDate>Sat, 04 Feb 2012 20:24:36 -0600</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: Anne Anderson</title>
		<link>http://www.mcwade.com/DesignTalk/2010/03/how-long-should-your-story-be/comment-page-1/#comment-2746</link>
		<dc:creator>Anne Anderson</dc:creator>
		<pubDate>Tue, 20 Apr 2010 22:44:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.mcwade.com/DesignTalk/?p=3409#comment-2746</guid>
		<description>Sarah hits the nail on the head here. It&#039;s not that people don&#039;t read, it&#039;s that people don&#039;t read boring stuff.  There&#039;s a formula &lt;em&gt;and&lt;/em&gt; an art to writing engaging material. And sometimes more is too much. I&#039;ve had clients who&#039;ve panicked believing that if they don&#039;t swamp the reader with details and flowery prose the reader won&#039;t be able to tell what a great event/cause/idea they have -- event announcement postcards with way too much detail, articles that are full of high-flown corporate-speak and nearly content-free as a result.</description>
		<content:encoded><![CDATA[<p>Sarah hits the nail on the head here. It&#8217;s not that people don&#8217;t read, it&#8217;s that people don&#8217;t read boring stuff.  There&#8217;s a formula <em>and</em> an art to writing engaging material. And sometimes more is too much. I&#8217;ve had clients who&#8217;ve panicked believing that if they don&#8217;t swamp the reader with details and flowery prose the reader won&#8217;t be able to tell what a great event/cause/idea they have &#8212; event announcement postcards with way too much detail, articles that are full of high-flown corporate-speak and nearly content-free as a result.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sarah</title>
		<link>http://www.mcwade.com/DesignTalk/2010/03/how-long-should-your-story-be/comment-page-1/#comment-2695</link>
		<dc:creator>Sarah</dc:creator>
		<pubDate>Mon, 29 Mar 2010 20:06:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.mcwade.com/DesignTalk/?p=3409#comment-2695</guid>
		<description>I agree. It really is about how meaningful and applicable the content is to me, the reader. If it&#039;s meaningful, I&#039;ll read three pages. 

I lead a blog for executives of our company. They write articles that they care about, but the &quot;meat&quot; is buried in there . . . somewhere. My job has been to pull the gems from their writing and dust them off so that readers can actually appreciate them. So yeah, it’s not so much about being short or brief, but making it clear, engaging, and easy to read. Concise, not academic. Keeping the audience in mind.</description>
		<content:encoded><![CDATA[<p>I agree. It really is about how meaningful and applicable the content is to me, the reader. If it&#8217;s meaningful, I&#8217;ll read three pages. </p>
<p>I lead a blog for executives of our company. They write articles that they care about, but the &#8220;meat&#8221; is buried in there . . . somewhere. My job has been to pull the gems from their writing and dust them off so that readers can actually appreciate them. So yeah, it’s not so much about being short or brief, but making it clear, engaging, and easy to read. Concise, not academic. Keeping the audience in mind.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Don Cheke</title>
		<link>http://www.mcwade.com/DesignTalk/2010/03/how-long-should-your-story-be/comment-page-1/#comment-2684</link>
		<dc:creator>Don Cheke</dc:creator>
		<pubDate>Wed, 24 Mar 2010 23:33:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.mcwade.com/DesignTalk/?p=3409#comment-2684</guid>
		<description>Very well said!

There are often times I have come across web sites where I wish wholeheartedly for much more information -- usually artistic web sites where I want to know more about the person behind the creations. 

Although I have been known to contact the artist(s) to inquire, this doesn&#039;t always seem appropriate.</description>
		<content:encoded><![CDATA[<p>Very well said!</p>
<p>There are often times I have come across web sites where I wish wholeheartedly for much more information &#8212; usually artistic web sites where I want to know more about the person behind the creations. </p>
<p>Although I have been known to contact the artist(s) to inquire, this doesn&#8217;t always seem appropriate.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

