<?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"
	>
<channel>
	<title>Comments on: Audience Response in Professional Presentations</title>
	<atom:link href="http://derekbruff.com/teachingwithcrs/?feed=rss2&#038;p=180" rel="self" type="application/rss+xml" />
	<link>http://derekbruff.com/teachingwithcrs/?p=180</link>
	<description>Resources for engaging and assessing students with clickers</description>
	<lastBuildDate>Sat, 04 Sep 2010 17:05:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: derekbruff</title>
		<link>http://derekbruff.com/teachingwithcrs/?p=180&#038;cpage=1#comment-311</link>
		<dc:creator>derekbruff</dc:creator>
		<pubDate>Sun, 03 May 2009 20:34:20 +0000</pubDate>
		<guid isPermaLink="false">http://derekbruff.com/teachingwithcrs/?p=180#comment-311</guid>
		<description>Thanks for the comment. I&#039;ve learned a lot about presentations from the Duarte Design blog (and the other resources I mentioned in my post), but until now, I&#039;ve seen little in the world of presentation design about technology-enhanced audience feedback / interactivity has been made.  It&#039;s great to see some connections being made on that topic.

Backchannel feedback of this sort poses a couple of related challenges, I think.  One is the technological challenge you described in your post.  The other is the facilitation challenge: How does one respond productively during or after a presentation to this kind of backchannel?  And there&#039;s potential for a nice intersection of solutions here.  It would be great to see software that can meaningfully aggregate, summarize, or visualize free-response backchannel feedback.  A tool like that would potentially make free-response feedback as easy to leverage as clicker responses shown on a bar chart.

And here&#039;s a little more on that other domain I mentioned, church services.  Time has an article out today on &lt;a href=&quot;http://is.gd/wmSL&quot; rel=&quot;nofollow&quot;&gt;pastors encouraging their church members to Twitter during sermons&lt;/a&gt;.  You raise a good point in your blog about the public nature of Twitter. I can see something like Meebo or Poll Everywhere having value in church settings since attendees could participate in the backchannel more anonymously.</description>
		<content:encoded><![CDATA[<p>Thanks for the comment. I&#8217;ve learned a lot about presentations from the Duarte Design blog (and the other resources I mentioned in my post), but until now, I&#8217;ve seen little in the world of presentation design about technology-enhanced audience feedback / interactivity has been made.  It&#8217;s great to see some connections being made on that topic.</p>
<p>Backchannel feedback of this sort poses a couple of related challenges, I think.  One is the technological challenge you described in your post.  The other is the facilitation challenge: How does one respond productively during or after a presentation to this kind of backchannel?  And there&#8217;s potential for a nice intersection of solutions here.  It would be great to see software that can meaningfully aggregate, summarize, or visualize free-response backchannel feedback.  A tool like that would potentially make free-response feedback as easy to leverage as clicker responses shown on a bar chart.</p>
<p>And here&#8217;s a little more on that other domain I mentioned, church services.  Time has an article out today on <a href="http://is.gd/wmSL" rel="nofollow">pastors encouraging their church members to Twitter during sermons</a>.  You raise a good point in your blog about the public nature of Twitter. I can see something like Meebo or Poll Everywhere having value in church settings since attendees could participate in the backchannel more anonymously.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Iufer</title>
		<link>http://derekbruff.com/teachingwithcrs/?p=180&#038;cpage=1#comment-307</link>
		<dc:creator>Chris Iufer</dc:creator>
		<pubDate>Tue, 28 Apr 2009 20:14:25 +0000</pubDate>
		<guid isPermaLink="false">http://derekbruff.com/teachingwithcrs/?p=180#comment-307</guid>
		<description>I really enjoyed your input on this. It hadn&#039;t occurred to me that the K12 system has already been there--done that in regards to audience polling. I asked my wife (a California HS teacher) about clickers after reading your comment and she confirmed that they use them in various class exercises. *smacks forehead. Clickers were outside the bounds of Nancy&#039;s needs, but it&#039;s still a viable solution to the root problem. 

I guess I missed out when I was in school because this kind of technology would have been a real highlight in my day. Your revelation about crossing domains is gold. I don&#039;t doubt that we have a lot to learn and share with the Education community because upon deeper analysis we are really trying to solve the same problems.</description>
		<content:encoded><![CDATA[<p>I really enjoyed your input on this. It hadn&#8217;t occurred to me that the K12 system has already been there&#8211;done that in regards to audience polling. I asked my wife (a California HS teacher) about clickers after reading your comment and she confirmed that they use them in various class exercises. *smacks forehead. Clickers were outside the bounds of Nancy&#8217;s needs, but it&#8217;s still a viable solution to the root problem. </p>
<p>I guess I missed out when I was in school because this kind of technology would have been a real highlight in my day. Your revelation about crossing domains is gold. I don&#8217;t doubt that we have a lot to learn and share with the Education community because upon deeper analysis we are really trying to solve the same problems.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
