<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Synap Software comments on Great Visual of Simplification by Reduction</title>
    <link>http://4webit.com/blogit/</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>Synap Software comments</description>
    <item>
      <title>"Great Visual of Simplification by Reduction" by smeade</title>
      <description>&lt;p style="float:left"&gt;&lt;img src="http://synapsoftware.com/images/reduceremote.png" alt="" /&gt;&lt;/p&gt;


	&lt;p&gt;I love &lt;a href="http://www.designinginteractions.com/chapters/4"&gt;this&lt;/a&gt;  photo &amp;#8211; &amp;#8220;Understanding how to use a remote is made easier by a friend&amp;#8221; &amp;#8211; as an example of the power of reduction to make something easier to understand and give people a better experience.  Take away all the stuff people don&amp;#8217;t need and suddenly instead of fumbling around feeling stupid, they easily start doing what they want.&lt;/p&gt;


	&lt;p&gt;Also, the instructions are written directly on the remotes.  The friend didn&amp;#8217;t write seperate notes on a piece of paper saying &amp;#8220;press the up and down arrows on the slim remote to change volume&amp;#8221;.  Instead, the friend wrote directly on the remote: &amp;#8220;Volume&amp;#8221;.  Similarly, seperate &amp;#8220;help&amp;#8221; files and manuals for software need to die.  There are better alternatives such as inline prompts and making a design so obvious and activity-centered that people do not need help files.&lt;/p&gt;

</description>
      <pubDate>Mon, 18 Jun 2007 10:01:00 EDT</pubDate>
      <guid>&lt;a href="/blogit/articles/2007/06/18/simplification-by-reduction"&gt;Great Visual of Simplification by Reduction&lt;/a&gt;</guid>
      <link>&lt;a href="/blogit/articles/2007/06/18/simplification-by-reduction"&gt;Great Visual of Simplification by Reduction&lt;/a&gt;</link>
    </item>
  </channel>
</rss>
