<?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: Designed to control rather than enable</title>
	<atom:link href="http://architectures.danlockton.co.uk/2006/09/13/designed-to-control-rather-than-enable/feed/" rel="self" type="application/rss+xml" />
	<link>http://architectures.danlockton.co.uk/2006/09/13/designed-to-control-rather-than-enable/</link>
	<description>How do people use products, systems and environments?  How can designers influence interaction?  How can we design for sustainable behaviour?</description>
	<pubDate>Sun, 12 Oct 2008 01:56:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>By: Dan</title>
		<link>http://architectures.danlockton.co.uk/2006/09/13/designed-to-control-rather-than-enable/#comment-9052</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Tue, 19 Sep 2006 14:11:53 +0000</pubDate>
		<guid isPermaLink="false">http://architectures.danlockton.co.uk/?p=115#comment-9052</guid>
		<description>Thanks Todd - of course, you're right. I've tried to look at some of these in the past, especially &lt;a href="http://architectures.danlockton.co.uk/?page_id=6#forcing" rel="nofollow"&gt;forcing functions&lt;/a&gt; and &lt;a href="http://architectures.danlockton.co.uk/?page_id=6#pokayoke" rel="nofollow"&gt;mistake-proofing&lt;/a&gt; (&lt;em&gt;poka-yoke&lt;/em&gt;) but it's true that recent posts have tended towards "pushing people around to meet business goals" rather than helping people "making systems work smoothly" or "keeping people safe". I'll try to remedy that!</description>
		<content:encoded><![CDATA[<p>Thanks Todd - of course, you&#8217;re right. I&#8217;ve tried to look at some of these in the past, especially <a href="http://architectures.danlockton.co.uk/?page_id=6#forcing" rel="nofollow">forcing functions</a> and <a href="http://architectures.danlockton.co.uk/?page_id=6#pokayoke" rel="nofollow">mistake-proofing</a> (<em>poka-yoke</em>) but it&#8217;s true that recent posts have tended towards &#8220;pushing people around to meet business goals&#8221; rather than helping people &#8220;making systems work smoothly&#8221; or &#8220;keeping people safe&#8221;. I&#8217;ll try to remedy that!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Todd Sieling</title>
		<link>http://architectures.danlockton.co.uk/2006/09/13/designed-to-control-rather-than-enable/#comment-8706</link>
		<dc:creator>Todd Sieling</dc:creator>
		<pubDate>Fri, 15 Sep 2006 15:49:32 +0000</pubDate>
		<guid isPermaLink="false">http://architectures.danlockton.co.uk/?p=115#comment-8706</guid>
		<description>It's worth noting that sometimes being controlled is a good thing - in traffic, for example, it's only possible to drive peacefully because we have lights and lines that tell us where to be, and laws to back them up. This is a form of control, but it's one that makes driving possible. In other cases, controls are in place to keep us out of danger or from making mistakes. A software confirmation message prior to executing a critical action, designed to psychologically engage a person's fear of loss, is an effective form of controlling against a serious mistake, and I think that's not a bad thing.

The kinds of controls that Cory is talking about are, I think, not the kind I'm talking about above, so his point is well taken. But I think it's worth noting, and if I can suggest, blogging about controls that actually help people rather than push them around to meet the business goals of vendors.</description>
		<content:encoded><![CDATA[<p>It&#8217;s worth noting that sometimes being controlled is a good thing - in traffic, for example, it&#8217;s only possible to drive peacefully because we have lights and lines that tell us where to be, and laws to back them up. This is a form of control, but it&#8217;s one that makes driving possible. In other cases, controls are in place to keep us out of danger or from making mistakes. A software confirmation message prior to executing a critical action, designed to psychologically engage a person&#8217;s fear of loss, is an effective form of controlling against a serious mistake, and I think that&#8217;s not a bad thing.</p>
<p>The kinds of controls that Cory is talking about are, I think, not the kind I&#8217;m talking about above, so his point is well taken. But I think it&#8217;s worth noting, and if I can suggest, blogging about controls that actually help people rather than push them around to meet the business goals of vendors.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
