<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: If markets are conversations &#8211; if media will be conversations &#8211; then what do we do?</title>
	<atom:link href="http://www.fastforwardblog.com/2007/07/23/if-markets-are-conversations-if-media-will-be-conversations-then-what-do-we-do/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fastforwardblog.com/2007/07/23/if-markets-are-conversations-if-media-will-be-conversations-then-what-do-we-do/</link>
	<description></description>
	<lastBuildDate>Sat, 07 Nov 2009 18:38:51 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rob Paterson</title>
		<link>http://www.fastforwardblog.com/2007/07/23/if-markets-are-conversations-if-media-will-be-conversations-then-what-do-we-do/comment-page-1/#comment-25900</link>
		<dc:creator>Rob Paterson</dc:creator>
		<pubDate>Tue, 24 Jul 2007 10:25:17 +0000</pubDate>
		<guid isPermaLink="false">http://fastforwardblog.com/2007/07/23/if-markets-are-conversations-if-media-will-be-conversations-then-what-do-we-do/#comment-25900</guid>
		<description>Thanks Paula - very helpful - we will be talking this through
Rob</description>
		<content:encoded><![CDATA[<p>Thanks Paula &#8211; very helpful &#8211; we will be talking this through<br />
Rob</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paula Thornton</title>
		<link>http://www.fastforwardblog.com/2007/07/23/if-markets-are-conversations-if-media-will-be-conversations-then-what-do-we-do/comment-page-1/#comment-25807</link>
		<dc:creator>Paula Thornton</dc:creator>
		<pubDate>Mon, 23 Jul 2007 20:32:42 +0000</pubDate>
		<guid isPermaLink="false">http://fastforwardblog.com/2007/07/23/if-markets-are-conversations-if-media-will-be-conversations-then-what-do-we-do/#comment-25807</guid>
		<description>The current design (http://www.ketc.org/yourstories/) is lacking 2.0 thinking. The conversation should be the feature...the &#039;fixed&#039; information should be &#039;teased&#039; to (it&#039;s the exception...a &#039;read once&#039; bit of content).

For best practice, see the space where the practitioners who design this stuff hang out -- it&#039;s all a conversation, and it&#039;s a community (everyone can have an identity, if they choose):  http://www.boxesandarrows.com/</description>
		<content:encoded><![CDATA[<p>The current design (<a href="http://www.ketc.org/yourstories/" rel="nofollow">http://www.ketc.org/yourstories/</a>) is lacking 2.0 thinking. The conversation should be the feature&#8230;the &#8216;fixed&#8217; information should be &#8216;teased&#8217; to (it&#8217;s the exception&#8230;a &#8216;read once&#8217; bit of content).</p>
<p>For best practice, see the space where the practitioners who design this stuff hang out &#8212; it&#8217;s all a conversation, and it&#8217;s a community (everyone can have an identity, if they choose):  <a href="http://www.boxesandarrows.com/" rel="nofollow">http://www.boxesandarrows.com/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paula Thornton</title>
		<link>http://www.fastforwardblog.com/2007/07/23/if-markets-are-conversations-if-media-will-be-conversations-then-what-do-we-do/comment-page-1/#comment-25806</link>
		<dc:creator>Paula Thornton</dc:creator>
		<pubDate>Mon, 23 Jul 2007 20:28:06 +0000</pubDate>
		<guid isPermaLink="false">http://fastforwardblog.com/2007/07/23/if-markets-are-conversations-if-media-will-be-conversations-then-what-do-we-do/#comment-25806</guid>
		<description>Classic error in the current design...calling out a &#039;blog&#039; as something separate. A blog is a technology, not an event. It supports a conversation...it&#039;s not the justification to have one, nor can it &#039;make&#039; one happen (as the current design supposes). The blog technology should support the exposed conversations (ala. the main page and/or teases into the latest comments on the right). See how the design practitioners in this space create their own publication and have everything as a conversation: http://www.boxesandarrows.com/

The current design misses the point altogether. It should be a &#039;here&#039;s what we&#039;re talking about&#039;. Every piece of content is a part of a conversation...don&#039;t separate the conversations out by technology/channel. Add the technology into the &#039;one-sided&#039; conversations. An easy fix to the current design, is to add 2.0 thinking. Get rid of the &#039;link&#039; on the left to the &#039;blog&#039; (navigation is &#039;out&#039; in 2.0). Expose the most recent entries with titles, authors and first lines in a collection on the right.

A better fix is to expose more of what changes and less of what doesn&#039;t. The &#039;featured text&#039; (http://www.ketc.org/yourstories/) should really be minimized into a right column &#039;tease&#039; to a full page further down. The actual conversation should be fully exposed on the main page.</description>
		<content:encoded><![CDATA[<p>Classic error in the current design&#8230;calling out a &#8216;blog&#8217; as something separate. A blog is a technology, not an event. It supports a conversation&#8230;it&#8217;s not the justification to have one, nor can it &#8216;make&#8217; one happen (as the current design supposes). The blog technology should support the exposed conversations (ala. the main page and/or teases into the latest comments on the right). See how the design practitioners in this space create their own publication and have everything as a conversation: <a href="http://www.boxesandarrows.com/" rel="nofollow">http://www.boxesandarrows.com/</a></p>
<p>The current design misses the point altogether. It should be a &#8216;here&#8217;s what we&#8217;re talking about&#8217;. Every piece of content is a part of a conversation&#8230;don&#8217;t separate the conversations out by technology/channel. Add the technology into the &#8216;one-sided&#8217; conversations. An easy fix to the current design, is to add 2.0 thinking. Get rid of the &#8216;link&#8217; on the left to the &#8216;blog&#8217; (navigation is &#8216;out&#8217; in 2.0). Expose the most recent entries with titles, authors and first lines in a collection on the right.</p>
<p>A better fix is to expose more of what changes and less of what doesn&#8217;t. The &#8216;featured text&#8217; (<a href="http://www.ketc.org/yourstories/" rel="nofollow">http://www.ketc.org/yourstories/</a>) should really be minimized into a right column &#8216;tease&#8217; to a full page further down. The actual conversation should be fully exposed on the main page.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Paterson</title>
		<link>http://www.fastforwardblog.com/2007/07/23/if-markets-are-conversations-if-media-will-be-conversations-then-what-do-we-do/comment-page-1/#comment-25802</link>
		<dc:creator>Rob Paterson</dc:creator>
		<pubDate>Mon, 23 Jul 2007 20:17:30 +0000</pubDate>
		<guid isPermaLink="false">http://fastforwardblog.com/2007/07/23/if-markets-are-conversations-if-media-will-be-conversations-then-what-do-we-do/#comment-25802</guid>
		<description>Yes yes yes Paula - I especially like your last point. Hope to have more to say about that in a week - Thanks
Rob</description>
		<content:encoded><![CDATA[<p>Yes yes yes Paula &#8211; I especially like your last point. Hope to have more to say about that in a week &#8211; Thanks<br />
Rob</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paula Thornton</title>
		<link>http://www.fastforwardblog.com/2007/07/23/if-markets-are-conversations-if-media-will-be-conversations-then-what-do-we-do/comment-page-1/#comment-25799</link>
		<dc:creator>Paula Thornton</dc:creator>
		<pubDate>Mon, 23 Jul 2007 20:11:15 +0000</pubDate>
		<guid isPermaLink="false">http://fastforwardblog.com/2007/07/23/if-markets-are-conversations-if-media-will-be-conversations-then-what-do-we-do/#comment-25799</guid>
		<description>Moreso in the case of public TV and radio, you&#039;re very much talking about opportunities to create the &#039;uber-experience&#039;, a total experience, or the endless event (imagine what that would have looked like for Woodstock, but then again, it still could in retrospect -- the closest thing is the collective story being composed on Wikipedia). The idea is to do varying levels of &#039;uber-experience&#039; -- being careful to decide how much attention can be dedicated internally. The rule of thumb might be to include this as part of any &#039;campaign&#039; planning for a major event.

The other thing would be to be sensitive to early &#039;noise&#039; about an event that the stations were not making much ado about, and make some quick adjustments.

One of the easiest &#039;misses&#039; to fix is the fact that the media does not see each &#039;piece&#039; that they publish as a conversation. For example, in the &#039;Current/Fischer&#039; piece it does not have a conversational component at the bottom (ala, treating the &#039;piece&#039; like a blog entry -- it&#039;s just a technology). For every magazine piece I read, I often have a comment I want to make, or a question I want to pose to the author. As long as comments are reviewed (again, requiring a commitment to having conversations -- which isn&#039;t a small thing, but is oh-so-relevant) they can be effective and make people feel &#039;engaged&#039;.  And, if stored, analysis of the comments help to identify where the most energy lies and what the issues/concerns are.

The idea is not necessarily to &#039;start&#039; conversations. The idea is to open a channel for the conversations waiting to take place.</description>
		<content:encoded><![CDATA[<p>Moreso in the case of public TV and radio, you&#8217;re very much talking about opportunities to create the &#8216;uber-experience&#8217;, a total experience, or the endless event (imagine what that would have looked like for Woodstock, but then again, it still could in retrospect &#8212; the closest thing is the collective story being composed on Wikipedia). The idea is to do varying levels of &#8216;uber-experience&#8217; &#8212; being careful to decide how much attention can be dedicated internally. The rule of thumb might be to include this as part of any &#8216;campaign&#8217; planning for a major event.</p>
<p>The other thing would be to be sensitive to early &#8216;noise&#8217; about an event that the stations were not making much ado about, and make some quick adjustments.</p>
<p>One of the easiest &#8216;misses&#8217; to fix is the fact that the media does not see each &#8216;piece&#8217; that they publish as a conversation. For example, in the &#8216;Current/Fischer&#8217; piece it does not have a conversational component at the bottom (ala, treating the &#8216;piece&#8217; like a blog entry &#8212; it&#8217;s just a technology). For every magazine piece I read, I often have a comment I want to make, or a question I want to pose to the author. As long as comments are reviewed (again, requiring a commitment to having conversations &#8212; which isn&#8217;t a small thing, but is oh-so-relevant) they can be effective and make people feel &#8216;engaged&#8217;.  And, if stored, analysis of the comments help to identify where the most energy lies and what the issues/concerns are.</p>
<p>The idea is not necessarily to &#8217;start&#8217; conversations. The idea is to open a channel for the conversations waiting to take place.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
