<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Web Design&gt;Intranets&gt;Usability</title>	<link>http://tc.eserver.org/dir/Articles/Web-Design/Intranets/Usability</link>
	<description>A listing of the most recently indexed works about Articles and Web Design and Intranets and Usability in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Articles&gt;Web Design&gt;Intranets&gt;Usability</title>
		<link>http://tc.eserver.org/dir/Articles/Web-Design/Intranets/Usability</link>
	</image>
	<item>
		<title>Ten Best Intranets of 2009</title>
		<link>http://tc.eserver.org/33596.html</link>
		<guid>http://tc.eserver.org/33596.html</guid>
		<description>Intranets are getting more strategic, with increased collaboration support. Team size is growing by 12% per year, and platforms are becoming integrated. Improving usability increased use by 106% on average.</description>
	</item>
	<item>
		<title>Intranets: Strategy First, Usability Second</title>
		<link>http://tc.eserver.org/33076.html</link>
		<guid>http://tc.eserver.org/33076.html</guid>
		<description>More and more intranet teams are buying into the need for usability. However, usability is not a strategy, and without a clear strategy, usability can become a pointless, wasteful and counter-productive exercise.</description>
	</item>
	<item>
		<title>Structuring Job Related Information on the Intranet: An Experimental Comparison of Task vs. an Organization-based Approach</title>
		<link>http://tc.eserver.org/29156.html</link>
		<guid>http://tc.eserver.org/29156.html</guid>
		<description>In this article, we present a usability experiment in which participants were asked to make intensive use of information on an intranet in order to execute job-related tasks. Participants had to work with one of two versions of an intranet: one with an organization-based hyperlink structure, and one with a task-based hyperlink structure. Efficiency and effectiveness were measured in terms of execution time and task accuracy, respectively. After the task execution, participants were asked to evaluate the task as well as the intranet. The results show that participants perform more efficiently with the organization-based structure, which is probably due to their familiarity with this structure. A post hoc analysis revealed, however, a learning effect in the task condition, which suggests that once users are acquainted with it, a task structure is at least as efficient.</description>
	</item>
	<item>
		<title>Developing Intranets Which People Use: Making Progress When Everyone has an Opinion</title>
		<link>http://tc.eserver.org/24079.html</link>
		<guid>http://tc.eserver.org/24079.html</guid>
		<description>The goal of an intranet site is to improve knowledge sharing and productivity. In a large company, it can be difficult to achieve consensus on how to make this happen. Knowledge management experts, information systems project managers, graphic designers, marketing leaders, HTML developers and usability engineers are used to fighting for their places, convinced that they know best. In truth, the intranet is not yet mature, and there are no definite answers. This chapter describes experiences with the intranet sites of two Fortune 500 companies. In both cases, the usability engineer was a consultant from outside the company, in one case part of a team of consultants and in the other working more closely with company employees. Both intranet projects were riddled with mishaps, bad decisions, personality conflicts, and compromises. Still, the usability engineers were able to improve the sites by becoming members of the project teams, and by tirelessly incorporating usability in everything they did.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Web-Design/Intranets/Usability.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>