<?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: Thoughts on User Testing</title>
	<atom:link href="http://lapsusapp.co.uk/2010/01/25/thoughts-on-user-testing/feed/" rel="self" type="application/rss+xml" />
	<link>http://lapsusapp.co.uk/2010/01/25/thoughts-on-user-testing/</link>
	<description>The excitable chap who&#039;s building a time tracking app</description>
	<lastBuildDate>Fri, 02 Sep 2011 20:07:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: John</title>
		<link>http://lapsusapp.co.uk/2010/01/25/thoughts-on-user-testing/comment-page-1/#comment-1318</link>
		<dc:creator>John</dc:creator>
		<pubDate>Tue, 26 Jan 2010 18:17:46 +0000</pubDate>
		<guid isPermaLink="false">http://synapticmishap.co.uk/synapticmishap/?p=244#comment-1318</guid>
		<description>Awesome comment, Andy.

It sounds like you went through a tremendous learning experience.

How much did my test cost? Well, I &quot;paid&quot; Gavin with a packet of biscuits. And essentially I&#039;ve saved probably 2-3 months of time that could have otherwise been completely wasted. That&#039;s a pretty good ratio :)

&quot;The more you learn the more you understand how little you know&quot;. 

Ain&#039;t that the truth. Hopefully I&#039;ll remember to design from the standpoint of complete ignorance from now on, realising that whatever I think I&#039;m probably wrong.

I&#039;ll be interested to hear your argument as to why paper wireframes should die and how this could apply to my project. I&#039;ll keep an eye on your blog.

Thanks for a great comment and I hope to see you at TechMeetup tomorrow. I might be late, but I&#039;ll try and get there.</description>
		<content:encoded><![CDATA[<p>Awesome comment, Andy.</p>
<p>It sounds like you went through a tremendous learning experience.</p>
<p>How much did my test cost? Well, I &#8220;paid&#8221; Gavin with a packet of biscuits. And essentially I&#8217;ve saved probably 2-3 months of time that could have otherwise been completely wasted. That&#8217;s a pretty good ratio <img src='http://lapsusapp.co.uk/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>&#8220;The more you learn the more you understand how little you know&#8221;. </p>
<p>Ain&#8217;t that the truth. Hopefully I&#8217;ll remember to design from the standpoint of complete ignorance from now on, realising that whatever I think I&#8217;m probably wrong.</p>
<p>I&#8217;ll be interested to hear your argument as to why paper wireframes should die and how this could apply to my project. I&#8217;ll keep an eye on your blog.</p>
<p>Thanks for a great comment and I hope to see you at TechMeetup tomorrow. I might be late, but I&#8217;ll try and get there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Bright</title>
		<link>http://lapsusapp.co.uk/2010/01/25/thoughts-on-user-testing/comment-page-1/#comment-1314</link>
		<dc:creator>Andy Bright</dc:creator>
		<pubDate>Tue, 26 Jan 2010 00:16:16 +0000</pubDate>
		<guid isPermaLink="false">http://synapticmishap.co.uk/synapticmishap/?p=244#comment-1314</guid>
		<description>Great post. And you&#039;re so right.

Not so many years ago was doing web design in an agency where my process involved doing a quick sketch or two before diving straight into a high-fidelity photoshop comp.

I would always get worried about the point where I&#039;d have to call my art director over to review my progress and endure some level of biting criticism of my design skills.

The problem with the situation was that after a few projects I was producing work with the sole objective of impressing the AD. Using visual techniques he favoured, etc.

Of course the reality was that the AD&#039;s preferences were irrelevant, and the areas where we would focus attention would be of little concern to the eventual users of the interfaces.

Later I developed the knowledge that, as an individual designer, I couldn&#039;t possibly understand how a user would interact with the pie-in-the-sky fancies we were building.

Fortunately I eventually got to the point in the organisation where I had the freedom to do some quick and dirty usability testing of my own. And I mean usability testing in the loosest possible terms... Basically just sitting an account director down in-front of an interface and watching him fail to succeed in completing even simple tasks.

As they say, the more you learn the more you understand how little you know. Many designers would take offence at someone questioning their design decision making, citing their education and experience as qualification enough. But I&#039;ve learned that in order to achieve success it&#039;s design research that should lead decision making - the skill of the designer is facilitating the use of techniques to uncover an understanding of the user. To an extent, letting the users design the interface themselves.

I think you made a great decision to sit someone down in-front of a prototype. How much would you say it cost to run the test? And how would you value what you learned in comparison to the cost?

I think rapid iterative prototyping is going to take off in a big way this year. In the last 3 months I&#039;ve been involved in 5 prototyping projects, and all of them have been a fantastic success. I hope to finish a blog post soon about how I prototype with html/css/js, and how paper wireframes as a design tool have to die.</description>
		<content:encoded><![CDATA[<p>Great post. And you&#8217;re so right.</p>
<p>Not so many years ago was doing web design in an agency where my process involved doing a quick sketch or two before diving straight into a high-fidelity photoshop comp.</p>
<p>I would always get worried about the point where I&#8217;d have to call my art director over to review my progress and endure some level of biting criticism of my design skills.</p>
<p>The problem with the situation was that after a few projects I was producing work with the sole objective of impressing the AD. Using visual techniques he favoured, etc.</p>
<p>Of course the reality was that the AD&#8217;s preferences were irrelevant, and the areas where we would focus attention would be of little concern to the eventual users of the interfaces.</p>
<p>Later I developed the knowledge that, as an individual designer, I couldn&#8217;t possibly understand how a user would interact with the pie-in-the-sky fancies we were building.</p>
<p>Fortunately I eventually got to the point in the organisation where I had the freedom to do some quick and dirty usability testing of my own. And I mean usability testing in the loosest possible terms&#8230; Basically just sitting an account director down in-front of an interface and watching him fail to succeed in completing even simple tasks.</p>
<p>As they say, the more you learn the more you understand how little you know. Many designers would take offence at someone questioning their design decision making, citing their education and experience as qualification enough. But I&#8217;ve learned that in order to achieve success it&#8217;s design research that should lead decision making &#8211; the skill of the designer is facilitating the use of techniques to uncover an understanding of the user. To an extent, letting the users design the interface themselves.</p>
<p>I think you made a great decision to sit someone down in-front of a prototype. How much would you say it cost to run the test? And how would you value what you learned in comparison to the cost?</p>
<p>I think rapid iterative prototyping is going to take off in a big way this year. In the last 3 months I&#8217;ve been involved in 5 prototyping projects, and all of them have been a fantastic success. I hope to finish a blog post soon about how I prototype with html/css/js, and how paper wireframes as a design tool have to die.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

