<?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: Insights and Interpretations: Determining Depth of Analysis for Reporting</title>
	<atom:link href="http://www.radian6.com/blog/2010/06/insights-and-interpretations-determining-depth-of-analysis-for-reporting/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.radian6.com/blog/2010/06/insights-and-interpretations-determining-depth-of-analysis-for-reporting/</link>
	<description>Social media monitoring tools, social media engagement software and social CRM and marketing from the industry leader in social analytics.</description>
	<lastBuildDate>Fri, 10 Feb 2012 21:26:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: SMEDIAM &#187; Reporting for Marketing and Corporate Communications</title>
		<link>http://www.radian6.com/blog/2010/06/insights-and-interpretations-determining-depth-of-analysis-for-reporting/#comment-4262</link>
		<dc:creator>SMEDIAM &#187; Reporting for Marketing and Corporate Communications</dc:creator>
		<pubDate>Mon, 26 Jul 2010 04:12:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.radian6.com/?p=4267#comment-4262</guid>
		<description>[...] plan reflect your business goals, objectives, and tactics.  What is trackable? What do you currently report on? Start there and the social metrics will become apparent far more quickly than starting from [...]</description>
		<content:encoded><![CDATA[<p>[...] plan reflect your business goals, objectives, and tactics.  What is trackable? What do you currently report on? Start there and the social metrics will become apparent far more quickly than starting from [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vargasl (Lauren Varg</title>
		<link>http://www.radian6.com/blog/2010/06/insights-and-interpretations-determining-depth-of-analysis-for-reporting/#comment-4260</link>
		<dc:creator>vargasl (Lauren Varg</dc:creator>
		<pubDate>Tue, 22 Jun 2010 14:04:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.radian6.com/?p=4267#comment-4260</guid>
		<description>&lt;a rel=&quot;nofollow&quot; href=&quot;http://twitter.com/B2Bento&quot; rel=&quot;nofollow&quot;&gt;@B2Bento&lt;/a&gt; Thank you for sharing latest blog post about reporting.  &lt;a href=&quot;http://bit.ly/amtbQd&quot; rel=&quot;nofollow&quot;&gt;http://bit.ly/amtbQd&lt;/a&gt; </description>
		<content:encoded><![CDATA[<p>&lt;a rel=&quot;nofollow&quot; href=&quot;<a href="http://twitter.com/B2Bento&#038;quot" rel="nofollow">http://twitter.com/B2Bento&#038;quot</a>; rel=&quot;nofollow&quot;&gt;@B2Bento Thank you for sharing latest blog post about reporting.  <a href="http://bit.ly/amtbQd" rel="nofollow">http://bit.ly/amtbQd</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: b2bento (B2Bento at</title>
		<link>http://www.radian6.com/blog/2010/06/insights-and-interpretations-determining-depth-of-analysis-for-reporting/#comment-4259</link>
		<dc:creator>b2bento (B2Bento at</dc:creator>
		<pubDate>Tue, 22 Jun 2010 14:00:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.radian6.com/?p=4267#comment-4259</guid>
		<description>Insights and Interpretations: Determining Depth of Analysis for Reporting - by &lt;a rel=&quot;nofollow&quot; href=&quot;http://twitter.com/vargasl&quot; rel=&quot;nofollow&quot;&gt;@vargasl&lt;/a&gt; at &lt;a rel=&quot;nofollow&quot; href=&quot;http://twitter.com/radian6&quot; rel=&quot;nofollow&quot;&gt;@radian6&lt;/a&gt; blog &lt;a href=&quot;http://bit.ly/amtbQd&quot; rel=&quot;nofollow&quot;&gt;http://bit.ly/amtbQd&lt;/a&gt; </description>
		<content:encoded><![CDATA[<p>Insights and Interpretations: Determining Depth of Analysis for Reporting &#8211; by &lt;a rel=&quot;nofollow&quot; href=&quot;<a href="http://twitter.com/vargasl&#038;quot" rel="nofollow">http://twitter.com/vargasl&#038;quot</a>; rel=&quot;nofollow&quot;&gt;@vargasl at &lt;a rel=&quot;nofollow&quot; href=&quot;<a href="http://twitter.com/radian6&#038;quot" rel="nofollow">http://twitter.com/radian6&#038;quot</a>; rel=&quot;nofollow&quot;&gt;@radian6 blog <a href="http://bit.ly/amtbQd" rel="nofollow">http://bit.ly/amtbQd</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carla Bobka</title>
		<link>http://www.radian6.com/blog/2010/06/insights-and-interpretations-determining-depth-of-analysis-for-reporting/#comment-9395</link>
		<dc:creator>Carla Bobka</dc:creator>
		<pubDate>Tue, 22 Jun 2010 11:58:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.radian6.com/?p=4267#comment-9395</guid>
		<description>Lauren-two elements I would add, the action of doing the reporting is not the time to showcase the amount of hard work you have put into the results. It is a time to highlight what&#039;s important in the amount of attention span you estimate is available. That&#039;s not the length of the meeting, that&#039;s a very different number. 
Second - prepare 2 sets of take away docs, one primarily visual, the other primarily text description. Play into people&#039;s preference for learning in either format, don&#039;t assume everyone will learn what you intend in the format that is most convenient for you or digestible for you. (this is a great time to recruit someone to help you create the other doc that isn&#039;t your strong suit). 
And, I totally agree with you on the stories part - everyone learns from hearing narrative. Link each key insight to a particular story. Those are what will be repeated through the organization and outside it&#039;s walls, not the charts. </description>
		<content:encoded><![CDATA[<p>Lauren-two elements I would add, the action of doing the reporting is not the time to showcase the amount of hard work you have put into the results. It is a time to highlight what&#039;s important in the amount of attention span you estimate is available. That&#039;s not the length of the meeting, that&#039;s a very different number.<br />
Second &#8211; prepare 2 sets of take away docs, one primarily visual, the other primarily text description. Play into people&#039;s preference for learning in either format, don&#039;t assume everyone will learn what you intend in the format that is most convenient for you or digestible for you. (this is a great time to recruit someone to help you create the other doc that isn&#039;t your strong suit).<br />
And, I totally agree with you on the stories part &#8211; everyone learns from hearing narrative. Link each key insight to a particular story. Those are what will be repeated through the organization and outside it&#039;s walls, not the charts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carla Bobka</title>
		<link>http://www.radian6.com/blog/2010/06/insights-and-interpretations-determining-depth-of-analysis-for-reporting/#comment-4258</link>
		<dc:creator>Carla Bobka</dc:creator>
		<pubDate>Tue, 22 Jun 2010 11:58:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.radian6.com/?p=4267#comment-4258</guid>
		<description>Lauren-two elements I would add, the action of doing the reporting is not the time to showcase the amount of hard work you have put into the results. It is a time to highlight what&#039;s important in the amount of attention span you estimate is available. That&#039;s not the length of the meeting, that&#039;s a very different number.  
Second - prepare 2 sets of take away docs, one primarily visual, the other primarily text description. Play into people&#039;s preference for learning in either format, don&#039;t assume everyone will learn what you intend in the format that is most convenient for you or digestible for you. (this is a great time to recruit someone to help you create the other doc that isn&#039;t your strong suit).  
And, I totally agree with you on the stories part - everyone learns from hearing narrative. Link each key insight to a particular story. Those are what will be repeated through the organization and outside it&#039;s walls, not the charts. </description>
		<content:encoded><![CDATA[<p>Lauren-two elements I would add, the action of doing the reporting is not the time to showcase the amount of hard work you have put into the results. It is a time to highlight what&#039;s important in the amount of attention span you estimate is available. That&#039;s not the length of the meeting, that&#039;s a very different number.<br />
Second &#8211; prepare 2 sets of take away docs, one primarily visual, the other primarily text description. Play into people&#039;s preference for learning in either format, don&#039;t assume everyone will learn what you intend in the format that is most convenient for you or digestible for you. (this is a great time to recruit someone to help you create the other doc that isn&#039;t your strong suit).<br />
And, I totally agree with you on the stories part &#8211; everyone learns from hearing narrative. Link each key insight to a particular story. Those are what will be repeated through the organization and outside it&#039;s walls, not the charts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets that mention Insights and Interpretations: Determining Depth of Analysis for Reporting « Social Media Monitoring and Engagement – Radian6 -- Topsy.com</title>
		<link>http://www.radian6.com/blog/2010/06/insights-and-interpretations-determining-depth-of-analysis-for-reporting/#comment-4257</link>
		<dc:creator>Tweets that mention Insights and Interpretations: Determining Depth of Analysis for Reporting « Social Media Monitoring and Engagement – Radian6 -- Topsy.com</dc:creator>
		<pubDate>Mon, 21 Jun 2010 22:19:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.radian6.com/?p=4267#comment-4257</guid>
		<description>[...] This post was mentioned on Twitter by Lauren Vargas, JGoldsborough, Social Solutions, ilikerashersrss, Bryon Cromlish and others. Bryon Cromlish said: Radian6: Insights and Interpretations: Determining Depth of Analysis for Reporting http://bit.ly/cyfTBP [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by Lauren Vargas, JGoldsborough, Social Solutions, ilikerashersrss, Bryon Cromlish and others. Bryon Cromlish said: Radian6: Insights and Interpretations: Determining Depth of Analysis for Reporting <a href="http://bit.ly/cyfTBP" rel="nofollow">http://bit.ly/cyfTBP</a> [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

