<?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: Does asking attendees in advance for program suggestions work?</title>
	<atom:link href="http://www.conferencesthatwork.com/index.php/uncategorized/2010/02/does-asking-attendees-in-advance-for-program-suggestions-work/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.conferencesthatwork.com/index.php/uncategorized/2010/02/does-asking-attendees-in-advance-for-program-suggestions-work/</link>
	<description>Unconferences, participant-driven events, and facilitation</description>
	<lastBuildDate>Thu, 09 Feb 2012 23:44:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: admin</title>
		<link>http://www.conferencesthatwork.com/index.php/uncategorized/2010/02/does-asking-attendees-in-advance-for-program-suggestions-work/comment-page-1/#comment-82</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Tue, 16 Feb 2010 04:17:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.conferencesthatwork.com/?p=534#comment-82</guid>
		<description>Hi Kevin, thanks for your inquiring comments! I agree that asking core attendees for input prior to an event makes that event better than when a program is blindly created without input. But I&#039;m not very impressed by the level of improvement, and that&#039;s because I believe (and attendees seem to agree) that I&#039;ve found a better way to make an event serve its participants.

Over the years, I&#039;ve tried numerous ways to build a standard program in advance by asking for attendee suggestions. And, for the reasons I describe in the post, I haven&#039;t found a way to do this that reliably creates a conference program that attendees rave about. Whereas, using the processes I&#039;ve developed for Conferences That Work develops a great program at the conference every time.

The longer events I run (&gt;2 days) normally have a mixture of attendee-created sessions and traditional predetermined sessions. This helps to market the event to people who are wary of the idea of a conference with no fixed schedule of sessions. However, &lt;em&gt;it&#039;s the peer sessions that invariably make the event meaningful and memorable for the attendees&lt;/em&gt; not the traditional sessions. As I describe in my book, I&#039;ve found that program committees normally predict less than half of the session themes that are actually chosen by attendees. So, in Conferences that Work, it turns out to be not the peer sessions but the &lt;em&gt;traditional&lt;/em&gt; sessions that &quot;flesh out the remainder of the experience&quot;.

I should add that every peer conference includes closing structured sessions that lead attendees through both personal and group introspection about the event they&#039;ve just experienced. Their feedback is then incorporated into future events. The community that is developed around repeated events is indeed, as you say, strengthened by this transparent feedback.</description>
		<content:encoded><![CDATA[<p>Hi Kevin, thanks for your inquiring comments! I agree that asking core attendees for input prior to an event makes that event better than when a program is blindly created without input. But I&#8217;m not very impressed by the level of improvement, and that&#8217;s because I believe (and attendees seem to agree) that I&#8217;ve found a better way to make an event serve its participants.</p>
<p>Over the years, I&#8217;ve tried numerous ways to build a standard program in advance by asking for attendee suggestions. And, for the reasons I describe in the post, I haven&#8217;t found a way to do this that reliably creates a conference program that attendees rave about. Whereas, using the processes I&#8217;ve developed for Conferences That Work develops a great program at the conference every time.</p>
<p>The longer events I run (>2 days) normally have a mixture of attendee-created sessions and traditional predetermined sessions. This helps to market the event to people who are wary of the idea of a conference with no fixed schedule of sessions. However, <em>it&#8217;s the peer sessions that invariably make the event meaningful and memorable for the attendees</em> not the traditional sessions. As I describe in my book, I&#8217;ve found that program committees normally predict less than half of the session themes that are actually chosen by attendees. So, in Conferences that Work, it turns out to be not the peer sessions but the <em>traditional</em> sessions that &#8220;flesh out the remainder of the experience&#8221;.</p>
<p>I should add that every peer conference includes closing structured sessions that lead attendees through both personal and group introspection about the event they&#8217;ve just experienced. Their feedback is then incorporated into future events. The community that is developed around repeated events is indeed, as you say, strengthened by this transparent feedback.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Richardson</title>
		<link>http://www.conferencesthatwork.com/index.php/uncategorized/2010/02/does-asking-attendees-in-advance-for-program-suggestions-work/comment-page-1/#comment-81</link>
		<dc:creator>Kevin Richardson</dc:creator>
		<pubDate>Tue, 16 Feb 2010 02:55:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.conferencesthatwork.com/?p=534#comment-81</guid>
		<description>Adrian,

Some terrific thoughts. In reading it strikes me that what you&#039;re saying is that attendees will indeed tell us what they&#039;re interested in discussing/learning, it all comes down to when we ask. In the moment yields better results than well prior to the event. If I&#039;ve understood the thought, that makes sense.

Wouldn&#039;t a mix of the two make sense? You&#039;ll have a small portion of your community offer suggestions well prior to a conference. Those ideas could build the pillars of an event, while in the moment suggestions can serve to flesh out the remainder of the experience.

In my experience that small community that provides input prior to an event does well when directed on core activities. I&#039;ve also seen that community grow over time if it&#039;s communicated that the changes seen at the event were provided by the community. Nothing brings ideas like seeing community ideas in action.</description>
		<content:encoded><![CDATA[<p>Adrian,</p>
<p>Some terrific thoughts. In reading it strikes me that what you&#8217;re saying is that attendees will indeed tell us what they&#8217;re interested in discussing/learning, it all comes down to when we ask. In the moment yields better results than well prior to the event. If I&#8217;ve understood the thought, that makes sense.</p>
<p>Wouldn&#8217;t a mix of the two make sense? You&#8217;ll have a small portion of your community offer suggestions well prior to a conference. Those ideas could build the pillars of an event, while in the moment suggestions can serve to flesh out the remainder of the experience.</p>
<p>In my experience that small community that provides input prior to an event does well when directed on core activities. I&#8217;ve also seen that community grow over time if it&#8217;s communicated that the changes seen at the event were provided by the community. Nothing brings ideas like seeing community ideas in action.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

