<?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: The conveyor belt</title>
	<atom:link href="http://www.richardingram.co.uk/2010/04/the-conveyor-belt/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.richardingram.co.uk/2010/04/the-conveyor-belt/</link>
	<description>Richard Ingram&#039;s blog about content strategy, information design, and web accessibility</description>
	<lastBuildDate>Tue, 04 Jun 2013 11:22:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.1.42</generator>
	<item>
		<title>By: Richard Ingram</title>
		<link>http://www.richardingram.co.uk/2010/04/the-conveyor-belt/comment-page-1/#comment-537</link>
		<dc:creator><![CDATA[Richard Ingram]]></dc:creator>
		<pubDate>Thu, 29 Apr 2010 09:13:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.richardingram.co.uk/?p=560#comment-537</guid>
		<description><![CDATA[Thanks Rahel.

I was focusing more on companies who don&#039;t produce a tremendous amount of content to start with. So rather than a collection of their best work it *is* the sum of their work for that period, or even dating back further.

They can be easily wooed by the prospect of publishing content regularly to their customer base, but often they&#039;re not prepared for the schedule they&#039;ll have to keep to and overlook the importance of sustaining its quality once they&#039;ve passed the honeymoon period.]]></description>
		<content:encoded><![CDATA[<p>Thanks Rahel.</p>
<p>I was focusing more on companies who don&#8217;t produce a tremendous amount of content to start with. So rather than a collection of their best work it *is* the sum of their work for that period, or even dating back further.</p>
<p>They can be easily wooed by the prospect of publishing content regularly to their customer base, but often they&#8217;re not prepared for the schedule they&#8217;ll have to keep to and overlook the importance of sustaining its quality once they&#8217;ve passed the honeymoon period.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rahel Bailie</title>
		<link>http://www.richardingram.co.uk/2010/04/the-conveyor-belt/comment-page-1/#comment-531</link>
		<dc:creator><![CDATA[Rahel Bailie]]></dc:creator>
		<pubDate>Wed, 28 Apr 2010 13:50:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.richardingram.co.uk/?p=560#comment-531</guid>
		<description><![CDATA[You make a good point, Richard. If I may look at the issue using a different metaphor, I would stop thinking &quot;newsletter&quot; altogether, and start thinking &quot;the best of&quot; collection. 

Newsletters are a hold-over from the days of pre-internet print. An organization couldn&#039;t afford to tell its constituents about every noteworthy item because the cost of mailing was prohibitive, and the time involved in publishing, printing, and stuffing envelopes would have been overwhelming. The newsletter was a nice, tidy solution to gather up all the news in one place, and get any decision-making deadlines out there (a &quot;sign up by 3 weeks from receipt of this newsletter&quot;). In fact, the timing of events and decisions often revolved around the issuance of the newsletter (I am definitely showing my age here!) and the receipt of the newsletter was an event in itself.

There is no longer a technical need to hold onto news for 3 months in order to issue a quarterly newsletter. Organizations can send separate communications for news and use a plethora of techniques to garner feedback from constituents. So how can/could/should affect the role of a newsletter? For organizations, the newsletter has become more of a compendium of &quot;the best of&quot; the newsworthy items since the last publication date.  User expectation has also changed, with regards to what would be communicated on a scheduled cycle as opposed to time-sensitive news, and would not expect, for example, a decision-critical issue to be an item within a periodic newsletter.

So while I agree that a conveyor belt metaphor works to an extent - you do have to produce before you can report - the impetus is not to produce for the newsletter but rather to use the newsletter to collect the &quot;best of&quot;, whether that be by theme, by time period, or any other facet of content. And that does mean, as you rightfully said, putting a plan into place and committing the appropriate resources to ensure that the newsletter lives up to its purpose.]]></description>
		<content:encoded><![CDATA[<p>You make a good point, Richard. If I may look at the issue using a different metaphor, I would stop thinking &#8220;newsletter&#8221; altogether, and start thinking &#8220;the best of&#8221; collection. </p>
<p>Newsletters are a hold-over from the days of pre-internet print. An organization couldn&#8217;t afford to tell its constituents about every noteworthy item because the cost of mailing was prohibitive, and the time involved in publishing, printing, and stuffing envelopes would have been overwhelming. The newsletter was a nice, tidy solution to gather up all the news in one place, and get any decision-making deadlines out there (a &#8220;sign up by 3 weeks from receipt of this newsletter&#8221;). In fact, the timing of events and decisions often revolved around the issuance of the newsletter (I am definitely showing my age here!) and the receipt of the newsletter was an event in itself.</p>
<p>There is no longer a technical need to hold onto news for 3 months in order to issue a quarterly newsletter. Organizations can send separate communications for news and use a plethora of techniques to garner feedback from constituents. So how can/could/should affect the role of a newsletter? For organizations, the newsletter has become more of a compendium of &#8220;the best of&#8221; the newsworthy items since the last publication date.  User expectation has also changed, with regards to what would be communicated on a scheduled cycle as opposed to time-sensitive news, and would not expect, for example, a decision-critical issue to be an item within a periodic newsletter.</p>
<p>So while I agree that a conveyor belt metaphor works to an extent &#8211; you do have to produce before you can report &#8211; the impetus is not to produce for the newsletter but rather to use the newsletter to collect the &#8220;best of&#8221;, whether that be by theme, by time period, or any other facet of content. And that does mean, as you rightfully said, putting a plan into place and committing the appropriate resources to ensure that the newsletter lives up to its purpose.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets that mention The conveyor belt &#124; Richard Ingram &#124; Shut the door on your way out Cicero… -- Topsy.com</title>
		<link>http://www.richardingram.co.uk/2010/04/the-conveyor-belt/comment-page-1/#comment-484</link>
		<dc:creator><![CDATA[Tweets that mention The conveyor belt &#124; Richard Ingram &#124; Shut the door on your way out Cicero… -- Topsy.com]]></dc:creator>
		<pubDate>Fri, 23 Apr 2010 12:04:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.richardingram.co.uk/?p=560#comment-484</guid>
		<description><![CDATA[[...] This post was mentioned on Twitter by Richard Ingram. Richard Ingram said: New blog entry: Publishing content directly to your audience is like sitting on a conveyor belt http://bit.ly/aXU6iv #contentstrategy [...]]]></description>
		<content:encoded><![CDATA[<p>[&#8230;] This post was mentioned on Twitter by Richard Ingram. Richard Ingram said: New blog entry: Publishing content directly to your audience is like sitting on a conveyor belt <a href="http://bit.ly/aXU6iv" rel="nofollow">http://bit.ly/aXU6iv</a> #contentstrategy [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
