<?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"
	>
<channel>
	<title>Comments on: Bias of the crowds</title>
	<atom:link href="http://www.nnyman.com/personal/2007/03/30/bias-of-the-crowds/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nnyman.com/personal/2007/03/30/bias-of-the-crowds/</link>
	<description>Niko Nyman's blog on shifting topics.</description>
	<pubDate>Fri, 21 Nov 2008 19:44:21 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: /personal &#187; Blog Archive &#187; Watching people, rather than asking people</title>
		<link>http://www.nnyman.com/personal/2007/03/30/bias-of-the-crowds/#comment-58713</link>
		<dc:creator>/personal &#187; Blog Archive &#187; Watching people, rather than asking people</dc:creator>
		<pubDate>Tue, 10 Jul 2007 21:20:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.nnyman.com/personal/2007/03/30/bias-of-the-crowds/#comment-58713</guid>
		<description>&lt;p&gt;[...] is something that started in a comment earlier this [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] is something that started in a comment earlier this [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Niko</title>
		<link>http://www.nnyman.com/personal/2007/03/30/bias-of-the-crowds/#comment-32889</link>
		<dc:creator>Niko</dc:creator>
		<pubDate>Sat, 31 Mar 2007 11:02:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.nnyman.com/personal/2007/03/30/bias-of-the-crowds/#comment-32889</guid>
		<description>&lt;p&gt;I obviously don't have anything to base my belief on, but I do rather believe in &lt;em&gt;watching the people&lt;/em&gt; than &lt;em&gt;asking the people&lt;/em&gt;.&lt;/p&gt;

&lt;p&gt;I acknowledge that a lot of bad decisions based on asking the people are a result of simply taking the answers literally, ie. not asking the &lt;a href="http://en.wikipedia.org/wiki/5_Whys" title="5 Whys (on Wikipedia)" rel="nofollow"&gt;five whys&lt;/a&gt;.  Taking an example from &lt;a href="http://blogs.s60.com/tommi/2007/03/how_would_you_revamp_the_phone.html" title="How would you revamp the phonebook? ...or would you? (on Tommi's S60 Applications Blog)" rel="nofollow"&gt;Tommi's post on S60 Address Book&lt;/a&gt;, someone asked to be able to undo edits in the address book.  Well, a nice idea!  But the only reason was because the user was deleting contacts accidentally -- so the better approach would be to fix the problem of accidental deletion rather than do what is being asked, and add yet another feature, the undo.  I guess this is the kind of examining you are thinking of?&lt;/p&gt;

&lt;p&gt;As said, I do believe (without any grounds ;) that by &lt;em&gt;watching&lt;/em&gt; the users, even more radical improvements to the user experience are possible.  Improvements on stuff that isn't perceived by the users.  Stuff that has become status quo, things that "are the way they are because they've always been that way".  Improvements that take features to the next level rather than tinker with the old way of doing things.&lt;/p&gt;

&lt;p&gt;It sounds like I'm talking about radical R&#38;D and experimental prototypes (which I do love to talk about in a different context ;) but really I'm not.  I believe in small changes which -- if found -- can radically change the user experience.  And I don't believe those can be found by asking.&lt;/p&gt;

&lt;p&gt;I could be wrong.  Would love to be wrong, actually. :)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I obviously don&#8217;t have anything to base my belief on, but I do rather believe in <em>watching the people</em> than <em>asking the people</em>.</p>

<p>I acknowledge that a lot of bad decisions based on asking the people are a result of simply taking the answers literally, ie. not asking the <a href="http://en.wikipedia.org/wiki/5_Whys" title="5 Whys (on Wikipedia)" rel="nofollow">five whys</a>.  Taking an example from <a href="http://blogs.s60.com/tommi/2007/03/how_would_you_revamp_the_phone.html" title="How would you revamp the phonebook? ...or would you? (on Tommi's S60 Applications Blog)" rel="nofollow">Tommi&#8217;s post on S60 Address Book</a>, someone asked to be able to undo edits in the address book.  Well, a nice idea!  But the only reason was because the user was deleting contacts accidentally &#8212; so the better approach would be to fix the problem of accidental deletion rather than do what is being asked, and add yet another feature, the undo.  I guess this is the kind of examining you are thinking of?</p>

<p>As said, I do believe (without any grounds ;) that by <em>watching</em> the users, even more radical improvements to the user experience are possible.  Improvements on stuff that isn&#8217;t perceived by the users.  Stuff that has become status quo, things that &#8220;are the way they are because they&#8217;ve always been that way&#8221;.  Improvements that take features to the next level rather than tinker with the old way of doing things.</p>

<p>It sounds like I&#8217;m talking about radical R&amp;D and experimental prototypes (which I do love to talk about in a different context ;) but really I&#8217;m not.  I believe in small changes which &#8212; if found &#8212; can radically change the user experience.  And I don&#8217;t believe those can be found by asking.</p>

<p>I could be wrong.  Would love to be wrong, actually. :)</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Janne Jalkanen</title>
		<link>http://www.nnyman.com/personal/2007/03/30/bias-of-the-crowds/#comment-32868</link>
		<dc:creator>Janne Jalkanen</dc:creator>
		<pubDate>Sat, 31 Mar 2007 09:11:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.nnyman.com/personal/2007/03/30/bias-of-the-crowds/#comment-32868</guid>
		<description>&lt;p&gt;It is a good way.  It's just that you have to examine the answers the right way.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>It is a good way.  It&#8217;s just that you have to examine the answers the right way.</p>]]></content:encoded>
	</item>
</channel>
</rss>
