<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: A solution to creeping featurism</title>
	<link>http://maadmob.net/donna/blog/2004/a-solution-to-creeping-featurism</link>
	<description>Information architecture, interaction design and much more</description>
	<pubDate>Tue, 07 Oct 2008 16:29:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Gary Davis</title>
		<link>http://maadmob.net/donna/blog/2004/a-solution-to-creeping-featurism#comment-280</link>
		<dc:creator>Gary Davis</dc:creator>
		<pubDate>Tue, 13 Apr 2004 15:46:52 +0000</pubDate>
		<guid>http://maadmob.net/donna/blog/2004/a-solution-to-creeping-featurism#comment-280</guid>
		<description>The method we use to deal with this is to allow only the most frequently used and basic features to be exposed at the top level where the user is likely to want them handy. (we call this the 20/80 rule a.k.a. Pareto principle; google it.) Progressively advanced features are usually behind a button or tab, with the most advanced labeled "Advanced." (or "Advanced " e.g. "Advanced Color" That label tends to scare away less savvy users which is precisely what we wanted. We have tried and tested other buttons names but users are too eager to click on a control just to see what is there. (and risk messing up settings needlessly) When we labeled it advanced, they were less interested. This makes the marketing folks happy as they can say they have a feature and it makes the user happy with a simple UI that tech-savvy users still feel meets their needs.
With this approach, if done right, most users will never encounter those pesky advanced features.
</description>
		<content:encoded><![CDATA[<p>The method we use to deal with this is to allow only the most frequently used and basic features to be exposed at the top level where the user is likely to want them handy. (we call this the 20/80 rule a.k.a. Pareto principle; google it.) Progressively advanced features are usually behind a button or tab, with the most advanced labeled &#8220;Advanced.&#8221; (or &#8220;Advanced &#8221; e.g. &#8220;Advanced Color&#8221; That label tends to scare away less savvy users which is precisely what we wanted. We have tried and tested other buttons names but users are too eager to click on a control just to see what is there. (and risk messing up settings needlessly) When we labeled it advanced, they were less interested. This makes the marketing folks happy as they can say they have a feature and it makes the user happy with a simple UI that tech-savvy users still feel meets their needs.<br />
With this approach, if done right, most users will never encounter those pesky advanced features.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
