<?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"
	>
<channel>
	<title>Comments on: Why Panels Suck</title>
	<atom:link href="http://www.blogarithms.com/index.php/archives/2007/02/24/why-panels-suck/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.blogarithms.com/index.php/archives/2007/02/24/why-panels-suck/</link>
	<description>Doug Kaye's Weblog</description>
	<pubDate>Fri, 16 May 2008 04:06:51 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: THD</title>
		<link>http://www.blogarithms.com/index.php/archives/2007/02/24/why-panels-suck/#comment-25368</link>
		<dc:creator>THD</dc:creator>
		<pubDate>Sun, 25 Mar 2007 21:46:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogarithms.com/index.php/archives/2007/02/24/why-panels-suck/#comment-25368</guid>
		<description>The other limitation of panels is all the time spent by panelists on the history of their work/org/initiative. This is not always the fault of the panelists, but perhaps this could be mitigate by referring the audience to a short description of the org or panelists in a program guide. I often find that the panel format takes a long time to jump straight to substantive issues or valuable opinions and key thoughts the panelists really have to offer. 

As an audience member I don't mind a short description or some marketing, but what I really want to hear is how this person thinks about an issue, what challenges they are facing or something else that I can't read on the the persons/organizations website.</description>
		<content:encoded><![CDATA[<p>The other limitation of panels is all the time spent by panelists on the history of their work/org/initiative. This is not always the fault of the panelists, but perhaps this could be mitigate by referring the audience to a short description of the org or panelists in a program guide. I often find that the panel format takes a long time to jump straight to substantive issues or valuable opinions and key thoughts the panelists really have to offer. </p>
<p>As an audience member I don&#8217;t mind a short description or some marketing, but what I really want to hear is how this person thinks about an issue, what challenges they are facing or something else that I can&#8217;t read on the the persons/organizations website.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Brogan...</title>
		<link>http://www.blogarithms.com/index.php/archives/2007/02/24/why-panels-suck/#comment-23908</link>
		<dc:creator>Chris Brogan...</dc:creator>
		<pubDate>Tue, 27 Feb 2007 17:28:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogarithms.com/index.php/archives/2007/02/24/why-panels-suck/#comment-23908</guid>
		<description>I attended your Podcast Academy 2 in Boston and loved your method for delivering quality speakers without panel blur. 

It's part of how Chris Penn and I modeled our plan for PodCamp. We wanted the most value translation between speaker and participant. 

At our spring Video on the Net event this spring, there will be single-speaker only spots, and no panels. We're hoping this helps answer your observation above. 

Best to you, Doug.</description>
		<content:encoded><![CDATA[<p>I attended your Podcast Academy 2 in Boston and loved your method for delivering quality speakers without panel blur. </p>
<p>It&#8217;s part of how Chris Penn and I modeled our plan for PodCamp. We wanted the most value translation between speaker and participant. </p>
<p>At our spring Video on the Net event this spring, there will be single-speaker only spots, and no panels. We&#8217;re hoping this helps answer your observation above. </p>
<p>Best to you, Doug.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
