<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>strongcaster</title>
	<atom:link href="http://strongcaster.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://strongcaster.com</link>
	<description>the secrets of communication</description>
	<lastBuildDate>Thu, 22 Jul 2010 23:38:33 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Email overload!</title>
		<link>http://strongcaster.com/email-overload/</link>
		<comments>http://strongcaster.com/email-overload/#comments</comments>
		<pubDate>Thu, 22 Jul 2010 19:34:34 +0000</pubDate>
		<dc:creator>Justin</dc:creator>
				<category><![CDATA[Email]]></category>

		<guid isPermaLink="false">http://strongcaster.com/?p=138</guid>
		<description><![CDATA[Note: I originally wrote this post for our company blog at Mailout Interactive Inc. At our recent workshop, I was speaking to the idea that readers will always prefer one simple message as opposed to many.  I also mentioned that most readers spend only 51 seconds per email.  One of our workshop participants stood up [...]]]></description>
			<content:encoded><![CDATA[<p><em>Note: I originally wrote this post for <a href="http://blog.mailoutinteractive.com">our company blog at Mailout Interactive Inc.</a></em></p>
<p>At our recent workshop, I was speaking to the idea that <strong>readers will always prefer <span style="text-decoration: underline;">one</span> simple message </strong>as opposed to many.  I also mentioned that most <a href="http://www.useit.com/alertbox/newsletters.html"><strong>readers spend only 51 seconds per email</strong></a>.  One of our workshop participants stood up and expressed what many of us feel:<strong> stress from too much email</strong>.</p>
<p><strong>We need to remember that our readers are like us: </strong>they get to work, they fire up their computer, and they see a long list of emails waiting for them.  Some of these are leftovers from the day before.  Added to that heap are new emails: messages from coworkers, their boss, and family.  There&#8217;s also spam, marketing emails, and finally <strong>your newsletter.</strong></p>
<p><strong>All of that email in our readers&#8217; inboxes is overwhelming. </strong>In a <a href="http://www.thisislondon.co.uk/news/article-23408089-workers-suffering-from-email-stress.do">2007 study by the universities of Glasgow and Paisley</a>, 34 percent of respondents were &#8220;stressed&#8221; about the number of emails they received.  To care for our audience, we need to think about what, and how often, we send in our newsletters.</p>
<p><span id="more-138"></span><strong>What you can do</strong></p>
<ul>
<li><strong>Make your content compelling: </strong>when you write, make it awesome.  Develop a reputation for sending really good content that is either <strong>helpful</strong> or <strong>entertaining</strong>.</li>
<li><strong>Send just 1-3 articles: </strong>less articles means a recipient can scan the email quickly, and improves the chances that they will &#8220;dive in deeper&#8221; to one of your articles.</li>
<li><strong>Don&#8217;t send too often: </strong>if you send an email too often, you contribute to the overload in your subscribers&#8217; inboxes.  Send at proper intervals; I think a frequency of 2-4 weeks is right for most audiences.</li>
<li><strong>Ask for feedback: </strong>call or email your recipients and ask them how you could improve your newsletter.</li>
<li><strong>Provide a way for them to opt-out: </strong>if a subscriber is too overwhelmed to continue receiving your emails, they should be able to unsubscribe quickly and easily.</li>
</ul>
<p>The customer above expressed relief at being able to read an email quickly, and then file it away.  Too many articles, or too much information, can overwhelm a reader.  <strong>This means you will need to prioritize: </strong>what is the most important thing(s) I need to say?  Cut down the number of articles, and the length of each article.</p>
<p>When you keep your newsletter simple, you will convey your message more effectively, and cut your subscribers&#8217; stress at the same time!</p>
<h2>Other resources on email stress</h2>
<ul>
<li>&#8220;<a href="E-mail is ruining my life! ">Email is ruining my life!</a>&#8220;, BBC, 2008</li>
<li>&#8220;<a href="http://www.thisislondon.co.uk/news/article-23408089-workers-suffering-from-email-stress.do">Workers suffer from email stress</a>&#8220;, London Evening Standard, 2007</li>
<li>&#8220;<a href="http://www.washingtonpost.com/wp-dyn/content/article/2007/05/24/AR2007052402258.html">Email reply to all: leave me alone</a>&#8220;, Washington Post, 2007</li>
<li>&#8220;<a href="http://orange.eserver.org/issues/5-1/pratt.html">Email Overload in the Workplace: A Multi-Dimensional Exploration</a>&#8220;, Orange, 2006</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://strongcaster.com/email-overload/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Defining the audience for your email newsletter</title>
		<link>http://strongcaster.com/defining-the-audience-for-your-email-newsletter/</link>
		<comments>http://strongcaster.com/defining-the-audience-for-your-email-newsletter/#comments</comments>
		<pubDate>Fri, 07 May 2010 19:53:44 +0000</pubDate>
		<dc:creator>Justin</dc:creator>
				<category><![CDATA[Email]]></category>
		<category><![CDATA[audience]]></category>

		<guid isPermaLink="false">http://strongcaster.com/?p=133</guid>
		<description><![CDATA[Note: I originally wrote this post for Mailout Interactive. I used to work for a national charity.  Each month, I would create an email newsletter.  My objective was clear: &#8220;I need to inform them!&#8221; So I would compile a series of articles on what we&#8217;d done in the past month, and what we were about [...]]]></description>
			<content:encoded><![CDATA[<p><em>Note: I originally wrote this post for <a href="http://mailoutinteractive.com">Mailout Interactive</a>.</em></p>
<p>I used to work for a national charity.  Each month, I would create an  email newsletter.  My objective was clear: <strong>&#8220;I need to inform them!&#8221;</strong> So I would compile a series of articles on what we&#8217;d done in the past  month, and what we were about to do.  I would also have articles on  events, donation opportunities, and photo features.  But the one  question I <span style="text-decoration: underline;"><strong>wasn&#8217;t</strong></span> asking was: <strong><span style="text-decoration: underline;">who</span> will be  reading this?</strong></p>
<p>&#8220;Who is my audience?&#8221; is the first question you should ask when you  sit down to write a newsletter.  <strong>The goal is to define groups of  people as specifically as you can, so that you can send them the content  they are the most likely to read.</strong></p>
<p><span id="more-133"></span></p>
<p>Here&#8217;s how it worked while I was working at the charity.  Generally,  we had two groups: <em>donors and stakeholders</em>.  I soon learned that  these groups differed in the way they processed email.<strong> </strong>Over the  years, I created profiles for my readers with the idea of serving them  the <strong>right type </strong>of content.  Here&#8217;s an example of how this worked  for <strong>donors </strong>and <strong>stakeholders</strong>:</p>
<h3><strong>For donors</strong></h3>
<p>Most of our donors were A-type personalities: they were always on the  move, moving from meeting to meeting, and generally consuming email  on-the-go.  I started calling different donors on my list to ask them  what kind of information they wanted to receive.  After interpreting  those conversations, I came up with two types of email they wanted to  receive:</p>
<ul>
<li><strong>Yearly: a longer update on where their money was going. </strong>This  email would say &#8220;Yearly report&#8221; right in the subject line.  It was  formal and contained an introduction, a financial chart, success  stories, and a conclusion.</li>
<li><strong>More frequently: quick &#8220;actionable&#8221; requests. </strong>These people  were problem solvers: they wanted just one article, that quickly and  clearly defined a problem for them to solve.  This could mean an urgent  financial need, or an important event that we wanted them to attend.   Because it was likely that they would be reading on their Blackberries,  the subject line and the first line of content were very important for  this type of email.</li>
</ul>
<h3>For stakeholders</h3>
<p>These were the people in the community who identified strongly with <strong>our  work </strong>and <strong>our narrative.</strong> This group was definitely more  relaxed when it came to email: they would read email leisurely.  For  them, I decided to send:</p>
<ul>
<li><strong>A regular monthly newsletter: </strong>this was a traditional  newsletter, with 3-5 articles.  Whenever I could, I included a photo  with each article that came from our charity work (no clipart  allowed!).  Each issue also included at least one <strong>story</strong>.  These  recipients loved hearing real-life stories and examples; these types of  articles were always my &#8220;most viewed.&#8221;</li>
</ul>
<p>If you don&#8217;t know you&#8217;re audience, it will be hard to know what to  say.  Building a profile for the different groups within your  subscription list is a great first step to understanding <strong>what</strong> to  send your audience.</p>
]]></content:encoded>
			<wfw:commentRss>http://strongcaster.com/defining-the-audience-for-your-email-newsletter/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Simple guidelines</title>
		<link>http://strongcaster.com/simple-guidelines/</link>
		<comments>http://strongcaster.com/simple-guidelines/#comments</comments>
		<pubDate>Fri, 16 Apr 2010 20:32:16 +0000</pubDate>
		<dc:creator>Justin</dc:creator>
				<category><![CDATA[Blogging]]></category>
		<category><![CDATA[Email]]></category>
		<category><![CDATA[Speaking]]></category>

		<guid isPermaLink="false">http://strongcaster.com/?p=131</guid>
		<description><![CDATA[Good communication guidelines: 1) when writing = 3 main points on 1 page. 2) when speaking = 3 main points in under 15 minutes.]]></description>
			<content:encoded><![CDATA[<p>Good communication guidelines:</p>
<p>1) when writing = 3 main points on 1 page.</p>
<p>2) when speaking = 3 main points in under 15 minutes.</p>
]]></content:encoded>
			<wfw:commentRss>http://strongcaster.com/simple-guidelines/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why are mass-mailers in love with PS?</title>
		<link>http://strongcaster.com/mass-mailers-love-ps/</link>
		<comments>http://strongcaster.com/mass-mailers-love-ps/#comments</comments>
		<pubDate>Thu, 15 Apr 2010 20:03:25 +0000</pubDate>
		<dc:creator>Justin</dc:creator>
				<category><![CDATA[Faux Pas]]></category>
		<category><![CDATA[Marketing]]></category>
		<category><![CDATA[banks]]></category>
		<category><![CDATA[letters]]></category>
		<category><![CDATA[political]]></category>

		<guid isPermaLink="false">http://strongcaster.com/?p=129</guid>
		<description><![CDATA[Ah, the post scriptum.  Best used at the end of love letters to reinforce the writer&#8217;s affection (PS &#8211; I love you), these two letters have found a new home.  They are used primarily by banks hawking high interest loans (PS &#8211; Act now to take advantage of this generous credit offer!) and by political [...]]]></description>
			<content:encoded><![CDATA[<p>Ah, the <em>post scriptum</em>.  Best used at the end of love letters to reinforce the writer&#8217;s affection (<em>PS &#8211; I love you</em>), these two letters have found a new home.  They are used primarily by banks hawking high interest loans (<em>PS &#8211; Act now to take advantage of this generous credit offer!</em>) <strong>and </strong>by political parties (<em>PS &#8211; Help us defeat the Liberals, send us your donation of $50 today!)</em>.</p>
<p>I find it hilarious that these types of communication have a &#8220;PS&#8221; at the end of every single thing they send.  No longer an afterword, or a last-minute addition,<strong> the &#8220;PS&#8221; now signifies one thing: that the sender is completely disingenuous. </strong></p>
]]></content:encoded>
			<wfw:commentRss>http://strongcaster.com/mass-mailers-love-ps/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Quit obessing over design details</title>
		<link>http://strongcaster.com/quit-obessing-over-design-details/</link>
		<comments>http://strongcaster.com/quit-obessing-over-design-details/#comments</comments>
		<pubDate>Thu, 08 Apr 2010 17:04:32 +0000</pubDate>
		<dc:creator>Justin</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[Faux Pas]]></category>

		<guid isPermaLink="false">http://strongcaster.com/?p=127</guid>
		<description><![CDATA[Design is important&#8230; BUT obsessing over a design, without just &#8220;getting on with it&#8221; and delivering some content is a huge mistake.]]></description>
			<content:encoded><![CDATA[<blockquote><p>Design is important&#8230; BUT obsessing over a design, without just &#8220;getting on with it&#8221; and delivering some content is a huge mistake.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://strongcaster.com/quit-obessing-over-design-details/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What is spam?</title>
		<link>http://strongcaster.com/what-is-spam/</link>
		<comments>http://strongcaster.com/what-is-spam/#comments</comments>
		<pubDate>Thu, 11 Mar 2010 00:55:47 +0000</pubDate>
		<dc:creator>Justin</dc:creator>
				<category><![CDATA[Email]]></category>
		<category><![CDATA[Faux Pas]]></category>

		<guid isPermaLink="false">http://strongcaster.com/?p=123</guid>
		<description><![CDATA[When Miles Libbey says that Yahoo &#8220;defines spam as anything users don&#8217;t want in their inbox&#8221; he is revealing that email recipients play a big role in affecting spam filters. Yahoo, and other ISPs, receive this information primarily through complaints: when a user clicks the &#8220;this is spam&#8221; button in their email software, it creates [...]]]></description>
			<content:encoded><![CDATA[<p>When <a href="http://www.dmnews.com/spam-finally-has-a-definition/article/107514/">Miles Libbey says</a> that Yahoo &#8220;<em>defines spam as anything users don&#8217;t want in their inbox</em>&#8221; he is revealing that <strong>email recipients </strong>play <strong>a big role </strong>in affecting spam filters.</p>
<p>Yahoo, and other ISPs, receive this information primarily through complaints: when a user clicks the <strong>&#8220;this is spam&#8221;</strong> button in their email software, it creates a complaint.  When multiple users complain about the same sender, or the same email, the internet service providers adjust their spam filters and start blocking that sender.</p>
<p>This underscores two important points:</p>
<ol>
<li><strong>You should never send email to someone who isn&#8217;t expecting it.</strong> This is especially true for an email that looks like a newsletter or marketing piece.  Even better: build your list from scratch using a subscription form.</li>
<li><strong>All email newsletters should have a visible unsubscribe link.</strong> People want an easy way to stop receiving email from you.  If they can&#8217;t find your unsubscribe link, there&#8217;s a greater chance they will hit the &#8220;this is spam&#8221; button.  I think it&#8217;s best to have a link at the top and the bottom of your email.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://strongcaster.com/what-is-spam/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Content should originate in your blog</title>
		<link>http://strongcaster.com/content-should-originate-in-your-blog/</link>
		<comments>http://strongcaster.com/content-should-originate-in-your-blog/#comments</comments>
		<pubDate>Thu, 14 Jan 2010 17:31:01 +0000</pubDate>
		<dc:creator>Justin</dc:creator>
				<category><![CDATA[Blogging]]></category>
		<category><![CDATA[blog]]></category>
		<category><![CDATA[newsletter]]></category>
		<category><![CDATA[publishing]]></category>
		<category><![CDATA[rss]]></category>

		<guid isPermaLink="false">http://strongcaster.com/?p=121</guid>
		<description><![CDATA[If you publish content to Facebook, Twitter, an email newsletter, and a print newsletter you should only be writing your content once in one place: your blog.  The beauty of a blog that generates an RSS feed is that your content becomes portable.  No need to copy and paste.  No need to wrack your brain [...]]]></description>
			<content:encoded><![CDATA[<p>If you publish content to Facebook, Twitter, an email newsletter, and a print newsletter you should only be writing your content <strong>once</strong> in <strong>one place</strong>: your blog.  The beauty of a blog that generates an RSS feed is that your content becomes portable.  No need to copy and paste.  No need to wrack your brain for articles to write for your next newsletter.  Just click publish, and have it happen automatically.</p>
<p>If you&#8217;re interested in this type of setup, <a href="http://justinjackson.ca">you can hire me to make it so</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://strongcaster.com/content-should-originate-in-your-blog/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Web design goes to hell</title>
		<link>http://strongcaster.com/web-design-goes-to-hell/</link>
		<comments>http://strongcaster.com/web-design-goes-to-hell/#comments</comments>
		<pubDate>Fri, 04 Dec 2009 05:35:47 +0000</pubDate>
		<dc:creator>Justin</dc:creator>
				<category><![CDATA[Design]]></category>

		<guid isPermaLink="false">http://strongcaster.com/?p=118</guid>
		<description><![CDATA[Had to share this brilliant (and true) comic from the Oatmeal.]]></description>
			<content:encoded><![CDATA[<p>Had to share this brilliant (and true) <a href="http://theoatmeal.com/comics/design_hell">comic from <em>the Oatmeal</em></a>.</p>
<p><a href="http://theoatmeal.com/comics/design_hell"><img class="alignnone size-full wp-image-119" title="comic" src="http://strongcaster.com/wp-content/uploads/2009/12/comic.jpg" alt="comic" width="499" height="276" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://strongcaster.com/web-design-goes-to-hell/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Options lead to bad design</title>
		<link>http://strongcaster.com/options-lead-to-bad-design/</link>
		<comments>http://strongcaster.com/options-lead-to-bad-design/#comments</comments>
		<pubDate>Tue, 24 Nov 2009 19:20:11 +0000</pubDate>
		<dc:creator>Justin</dc:creator>
				<category><![CDATA[Design]]></category>

		<guid isPermaLink="false">http://strongcaster.com/?p=115</guid>
		<description><![CDATA[Via Signal vs. Noise: a quote from a Paul Rand essay. The discussion here is on how a client/manager&#8217;s expectations for multiple options ultimately leads to bad design. What do you think? One of the more common problems which tends to create doubt and confusion is caused by the inexperienced and anxious executive who innocently [...]]]></description>
			<content:encoded><![CDATA[<p>Via <a href="http://37signals.com/svn/posts/2023-paul-rand-good-ideas-rarely-come-in-bunches">Signal vs. Noise</a>: a quote from a <a href="http://www.paul-rand.com/thoughts_politics.shtml">Paul Rand essay</a>. The discussion here is on how a client/manager&#8217;s expectations for multiple options ultimately leads to bad design.  <strong>What do you think?</strong></p>
<blockquote><p>One of the more common problems which tends to create doubt and confusion is caused by the inexperienced and anxious executive who innocently expects, or even demands, to see not one but many solutions to a problem. These may include a number of visual and/or verbal concepts, an assortment of layouts, a variety of pictures and color schemes, as well as a choice of type styles. He needs the reassurance of numbers and the opportunity to exercise his personal preferences. He is also most likely to be the one to insist on endless revisions with unrealistic deadlines, adding to an already wasteful and time-consuming ritual. Theoretically, a great number of ideas assures a great number of choices, but such choices are essentially quantitative. This practice is as bewildering as it is wasteful. It discourages spontaneity, encourages indifference, and more often than not produces results which are neither distinguished, interesting, nor effective. In short, good ideas rarely come in bunches.</p>
<p>The designer who voluntarily presents his client with a batch of layouts does so not out prolificacy, but out of uncertainty or fear. He thus encourages the client to assume the role of referee. In the event of genuine need, however, the skillful designer is able to produce a reasonable number of good ideas. But quantity by demand is quite different than quantity by choice. Design is a time-consuming occupation. Whatever his working habits, the designer fills many a wastebasket in order to produce one good idea. Advertising agencies can be especially guilty in this numbers game. Bent on impressing the client with their ardor, they present a welter of layouts, many of which are superficial interpretations of potentially good ideas, or slick renderings of trite ones…</p>
<p>Expertise in business administration, journalism, accounting, or selling, though necessary in its place, is not expertise in problems dealing with visual appearance. The salesman who can sell you the most sophisticated computer typesetting equipment is rarely one who appreciates fine typography or elegant proportions. Actually, the plethora of bad design that we see all around us can probably be attributed as much to good salesmanship as to bad taste.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://strongcaster.com/options-lead-to-bad-design/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Naked and beautiful</title>
		<link>http://strongcaster.com/naked-and-beautiful/</link>
		<comments>http://strongcaster.com/naked-and-beautiful/#comments</comments>
		<pubDate>Thu, 19 Nov 2009 21:06:57 +0000</pubDate>
		<dc:creator>Justin</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[coke]]></category>
		<category><![CDATA[naked]]></category>

		<guid isPermaLink="false">http://strongcaster.com/?p=112</guid>
		<description><![CDATA[This naked Coke can (the invention of Ryan Harc) is one of the most beautiful things I have seen.  Whats more, by removing the color, this packaging reduces the energy needed to both create and recycle the cans.]]></description>
			<content:encoded><![CDATA[<p>This naked Coke can (the invention of <a href="http://www.7760.org/ecopackage">Ryan Harc</a>) is one of the most beautiful things I have seen.  Whats more, by removing the color, this packaging reduces the energy needed to both create and recycle the cans.</p>
<p><a href="http://www.7760.org/ecopackage/ecopackage2"><img class="alignnone size-full wp-image-113" title="coke" src="http://strongcaster.com/wp-content/uploads/2009/11/coke.jpg" alt="coke" width="499" height="290" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://strongcaster.com/naked-and-beautiful/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
