<?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>Web Development, Usability &#38; SEO &#187; Usability</title>
	<atom:link href="http://www.temi.ro/tag/usability/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.temi.ro</link>
	<description>Temi Odurinde's user centered website development Tips</description>
	<lastBuildDate>Tue, 23 Feb 2010 17:36:35 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Usability and Your Website &#8211; Basic Implementation of Usability Testing</title>
		<link>http://www.temi.ro/usability-and-your-website-part-iv/</link>
		<comments>http://www.temi.ro/usability-and-your-website-part-iv/#comments</comments>
		<pubDate>Sun, 11 Jan 2009 19:46:22 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[SEO]]></category>
		<category><![CDATA[basic testing]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[user centred design]]></category>

		<guid isPermaLink="false">http://www.temi.ro/?p=26</guid>
		<description><![CDATA[<div style="float: right; width: 42px; padding-right: 10px; margin: 0 0 0 10px;"><script type="text/javascript">
<!--
digg_url = 'http://www.temi.ro/usability-and-your-website-part-iv/';
digg_bgcolor = '';
digg_skin = '';
digg_window = '';
digg_title = 'Usability and Your Website &#8211; Basic Implementation of Usability Testing';
digg_bodytext = '';
digg_media = '';
digg_topic = '';
//-->
</script>
<script src="http://digg.com/tools/diggthis.js" type="text/javascript"></script>
</div>
Basic Implementation of Usability  Testing
You have done all the hard  parts, planning, analyzing, and designing. Now comes the implementation  of usability testing. Throughout the previous analyses, there were most  likely several negative findings. So many that it may be difficult to  implement the changes to fix them all. In fact, [...]]]></description>
			<content:encoded><![CDATA[<div style="float: right; width: 42px; padding-right: 10px; margin: 0 0 0 10px;"><script type="text/javascript">
<!--
digg_url = 'http://www.temi.ro/usability-and-your-website-part-iv/';
digg_bgcolor = '';
digg_skin = '';
digg_window = '';
digg_title = 'Usability and Your Website &#8211; Basic Implementation of Usability Testing';
digg_bodytext = '';
digg_media = '';
digg_topic = '';
//-->
</script>
<script src="http://digg.com/tools/diggthis.js" type="text/javascript"></script>
</div>
<h1><span style="font-size: large; font-family: Arial;"><strong>Basic Implementation of Usability  Testing</strong></span></h1>
<p><span style="font-size: large; font-family: Arial;"><strong></strong></span><span style="font-size: small; font-family: Times New Roman;">You have done all the hard  parts, planning, analyzing, and designing. Now comes the implementation  of usability testing. Throughout the previous analyses, there were most  likely several negative findings. So many that it may be difficult to  implement the changes to fix them all. In fact, you may not want to  regardless of budget or time issues.</span></p>
<p><span style="font-size: small; font-family: Times New Roman;"><strong>Develop Priorities</strong></span></p>
<p><span style="font-size: small; font-family: Times New Roman;">The next step is to create  a list of priorities on what needs fixing first. Look for simple easy  fixes, or try finding the ones that can affect most of your users. Fixing  a poor Terms of Agreement page hardly compares to poorly done new user  form or confusing navigation bar. A common side effect of fixing the  larger issues first is that lesser issues become resolved on there own.</span></p>
<p><span style="font-size: small; font-family: Times New Roman;">Another reason you might want  to hold off on making all the fixes at once is that it may be difficult  to determine what new changes made, make the greater impact. It’s  easy to see improvements if all you did was move a menu to the left  instead of the right versus moving the menu, redoing the menu’s organization,  and changing the header all at the same time. Take little bites. It  could be that moving to the left did work better for your users, but  now using another feature has become more complex. Maybe the fix needed  to be not moving the menu, but reorganizing it.</span></p>
<p><span style="font-size: small; font-family: Times New Roman;"><strong>Test Again</strong></span></p>
<p><span style="font-size: small; font-family: Times New Roman;">Now comes the fun and ongoing  part. Test and test again. A site is never really ever done. Even the  big guns like eBay, Microsoft, or Google are constantly testing. I have  been lucky enough to participate as a test subject for Google’s Adwords  and AdSense. It’s the advantages to living nearby that I got to participate  at Google I guess. Don’t forget, testing is one of the most important  steps to building a website, and if you don’t do it don’t expect  much. I’m guessing not everyone will like it. </span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.temi.ro/usability-and-your-website-part-iv/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Usability and Your Website &#8211; User Centered Design</title>
		<link>http://www.temi.ro/usability-and-your-website-part-ii-user-centered-design/</link>
		<comments>http://www.temi.ro/usability-and-your-website-part-ii-user-centered-design/#comments</comments>
		<pubDate>Thu, 25 Dec 2008 18:14:29 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Usability]]></category>
		<category><![CDATA[ucd]]></category>
		<category><![CDATA[user centred design]]></category>

		<guid isPermaLink="false">http://www.temi.ro/?p=22</guid>
		<description><![CDATA[<div style="float: right; width: 42px; padding-right: 10px; margin: 0 0 0 10px;"><script type="text/javascript">
<!--
digg_url = 'http://www.temi.ro/usability-and-your-website-part-ii-user-centered-design/';
digg_bgcolor = '';
digg_skin = '';
digg_window = '';
digg_title = 'Usability and Your Website &#8211; User Centered Design';
digg_bodytext = '';
digg_media = '';
digg_topic = '';
//-->
</script>
<script src="http://digg.com/tools/diggthis.js" type="text/javascript"></script>
</div>
UCD is short for User-centered Design, and is an important part of developing a website. Quickly defined, UCD is designing a website that meets users needs. Are you building a website for you to use, or your users? When building a website, you should design with your target audience in mind.
It’s Not a Waste of [...]]]></description>
			<content:encoded><![CDATA[<div style="float: right; width: 42px; padding-right: 10px; margin: 0 0 0 10px;"><script type="text/javascript">
<!--
digg_url = 'http://www.temi.ro/usability-and-your-website-part-ii-user-centered-design/';
digg_bgcolor = '';
digg_skin = '';
digg_window = '';
digg_title = 'Usability and Your Website &#8211; User Centered Design';
digg_bodytext = '';
digg_media = '';
digg_topic = '';
//-->
</script>
<script src="http://digg.com/tools/diggthis.js" type="text/javascript"></script>
</div>
<p>UCD is short for User-centered Design, and is an important part of developing a website. Quickly defined, UCD is designing a website that meets users needs. Are you building a website for you to use, or your users? When building a website, you should design with your target audience in mind.</p>
<p>It’s Not a Waste of Time and Money</p>
<p>As a business owner myself, I’ve learned to not spend money on unnecessary items, but I have also learned that sometimes you need to have a bigger budget before implementing something new. “Can’t I just build a website without doing all this testing?” Yes, you can. Will your site be effective? It might. Will you need to rebuild your site when you realize that the current version is the problem? Most likely. Will you rebuild your site doing it the right way the second time? You better, or you are just setting yourself up to fail again.</p>
<p>It’s not a waste of time or money if you do it the right way the first time. It’s the best way you can spend your time and money. Before you jump into building a website though you need to clearly define its purpose, similar to setting up a business plan. In building a site, while thinking UCD, here is a list of important things to consider.</p>
<p>Important Factors:<br />
·    Sites primary objective<br />
·    Who is the target audience and their web user skills<br />
·    Potential tasks and goals of the user<br />
·    How would the users expect the site to work<br />
·    How easy will your site be for users</p>
<p>All of these items should be considered, plus any other additional items that you can think of when developing the site concept. The key here is “Who is this user?” and “How will they use my site?” Designing the UCD way is understanding your audience, working/testing with audience, and creating the best platform for your audience to succeed.</p>
<p>Where Do I Start?</p>
<p>Assuming you have clearly defined the important factors for your new site, knowing where to start on the design process could be the hardest part. Usability.gov has a great little flow char on just that, Visual Overview. Not all steps are required, but it does offer some great insight on what should be happening when developing a site while thinking UCD.</p>
<p>It’s all about designing with users in mind, then testing with users, and then finalizing with a site that you know users can benefit from. It’s what building websites is all about.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.temi.ro/usability-and-your-website-part-ii-user-centered-design/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
