<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Random Sampling &#187; Research Tips</title>
	<atom:link href="http://www.ericksonresearch.com/blog/category/research-tips/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ericksonresearch.com/blog</link>
	<description>Musings on Marketing and Research</description>
	<lastBuildDate>Tue, 06 Sep 2011 15:00:22 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Research Tip:  Tell a Story</title>
		<link>http://www.ericksonresearch.com/blog/2008/04/research-tip-tell-a-story/</link>
		<comments>http://www.ericksonresearch.com/blog/2008/04/research-tip-tell-a-story/#comments</comments>
		<pubDate>Tue, 01 Apr 2008 17:55:19 +0000</pubDate>
		<dc:creator>Ed</dc:creator>
				<category><![CDATA[Research Tips]]></category>

		<guid isPermaLink="false">http://blog.ericksonmr.com/2008/04/01/research-tip-tell-a-story/</guid>
		<description><![CDATA[I&#8217;m sure we&#8217;ve all seen the &#8220;report&#8221; that amounted to little more than a data dump. Usually, they devote one page to each question and every page follows the format of bar chart and two bullet points telling you what is obvious from looking at the chart. Also, the bullets are often written as if [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m sure we&#8217;ve all seen the &#8220;report&#8221; that amounted to little more than a data dump.  Usually, they devote one page to each question and every page follows the format of bar chart and two bullet points telling you what is obvious from looking at the chart.  Also, the bullets are often written as if the intent was to be as obtuse as possible.</p>
<p>These reports often look something like this:</p>
<p><img src="http://www.ericksonmr.com/images/blogimages/badchart.jpg" alt="don't do this" /></p>
<p>In a world where you need to constantly demonstrate the value you bring to the business, reports like this earn you negative points.  An improved version of the same slide might look something like this:</p>
<p><img src="http://www.ericksonmr.com/images/blogimages/betterchart.jpg" alt="Do this" /></p>
<p>Making individual slides more readable and information (rather than data) packed is a big improvement.  But don&#8217;t stop there.</p>
<p>I suggest you use the following approach when developing your next research report:</p>
<ul>
<li>Find the story in the data.  What is the one huge overarching result of the research.</li>
<li>Identify three to five key findings that add up to the huge overarching result</li>
<li>Organize the flow of the report around the three to five key findings</li>
</ul>
<p>Using this approach, the basic outline of your report would look like this:</p>
<ul>
<li>Introduction: Tell them the huge result and the 3 to 5 supporting findings.</li>
<li>Finding #1:  Explain the finding and provide supporting evidence from the data.  Then explain why that finding is important for the business.</li>
<li>Finding #2: Same as #1</li>
<li>Finding #3: Same as #1</li>
<li>Wrap up:  Re-iterate the huge overall result and the key findings and explain what that means for the business.</li>
</ul>
<p>That&#8217;s quite a bit better than: Question 1, Question 2, Question 3, Question 4, and on (and on and on and on) until you reach the end of the survey.  Telling a story keeps the readers (or listeners) engaged and positions you as a valuable member of the team instead of a talking spreadsheet.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.ericksonresearch.com/blog/2008/04/research-tip-tell-a-story/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

