<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: User Centric IT</title>
	<atom:link href="http://blog.schenkin.com/2009/07/user-centric-it/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.schenkin.com/2009/07/user-centric-it/</link>
	<description>Sam's musings on technology in the zany nonprofit world</description>
	<lastBuildDate>Thu, 16 Jul 2009 16:54:02 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: schenkin</title>
		<link>http://blog.schenkin.com/2009/07/user-centric-it/comment-page-1/#comment-40</link>
		<dc:creator>schenkin</dc:creator>
		<pubDate>Thu, 16 Jul 2009 16:54:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.schenkin.com/?p=76#comment-40</guid>
		<description>It&#039;s all about your audience. Excel and Photoshop get away with it because their users have a level of sophistication. And for entry level users, it tends to hide the complicated stuff away behind menus and shortcuts.

With that said, I&#039;m not really interested in debating the merits of complicated software -- find a UX person for that :). I want to explore how you can take these lessons from software development and apply them to the Information System as a whole.</description>
		<content:encoded><![CDATA[<p>It&#8217;s all about your audience. Excel and Photoshop get away with it because their users have a level of sophistication. And for entry level users, it tends to hide the complicated stuff away behind menus and shortcuts.</p>
<p>With that said, I&#8217;m not really interested in debating the merits of complicated software &#8212; find a UX person for that <img src='http://blog.schenkin.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> . I want to explore how you can take these lessons from software development and apply them to the Information System as a whole.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Misczak</title>
		<link>http://blog.schenkin.com/2009/07/user-centric-it/comment-page-1/#comment-39</link>
		<dc:creator>John Misczak</dc:creator>
		<pubDate>Thu, 16 Jul 2009 16:46:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.schenkin.com/?p=76#comment-39</guid>
		<description>The problem is that far too often, &quot;intuitive&quot; means &quot;familiar&quot; to users. It&#039;s a bias problem really. For someone who has used traditional corporate mail their entire lives, such as Outlook or Lotus, Hotmail will be a more intuitive system than Gmail because the folder interface is more familiar to what they already know. Never mind the fact that Gmail is far more flexible with its labels and archiving features (and objectively speaking, more intuitive to a technological neophyte).

A lot of times, &quot;minimizing&quot; the amount of knowledge a system requires a user to know doesn&#039;t remove that much information at all. Powerful pieces of software, such as Excel, Photoshop, Final Cut, etc. are powerful because they require a commitment to learn them. Sure, it&#039;s easier for a user to pick up Windows Movie Maker or Paint, but they won&#039;t be given nearly as many features to utilize in order to perform their job. I would say it&#039;s not the minimizing that&#039;s important - it&#039;s the art of providing enough of a reward for the commitment a user makes at all parts of the user spectrum.</description>
		<content:encoded><![CDATA[<p>The problem is that far too often, &#8220;intuitive&#8221; means &#8220;familiar&#8221; to users. It&#8217;s a bias problem really. For someone who has used traditional corporate mail their entire lives, such as Outlook or Lotus, Hotmail will be a more intuitive system than Gmail because the folder interface is more familiar to what they already know. Never mind the fact that Gmail is far more flexible with its labels and archiving features (and objectively speaking, more intuitive to a technological neophyte).</p>
<p>A lot of times, &#8220;minimizing&#8221; the amount of knowledge a system requires a user to know doesn&#8217;t remove that much information at all. Powerful pieces of software, such as Excel, Photoshop, Final Cut, etc. are powerful because they require a commitment to learn them. Sure, it&#8217;s easier for a user to pick up Windows Movie Maker or Paint, but they won&#8217;t be given nearly as many features to utilize in order to perform their job. I would say it&#8217;s not the minimizing that&#8217;s important &#8211; it&#8217;s the art of providing enough of a reward for the commitment a user makes at all parts of the user spectrum.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
