<?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: Seeking examples of design informed by user research&#8230;</title>
	<atom:link href="http://www.adaptivepath.com/blog/2007/01/10/seeking-examples-of-design-informed-by-user-research/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adaptivepath.com/blog/2007/01/10/seeking-examples-of-design-informed-by-user-research/</link>
	<description>Adaptive Path Blog</description>
	<pubDate>Thu, 08 Jan 2009 17:15:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: pauric</title>
		<link>http://www.adaptivepath.com/blog/2007/01/10/seeking-examples-of-design-informed-by-user-research/#comment-35990</link>
		<dc:creator>pauric</dc:creator>
		<pubDate>Thu, 11 Jan 2007 14:44:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2007/01/10/seeking-examples-of-design-informed-by-user-research/#comment-35990</guid>
		<description>In my realm of embedded interfaces, web apps on devices, I practice something that could be called 'method acting persona' or 'become the user'.  I take an existing device and understand how it is used, who uses it, what it is used for etc.  I then try to become a user myself. 

I think this can only work well when you have a physical device, also, there is a hit in the time it takes to get this method up and running.  This works for me as an innie with the luxury of being able to plan according to a long term roadmap. I'm not sure a consultant could afford the extra lead time.

I find myself being the most creative and productive with this method.  I enter a mode of being always on, in terms of solving issues and creating soltuions.  I am dyslexic and this feels like a much more intuitive way to design than some of the more traditional UCD approaches.   I would say it allows for a lot more creativity.  Its easier to get a view of the larger picture, gives me more focus on the overall solution.

In one particular design I created a widget which was a functional representation of the device within the web management interface.  Being both the designer and user I was able to work from both sides on the interface.   I instantiated the widget across all aspects of the interface, from information display to configuration to navigation, each instance a tailored version of a core interaction.  Resulting in, what I feel anyway, was a unified approach to the look and feel.  Something I'm not sure would have happened as well if I focused on a set of users or activities.</description>
		<content:encoded><![CDATA[<p>In my realm of embedded interfaces, web apps on devices, I practice something that could be called &#8216;method acting persona&#8217; or &#8216;become the user&#8217;.  I take an existing device and understand how it is used, who uses it, what it is used for etc.  I then try to become a user myself. </p>
<p>I think this can only work well when you have a physical device, also, there is a hit in the time it takes to get this method up and running.  This works for me as an innie with the luxury of being able to plan according to a long term roadmap. I&#8217;m not sure a consultant could afford the extra lead time.</p>
<p>I find myself being the most creative and productive with this method.  I enter a mode of being always on, in terms of solving issues and creating soltuions.  I am dyslexic and this feels like a much more intuitive way to design than some of the more traditional UCD approaches.   I would say it allows for a lot more creativity.  Its easier to get a view of the larger picture, gives me more focus on the overall solution.</p>
<p>In one particular design I created a widget which was a functional representation of the device within the web management interface.  Being both the designer and user I was able to work from both sides on the interface.   I instantiated the widget across all aspects of the interface, from information display to configuration to navigation, each instance a tailored version of a core interaction.  Resulting in, what I feel anyway, was a unified approach to the look and feel.  Something I&#8217;m not sure would have happened as well if I focused on a set of users or activities.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
