<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Ease of use is a feature</title>
	<atom:link href="http://mdzlog.alcor.net/2008/08/25/ease-of-use-is-a-feature/feed/" rel="self" type="application/rss+xml" />
	<link>http://mdzlog.alcor.net/2008/08/25/ease-of-use-is-a-feature/</link>
	<description>a potpourri of mirth and madness</description>
	<lastBuildDate>Mon, 23 Jan 2012 03:06:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Thorsten Wilms</title>
		<link>http://mdzlog.alcor.net/2008/08/25/ease-of-use-is-a-feature/#comment-22</link>
		<dc:creator><![CDATA[Thorsten Wilms]]></dc:creator>
		<pubDate>Thu, 28 Aug 2008 11:47:21 +0000</pubDate>
		<guid isPermaLink="false">http://mdzlog.wordpress.com/?p=15#comment-22</guid>
		<description><![CDATA[To expand on my previous post, drawing in some material from my archive :)
On how to systematically improve usability for Ubuntu.


First: Try to agree on one central, official definition of usability!

My preferred definition of usability goes along the lines of: the combination of effectiveness, efficiency and user satisfaction for a specific context made up of a goal to accomplish, a user and his environment.

So after defining the context, you have to ask if the goal can be accomplished by the user(s) at all. Then how well it can be accomplished (there can several factors such as how long different stages take or the stress level of the user, so you need a weighting). Finally how satisfied the user feels. Happy people tend to perform better, so this could be seen as an aspect of efficiency, but it is well possible that a less efficient design is more satisfying.

All other aspects such as learnability, memorability, predictability, responsiveness, robustness, ... follow from the above.


1. Incremental approach, works mainly on detail level
- Do expert UI reviews per package.
- Use checklists.
- Test by observing users.
- Use above as input for a brief conception stage.
- Implement changes and repeat.

2. Context approach, can be used outside of package boundaries
- Define user groups, environments and matching common activities/goals. Do surveys, interviews and on-site visits to learn about all these. Prioritises by importance for Ubuntu. You may have to explicitly exclude some fields.
- Break activities down into tasks (Activity: browse the web, task: find a picture of an Ibex)
- Evaluate if and how well the tasks can be performed / goals can be reached within their context with what Ubuntu currently has to offer.
- Consider the knowledge a user has to have for each task. See if it can be reduced.
- Go into research and conception to fix the holes you find.
- Implement changes and switch to 1.

3. Research approach, increase your knowledge
- Study potentially relevant HCI/usability and cognitive psychology research.
- Fund additional research if necessary.
- Build a hierarchical system of goals to facilitate objective and exhaustive judgment of concepts.
- Create concepts for basic interaction based on human-centered research (instead of what has been convenient for technical reasons).
- Add detail by going through user groups, environments, activities/tasks.

4. Vision approach, look ahead
- Create at least one scenario concerning upcoming technology, trends and cultural change in 5, 10 or 15 years.
- Extract new user goals, tasks and the resulting requirements.
- Combine this with 3.
- Write a roadmap to get from now to then and act accordingly.
- Communicate the vision and conclusions to the community.

5. Community and education approach
- Document everything of the above in an open manner. Facilitate participation.
- Publish examples of expert UI reviews and checklists and invite users and developers to try it themselves (many eyes ...).
- Build or recommend a portal to usability related research.
- Build a manual on how to design or refine software UI to our best knowledge.
- Highlight successful developments.

6. Framework approach, allow it to happen.
- Make it easier to design, implement, test and change UI. Especially for those who don&#039;t consider themselves developers.
- Push for engine/UI separation
- Build tools to manage the user- and/or activity-centered design of software. Starting from goals and requirements.]]></description>
		<content:encoded><![CDATA[<p>To expand on my previous post, drawing in some material from my archive :)<br />
On how to systematically improve usability for Ubuntu.</p>
<p>First: Try to agree on one central, official definition of usability!</p>
<p>My preferred definition of usability goes along the lines of: the combination of effectiveness, efficiency and user satisfaction for a specific context made up of a goal to accomplish, a user and his environment.</p>
<p>So after defining the context, you have to ask if the goal can be accomplished by the user(s) at all. Then how well it can be accomplished (there can several factors such as how long different stages take or the stress level of the user, so you need a weighting). Finally how satisfied the user feels. Happy people tend to perform better, so this could be seen as an aspect of efficiency, but it is well possible that a less efficient design is more satisfying.</p>
<p>All other aspects such as learnability, memorability, predictability, responsiveness, robustness, &#8230; follow from the above.</p>
<p>1. Incremental approach, works mainly on detail level<br />
- Do expert UI reviews per package.<br />
- Use checklists.<br />
- Test by observing users.<br />
- Use above as input for a brief conception stage.<br />
- Implement changes and repeat.</p>
<p>2. Context approach, can be used outside of package boundaries<br />
- Define user groups, environments and matching common activities/goals. Do surveys, interviews and on-site visits to learn about all these. Prioritises by importance for Ubuntu. You may have to explicitly exclude some fields.<br />
- Break activities down into tasks (Activity: browse the web, task: find a picture of an Ibex)<br />
- Evaluate if and how well the tasks can be performed / goals can be reached within their context with what Ubuntu currently has to offer.<br />
- Consider the knowledge a user has to have for each task. See if it can be reduced.<br />
- Go into research and conception to fix the holes you find.<br />
- Implement changes and switch to 1.</p>
<p>3. Research approach, increase your knowledge<br />
- Study potentially relevant HCI/usability and cognitive psychology research.<br />
- Fund additional research if necessary.<br />
- Build a hierarchical system of goals to facilitate objective and exhaustive judgment of concepts.<br />
- Create concepts for basic interaction based on human-centered research (instead of what has been convenient for technical reasons).<br />
- Add detail by going through user groups, environments, activities/tasks.</p>
<p>4. Vision approach, look ahead<br />
- Create at least one scenario concerning upcoming technology, trends and cultural change in 5, 10 or 15 years.<br />
- Extract new user goals, tasks and the resulting requirements.<br />
- Combine this with 3.<br />
- Write a roadmap to get from now to then and act accordingly.<br />
- Communicate the vision and conclusions to the community.</p>
<p>5. Community and education approach<br />
- Document everything of the above in an open manner. Facilitate participation.<br />
- Publish examples of expert UI reviews and checklists and invite users and developers to try it themselves (many eyes &#8230;).<br />
- Build or recommend a portal to usability related research.<br />
- Build a manual on how to design or refine software UI to our best knowledge.<br />
- Highlight successful developments.</p>
<p>6. Framework approach, allow it to happen.<br />
- Make it easier to design, implement, test and change UI. Especially for those who don&#8217;t consider themselves developers.<br />
- Push for engine/UI separation<br />
- Build tools to manage the user- and/or activity-centered design of software. Starting from goals and requirements.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mdz</title>
		<link>http://mdzlog.alcor.net/2008/08/25/ease-of-use-is-a-feature/#comment-21</link>
		<dc:creator><![CDATA[mdz]]></dc:creator>
		<pubDate>Wed, 27 Aug 2008 19:06:51 +0000</pubDate>
		<guid isPermaLink="false">http://mdzlog.wordpress.com/?p=15#comment-21</guid>
		<description><![CDATA[Thanks for all the feedback.  Note that I&#039;m particularly interested in how we can *systematically* improve usability, more so than specific usability improvements, though I&#039;ll have a look at those suggestions.]]></description>
		<content:encoded><![CDATA[<p>Thanks for all the feedback.  Note that I&#8217;m particularly interested in how we can *systematically* improve usability, more so than specific usability improvements, though I&#8217;ll have a look at those suggestions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Azrael Nightwalker</title>
		<link>http://mdzlog.alcor.net/2008/08/25/ease-of-use-is-a-feature/#comment-20</link>
		<dc:creator><![CDATA[Azrael Nightwalker]]></dc:creator>
		<pubDate>Tue, 26 Aug 2008 21:24:50 +0000</pubDate>
		<guid isPermaLink="false">http://mdzlog.wordpress.com/?p=15#comment-20</guid>
		<description><![CDATA[I have some simple ideas: 
1) add an ability to nautilus to pause and file operations (moving, copying...)
2) add an operation queuing to nautilus to prevent unnecessary disk seeks and thus slowing the whole operation
3) develop a tool to manage gnome panel(s) layout (and applets&#039; layout)
4) add a gui for mounting drives
5) add an option for livecd to load itself to ram and free the cd drive
6) add an easier to discover gui for autostarting programs

See also:
wiki.ubuntu.com/DesktopTeam/UsabilityWishlis
wiki.ubuntu.com/CommunityGutsyIdeas/Other
wiki.ubuntu.com/CommunityGutsyIdeas/Usability
wiki.ubuntu.com/UsabilityInPractice
wiki.ubuntu.com/UsabilityTheories
wiki.ubuntu.com/GutsyForumIdeas
(I hope this comment won&#039;t land in spam)]]></description>
		<content:encoded><![CDATA[<p>I have some simple ideas:<br />
1) add an ability to nautilus to pause and file operations (moving, copying&#8230;)<br />
2) add an operation queuing to nautilus to prevent unnecessary disk seeks and thus slowing the whole operation<br />
3) develop a tool to manage gnome panel(s) layout (and applets&#8217; layout)<br />
4) add a gui for mounting drives<br />
5) add an option for livecd to load itself to ram and free the cd drive<br />
6) add an easier to discover gui for autostarting programs</p>
<p>See also:<br />
wiki.ubuntu.com/DesktopTeam/UsabilityWishlis<br />
wiki.ubuntu.com/CommunityGutsyIdeas/Other<br />
wiki.ubuntu.com/CommunityGutsyIdeas/Usability<br />
wiki.ubuntu.com/UsabilityInPractice<br />
wiki.ubuntu.com/UsabilityTheories<br />
wiki.ubuntu.com/GutsyForumIdeas<br />
(I hope this comment won&#8217;t land in spam)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thorsten Wilms</title>
		<link>http://mdzlog.alcor.net/2008/08/25/ease-of-use-is-a-feature/#comment-19</link>
		<dc:creator><![CDATA[Thorsten Wilms]]></dc:creator>
		<pubDate>Tue, 26 Aug 2008 16:59:05 +0000</pubDate>
		<guid isPermaLink="false">http://mdzlog.wordpress.com/?p=15#comment-19</guid>
		<description><![CDATA[I can think of 3 broad strategies for improving the ease of use, or maybe I should say usefulness, of Ubuntu or any distribution:
- Work from the current state. I think UI reviews should play a central role. You should also define user groups, environments and tasks to analyse the usability for said tasks within context. This is important to not get stuck on a per-package level.
- Build infrastructure that will make it faster and simpler to design, implement, test and tweak UIs. Specifically make it possible for non-coders.
- Do an activity-centered top-down design of the base system. What we have now has much to do with what has been convenient, technically. I think this is necessary to address some deep issues  that are hard to impossible to get at with an incremental process.

See http://www.jnd.org/dn.mss/human-centered.html for a take on human-centered vs activity-centered design.]]></description>
		<content:encoded><![CDATA[<p>I can think of 3 broad strategies for improving the ease of use, or maybe I should say usefulness, of Ubuntu or any distribution:<br />
- Work from the current state. I think UI reviews should play a central role. You should also define user groups, environments and tasks to analyse the usability for said tasks within context. This is important to not get stuck on a per-package level.<br />
- Build infrastructure that will make it faster and simpler to design, implement, test and tweak UIs. Specifically make it possible for non-coders.<br />
- Do an activity-centered top-down design of the base system. What we have now has much to do with what has been convenient, technically. I think this is necessary to address some deep issues  that are hard to impossible to get at with an incremental process.</p>
<p>See <a href="http://www.jnd.org/dn.mss/human-centered.html" rel="nofollow">http://www.jnd.org/dn.mss/human-centered.html</a> for a take on human-centered vs activity-centered design.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mdz</title>
		<link>http://mdzlog.alcor.net/2008/08/25/ease-of-use-is-a-feature/#comment-18</link>
		<dc:creator><![CDATA[mdz]]></dc:creator>
		<pubDate>Tue, 26 Aug 2008 10:58:11 +0000</pubDate>
		<guid isPermaLink="false">http://mdzlog.wordpress.com/?p=15#comment-18</guid>
		<description><![CDATA[The problem with truncated posts on Planet Ubuntu should be fixed now, by switching from RSS to Atom.]]></description>
		<content:encoded><![CDATA[<p>The problem with truncated posts on Planet Ubuntu should be fixed now, by switching from RSS to Atom.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stefano</title>
		<link>http://mdzlog.alcor.net/2008/08/25/ease-of-use-is-a-feature/#comment-17</link>
		<dc:creator><![CDATA[Stefano]]></dc:creator>
		<pubDate>Tue, 26 Aug 2008 01:19:14 +0000</pubDate>
		<guid isPermaLink="false">http://mdzlog.wordpress.com/?p=15#comment-17</guid>
		<description><![CDATA[I agree with jldugger. Matt, please set your blog to use full feeds.]]></description>
		<content:encoded><![CDATA[<p>I agree with jldugger. Matt, please set your blog to use full feeds.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jldugger</title>
		<link>http://mdzlog.alcor.net/2008/08/25/ease-of-use-is-a-feature/#comment-14</link>
		<dc:creator><![CDATA[jldugger]]></dc:creator>
		<pubDate>Mon, 25 Aug 2008 19:53:40 +0000</pubDate>
		<guid isPermaLink="false">http://mdzlog.wordpress.com/?p=15#comment-14</guid>
		<description><![CDATA[What&#039;s with the half sentence cuts?  I think something like 97 percent of all planet hits are RSS based!]]></description>
		<content:encoded><![CDATA[<p>What&#8217;s with the half sentence cuts?  I think something like 97 percent of all planet hits are RSS based!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anonim</title>
		<link>http://mdzlog.alcor.net/2008/08/25/ease-of-use-is-a-feature/#comment-13</link>
		<dc:creator><![CDATA[anonim]]></dc:creator>
		<pubDate>Mon, 25 Aug 2008 19:12:15 +0000</pubDate>
		<guid isPermaLink="false">http://mdzlog.wordpress.com/?p=15#comment-13</guid>
		<description><![CDATA[How about http://www.betterdesktop.org ?

Maybe ubuntu should collaborate with this proyect.]]></description>
		<content:encoded><![CDATA[<p>How about <a href="http://www.betterdesktop.org" rel="nofollow">http://www.betterdesktop.org</a> ?</p>
<p>Maybe ubuntu should collaborate with this proyect.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zimmerman Matt</title>
		<link>http://mdzlog.alcor.net/2008/08/25/ease-of-use-is-a-feature/#comment-12</link>
		<dc:creator><![CDATA[Zimmerman Matt]]></dc:creator>
		<pubDate>Mon, 25 Aug 2008 19:05:18 +0000</pubDate>
		<guid isPermaLink="false">http://mdzlog.wordpress.com/?p=15#comment-12</guid>
		<description><![CDATA[@Eric Pritchett, I&#039;ve explored some similar ideas in a usability context.  A workable approach to usability testing for Ubuntu would need to support distributed operation, remotely observing user behavior.  I wonder how successful this would be with simple observation of the desktop session.  The cues from the user&#039;s physical posture can be telling, and their spoken commentary can be invaluable.]]></description>
		<content:encoded><![CDATA[<p>@Eric Pritchett, I&#8217;ve explored some similar ideas in a usability context.  A workable approach to usability testing for Ubuntu would need to support distributed operation, remotely observing user behavior.  I wonder how successful this would be with simple observation of the desktop session.  The cues from the user&#8217;s physical posture can be telling, and their spoken commentary can be invaluable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mdzlog</title>
		<link>http://mdzlog.alcor.net/2008/08/25/ease-of-use-is-a-feature/#comment-11</link>
		<dc:creator><![CDATA[mdzlog]]></dc:creator>
		<pubDate>Mon, 25 Aug 2008 18:56:10 +0000</pubDate>
		<guid isPermaLink="false">http://mdzlog.wordpress.com/?p=15#comment-11</guid>
		<description><![CDATA[@seele, I&#039;d like to live in a world where usability could be taken for granted this way, but we aren&#039;t there yet.  You&#039;re right that this needs to be a core value, not something which is relegated to certain people or teams, though such people and teams can make a big difference in promoting it.

Nobody said it would be easy, but this is an area where we (Canonical in this case) can justify making an investment.  Watch this space.]]></description>
		<content:encoded><![CDATA[<p>@seele, I&#8217;d like to live in a world where usability could be taken for granted this way, but we aren&#8217;t there yet.  You&#8217;re right that this needs to be a core value, not something which is relegated to certain people or teams, though such people and teams can make a big difference in promoting it.</p>
<p>Nobody said it would be easy, but this is an area where we (Canonical in this case) can justify making an investment.  Watch this space.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

