<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
<channel>
	<title>Comments for Design with Intent</title>
	
	<link>http://architectures.danlockton.co.uk</link>
	<description>Design and human behaviour</description>
	<lastBuildDate>Wed, 22 Feb 2012 12:10:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/ArchitecturesOfControlInDesignComments" /><feedburner:info uri="architecturesofcontrolindesigncomments" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:browserFriendly></feedburner:browserFriendly><item>
		<title>Comment on Architecture, urbanism, design and behaviour: a brief review by Designer Myopia: How To Stop Designing For Ourselves | Wordpress Themes</title>
		<link>http://architectures.danlockton.co.uk/2011/09/12/architecture-urbanism-design-and-behaviour-a-brief-review/comment-page-1/#comment-606016</link>
		<dc:creator>Designer Myopia: How To Stop Designing For Ourselves | Wordpress Themes</dc:creator>
		<pubDate>Wed, 22 Feb 2012 12:10:01 +0000</pubDate>
		<guid isPermaLink="false">http://architectures.danlockton.co.uk/?p=1679#comment-606016</guid>
		<description>[...] that form part of our users’ landscapes (rather than break their mental models). In “Architecture, Urbanism, Design and Behaviour: A Brief Review,” Dan Lockton [...]</description>
		<content:encoded><![CDATA[<p>[...] that form part of our users’ landscapes (rather than break their mental models). In “Architecture, Urbanism, Design and Behaviour: A Brief Review,” Dan Lockton [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dan Lockton by Ben Spak</title>
		<link>http://architectures.danlockton.co.uk/dan-lockton/comment-page-1/#comment-605982</link>
		<dc:creator>Ben Spak</dc:creator>
		<pubDate>Wed, 22 Feb 2012 07:21:51 +0000</pubDate>
		<guid isPermaLink="false">http://architectures.danlockton.co.uk/dan-lockton/#comment-605982</guid>
		<description>Great info on your site Dan, I'll have to dig a bit deeper when I have the time. Have you considered doing CRO (Conversion Rate Optimization) consulting in the internet marketing sector?</description>
		<content:encoded><![CDATA[<p>Great info on your site Dan, I&#8217;ll have to dig a bit deeper when I have the time. Have you considered doing CRO (Conversion Rate Optimization) consulting in the internet marketing sector?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Projected images designed to scare an enemy by denise</title>
		<link>http://architectures.danlockton.co.uk/2006/12/14/projected-images-designed-to-scare-an-enemy/comment-page-1/#comment-605940</link>
		<dc:creator>denise</dc:creator>
		<pubDate>Wed, 22 Feb 2012 02:41:50 +0000</pubDate>
		<guid isPermaLink="false">http://architectures.danlockton.co.uk/2006/12/14/projected-images-designed-to-scare-an-enemy/#comment-605940</guid>
		<description>so i learnimg it a shadow come upon me and wake up to see this knowing its not real how is it being put in my room</description>
		<content:encoded><![CDATA[<p>so i learnimg it a shadow come upon me and wake up to see this knowing its not real how is it being put in my room</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Architecture, urbanism, design and behaviour: a brief review by Designer Myopia: How To Stop Designing For Ourselves | Blog.Grooowbox.Com</title>
		<link>http://architectures.danlockton.co.uk/2011/09/12/architecture-urbanism-design-and-behaviour-a-brief-review/comment-page-1/#comment-605803</link>
		<dc:creator>Designer Myopia: How To Stop Designing For Ourselves | Blog.Grooowbox.Com</dc:creator>
		<pubDate>Tue, 21 Feb 2012 14:04:45 +0000</pubDate>
		<guid isPermaLink="false">http://architectures.danlockton.co.uk/?p=1679#comment-605803</guid>
		<description>[...] that form part of our users’ landscapes (rather than break their mental models). In “Architecture, Urbanism, Design and Behaviour: A Brief Review,” Dan Lockton writes: One emergent behavior-related concept arising from architecture and [...]</description>
		<content:encoded><![CDATA[<p>[...] that form part of our users’ landscapes (rather than break their mental models). In “Architecture, Urbanism, Design and Behaviour: A Brief Review,” Dan Lockton writes: One emergent behavior-related concept arising from architecture and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dan Lockton by Behavioral heuristics | User experience design</title>
		<link>http://architectures.danlockton.co.uk/dan-lockton/comment-page-1/#comment-605646</link>
		<dc:creator>Behavioral heuristics | User experience design</dc:creator>
		<pubDate>Mon, 20 Feb 2012 12:10:33 +0000</pubDate>
		<guid isPermaLink="false">http://architectures.danlockton.co.uk/dan-lockton/#comment-605646</guid>
		<description>[...] van mooie producten met bruikbare interfaces, maar om een dieper niveau van betrokkenheid. Dan Lockton houdt zich al vrij lang met deze overlapping van gebieden bezig waar bij zijn Design with Intent [...]</description>
		<content:encoded><![CDATA[<p>[...] van mooie producten met bruikbare interfaces, maar om een dieper niveau van betrokkenheid. Dan Lockton houdt zich al vrij lang met deze overlapping van gebieden bezig waar bij zijn Design with Intent [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Architecture, urbanism, design and behaviour: a brief review by Designer Myopia: How To Stop Designing For Ourselves | Web Design Course Brisbane: Next Course Sat 10th Dec 2011</title>
		<link>http://architectures.danlockton.co.uk/2011/09/12/architecture-urbanism-design-and-behaviour-a-brief-review/comment-page-1/#comment-604950</link>
		<dc:creator>Designer Myopia: How To Stop Designing For Ourselves | Web Design Course Brisbane: Next Course Sat 10th Dec 2011</dc:creator>
		<pubDate>Thu, 16 Feb 2012 11:30:50 +0000</pubDate>
		<guid isPermaLink="false">http://architectures.danlockton.co.uk/?p=1679#comment-604950</guid>
		<description>[...] that form part of our users’ landscapes (rather than break their mental models). In “Architecture, Urbanism, Design and Behaviour: A Brief Review,” Dan Lockton [...]</description>
		<content:encoded><![CDATA[<p>[...] that form part of our users’ landscapes (rather than break their mental models). In “Architecture, Urbanism, Design and Behaviour: A Brief Review,” Dan Lockton [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Architecture, urbanism, design and behaviour: a brief review by Designer Myopia: How To Stop Designing For Ourselves | Web Designer Bacolod City | Ricky Noel Diancin Jr. Webmaster | Wordpress Expert</title>
		<link>http://architectures.danlockton.co.uk/2011/09/12/architecture-urbanism-design-and-behaviour-a-brief-review/comment-page-1/#comment-604908</link>
		<dc:creator>Designer Myopia: How To Stop Designing For Ourselves | Web Designer Bacolod City | Ricky Noel Diancin Jr. Webmaster | Wordpress Expert</dc:creator>
		<pubDate>Thu, 16 Feb 2012 06:13:00 +0000</pubDate>
		<guid isPermaLink="false">http://architectures.danlockton.co.uk/?p=1679#comment-604908</guid>
		<description>[...] that form part of our users’ landscapes (rather than break their mental models). In “Architecture, Urbanism, Design and Behaviour: A Brief Review,” Dan Lockton [...]</description>
		<content:encoded><![CDATA[<p>[...] that form part of our users’ landscapes (rather than break their mental models). In “Architecture, Urbanism, Design and Behaviour: A Brief Review,” Dan Lockton [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Architecture, urbanism, design and behaviour: a brief review by Designer Myopia: How To Stop Designing For Ourselves | Testing themes</title>
		<link>http://architectures.danlockton.co.uk/2011/09/12/architecture-urbanism-design-and-behaviour-a-brief-review/comment-page-1/#comment-604890</link>
		<dc:creator>Designer Myopia: How To Stop Designing For Ourselves | Testing themes</dc:creator>
		<pubDate>Thu, 16 Feb 2012 02:20:36 +0000</pubDate>
		<guid isPermaLink="false">http://architectures.danlockton.co.uk/?p=1679#comment-604890</guid>
		<description>[...] that form part of our users’ landscapes (rather than break their mental models). In “Architecture, Urbanism, Design and Behaviour: A Brief Review,” Dan Lockton [...]</description>
		<content:encoded><![CDATA[<p>[...] that form part of our users’ landscapes (rather than break their mental models). In “Architecture, Urbanism, Design and Behaviour: A Brief Review,” Dan Lockton [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Architecture, urbanism, design and behaviour: a brief review by Designer Myopia: How To Stop Designing For Ourselves | DigitalMofo</title>
		<link>http://architectures.danlockton.co.uk/2011/09/12/architecture-urbanism-design-and-behaviour-a-brief-review/comment-page-1/#comment-604853</link>
		<dc:creator>Designer Myopia: How To Stop Designing For Ourselves | DigitalMofo</dc:creator>
		<pubDate>Wed, 15 Feb 2012 22:52:51 +0000</pubDate>
		<guid isPermaLink="false">http://architectures.danlockton.co.uk/?p=1679#comment-604853</guid>
		<description>[...] that form part of our users’ landscapes (rather than break their mental models). In “Architecture, Urbanism, Design and Behaviour: A Brief Review,” Dan Lockton [...]</description>
		<content:encoded><![CDATA[<p>[...] that form part of our users’ landscapes (rather than break their mental models). In “Architecture, Urbanism, Design and Behaviour: A Brief Review,” Dan Lockton [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Architecture, urbanism, design and behaviour: a brief review by Designer Myopia: How To Stop Designing For Ourselves | IdentityNepal.com</title>
		<link>http://architectures.danlockton.co.uk/2011/09/12/architecture-urbanism-design-and-behaviour-a-brief-review/comment-page-1/#comment-604835</link>
		<dc:creator>Designer Myopia: How To Stop Designing For Ourselves | IdentityNepal.com</dc:creator>
		<pubDate>Wed, 15 Feb 2012 20:46:43 +0000</pubDate>
		<guid isPermaLink="false">http://architectures.danlockton.co.uk/?p=1679#comment-604835</guid>
		<description>[...] that form part of our users’ landscapes (rather than break their mental models). In “Architecture, Urbanism, Design and Behaviour: A Brief Review,” Dan Lockton [...]</description>
		<content:encoded><![CDATA[<p>[...] that form part of our users’ landscapes (rather than break their mental models). In “Architecture, Urbanism, Design and Behaviour: A Brief Review,” Dan Lockton [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Architecture, urbanism, design and behaviour: a brief review by Designer Myopia: How To Stop Designing For Ourselves | Gold Star Web Design</title>
		<link>http://architectures.danlockton.co.uk/2011/09/12/architecture-urbanism-design-and-behaviour-a-brief-review/comment-page-1/#comment-604797</link>
		<dc:creator>Designer Myopia: How To Stop Designing For Ourselves | Gold Star Web Design</dc:creator>
		<pubDate>Wed, 15 Feb 2012 16:33:52 +0000</pubDate>
		<guid isPermaLink="false">http://architectures.danlockton.co.uk/?p=1679#comment-604797</guid>
		<description>[...] that form part of our users’ landscapes (rather than break their mental models). In “Architecture, Urbanism, Design and Behaviour: A Brief Review,” Dan Lockton [...]</description>
		<content:encoded><![CDATA[<p>[...] that form part of our users’ landscapes (rather than break their mental models). In “Architecture, Urbanism, Design and Behaviour: A Brief Review,” Dan Lockton [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Architecture, urbanism, design and behaviour: a brief review by Designer Myopia: How To Stop Designing For Ourselves | FloroGraphics.com</title>
		<link>http://architectures.danlockton.co.uk/2011/09/12/architecture-urbanism-design-and-behaviour-a-brief-review/comment-page-1/#comment-604755</link>
		<dc:creator>Designer Myopia: How To Stop Designing For Ourselves | FloroGraphics.com</dc:creator>
		<pubDate>Wed, 15 Feb 2012 11:55:17 +0000</pubDate>
		<guid isPermaLink="false">http://architectures.danlockton.co.uk/?p=1679#comment-604755</guid>
		<description>[...] that form part of our users’ landscapes (rather than break their mental models). In “Architecture, Urbanism, Design and Behaviour: A Brief Review,” Dan Lockton [...]</description>
		<content:encoded><![CDATA[<p>[...] that form part of our users’ landscapes (rather than break their mental models). In “Architecture, Urbanism, Design and Behaviour: A Brief Review,” Dan Lockton [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Architecture, urbanism, design and behaviour: a brief review by Designer Myopia: How To Stop Designing For Ourselves | Blogs – NG Outsourcing</title>
		<link>http://architectures.danlockton.co.uk/2011/09/12/architecture-urbanism-design-and-behaviour-a-brief-review/comment-page-1/#comment-604743</link>
		<dc:creator>Designer Myopia: How To Stop Designing For Ourselves | Blogs – NG Outsourcing</dc:creator>
		<pubDate>Wed, 15 Feb 2012 10:17:59 +0000</pubDate>
		<guid isPermaLink="false">http://architectures.danlockton.co.uk/?p=1679#comment-604743</guid>
		<description>[...] that form part of our users’ landscapes (rather than break their mental models). In “Architecture, Urbanism, Design and Behaviour: A Brief Review,” Dan Lockton [...]</description>
		<content:encoded><![CDATA[<p>[...] that form part of our users’ landscapes (rather than break their mental models). In “Architecture, Urbanism, Design and Behaviour: A Brief Review,” Dan Lockton [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Architecture, urbanism, design and behaviour: a brief review by Designer Myopia: How To Stop Designing For Ourselves@smashing | seo博客大全</title>
		<link>http://architectures.danlockton.co.uk/2011/09/12/architecture-urbanism-design-and-behaviour-a-brief-review/comment-page-1/#comment-604742</link>
		<dc:creator>Designer Myopia: How To Stop Designing For Ourselves@smashing | seo博客大全</dc:creator>
		<pubDate>Wed, 15 Feb 2012 10:06:33 +0000</pubDate>
		<guid isPermaLink="false">http://architectures.danlockton.co.uk/?p=1679#comment-604742</guid>
		<description>[...] that form part of our users’ landscapes (rather than break their mental models). In “Architecture, Urbanism, Design and Behaviour: A Brief Review,” Dan Lockton [...]</description>
		<content:encoded><![CDATA[<p>[...] that form part of our users’ landscapes (rather than break their mental models). In “Architecture, Urbanism, Design and Behaviour: A Brief Review,” Dan Lockton [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on If… by If… | Design with Intent | relevant entertainment | Scoop.it</title>
		<link>http://architectures.danlockton.co.uk/2012/02/09/if/comment-page-1/#comment-604578</link>
		<dc:creator>If… | Design with Intent | relevant entertainment | Scoop.it</dc:creator>
		<pubDate>Tue, 14 Feb 2012 10:38:03 +0000</pubDate>
		<guid isPermaLink="false">http://architectures.danlockton.co.uk/?p=1766#comment-604578</guid>
		<description>[...] background-position: 50% 0px; background-color:#222222; background-repeat : no-repeat; }         architectures.danlockton.co.uk  - Today, 12:37 [...]</description>
		<content:encoded><![CDATA[<p>[...] background-position: 50% 0px; background-color:#222222; background-repeat : no-repeat; }         architectures.danlockton.co.uk  &#8211; Today, 12:37 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on If… by Sebastian Deterding</title>
		<link>http://architectures.danlockton.co.uk/2012/02/09/if/comment-page-1/#comment-604434</link>
		<dc:creator>Sebastian Deterding</dc:creator>
		<pubDate>Mon, 13 Feb 2012 17:54:14 +0000</pubDate>
		<guid isPermaLink="false">http://architectures.danlockton.co.uk/?p=1766#comment-604434</guid>
		<description>Hi Dan,

thanks for the long, very insightful reply – and thanks again for the long, insightful post itself :).

First off, your description of how one heuristic "bundle" comes to outweigh another one has a striking resemblance to how connectionism (http://en.wikipedia.org/wiki/Connectionism) models cognition. 

Next, I basically put you on the spot for something that I do myself – namely using "the 5 Why's"/"laddering"/however you name it, and not accountig for how prone it is to post-rationalisation errors. It strikes me that this really, really gets at the root of the distinction between humanistic/phenomenological and behavioristic approaches. 

For if you take post-rationalisation *really* seriously (as Skinner did), you have no choice to validate that your if-then rule is a fitting description but to run a series of experimental tests where you try to test and falsify all other alternative plausible rules that could also describe my behaviour. To stick with techcrunch: Is my rule "don't trust anything with a 't' in the domain name"? Or "don't trust anything with a .com domain ending"? So you amass data until you can say: "This if-then rule (don't trust anything that has 'techcrunch' in the URL) is the only one congruent with all data, so I stick with it". Wich is essentially what behavioral (re)targeting does: Run with whatever fits the data best, not knowing whether you follow a correlation or causation. 

Whereas if you grant that people may have at least *some* self-insight into their mental states (not, mind you, the underlying cognitive processes), and that these mental states do correlate at least to *some* degree with underlying cognitive processes, then you are allowed to ask the individual to introspect. Which is why I try – in my guidelines for user research – to instruct people to stick to *describing their lived experience*, rather than explaining what caused this experience.

Why then use the "5 Why's"? I think we can cut ourselves some slack if we shift the interpretation of what the interviewed person does when engaging in "5 Why's" – namely, that the person is not somehow magically lifting the mind-body veil and looking at its own cognitive wheels –, but that by and large, we are our own best oberservers in that we have amassed the largest data set of our own past behaviours from which to conjecture. The only remaining issue is that we also tend towards many self-serving biases. Hence we should take the answers to the 5 Why's as yet one more data point, and nothing more.

Finally, on the levels of abstraction: If you assume that these heuristics 'exist' on different levels of abstraction, then that implies that they are not merely the emergent result of what happens in the black box, because that emergent result will by definition always be one and just one rule (if a complex one). But what I consider even more important is that thinking through design for long-term changes or change processes with mental heuristics will likely be *impractical*, because – to go back to the exercising example – you would have to map a "decision journey" of some sort with a million single decision points for every relevant decision on the way. That's where I think the usefulness of the model breaks down, and we need another model – equally wrong, but more useful.

And yes, definitely, this debate could use another typographical space ;-).</description>
		<content:encoded><![CDATA[<p>Hi Dan,</p>
<p>thanks for the long, very insightful reply – and thanks again for the long, insightful post itself <img src='http://architectures.danlockton.co.uk/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> .</p>
<p>First off, your description of how one heuristic &#8220;bundle&#8221; comes to outweigh another one has a striking resemblance to how connectionism (<a href="http://en.wikipedia.org/wiki/Connectionism" rel="nofollow">http://en.wikipedia.org/wiki/Connectionism</a>) models cognition. </p>
<p>Next, I basically put you on the spot for something that I do myself – namely using &#8220;the 5 Why&#8217;s&#8221;/&#8221;laddering&#8221;/however you name it, and not accountig for how prone it is to post-rationalisation errors. It strikes me that this really, really gets at the root of the distinction between humanistic/phenomenological and behavioristic approaches. </p>
<p>For if you take post-rationalisation *really* seriously (as Skinner did), you have no choice to validate that your if-then rule is a fitting description but to run a series of experimental tests where you try to test and falsify all other alternative plausible rules that could also describe my behaviour. To stick with techcrunch: Is my rule &#8220;don&#8217;t trust anything with a &#8216;t&#8217; in the domain name&#8221;? Or &#8220;don&#8217;t trust anything with a .com domain ending&#8221;? So you amass data until you can say: &#8220;This if-then rule (don&#8217;t trust anything that has &#8216;techcrunch&#8217; in the URL) is the only one congruent with all data, so I stick with it&#8221;. Wich is essentially what behavioral (re)targeting does: Run with whatever fits the data best, not knowing whether you follow a correlation or causation. </p>
<p>Whereas if you grant that people may have at least *some* self-insight into their mental states (not, mind you, the underlying cognitive processes), and that these mental states do correlate at least to *some* degree with underlying cognitive processes, then you are allowed to ask the individual to introspect. Which is why I try – in my guidelines for user research – to instruct people to stick to *describing their lived experience*, rather than explaining what caused this experience.</p>
<p>Why then use the &#8220;5 Why&#8217;s&#8221;? I think we can cut ourselves some slack if we shift the interpretation of what the interviewed person does when engaging in &#8220;5 Why&#8217;s&#8221; – namely, that the person is not somehow magically lifting the mind-body veil and looking at its own cognitive wheels –, but that by and large, we are our own best oberservers in that we have amassed the largest data set of our own past behaviours from which to conjecture. The only remaining issue is that we also tend towards many self-serving biases. Hence we should take the answers to the 5 Why&#8217;s as yet one more data point, and nothing more.</p>
<p>Finally, on the levels of abstraction: If you assume that these heuristics &#8216;exist&#8217; on different levels of abstraction, then that implies that they are not merely the emergent result of what happens in the black box, because that emergent result will by definition always be one and just one rule (if a complex one). But what I consider even more important is that thinking through design for long-term changes or change processes with mental heuristics will likely be *impractical*, because – to go back to the exercising example – you would have to map a &#8220;decision journey&#8221; of some sort with a million single decision points for every relevant decision on the way. That&#8217;s where I think the usefulness of the model breaks down, and we need another model – equally wrong, but more useful.</p>
<p>And yes, definitely, this debate could use another typographical space <img src='http://architectures.danlockton.co.uk/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> .</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on If… by Dan</title>
		<link>http://architectures.danlockton.co.uk/2012/02/09/if/comment-page-1/#comment-604139</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Sun, 12 Feb 2012 22:03:55 +0000</pubDate>
		<guid isPermaLink="false">http://architectures.danlockton.co.uk/?p=1766#comment-604139</guid>
		<description>And no comment permalinks? OK, may have to spend some time fixing this. I apologise.</description>
		<content:encoded><![CDATA[<p>And no comment permalinks? OK, may have to spend some time fixing this. I apologise.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on If… by Dan</title>
		<link>http://architectures.danlockton.co.uk/2012/02/09/if/comment-page-1/#comment-604127</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Sun, 12 Feb 2012 20:13:53 +0000</pubDate>
		<guid isPermaLink="false">http://architectures.danlockton.co.uk/?p=1766#comment-604127</guid>
		<description>Wow, the formatting of these comments is awful. I apologise - didn't test this WP theme well enough before installing it, and am reluctant to use Disqus or similar due to their cross-site tracking.</description>
		<content:encoded><![CDATA[<p>Wow, the formatting of these comments is awful. I apologise &#8211; didn&#8217;t test this WP theme well enough before installing it, and am reluctant to use Disqus or similar due to their cross-site tracking.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on If… by Dan</title>
		<link>http://architectures.danlockton.co.uk/2012/02/09/if/comment-page-1/#comment-604126</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Sun, 12 Feb 2012 20:12:14 +0000</pubDate>
		<guid isPermaLink="false">http://architectures.danlockton.co.uk/?p=1766#comment-604126</guid>
		<description>Right, sorry for the hiatus. Continuing from my last comment:

- About the 'levels of abstraction' at which these heuristics operate, I suppose the most sensible way I can conceive it working is that in a situation, we will inevitably have a number of relevant heuristics which are applicable, some of which are 'universal' like "if it's going to take a long time to do, then don't do it" and others such as "if you think it's going to be tasty, then eat it", "if it's fatty, then don't eat it" and so on. They interact and clash and work on different levels as you suggest. We may have overarching heuristics like "if something is bad for the environment, then don't do it" yet at the coal-face, we follow heuristics like "if it's cheaper to drive to work than get the bus, then drive to work". 

Imagine a friend has given you a recipe for a pie which sounds delicious, but will take some time and effort to cook, and is also going to be quite fatty. One or more of those (potentially conflicting) heuristics is going to 'win', but it's unlikely to be simply a case of adding up columns of pros and cons for each possible action (like &lt;a href="http://www.economictheories.org/2008/12/jeremy-bentham-felicific-calculus.html" rel="nofollow"&gt;Bentham&lt;/a&gt;) or enumerating the possibilities of each (à la &lt;a href="http://www.darwinproject.ac.uk/darwins-notes-on-marriage" rel="nofollow"&gt;Darwin&lt;/a&gt;) - rather, something will lead one heuristic to dominate. Maybe if you're hungry right now, the rule about time will dominate (and lead you to follow the course of action of eating something else instead), but maybe the potential tastiness will dominate. The presence of other actors might also sway you one way or the other - is it fair to inflict this fatty pie on someone you're dating if you know she watches her weight, or will she be impressed by the time/effort/kindness/tastiness? 

Why exactly one/a set of heuristics dominates, and why the dominant one(s) is/are different for different people in different contexts, is, I guess, basically what the entire field of decision research is about. Maybe all of psychology. But from the entirely pragmatic design point of view, I would venture that even the process of trying to understand the heuristics which are present at the point of decision, and what choices are really being made (e.g. is it fatty vs healthy, or time vs taste, or impress-the-girl-by-cooking vs impress-her-by-considering-her-health?) by particular users ought to give us a much better insight into what design techniques would help support / change particular decisions and behaviours.

- Getting at the heuristics. Yes, you're right, the challenge of actually uncovering them is massive, and I did skirt round the issue in the post. There could indeed be infinite interpretations of each, and there will be post-rationalisation by both the researcher and the participant, I'm sure. I suppose my reasons for considering the heuristics as something like black boxes is exactly for this reason: compare outputs to inputs and if you can describe the results in terms of a rule - even if the reasons given behind the rule are wrong or absent - the rule may still be useful. To take your Techcrunch example, describing the heuristic as “don’t click on anything saying ‘techcrunch’” doesn't presuppose the reasons for itself - which may be due to disliking their style, may be due to having learned that the articles will make you angry / waste your time, or it may be something else entirely (like not wanting to be exposed to YouTube-like levels of comments). But the rule "If it says Techcrunch in the URL, don't click on it" is detailed enough to inform at least a basic model of your behaviour when presented with URLs. It's enough to know that to get you to click on a Techcrunch link, the URL will have to be obfuscated. To the extent that I've thought about a process for this (which I haven't yet in detail - hence why your comment is so helpful!) I would venture that the really basic, solely descriptive behavioural heuristics, with no motivation or reasoning assigned to them, could act as a kind of first step to investigating (and influencing) behaviour, with more detailed investigation following. 

Something why always struck me about the 'Five whys' technique was that while it might be intended as a 'root cause' analysis, each level of 'Why?' potentially offers useful opportunities for intervention to solve a problem. If someone asks me "Dan, why don't you do more exercise?", my initial answer will probably be "I'm just too busy to be able to take the time to do it" (which might suggest design interventions like exercise equipment that I could use while at my desk). Further stages of 'Why?' might reveal "I'm too busy because I'm poor at organising my time" (which might suggest a design intervention around scheduling) or "I'm poor at organising my time because I get too easily distracted" (which might suggest some kind of focus-based design intervention) and so on. Each of them could be a valid behaviour change solution, just operating at different levels of abstraction. Of course many 'solutions' are basically treating the symptoms of an underlying disease rather than the disease itself, but this is not uncommon. We still find painkillers useful even though they don't root out what the cause of the pain is in the first place. And I think design for behaviour change can still be a useful painkiller in many circumstances even as we try to understand the disease in others.

- The parcours and affordances example is interesting. There is some work in the human factors literature on 'econiches', e.g. &lt;a href="http://www.colby.edu/psychology/ps272sp09/Warren_1995.pdf" rel="nofollow"&gt;Warren (1995)&lt;/a&gt; which is relevant here. I would say, of course, the 'same' heuristics may be interpreted differently by different users as they relate to themselves, but if they are derived from empirical observations of behaviour, then we just need to find a level which we are able to address through the design techniques available to us.

- You're probably right that the design patterns don't need to follow from the heuristics. If the heuristics are stated clearly enough, the general form of the solution will be obvious. Perhaps the value of the design patterns is really in situations where the heuristics are difficult to uncover or state, or are unclear. Maybe the two approaches could meet in the middle, working backwards from design patterns which seem like they might be relevant and forward from a set of plausible heuristics to define more fully the possibility space for the problem and possible solutions. This is something I'll try to explore through future workshops!

I probably haven't answered all your points, but thanks again for a really helpful comment which has certainly given me the opportunity to think this stuff through a bit more clearly!</description>
		<content:encoded><![CDATA[<p>Right, sorry for the hiatus. Continuing from my last comment:</p>
<p>- About the &#8216;levels of abstraction&#8217; at which these heuristics operate, I suppose the most sensible way I can conceive it working is that in a situation, we will inevitably have a number of relevant heuristics which are applicable, some of which are &#8216;universal&#8217; like &#8220;if it&#8217;s going to take a long time to do, then don&#8217;t do it&#8221; and others such as &#8220;if you think it&#8217;s going to be tasty, then eat it&#8221;, &#8220;if it&#8217;s fatty, then don&#8217;t eat it&#8221; and so on. They interact and clash and work on different levels as you suggest. We may have overarching heuristics like &#8220;if something is bad for the environment, then don&#8217;t do it&#8221; yet at the coal-face, we follow heuristics like &#8220;if it&#8217;s cheaper to drive to work than get the bus, then drive to work&#8221;. </p>
<p>Imagine a friend has given you a recipe for a pie which sounds delicious, but will take some time and effort to cook, and is also going to be quite fatty. One or more of those (potentially conflicting) heuristics is going to &#8216;win&#8217;, but it&#8217;s unlikely to be simply a case of adding up columns of pros and cons for each possible action (like <a href="http://www.economictheories.org/2008/12/jeremy-bentham-felicific-calculus.html" rel="nofollow">Bentham</a>) or enumerating the possibilities of each (à la <a href="http://www.darwinproject.ac.uk/darwins-notes-on-marriage" rel="nofollow">Darwin</a>) &#8211; rather, something will lead one heuristic to dominate. Maybe if you&#8217;re hungry right now, the rule about time will dominate (and lead you to follow the course of action of eating something else instead), but maybe the potential tastiness will dominate. The presence of other actors might also sway you one way or the other &#8211; is it fair to inflict this fatty pie on someone you&#8217;re dating if you know she watches her weight, or will she be impressed by the time/effort/kindness/tastiness? </p>
<p>Why exactly one/a set of heuristics dominates, and why the dominant one(s) is/are different for different people in different contexts, is, I guess, basically what the entire field of decision research is about. Maybe all of psychology. But from the entirely pragmatic design point of view, I would venture that even the process of trying to understand the heuristics which are present at the point of decision, and what choices are really being made (e.g. is it fatty vs healthy, or time vs taste, or impress-the-girl-by-cooking vs impress-her-by-considering-her-health?) by particular users ought to give us a much better insight into what design techniques would help support / change particular decisions and behaviours.</p>
<p>- Getting at the heuristics. Yes, you&#8217;re right, the challenge of actually uncovering them is massive, and I did skirt round the issue in the post. There could indeed be infinite interpretations of each, and there will be post-rationalisation by both the researcher and the participant, I&#8217;m sure. I suppose my reasons for considering the heuristics as something like black boxes is exactly for this reason: compare outputs to inputs and if you can describe the results in terms of a rule &#8211; even if the reasons given behind the rule are wrong or absent &#8211; the rule may still be useful. To take your Techcrunch example, describing the heuristic as “don’t click on anything saying ‘techcrunch’” doesn&#8217;t presuppose the reasons for itself &#8211; which may be due to disliking their style, may be due to having learned that the articles will make you angry / waste your time, or it may be something else entirely (like not wanting to be exposed to YouTube-like levels of comments). But the rule &#8220;If it says Techcrunch in the URL, don&#8217;t click on it&#8221; is detailed enough to inform at least a basic model of your behaviour when presented with URLs. It&#8217;s enough to know that to get you to click on a Techcrunch link, the URL will have to be obfuscated. To the extent that I&#8217;ve thought about a process for this (which I haven&#8217;t yet in detail &#8211; hence why your comment is so helpful!) I would venture that the really basic, solely descriptive behavioural heuristics, with no motivation or reasoning assigned to them, could act as a kind of first step to investigating (and influencing) behaviour, with more detailed investigation following. </p>
<p>Something why always struck me about the &#8216;Five whys&#8217; technique was that while it might be intended as a &#8216;root cause&#8217; analysis, each level of &#8216;Why?&#8217; potentially offers useful opportunities for intervention to solve a problem. If someone asks me &#8220;Dan, why don&#8217;t you do more exercise?&#8221;, my initial answer will probably be &#8220;I&#8217;m just too busy to be able to take the time to do it&#8221; (which might suggest design interventions like exercise equipment that I could use while at my desk). Further stages of &#8216;Why?&#8217; might reveal &#8220;I&#8217;m too busy because I&#8217;m poor at organising my time&#8221; (which might suggest a design intervention around scheduling) or &#8220;I&#8217;m poor at organising my time because I get too easily distracted&#8221; (which might suggest some kind of focus-based design intervention) and so on. Each of them could be a valid behaviour change solution, just operating at different levels of abstraction. Of course many &#8216;solutions&#8217; are basically treating the symptoms of an underlying disease rather than the disease itself, but this is not uncommon. We still find painkillers useful even though they don&#8217;t root out what the cause of the pain is in the first place. And I think design for behaviour change can still be a useful painkiller in many circumstances even as we try to understand the disease in others.</p>
<p>- The parcours and affordances example is interesting. There is some work in the human factors literature on &#8216;econiches&#8217;, e.g. <a href="http://www.colby.edu/psychology/ps272sp09/Warren_1995.pdf" rel="nofollow">Warren (1995)</a> which is relevant here. I would say, of course, the &#8216;same&#8217; heuristics may be interpreted differently by different users as they relate to themselves, but if they are derived from empirical observations of behaviour, then we just need to find a level which we are able to address through the design techniques available to us.</p>
<p>- You&#8217;re probably right that the design patterns don&#8217;t need to follow from the heuristics. If the heuristics are stated clearly enough, the general form of the solution will be obvious. Perhaps the value of the design patterns is really in situations where the heuristics are difficult to uncover or state, or are unclear. Maybe the two approaches could meet in the middle, working backwards from design patterns which seem like they might be relevant and forward from a set of plausible heuristics to define more fully the possibility space for the problem and possible solutions. This is something I&#8217;ll try to explore through future workshops!</p>
<p>I probably haven&#8217;t answered all your points, but thanks again for a really helpful comment which has certainly given me the opportunity to think this stuff through a bit more clearly!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on If… by If… | Design with Intent | UX Design | Scoop.it</title>
		<link>http://architectures.danlockton.co.uk/2012/02/09/if/comment-page-1/#comment-603865</link>
		<dc:creator>If… | Design with Intent | UX Design | Scoop.it</dc:creator>
		<pubDate>Sat, 11 Feb 2012 15:34:54 +0000</pubDate>
		<guid isPermaLink="false">http://architectures.danlockton.co.uk/?p=1766#comment-603865</guid>
		<description>[...] } #themeHeader #titleAndDescription * { color: black; }         architectures.danlockton.co.uk  (via @uxfeeds)  - Today, 5:34 [...]</description>
		<content:encoded><![CDATA[<p>[...] } #themeHeader #titleAndDescription * { color: black; }         architectures.danlockton.co.uk  (via @uxfeeds)  &#8211; Today, 5:34 [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

