<?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>INFLUX&#187; website usability</title>
	<atom:link href="http://influx.us/category/website-usability/feed" rel="self" type="application/rss+xml" />
	<link>http://influx.us</link>
	<description>library user experience</description>
	<lastBuildDate>Tue, 20 Apr 2010 06:00:26 +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>Improve Your Website: #02 Navigation &amp; Wayfinding</title>
		<link>http://influx.us/1151</link>
		<comments>http://influx.us/1151#comments</comments>
		<pubDate>Mon, 25 Jan 2010 12:00:15 +0000</pubDate>
		<dc:creator>Aaron &#38; Amanda</dc:creator>
				<category><![CDATA[interfaces]]></category>
		<category><![CDATA[user experience]]></category>
		<category><![CDATA[website usability]]></category>

		<guid isPermaLink="false">http://influx.us/?p=1151</guid>
		<description><![CDATA[The second in a series of posts about improving your library website.]]></description>
			<content:encoded><![CDATA[<p>Navigation is a Big Deal. You might be thinking that it&#8217;s such a big deal that short of a complete arcitectural overhaul of your site, there isn&#8217;t a whole lot of &#8220;tinkering&#8221; you can do to make any real difference. Well, hold on to your hats, because that&#8217;s exactly what this post is about: quick, easy changes you can make to your library website to improve navigation and wayfinding.</p>
<h3>Consistent Labeling</h3>
<p>There is nothing more disorienting than links labels that don&#8217;t match page titles. Imagine clicking a link called &#8220;Find Books&#8221; and ending up at a page called &#8220;Search The Library Catalogue&#8221;. After a while, your users might start associating their quest to find books with searching the catalogue, but why force them to make that cognitive leap when you can easily synchronize your link labels with your page titles? If the link says &#8220;Find Books&#8221;, that&#8217;s exactly what they should see (preferably in unapologetically large text) on the resulting page.</p>
<p>So, spend some time clicking around your site. Make sure the link labels you click on match the page titles that come up. If they don&#8217;t, change them.</p>
<h3>Search</h3>
<p>There is a usability theory out there that says that users only search a site when they can&#8217;t figure out how the site navigation works or when they lose the &#8220;scent&#8221; of what they&#8217;re looking for. While that might be true, in the strictest human-computer interaction sense, there is a whole subset of users who would rather just search your site to start with instead of clicking on navigation options. Blame Google.</p>
<p>If your library website doesn&#8217;t have a site search box, it should. Devote some template space to it so that users get used to seeing that search box in the same place on every page. Make the searchers happy and provide a simple wayfinding option at the same time.</p>
<h3>Breadcrumbs</h3>
<p>Think of breadcrumbs as the GPS of your website, the &#8220;You Are Here&#8221; marker that instantly orients users to where they are in your site&#8217;s architecture. Breadcrumbs are a perfect wayfinding tool because they provide a reminder to users about what section of the site they are in and how they got there.</p>
<p>If you don&#8217;t already have breadcrumbs on your site, there is no quick &amp; dirty way to implement them unfortunately. But if you are using breadcrumbs, do a quick audit to make sure they are meaningful and provide some useful orientation to your users. Remember, your home page is not always the starting point for a lot of users (thank you, search engines), so make sure that every page has breadcrumbs that will also orient those who land on your site as a result of a search engine hit.</p>
<h3>Next Up</h3>
<p>#3: Online Library Card Application</p>
]]></content:encoded>
			<wfw:commentRss>http://influx.us/1151/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Improve Your Website: #01 Wrangling Content</title>
		<link>http://influx.us/1000</link>
		<comments>http://influx.us/1000#comments</comments>
		<pubDate>Mon, 14 Dec 2009 13:21:50 +0000</pubDate>
		<dc:creator>Aaron &#38; Amanda</dc:creator>
				<category><![CDATA[website usability]]></category>

		<guid isPermaLink="false">http://influx.us/?p=1000</guid>
		<description><![CDATA[The first in a series of posts about improving your library website.]]></description>
			<content:encoded><![CDATA[<h3>Summary</h3>
<p>You can make your website more effective by making it smaller, using less words and by being friendly.</p>
<h3>Article</h3>
<p>Think of the content on your site in two ways:</p>
<ul>
<li>the broad picture of what is on your site</li>
<li>the narrower scope of how this stuff is presented</li>
</ul>
<p>Both are important and both need continual attention.</p>
<p><strong>Less is Less (&amp; That&#8217;s Good)</strong><br />
We bet that your library&#8217;s website has too many pages.  You might think that there&#8217;s no harm in keeping pages around just in case someone needs the info there.  You&#8217;re probably wrong.  More stuff on your site means that:</p>
<ul>
<li>it takes more time to make sure it is still relevant and up to date.</li>
<li>your patrons are forced to sift through junk to find what they really need.</li>
<li>your navigation has to be increasingly complicated.</li>
</ul>
<p>It is better to have a website consisting of 25 effective pages that are well written and answer people&#8217;s questions than it is to have 50 sloppy pages that aren&#8217;t as useful.</p>
<p>You should look at every page on your website.  You might cry a little bit during the process but if you do, let it be a lesson.</p>
<p><strong>Making the Cut</strong><br />
Caution.  This is dangerous stuff.  People can get territorial about content related to their part of the library.  Even if they haven&#8217;t updated it in 10 months.  With any luck you&#8217;re in a situation where you can prune away and deselect pages just like you would a print collection.  But you might not be so lucky.</p>
<p>Hopefully you have web analytics to see what people are using and what people aren&#8217;t using.  If not, install <a href="http://www.google.com/analytics/">Google Analytics</a> now.  It is free and easy.  Wait a few months for an accurate report and you&#8217;ll have some data to back up your pruning shears.  Any pages that people haven&#8217;t looked at in a few months need to go.  It is really quite liberating!</p>
<p>Pages that are getting hit the most should be priorities for the next step of improving your content.</p>
<p>There are other big picture content issues that are just as important.  More questions you can ask yourself or your web team are:</p>
<ul>
<li>Who has the final say about content on your site?</li>
<li>What process is creating the stuff that goes on your site?</li>
</ul>
<p><strong>Write for the web</strong><br />
People using your site want to accomplish something or have a question answered.  Your content is supposed to make these things happen.  In other words, your content is the reason people visit your site.</p>
<p>In general, library websites have too many words.  If you only do one thing with the content on your library website, do this:</p>
<p><span style="font-size:24px;"><strong>Remove as many words as possible.</strong></span></p>
<p>Just like superfluous pages get in the way of people finding what they want, so do superfluous words.  The information on your site should be grab and go.  Provide an apple tree that patrons can pick from rather than forcing them to sit through a 7 course meal.  For a visual example, see our post <a href="http://influx.us/948">Making Content Shine</a>.</p>
<p><strong>Make it Scannable</strong><br />
Since you got rid of a bunch of useless pages in the previous step you&#8217;ll have an easier time going through every page again.  This time, though, make your pages scannable by providing plenty of subheadings above relatively short paragraphs.  We&#8217;re skeptical of paragraphs more than 4 sentences long.  If you&#8217;re unconvinced of the utility of this, do a <a href="http://www.walkingpaper.org/2005">five second test</a> on a before and after page.</p>
<p>Also, review every page with your users&#8217; needs in mind. Ask yourself why they would come to each page. Those reasons are their <strong>trigger words</strong>. Use them. Bold them.</p>
<p><strong>Be Nice</strong><br />
Does the tone of our content reflect how friendly you are face to face?  If so, either your content is conversational and welcoming or you need to be more friendly face to face.  As you&#8217;re rewriting content you should be writing as if you&#8217;re answering questions asked by a really good friend.</p>
<p><strong>Additional Resources</strong><br />
The first step in today&#8217;s post is just the tip of a content strategy iceberg.  Read Kristina Halvorson&#8217;s <a href="http://www.amazon.com/Content-Strategy-Web-Kristina-Halvorson/dp/0321620062">Content Strategy for the Web</a> to learn more about big picture thinking about what is on your website.</p>
<p>For a comprehensive look at writing for the web, check out <a href="http://www.amazon.com/Letting-Go-Words-Interactive-Technologies/dp/0123694868/ref=sr_1_1?ie=UTF8&amp;s=books&amp;qid=1260489875&amp;sr=1-1">Letting Go of the Words</a> by Ginny Reddish.  It is super good.</p>
<h3>Next up</h3>
<p>#02 Navigation &amp; Wayfinding</p>
]]></content:encoded>
			<wfw:commentRss>http://influx.us/1000/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>UX Link Roundup #04</title>
		<link>http://influx.us/1045</link>
		<comments>http://influx.us/1045#comments</comments>
		<pubDate>Thu, 19 Nov 2009 06:00:17 +0000</pubDate>
		<dc:creator>Aaron</dc:creator>
				<category><![CDATA[ux link roundup]]></category>
		<category><![CDATA[website usability]]></category>
		<category><![CDATA[budget]]></category>
		<category><![CDATA[hostage]]></category>
		<category><![CDATA[library initiative]]></category>
		<category><![CDATA[michael beriut]]></category>

		<guid isPermaLink="false">http://influx.us/?p=1045</guid>
		<description><![CDATA[A collection of UX links that will help and/or entertain you.]]></description>
			<content:encoded><![CDATA[<p><a href="http://new.uxmatters.com/mt/archives/2009/11/usability-testing-on-a-budget.php">Usability Testing on a Budget</a><br />
A solid overview of how to fit testing into your situation.</p>
<p><a href="http://www.boxesandarrows.com/view/what-design?utm_source=feedburner&#038;utm_medium=feed&#038;utm_campaign=Feed%3A+BoxesAndArrows_Stories+%28Boxes+and+Arrows%29">What design researchers can learn from hostage negotiators</a><br />
&#8220;In essence, both parties are attempting to establish a relationship, both are trying to keep the communication flowing, and most importantly, both are trying to extract valuable data.&#8221;</p>
<p><a href="http://www.pentagram.com/en/new/2009/03/murals-for-the-library-initiat.php">Murals for the Library Initiative</a></p>
<p>And check out the identity for the Library Initiative.</p>
<p><a href="http://influx.us/wordpress/wp-content/uploads/2009/11/Library_Logo.jpg" rel="shadowbox[post-1045];player=img;"><img src="http://influx.us/wordpress/wp-content/uploads/2009/11/Library_Logo.jpg" alt="Library_Logo" title="Library_Logo" width="450" height="121" class="aligncenter size-full wp-image-1048" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://influx.us/1045/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Typekit Launches for All</title>
		<link>http://influx.us/1002</link>
		<comments>http://influx.us/1002#comments</comments>
		<pubDate>Thu, 12 Nov 2009 19:16:43 +0000</pubDate>
		<dc:creator>Aaron</dc:creator>
				<category><![CDATA[website usability]]></category>
		<category><![CDATA[fonts]]></category>
		<category><![CDATA[typekit]]></category>

		<guid isPermaLink="false">http://influx.us/?p=1002</guid>
		<description><![CDATA[Typekit makes using nice fonts easy, and legal.  ]]></description>
			<content:encoded><![CDATA[<div class="test">Attention font nerds.</div>
<p><a href="http://typekit.com"> Typekit</a> has gone from invite only to open registration.  </p>
<p>What is Typekit?  Think of it as YouTube for fonts.  With it you can consistently display non-standard fonts on websites.  Previous solutions haven&#8217;t been as easy to use, nor have they been as respectful of type foundries&#8217; rights.  Despite a (currently) somewhat limited amount of fonts from which to choose, Typekit is win-win.   </p>
<p>Take a look at &#8220;Attention font nerds&#8221; above.  It isn&#8217;t an image.  You can copy the characters.  They&#8217;ll be indexed by search engines and be read by screen readers.           </p>
<h3>A word of caution</h3>
<p>Typekit might let us express ourselves more effectively on the web but it could also lead to some ransom note looking pages.  Please be responsible with Typekit.  When in doubt, limit your font use to one serif and one sans-serif per page.  Use size, color and weight for emphasis.  </p>
<div class="test">And never stretch type!</div>
]]></content:encoded>
			<wfw:commentRss>http://influx.us/1002/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>INFLUX&#8217;s Workshop at IL 2009</title>
		<link>http://influx.us/981</link>
		<comments>http://influx.us/981#comments</comments>
		<pubDate>Mon, 02 Nov 2009 03:23:52 +0000</pubDate>
		<dc:creator>Aaron &#38; Amanda</dc:creator>
				<category><![CDATA[website usability]]></category>
		<category><![CDATA[il2009]]></category>
		<category><![CDATA[workshop]]></category>

		<guid isPermaLink="false">http://influx.us/?p=981</guid>
		<description><![CDATA[Slides from our workshop about website usability and design.]]></description>
			<content:encoded><![CDATA[<p>Team INFLUX gave a workshop at Internet Librarian 2009.  Here are the slides which may or may not help you without our captivating narration.  </p>
<p>Question about the presentation?  <a href="http://influx.us/contact" class="smcf-link">Just ask</a>.</p>
<p><object style="margin:0px" width="425" height="355"><param name="movie" value="http://static.slidesharecdn.com/swf/ssplayer2.swf?doc=il09workshop-091030174522-phpapp01&#038;rel=0&#038;stripped_title=website-usability-2387280" /><param name="allowFullScreen" value="true"/><param name="allowScriptAccess" value="always"/><embed src="http://static.slidesharecdn.com/swf/ssplayer2.swf?doc=il09workshop-091030174522-phpapp01&#038;rel=0&#038;stripped_title=website-usability-2387280" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="425" height="355"></embed></object></p>
]]></content:encoded>
			<wfw:commentRss>http://influx.us/981/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
