<?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: Coping With The Features Conundrum</title>
	<atom:link href="http://dbl.lishost.org/blog/2007/05/31/coping-with-the-features-conundrum/feed/" rel="self" type="application/rss+xml" />
	<link>http://dbl.lishost.org/blog/2007/05/31/coping-with-the-features-conundrum/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Tue, 07 Feb 2012 15:51:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: stevenb</title>
		<link>http://dbl.lishost.org/blog/2007/05/31/coping-with-the-features-conundrum/comment-page-1/#comment-218</link>
		<dc:creator>stevenb</dc:creator>
		<pubDate>Wed, 27 Jun 2007 12:06:32 +0000</pubDate>
		<guid isPermaLink="false">http://dbl.lishost.org/blog/2007/05/31/coping-with-the-features-conundrum/#comment-218</guid>
		<description>Thanks for sharing those CPU links Darlene. I agree that some of the CPU posts on developing passion among users are well worth reading. It got me to thinking that it is critical to engaging them in features that can really be of benefit to them. I covered similar territory in posts over at ACRLog (after being inspired by CPU). Here is a link to one of them:

http://acrlblog.org/2006/08/15/moving-beyond-beginners-level/</description>
		<content:encoded><![CDATA[<p>Thanks for sharing those CPU links Darlene. I agree that some of the CPU posts on developing passion among users are well worth reading. It got me to thinking that it is critical to engaging them in features that can really be of benefit to them. I covered similar territory in posts over at ACRLog (after being inspired by CPU). Here is a link to one of them:</p>
<p><a href="http://acrlblog.org/2006/08/15/moving-beyond-beginners-level/" rel="nofollow">http://acrlblog.org/2006/08/15/moving-beyond-beginners-level/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Darlene Fichter</title>
		<link>http://dbl.lishost.org/blog/2007/05/31/coping-with-the-features-conundrum/comment-page-1/#comment-214</link>
		<dc:creator>Darlene Fichter</dc:creator>
		<pubDate>Wed, 27 Jun 2007 01:29:59 +0000</pubDate>
		<guid isPermaLink="false">http://dbl.lishost.org/blog/2007/05/31/coping-with-the-features-conundrum/#comment-214</guid>
		<description>I think there is a features conundrum.  It&#039;s easy to say that a site should be simple and easy to use, but for whom?  The expectations  and the features considered essential and useful by one group are considered unnecessary by another group.  All users are not equal.  

I also don&#039;t know if it&#039;s the number of features that are the major issue but how and when they&#039;re presented to the users and in what way.  

I think the biggest challenge libraries face isn&#039;t simplifying interfaces (although we have work to do there for sure) but getting our users our of &quot;P&quot; mode or default mode.  How often do you meet a library user passionate about maximizing their use of the library interfaces?  Do we inspire them to learn?

This is something Kathy Sierra, at Creating Passionate Users, posted eloquently about here 

Are your users stuck in &quot;P&quot; mode?
http://headrush.typepad.com/creating_passionate_users/2006/08/are_your_users_.html

and here 

The hi-res user experience
http://headrush.typepad.com/creating_passionate_users/2005/12/the_hires_user_.html)

I think about systems or programs where I start off using one or two features like the DVR or email program or social software site and I stay at that level using the &quot;default&quot; mode and which ones do I learn more and more about and have a &quot;highres&quot; user experience.  For example with Flickr, I clearly got out of default mode pretty quickly and continued to learn stuff. Other sites I stay pretty much in P mode (usually do to frustration with the time it takes to do what I consider &quot;simple&quot; things.)

Designing simple is darn difficult.</description>
		<content:encoded><![CDATA[<p>I think there is a features conundrum.  It&#8217;s easy to say that a site should be simple and easy to use, but for whom?  The expectations  and the features considered essential and useful by one group are considered unnecessary by another group.  All users are not equal.  </p>
<p>I also don&#8217;t know if it&#8217;s the number of features that are the major issue but how and when they&#8217;re presented to the users and in what way.  </p>
<p>I think the biggest challenge libraries face isn&#8217;t simplifying interfaces (although we have work to do there for sure) but getting our users our of &#8220;P&#8221; mode or default mode.  How often do you meet a library user passionate about maximizing their use of the library interfaces?  Do we inspire them to learn?</p>
<p>This is something Kathy Sierra, at Creating Passionate Users, posted eloquently about here </p>
<p>Are your users stuck in &#8220;P&#8221; mode?<br />
<a href="http://headrush.typepad.com/creating_passionate_users/2006/08/are_your_users_.html" rel="nofollow">http://headrush.typepad.com/creating_passionate_users/2006/08/are_your_users_.html</a></p>
<p>and here </p>
<p>The hi-res user experience<br />
<a href="http://headrush.typepad.com/creating_passionate_users/2005/12/the_hires_user_.html" rel="nofollow">http://headrush.typepad.com/creating_passionate_users/2005/12/the_hires_user_.html</a>)</p>
<p>I think about systems or programs where I start off using one or two features like the DVR or email program or social software site and I stay at that level using the &#8220;default&#8221; mode and which ones do I learn more and more about and have a &#8220;highres&#8221; user experience.  For example with Flickr, I clearly got out of default mode pretty quickly and continued to learn stuff. Other sites I stay pretty much in P mode (usually do to frustration with the time it takes to do what I consider &#8220;simple&#8221; things.)</p>
<p>Designing simple is darn difficult.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Theresa</title>
		<link>http://dbl.lishost.org/blog/2007/05/31/coping-with-the-features-conundrum/comment-page-1/#comment-151</link>
		<dc:creator>Theresa</dc:creator>
		<pubDate>Fri, 01 Jun 2007 13:52:32 +0000</pubDate>
		<guid isPermaLink="false">http://dbl.lishost.org/blog/2007/05/31/coping-with-the-features-conundrum/#comment-151</guid>
		<description>Great post! i agree with this perspective on the user experience.  In my short presence in a public linrary, I have found that users want is simple service.  They don&#039;t need &quot;features&quot;.  Librarians should follow the KISS method of life.</description>
		<content:encoded><![CDATA[<p>Great post! i agree with this perspective on the user experience.  In my short presence in a public linrary, I have found that users want is simple service.  They don&#8217;t need &#8220;features&#8221;.  Librarians should follow the KISS method of life.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

