<?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: WEC Final: Love 161, Fiasco Zero</title>
	<atom:link href="https://www.interactivemeetingtechnology.com/wec-final-love-161-fiasco-zero/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.interactivemeetingtechnology.com/wec-final-love-161-fiasco-zero/</link>
	<description>Attendee Engagement for Events</description>
	<lastBuildDate>Sun, 19 May 2013 23:09:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.2.38</generator>
	<item>
		<title>By: samueljsmith</title>
		<link>https://www.interactivemeetingtechnology.com/wec-final-love-161-fiasco-zero/#comment-749</link>
		<dc:creator><![CDATA[samueljsmith]]></dc:creator>
		<pubDate>Mon, 16 Aug 2010 13:56:05 +0000</pubDate>
		<guid isPermaLink="false">http://interactivemeetingtechnology.com/?p=1792#comment-749</guid>
		<description><![CDATA[Hi Mitchell,

Thanks for your comment. It was great to meet you at WEC. I remember a few sessions where you were typing so fast that I thought your keyboard was going to catch on fire.

While I can’t think of an event where live tweeting was done by a reporter - I can think of several examples where attendees have assumed the role of “fact based tweeter” during live sessions.

I think this role is important role for events that want to use Twitter to spread their messages beyond their four walls. These highlights or sound bite tweets are the ones that seem to be retweeted the most.]]></description>
		<content:encoded><![CDATA[<p>Hi Mitchell,</p>
<p>Thanks for your comment. It was great to meet you at WEC. I remember a few sessions where you were typing so fast that I thought your keyboard was going to catch on fire.</p>
<p>While I can’t think of an event where live tweeting was done by a reporter &#8211; I can think of several examples where attendees have assumed the role of “fact based tweeter” during live sessions.</p>
<p>I think this role is important role for events that want to use Twitter to spread their messages beyond their four walls. These highlights or sound bite tweets are the ones that seem to be retweeted the most.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mitchell Beer, The Conference Publishers Inc.</title>
		<link>https://www.interactivemeetingtechnology.com/wec-final-love-161-fiasco-zero/#comment-748</link>
		<dc:creator><![CDATA[Mitchell Beer, The Conference Publishers Inc.]]></dc:creator>
		<pubDate>Mon, 16 Aug 2010 03:11:30 +0000</pubDate>
		<guid isPermaLink="false">http://interactivemeetingtechnology.com/?p=1792#comment-748</guid>
		<description><![CDATA[That&#039;s a really interesting analysis, Samuel. While we were onsite, I had a sense that there was a lot of activity going on -- most obviously during the general sessions, when the volume of tweets swamped the available capacity -- and that people were generally pleased with the social media side of the conference. But the plural of &quot;anecdote&quot; is not &quot;evidence&quot; (I didn&#039;t make that up, but it&#039;s one of my favourite quotes), and I&#039;m glad you&#039;ve put some numbers behind the overall impression.
 
I&#039;m also pleased that the word &#039;reporter&#039; figured fairly prominently in the word cloud. The story behind that points to something new that was introduced to the Twitter stream during WEC. The &#039;reporter&#039; tag might point toward a solution for organizations that have been interested in onsite social media but nervous that their messaging will be overwhelmed by the sheer volume of independent voices.
 
As usual at WEC, I was onsite wearing a few different hats -- as an MPI member and volunteer, but also as one of several companies involved in producing the two general sessions. For each of those sessions, we had a team of two writers and one writer/editor live-tweeting the content as it was presented -- so, yes, as the writer/editor on the team, I can echo your comment that it&#039;s a tough job. 

Between the two sessions, we produced 145 tweets, but the nature of the content was more important than the character count: we wouldn&#039;t have contributed to the &#039;good&#039;, &#039;bad&#039;, or &#039;fiasco&#039; count in the word cloud because everything we produced was focused on reporting **someone else&#039;s opinion**, not our own. (The exception was when I shouted WELCOME, ERIC! when the gavel passed to MPI&#039;s new International Chair.) The intent of the experiment was not to offset or dilute the social media content, but to lead toward the kind of balance that daily newspapers achieve between news reporting and opinion content.
 
To my knowledge, this was the first time a conference had used live-tweeting to deliver reporting as well as opinion. Time will tell whether it turns out to be a one-off attempt or a productive new way of integrating onsite content and social media. I&#039;m telling the story at some length, not to promote the approach, but because we&#039;re genuinely interested in gathering feedback on whether it had an impact...and if not, whether we could have produced or signposted the tweets more effectively. I’d really appreciate comments from you and your readers.]]></description>
		<content:encoded><![CDATA[<p>That&#8217;s a really interesting analysis, Samuel. While we were onsite, I had a sense that there was a lot of activity going on &#8212; most obviously during the general sessions, when the volume of tweets swamped the available capacity &#8212; and that people were generally pleased with the social media side of the conference. But the plural of &#8220;anecdote&#8221; is not &#8220;evidence&#8221; (I didn&#8217;t make that up, but it&#8217;s one of my favourite quotes), and I&#8217;m glad you&#8217;ve put some numbers behind the overall impression.</p>
<p>I&#8217;m also pleased that the word &#8216;reporter&#8217; figured fairly prominently in the word cloud. The story behind that points to something new that was introduced to the Twitter stream during WEC. The &#8216;reporter&#8217; tag might point toward a solution for organizations that have been interested in onsite social media but nervous that their messaging will be overwhelmed by the sheer volume of independent voices.</p>
<p>As usual at WEC, I was onsite wearing a few different hats &#8212; as an MPI member and volunteer, but also as one of several companies involved in producing the two general sessions. For each of those sessions, we had a team of two writers and one writer/editor live-tweeting the content as it was presented &#8212; so, yes, as the writer/editor on the team, I can echo your comment that it&#8217;s a tough job. </p>
<p>Between the two sessions, we produced 145 tweets, but the nature of the content was more important than the character count: we wouldn&#8217;t have contributed to the &#8216;good&#8217;, &#8216;bad&#8217;, or &#8216;fiasco&#8217; count in the word cloud because everything we produced was focused on reporting **someone else&#8217;s opinion**, not our own. (The exception was when I shouted WELCOME, ERIC! when the gavel passed to MPI&#8217;s new International Chair.) The intent of the experiment was not to offset or dilute the social media content, but to lead toward the kind of balance that daily newspapers achieve between news reporting and opinion content.</p>
<p>To my knowledge, this was the first time a conference had used live-tweeting to deliver reporting as well as opinion. Time will tell whether it turns out to be a one-off attempt or a productive new way of integrating onsite content and social media. I&#8217;m telling the story at some length, not to promote the approach, but because we&#8217;re genuinely interested in gathering feedback on whether it had an impact&#8230;and if not, whether we could have produced or signposted the tweets more effectively. I’d really appreciate comments from you and your readers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
