<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Wikimedia blog &#187; usability</title>
	<atom:link href="http://blog.wikimedia.org/tag/usability/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.wikimedia.org</link>
	<description>News from inside the Wikimedia Foundation.org</description>
	<lastBuildDate>Tue, 24 Nov 2009 01:49:01 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>UX + Usability Study Take Two!</title>
		<link>http://blog.wikimedia.org/2009/11/18/ux-usability-study-take-two/</link>
		<comments>http://blog.wikimedia.org/2009/11/18/ux-usability-study-take-two/#comments</comments>
		<pubDate>Wed, 18 Nov 2009 01:40:34 +0000</pubDate>
		<dc:creator>Parul</dc:creator>
				<category><![CDATA[Wikimedia]]></category>
		<category><![CDATA[Wikipedia]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[usabilty mediawiki]]></category>

		<guid isPermaLink="false">http://blog.wikimedia.org/?p=1206</guid>
		<description><![CDATA[

The Wikipedia Usability Initiative partnered with Bolt Peters and Davis Research to evaluate the changes we&#8217;ve implemented so far and inform our work moving forward.  If you don&#8217;t know what changes we are talking about, check out our Beta (including a new skin, new toolbar, improved search, and more) by following these instructions.
Overall, the study [...]]]></description>
			<content:encoded><![CDATA[<p style="text-align: center;"><img class="aligncenter" src="http://upload.wikimedia.org/wikipedia/commons/2/2f/WPUI_study2_screenshots.jpg" alt="Usability Study No. 2" width="700" align="center" /></p>
<p><br/></p>
<p>The Wikipedia Usability Initiative partnered with <a href="http://boltpeters.com/" target="_blank">Bolt Peters</a> and <a href="http://www.davisresearch.com/" target="_blank">Davis Research</a> to evaluate the changes we&#8217;ve implemented so far and inform our work moving forward.  If you don&#8217;t know what changes we are talking about, check out our Beta (including a new skin, new toolbar, improved search, and more) by following <a href="http://techblog.wikimedia.org/2009/08/try-the-usability-beta/">these</a> instructions.</p>
<p>Overall, the study confirmed that we are on the right track with our beta features &#8211; showing us room for improvements, maybe a bug or two along the way, and work yet to be done!  You can view the <a href="http://usability.wikimedia.org/wiki/Usability,_Experience,_and_Progress_Study" target="_blank">full report</a> (and soon the <a href="http://usability.wikimedia.org/wiki/Usability,_Experience,_and_Progress_Study#Full_Interview_Videos" target="_blank">full videos</a>) on our <a href="http://usability.wikimedia.org/wiki/Main_Page" target="_blank">project wiki</a>, but we thought we&#8217;d share with you some highlights:</p>
<p><span style="text-decoration: underline;">Success</span><span style="color: gray;"> </span></p>
<p><span style="color: gray;"><em>“It was easy, and I wouldn’t have thought it would be that easy.”</em></span></p>
<p><span style="color: gray;"><em>“Before there were a lot of tools, and I liked that they were all spread out in front of you, but this actually makes a lot of sense. I had to muddle my way through the older system, but this one seemed fine.”</em></span></p>
<p><span style="color: gray;"><em>&#8220;Websites don&#8217;t have common sense, but programmers do.&#8221;</em></span></p>
<p>The majority of our 8 interview subjects found and used our features and tools without instruction and with success.  Special victories go to our more spacious and grouped tabbed navigation, improved search and new searchbox location, and built-in toolbar.  In using these features, users were not only less intimidated, but also showed a greater ease of use and increased performance.  All of the 8 users successfully found the &#8220;edit&#8221; tab with a minimum of hunting; no one resorted to Google to get to the Wikipedia article they were seeking; two of our users even expressed pleasure and delight in the process!  Perhaps small victories, but a major change from our <a href="http://usability.wikimedia.org/wiki/Usability_and_Experience_Study">first study</a> if you remember!</p>
<p><span style="text-decoration: underline;">Needs Improvement</span><span style="color: gray;"><em> </em></span></p>
<p><span style="color: gray;"><em>“Uh-oh, I think I may have made the wrong kind of link before. I&#8217;ll go to the preview window to see if this is a link. It would have been nice to just edit it in the preview.”</em></span></p>
<p><span style="color: gray;"><em>“This is different, it&#8217;s got these hot-links [the table of contents]. That&#8217;s nice.&#8221;</em></span></p>
<p><span style="color: gray;"><em>“Links are so easy to screw up. I’m not sure if we&#8217;ve correctly typed the link markup. Ah, there are these buttons&#8230;”</em></span></p>
<p>Some of our tools are definitely still rough around the edges &#8211; their flaws and failures were seen in technicolor when observing people using them.  Our link dialog caused the most confusion.  6 of our 8 users initially made some errors in using it, and some received a false positive assurance when they had not actually accomplished the link behavior they were attempting.  Oops!  Our features need to err on the side of a user&#8217;s expectation rather than giving users access to the technical structure or wiki syntax, which they did not in this case.  For example, to create a new link in our prototype, users were asked to specify whether they wanted to create an &#8220;external link&#8221; (to a website) or &#8220;internal&#8221; link (to a different article) &#8211; a differentiation that exists in wiki code, but not in the eyes of a novice user.  Additionally, our toolbar buttons need to behave consistently and be grouped accordingly.  Having dialogs for links and tables, and not having one for a reference was not acceptable and led to some quite confused and persistent button pushing by our subjects.</p>
<p>Speaking of buttons, our &#8220;Bold&#8221; and &#8220;Italics&#8221; toolbar buttons use the roman character &#8220;a&#8221; &#8211; the result of our struggled effort to be accessible to an international community while attempting to take advantage of software standards.  In our effort to generalize, we became too general &#8211; even those users who correctly guessed the purpose of these buttons had to hover over or use them to confirm their assumptions.  We&#8217;re going all in &#8211; look out for our efforts to make our toolbar icons language specific soon!</p>
<p>As if we didn&#8217;t already know it &#8211; adding media or &#8220;embedding a file&#8221; was the least understood toolbar action of our study.  Most users avoided it, but when they did the sample text that it inserted provided no additional insight.</p>
<p><span style="text-decoration: underline;">Moving Forward</span></p>
<p><span style="color: gray;"><em>“I’m completely intimidated by that [template].”</em></span></p>
<p><span style="color: gray;"><em>“I’m not sure what that is. I&#8217;m going to save it and then see, because this preview is too confusing.”</em></span></p>
<p>Our study illustrated how large an effect a small change can have and brought to our attention tweaks and enhancements that need to be made to our current features.  It also showed us that we are just a slice of what is a very, very large pie.  We had many deja vu moments seeing users flounder around previewing and saving, many times adopting strange techniques and multiple windows to add a simple sentence.  The terms &#8220;code,&#8221; &#8220;computer lingo,&#8221; &#8220;html&#8221; often came up and highlighted the separation users feel from their content while editing.  The expectation for editing a wiki to be similar to editing a blog or word processing document was still prevalent.  And though our Table of Contents and built-in cheat sheet put out some small fires, when navigating an lengthy article or searching for help, we again heard <span style="color: #808080;"><em>&#8220;there sure is a lot of stuff to read&#8221;</em></span> and <span style="color: #808080;"><em>&#8220;this is where I&#8217;d give up.&#8221;</em></span></p>
<p>As we&#8217;ve mentioned <a href="http://blog.wikimedia.org/2009/04/24/usability-study-results-sneak-preview/">before</a>, we cannot tackle the full scope of issues that our study participants surface.  But I think I can speak for our team when I say we all felt a certain amount of satisfaction in the results of those problems we did address and it has only made us more eager to attack new problems and iterate on solutions we&#8217;ve proposed.  As always, we look forward to your comments, insights, and feedback!  We also appreciate your <a href="http://wikimediafoundation.org/wiki/Fundraising?sess=eceff27e3ba82c58e3e65526f95ce380">contributions</a> during our fundraiser &#8211; it&#8217;s in part <a href="http://wikimediafoundation.org/wiki/Special:ContributionHistory/en">community support</a> like this that makes the Foundation&#8217;s work possible.</p>
<p>Parul Vora + the Wikimedia Usability Initiative</p>
<p style="text-align: center;"><a href="http://wikimediafoundation.org/wiki/Donate"><img class="aligncenter" title="http://wikimediafoundation.org/w/extensions/skins/Donate/images/banners/Banner_468x60_0000_A.jpg" src="http://wikimediafoundation.org/w/extensions/skins/Donate/images/banners/Banner_468x60_0000_A.jpg" alt="" width="468" height="60" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wikimedia.org/2009/11/18/ux-usability-study-take-two/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>English Wikinews adopted the usability beta as default</title>
		<link>http://blog.wikimedia.org/2009/10/30/englsih-wikinews-adopted-the-usability-beta-as-default/</link>
		<comments>http://blog.wikimedia.org/2009/10/30/englsih-wikinews-adopted-the-usability-beta-as-default/#comments</comments>
		<pubDate>Fri, 30 Oct 2009 23:32:21 +0000</pubDate>
		<dc:creator>Naoko</dc:creator>
				<category><![CDATA[Community]]></category>
		<category><![CDATA[MediaWiki]]></category>
		<category><![CDATA[Wikinews]]></category>
		<category><![CDATA[tech]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://blog.wikimedia.org/?p=1153</guid>
		<description><![CDATA[
Earlier today, English Wikinews adopted the usability beta as a default interface.  The usability team is thrilled that en.wikinews community has reached the consensus to be the first adopter of the usability beta as default.  We will continue enhancing the interface to simplify and make it easy to navigate and edit.  Our sincere [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://en.wikinews.org/wiki/Main_Page"><img class="alignright" title="Wikenews" src="http://upload.wikimedia.org/wikipedia/commons/archive/b/bd/20050625031102!Wikinews-logo-en.png" alt="Wikinews" width="135" height="104" align="right"  /></a></p>
<p>Earlier today, <a href="http://en.wikinews.org/wiki/Main_Page">English Wikinews</a> adopted <a href="http://techblog.wikimedia.org/2009/08/try-the-usability-beta/">the usability beta</a> as a default interface.  The usability team is thrilled that en.wikinews community has reached <a href="http://en.wikinews.org/w/index.php?title=Wikinews:Water_cooler/proposals#Vector_Vote_-_Now_with_50.25_more_drama">the consensus</a> to be the first adopter of the usability beta as default.  We will continue enhancing the interface to simplify and make it easy to navigate and edit.  Our sincere appreciation goes to the entire en.wikinews community for embracing our work.  It is a great day for the usability team.  We feel blessed.  </p>
<p>Naoko Komura on behalf of the entire usability team<br />
Program Manager, Usability Initiative</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wikimedia.org/2009/10/30/englsih-wikinews-adopted-the-usability-beta-as-default/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>Usability Beta Status</title>
		<link>http://blog.wikimedia.org/2009/09/14/usability-beta-status/</link>
		<comments>http://blog.wikimedia.org/2009/09/14/usability-beta-status/#comments</comments>
		<pubDate>Mon, 14 Sep 2009 21:07:31 +0000</pubDate>
		<dc:creator>Naoko</dc:creator>
				<category><![CDATA[MediaWiki]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Wikimedia]]></category>
		<category><![CDATA[opensource]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://blog.wikimedia.org/?p=1071</guid>
		<description><![CDATA[Here&#8217;s a brief update on the status of our recently launched usability improvements.
Since the launch of the beta invitation to the first set of usability improvements on August 6th, about 173,000 people tried out the beta and about 134,000 people continue to use the beta as of September 12th.
Beta retention rate is interpreted roughly 77%. [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://en.wikipedia.org/w/index.php?title=Special:PrefStats/skin&amp;inc=168"><img class="alignright" title="English Wikipedia Beta Preference Statistics " src="http://upload.wikimedia.org/wikipedia/usability/4/43/Prefstat091209.png" alt="" width="500" height="273" align="right" /></a>Here&#8217;s a brief update on the status of our recently launched usability improvements.</p>
<p>Since the launch of the beta invitation to the first set of usability improvements on August 6th, about 173,000 people tried out the beta and about 134,000 people continue to use the beta as of September 12th.</p>
<p>Beta retention rate is interpreted roughly 77%.  These numbers are aggregation of all Wikimedia projects in all available languages.  If we look at the retention rate by project or by language, the number varies significantly.  For example, the beta retention rate of English Wikipedia is 82% and Spanish Wikipedia is 80%, while the beta struggles to retain beta trial users of the language communities such as Japanese and Korean at the retention rate of 59% and 54% respectively.</p>
<p>We are reviewing the survey feedback and trying to isolate specific issues of languages whose retention rate is below average.  If you are curious about how the beta opt-in and opt-out look like at daily or weekly basis, you can visit the preference statistics page.  Here is <a href="http://en.wikipedia.org/w/index.php?title=Special:PrefStats/skin&amp;inc=168">the example link</a> to English Wikpedia.  Just change the language prefix or project name to get to the project of your preference.</p>
<p>Naoko Komura<br />
Program Manager<br />
Wikipedia Usability Initiative</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wikimedia.org/2009/09/14/usability-beta-status/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>The abc&#8217;s of Usability!</title>
		<link>http://blog.wikimedia.org/2009/07/29/the-abcs-of-usability/</link>
		<comments>http://blog.wikimedia.org/2009/07/29/the-abcs-of-usability/#comments</comments>
		<pubDate>Wed, 29 Jul 2009 23:06:16 +0000</pubDate>
		<dc:creator>Parul</dc:creator>
				<category><![CDATA[MediaWiki]]></category>
		<category><![CDATA[Wikipedia]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://blog.wikimedia.org/?p=996</guid>
		<description><![CDATA[

Hopefully by now you&#8217;ve had a chance to try the new skin &#8216;Vector&#8216; that the Usability Team has implemented as part of our first release, also known as Acai!  If you haven&#8217;t yet, we invite you to check it out by going to Appearance &#62; Skin in your preferences and selecting &#8216;Vector&#8217;.  As you play [...]]]></description>
			<content:encoded><![CDATA[<div class="thumb center">
<p><a href="http://commons.wikimedia.org/wiki/File:UsabilityABC.jpg"><img title="http://upload.wikimedia.org/wikipedia/commons/6/6a/UsabilityABC.jpg" src="http://upload.wikimedia.org/wikipedia/commons/6/6a/UsabilityABC.jpg" alt="Basket of berries, remixed by Parul V; photos by Dinowx, Siegert, and Yuval Y (CCBYSA)" width="457" height="184" /></a></div>
<p>Hopefully by now you&#8217;ve had a chance to try the new skin &#8216;<em>Vector</em>&#8216; that the <a href="http://usability.wikimedia.org/wiki/Main_Page">Usability Team</a> has implemented as part of our first release, also known as <a href="http://usability.wikimedia.org/wiki/Releases/Acai">Acai</a>!  If you haven&#8217;t yet, we invite you to check it out by going to <strong>Appearance &gt; Skin</strong> in your preferences and selecting &#8216;Vector&#8217;.  As you play with the new skin and enhanced toolbar, the Usability Team is looking forward to our next release &#8211; codename Babaco &#8211; the next alphabetical tropical fruit in what we expect to be a delicious series.</p>
<p>We hope to continue adding <a href="http://usability.wikimedia.org/wiki/Babaco_Designs">features</a> to enhance the editing process &#8211; including but not limited to further <a href="http://usability.wikimedia.org/wiki/Babaco_Designs#Toolbar_Upgrades:_Button_Interaction">toolbar</a> enhancements; <a href="http://usability.wikimedia.org/wiki/Babaco_Designs#Toolbar_Upgrades:_Dialogs">dialogs</a> for the creation of links, tables, and references; and tools to aid in <a href="http://usability.wikimedia.org/wiki/Babaco_Designs#Table_of_Contents_.2B_Help">navigation of article content</a> during editing.  Our research, design, and development depends on feedback from users, community members, and interested parties like you.  We invite you to take a look at our work and if you have any opinions, praise, concerns, or criticism, please let us know <a href="http://usability.wikimedia.org/wiki/Talk:Babaco_Designs">here</a>.  We look forward to hearing from you!</p>
<p>Parul Vora, Wikimedia Usability Initiative</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wikimedia.org/2009/07/29/the-abcs-of-usability/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Brewing ideas for the Wikipedia usability initiative</title>
		<link>http://blog.wikimedia.org/2009/06/02/brewing-ideas-for-the-wikipedia-usability-initiative/</link>
		<comments>http://blog.wikimedia.org/2009/06/02/brewing-ideas-for-the-wikipedia-usability-initiative/#comments</comments>
		<pubDate>Tue, 02 Jun 2009 23:57:07 +0000</pubDate>
		<dc:creator>Naoko</dc:creator>
				<category><![CDATA[MediaWiki]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Wikipedia]]></category>
		<category><![CDATA[tech]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://blog.wikimedia.org/?p=825</guid>
		<description><![CDATA[The usability team has been translating the usability study into a new design and software for the last four weeks.  The current focus is to implement easy improvement to overall usage of Wikipedia with the focus of editing interface in the next three months.  The proposed skin by the usability team, Vector, will [...]]]></description>
			<content:encoded><![CDATA[<p>The usability team has been translating the usability study into a new design and software for the last four weeks.  The current focus is to implement easy improvement to overall usage of Wikipedia with the focus of editing interface in the next three months.  The proposed skin by the usability team, Vector, will have streamlined tab layout, so that users will not lose the state of reading or editing whether in articles or in discussion pages.</p>
<p>Another usability improvement we are working on is the action-grouped toolbar, which hides the overwhelming number of tool icons which are not being used by novice users, but they are available for power users in the expanded mode.  Lots of clutters will be removed from the editing interface.</p>
<p>You can see some of design mock-ups from <a href="http://usability.wikimedia.org/wiki/Designs">our project page</a>.  Some of these proposed design concepts will be staged at <a href="http://usability.wikimedia.org/wiki/Prototype">the prototype environments</a> this month and for any future improvements.  (The action-based tool bar will not be seen on prototypes till June 8.)</p>
<p>If all goes well, these new features will be available from a user preference configuration early July.  In the subsequent release in August, additional navigation aids are in the plan.  We will be sharing the product feature at <a href="http://usability.wikimedia.org/wiki/Main_Page">our project page</a> in coming weeks.  We look forward to <a href="http://usability.wikimedia.org/wiki/Talk:Prototype">your feedback</a>.</p>
<p>Naoko Komura<br />
The Wikipedia Usability Team</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wikimedia.org/2009/06/02/brewing-ideas-for-the-wikipedia-usability-initiative/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>The Wikipedia Usability Initiative is still hiring.</title>
		<link>http://blog.wikimedia.org/2009/05/12/the-wikipedia-usability-initiative-is-still-hiring/</link>
		<comments>http://blog.wikimedia.org/2009/05/12/the-wikipedia-usability-initiative-is-still-hiring/#comments</comments>
		<pubDate>Tue, 12 May 2009 23:39:57 +0000</pubDate>
		<dc:creator>Naoko</dc:creator>
				<category><![CDATA[Jobs]]></category>
		<category><![CDATA[MediaWiki]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Wikipedia]]></category>
		<category><![CDATA[tech]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://blog.wikimedia.org/?p=776</guid>
		<description><![CDATA[The Wikipedia Usability Initiative has extended the application deadline for the Software Developer position till May 30th.  We are recruiting two candidates for this position.  Both local applicants to the San Francisco Bay Area and remote applicants are encouraged to apply.  Please help spread the word. 
http://wikimediafoundation.org/wiki/Job_openings/Software_Developer_(project)
Naoko Komura
Wikipedia Usability Initiative 
]]></description>
			<content:encoded><![CDATA[<p>The Wikipedia Usability Initiative has extended the application deadline for the Software Developer position till May 30th.  We are recruiting two candidates for this position.  Both local applicants to the San Francisco Bay Area and remote applicants are encouraged to apply.  Please help spread the word. </p>
<p><a href="http://wikimediafoundation.org/wiki/Job_openings/Software_Developer_(project)">http://wikimediafoundation.org/wiki/Job_openings/Software_Developer_(project)</a></p>
<p>Naoko Komura<br />
Wikipedia Usability Initiative </p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wikimedia.org/2009/05/12/the-wikipedia-usability-initiative-is-still-hiring/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
