<?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: Why collaborative research analysis rocks out.</title>
	<atom:link href="http://www.disambiguity.com/why-collaborative-research-analysis-rocks-out/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.disambiguity.com/why-collaborative-research-analysis-rocks-out/</link>
	<description>pretty design pending</description>
	<lastBuildDate>Mon, 15 Feb 2010 23:30:46 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: designmartini &#187; Why collaborative research analysis rocks out.</title>
		<link>http://www.disambiguity.com/why-collaborative-research-analysis-rocks-out/comment-page-1/#comment-40767</link>
		<dc:creator>designmartini &#187; Why collaborative research analysis rocks out.</dc:creator>
		<pubDate>Wed, 24 Oct 2007 16:05:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/why-collaborative-research-analysis-rocks-out/#comment-40767</guid>
		<description>[...] Why collaborative research analysis rocks out. [...]</description>
		<content:encoded><![CDATA[<p>[...] Why collaborative research analysis rocks out. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Why collaborative research analysis rocks out &#171; Ralph&#8217;s Weblog</title>
		<link>http://www.disambiguity.com/why-collaborative-research-analysis-rocks-out/comment-page-1/#comment-40494</link>
		<dc:creator>Why collaborative research analysis rocks out &#171; Ralph&#8217;s Weblog</dc:creator>
		<pubDate>Tue, 23 Oct 2007 03:33:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/why-collaborative-research-analysis-rocks-out/#comment-40494</guid>
		<description>[...] Why collaborative research analysis rocks&#160;out Filed under: research &#8212; Ralph Hockens @ 3:33 am   Full article: Why collaborative research analysis rocks out.   It&#8217;s been my experience that if you can get your project team members (and their associated and diverse expertise) involved in the research analysis process, then you will most definitely get more accurate and more useful research findings. [...]</description>
		<content:encoded><![CDATA[<p>[...] Why collaborative research analysis rocks&nbsp;out Filed under: research &#8212; Ralph Hockens @ 3:33 am   Full article: Why collaborative research analysis rocks out.   It&rsquo;s been my experience that if you can get your project team members (and their associated and diverse expertise) involved in the research analysis process, then you will most definitely get more accurate and more useful research findings. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Ashe</title>
		<link>http://www.disambiguity.com/why-collaborative-research-analysis-rocks-out/comment-page-1/#comment-40404</link>
		<dc:creator>Peter Ashe</dc:creator>
		<pubDate>Mon, 22 Oct 2007 13:28:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/why-collaborative-research-analysis-rocks-out/#comment-40404</guid>
		<description>Leisa,

while looking at your description and the original KJ-Technique post, the notion of card-sorting came to mind - is there enough similarity between the large-scale affinity sort that you mention, and card-sorting, to warrant any further thought? A couple of your other commenters have mentioned the difficulty that people have with freeing up anough time to participate. And I thought that an aspect of that might be the difficulty with getting people to free up time *at the same time* - corporate diary-making is the worst task in the project management lexicon! This triggered a thought about on-line card-sorting tools, and whether anyone had tried using any of those to spread th time-burden a bit. Then again, it would be handy of the tools could be a bit more social...surely a start-up somewhere is already working on this ;-)

But I meant to say first (sorry!), thanks for doing this excellent review and pointing at the original article. Perhaps pure science might suffer a little, but the advantages for getting translation from research to action far outweigh such considerations</description>
		<content:encoded><![CDATA[<p>Leisa,</p>
<p>while looking at your description and the original KJ-Technique post, the notion of card-sorting came to mind &#8211; is there enough similarity between the large-scale affinity sort that you mention, and card-sorting, to warrant any further thought? A couple of your other commenters have mentioned the difficulty that people have with freeing up anough time to participate. And I thought that an aspect of that might be the difficulty with getting people to free up time *at the same time* &#8211; corporate diary-making is the worst task in the project management lexicon! This triggered a thought about on-line card-sorting tools, and whether anyone had tried using any of those to spread th time-burden a bit. Then again, it would be handy of the tools could be a bit more social&#8230;surely a start-up somewhere is already working on this <img src='http://www.disambiguity.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>But I meant to say first (sorry!), thanks for doing this excellent review and pointing at the original article. Perhaps pure science might suffer a little, but the advantages for getting translation from research to action far outweigh such considerations</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Governor&#8217;s Monkchips &#187; The Analyst Business Should Learn From Disambiguity</title>
		<link>http://www.disambiguity.com/why-collaborative-research-analysis-rocks-out/comment-page-1/#comment-39706</link>
		<dc:creator>James Governor&#8217;s Monkchips &#187; The Analyst Business Should Learn From Disambiguity</dc:creator>
		<pubDate>Thu, 18 Oct 2007 11:16:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/why-collaborative-research-analysis-rocks-out/#comment-39706</guid>
		<description>[...] With a headline like Why collaborative research analysis rocks out&#160;it was no surprise I found Leisa Riechelt&#8217;s recent blog made very interesting reading. Leisa, originator of the wonderfully evocative phrase Ambient Intimacy, and all round sticky note queen (3M should sponsor her) argues thusly: These days when I’m doing any kind of user research, rather than going to my secret consultant place and doing that consultant magic that results in a presentation of research findings, I much prefer to get into a big room with clean walls and several hundred sticky notes and my clients/project team, and to work out the research findings collaboratively. [...]</description>
		<content:encoded><![CDATA[<p>[...] With a headline like Why collaborative research analysis rocks out&nbsp;it was no surprise I found Leisa Riechelt&#8217;s recent blog made very interesting reading. Leisa, originator of the wonderfully evocative phrase Ambient Intimacy, and all round sticky note queen (3M should sponsor her) argues thusly: These days when I’m doing any kind of user research, rather than going to my secret consultant place and doing that consultant magic that results in a presentation of research findings, I much prefer to get into a big room with clean walls and several hundred sticky notes and my clients/project team, and to work out the research findings collaboratively. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: leisa.reichelt</title>
		<link>http://www.disambiguity.com/why-collaborative-research-analysis-rocks-out/comment-page-1/#comment-39516</link>
		<dc:creator>leisa.reichelt</dc:creator>
		<pubDate>Wed, 17 Oct 2007 08:28:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/why-collaborative-research-analysis-rocks-out/#comment-39516</guid>
		<description>@ Chris - I think the only thing we&#039;re missing is a stop watch and some kind of a leaders board to see who can get their research findings in the least possible time.

Not that it&#039;s a competition, of course, and research analysis tends to take the time that it takes (and shouldn&#039;t be rushed)... but I think I did forget to mention that the other great advantage of this approach is that it does tend to get you to your implementable results much more quickly :)</description>
		<content:encoded><![CDATA[<p>@ Chris &#8211; I think the only thing we&#8217;re missing is a stop watch and some kind of a leaders board to see who can get their research findings in the least possible time.</p>
<p>Not that it&#8217;s a competition, of course, and research analysis tends to take the time that it takes (and shouldn&#8217;t be rushed)&#8230; but I think I did forget to mention that the other great advantage of this approach is that it does tend to get you to your implementable results much more quickly <img src='http://www.disambiguity.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: leisa.reichelt</title>
		<link>http://www.disambiguity.com/why-collaborative-research-analysis-rocks-out/comment-page-1/#comment-39514</link>
		<dc:creator>leisa.reichelt</dc:creator>
		<pubDate>Wed, 17 Oct 2007 08:19:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/why-collaborative-research-analysis-rocks-out/#comment-39514</guid>
		<description>@Paul - yeah, good point. The time consuming aspect is tricky. I have found it quite successful though to try to get as much of people&#039;s time as I can but to let them come and go (to meetings etc.) as they need to. You don&#039;t actually need to have everyone in the room all the time to get the value from the approach - although getting as much time from the core stakeholders as you can is great.</description>
		<content:encoded><![CDATA[<p>@Paul &#8211; yeah, good point. The time consuming aspect is tricky. I have found it quite successful though to try to get as much of people&#8217;s time as I can but to let them come and go (to meetings etc.) as they need to. You don&#8217;t actually need to have everyone in the room all the time to get the value from the approach &#8211; although getting as much time from the core stakeholders as you can is great.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christopher Fahey</title>
		<link>http://www.disambiguity.com/why-collaborative-research-analysis-rocks-out/comment-page-1/#comment-39432</link>
		<dc:creator>Christopher Fahey</dc:creator>
		<pubDate>Tue, 16 Oct 2007 22:24:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/why-collaborative-research-analysis-rocks-out/#comment-39432</guid>
		<description>This would be interesting to combine with Jakob Neilsen&#039;s recent description of &quot;&lt;a href=&quot;http://www.useit.com/alertbox/multiple-user-testing.html&quot; rel=&quot;nofollow&quot;&gt;Multiple-User Simultaneous Testing&lt;/a&gt;&quot;. It would be quite a scene, with ten subjects and five designers/stakeholders all in a room at the same time. That&#039;d be fun.</description>
		<content:encoded><![CDATA[<p>This would be interesting to combine with Jakob Neilsen&#8217;s recent description of &#8220;<a href="http://www.useit.com/alertbox/multiple-user-testing.html" rel="nofollow">Multiple-User Simultaneous Testing</a>&#8220;. It would be quite a scene, with ten subjects and five designers/stakeholders all in a room at the same time. That&#8217;d be fun.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Adams</title>
		<link>http://www.disambiguity.com/why-collaborative-research-analysis-rocks-out/comment-page-1/#comment-39412</link>
		<dc:creator>Paul Adams</dc:creator>
		<pubDate>Tue, 16 Oct 2007 20:54:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/why-collaborative-research-analysis-rocks-out/#comment-39412</guid>
		<description>Leisa, I&#039;m with you all the way on the collaboration front. I no longer give research presentations. Everything these days is based on workshops with a very high level of collaboration. However, one constraint I continually battle against is other people&#039;s time. In the vast majority of circumstances, it&#039;s simply not feasible for all the project team to attend all (or even a majority) of the research sessions - whether they be lab based or in the field. And this seems to be a critical factor in the success of your collaborative analysis. I have found collaborative analysis to work brilliantly when analysing data from one research participant e.g. a small team of 3 analyse their observations after a day shadowing someone in the field. However, for higher level analysis across many research participants, an issue I&#039;ve experienced is that when people have only seen a subset of the research sessions, their analysis is heavily skewed towards their own observations and experiences. To be honest, I&#039;m also guilty of skewing when I&#039;ve done field research as part of a team. So I tend to turn up to the workshop with much of the analysis done, and use storytelling techniques amongst participants where they share the research findings with each other. Everyone is on a path of discovery and everything is very collaborative. I&#039;ve found this to create significant buy-in.
My conclusion is that the research analysis is imperfect, but that&#039;s OK because I have traded perfection for project team buy-in. And it didn&#039;t take huge amounts of people&#039;s time.</description>
		<content:encoded><![CDATA[<p>Leisa, I&#8217;m with you all the way on the collaboration front. I no longer give research presentations. Everything these days is based on workshops with a very high level of collaboration. However, one constraint I continually battle against is other people&#8217;s time. In the vast majority of circumstances, it&#8217;s simply not feasible for all the project team to attend all (or even a majority) of the research sessions &#8211; whether they be lab based or in the field. And this seems to be a critical factor in the success of your collaborative analysis. I have found collaborative analysis to work brilliantly when analysing data from one research participant e.g. a small team of 3 analyse their observations after a day shadowing someone in the field. However, for higher level analysis across many research participants, an issue I&#8217;ve experienced is that when people have only seen a subset of the research sessions, their analysis is heavily skewed towards their own observations and experiences. To be honest, I&#8217;m also guilty of skewing when I&#8217;ve done field research as part of a team. So I tend to turn up to the workshop with much of the analysis done, and use storytelling techniques amongst participants where they share the research findings with each other. Everyone is on a path of discovery and everything is very collaborative. I&#8217;ve found this to create significant buy-in.<br />
My conclusion is that the research analysis is imperfect, but that&#8217;s OK because I have traded perfection for project team buy-in. And it didn&#8217;t take huge amounts of people&#8217;s time.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
