<?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>The Web Usability Blog&#187; user research</title>
	<atom:link href="http://webusability-blog.com/tags/user-research/feed/" rel="self" type="application/rss+xml" />
	<link>http://webusability-blog.com</link>
	<description>Tips, insights and meandering thoughts about usability and information architecture</description>
	<lastBuildDate>Sun, 20 Feb 2011 16:47:59 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Analyse your site search to increase ROI</title>
		<link>http://webusability-blog.com/analyse-your-site-search-to-increase-roi/</link>
		<comments>http://webusability-blog.com/analyse-your-site-search-to-increase-roi/#comments</comments>
		<pubDate>Thu, 29 Jul 2010 09:15:01 +0000</pubDate>
		<dc:creator>Els Aerts</dc:creator>
				<category><![CDATA[Usability]]></category>
		<category><![CDATA[search]]></category>
		<category><![CDATA[user research]]></category>

		<guid isPermaLink="false">http://webusability-blog.com/?p=1055</guid>
		<description><![CDATA[Finding out what people use your search feature for, helps you to know what your visitors really want. Once you know that, you can adjust your site accordingly and turn that knowledge into profit. Read our tips. ]]></description>
			<content:encoded><![CDATA[<h1>Why is it important to analyse your own site search?</h1>
<p>Knowing what people search for on your site is very, very interesting. </p>
<p>After all, these people are already on your website. And they&#8217;re probably using your search feature because they can&#8217;t immediately find what they&#8217;re looking for. At least, that&#8217;s what we usually notice during user tests. </p>
<h3>What do you have to do?</h3>
<ol>
<li><strong>Make sure you can analyse the search queries on your website<br />
</strong>Earlier, we talked about <a href="http://webusability-blog.com/analyse-your-own-site-search-with-google-analytics/">how to hook up your own site search to Google Analytics</a>.<br />
Of course there are other tools out there, but they&#8217;re often expensive and quite frankly not as good.
 </li>
<li><strong>Analyse the list of most frequently used search words a couple of times per year</strong><br />
Take into account spelling and wording variations and group these together. People looking for a &#8216;gun license&#8217;, &#8216;handgun license&#8217; and &#8216;gun permit&#8217; are all looking for the same thing. The filters in Google Analytics come in quite handy here. </li>
</ol>
<h3>Typical discoveries when analysing a search feature</h3>
<ul>
<li>People look for things that appear to be hard to find through the navigation structure</li>
<li>They look for things that aren&#8217;t on your website</li>
<li>They type in old product names and even your competitors&#8217; product names</li>
<li>They don&#8217;t use the same words you do</li>
<li>People can&#8217;t spell very well&#8230; at all<span id="more-1055"></span></li>
</ul>
<h3>How can you turn that knowledge into a profit?</h3>
<ul>
<li><strong>Improve the structure of your website and your overview pages<br />
</strong>Bring the top tasks to the fore in your structure or draw attention to them by giving them a prominent place on the homepage and overview pages (also called landing pages, index pages or category pages).<br />
Rewrite your content where necessary. Make sure you create pages that are easily scannable.<br />
That way you improve your <a href="http://webusability-blog.com/information-architecture-the-basics/">information architecture</a> and overall <a href="http://agconsult.be/en/web-usability.asp">website usability</a>.
 </li>
<p></p>
<li><strong>Expand your content<br />
</strong>Don&#8217;t get me wrong. I&#8217;m not saying you should start churning out random content. Far from it. But, after you&#8217;ve deleted all the content people aren&#8217;t interested in (and there will be loads of it, trust me), you should think about creating content people áre looking for but that you&#8217;re not offering yet.
 </li>
<p></p>
<li><strong>Connect discontinued products to similar new products</strong><br />
Don&#8217;t disappoint people who type in names of discontinued products or old product names. Tell them which current products correspond to those older products they already know and apparently still want.<br />
Do the same if people type in your competitors&#8217; product names or product codes. People who do that are most likely not looking for that exact product but just something similar.
 </li>
<p></p>
<li><strong>Use the same words as your users or make your search feature smarter</strong><br />
If your visitors don&#8217;t use the same words your website does, you&#8217;re the one who needs to change. Or at least expand your vocabulary. You can also make your search feature smarter by hooking it up to a thesaurus with synonyms.
 </li>
<p></p>
<li><strong>Take common spelling errors into account</strong><br />
Depending on your search software (and your budget) you can automatically correct spelling errors or suggest alternatives.<br />
If you can&#8217;t afford to do that, and it turns out 1 out of 4 people use the same miss-spelling for a particular word, put that spelling error in the meta-data of the most relevant page, or use the wrong spelling on the page somewhere.</li>
</ul>
<h3>Examples</h3>
<ul>
<li><strong>Gun permit on government site</strong><br />
On a government site, we noticed that &#8216;gun permit&#8217; (and all its variants) was continually in the top 5 searches. Because guns aren&#8217;t exactly a popular topic, it wasn&#8217;t deemed very important and was put on the 3rd level of the structure somewhere. But it&#8217;s apparently one of the site&#8217;s top tasks.</p>
</li>
<p></p>
<li><strong>E-commerce site with unclear delivery information</strong><br />
Almost the entire top 5 searches on this e-commerce site consisted of things like delivery options, shipping costs, payment methods etc. A clear indication these things needed to be clearer and not just tucked away under a link &#8216;Terms of sale&#8217;.
 </li>
<p></p>
<li><strong>Old product names and competitors&#8217; product codes at a cable manufacturer&#8217;s site</strong><br />
On the site of a leading cable manufacturer we noticed large volumes of searches on product codes and product names. Makes sense, right. But when we probed a little deeper, we noticed that a lot of the searches weren&#8217;t producing any results. Delving deeper still, it appeared that the product names were old names the cable cmpany didn&#8217;t use anymore but apparently the customers still did.<br />
User research taught us those people weren&#8217;t looking for support for the old products, they were simply looking for a replacement. They wanted to re-order the product.<br />
The solution: tell customers the old product name or code doesn&#8217;t exist anymore and show them the new products with similar characteristics.<br />
The result: an increase in sales.
 </li>
</ul>
<h3>You might also like:</h3>
<ul>
<li><a href="http://webusability-blog.com/analyse-your-own-site-search-with-google-analytics/">How to hook up your own site search to Google Analytics</a></li>
<li><a href="http://webusability-blog.com/navigation-versus-search/">Navigation versus search</a></li>
<li><a href="http://webusability-blog.com/search-results-layout-tips/">Search results: layout tips</a></li>
<li><a href="http://webusability-blog.com/search-type-in-field-button/">Search = type-in field+ button</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://webusability-blog.com/analyse-your-site-search-to-increase-roi/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Experts don&#8217;t know everything, not even usability experts</title>
		<link>http://webusability-blog.com/experts-dont-know-everythin/</link>
		<comments>http://webusability-blog.com/experts-dont-know-everythin/#comments</comments>
		<pubDate>Fri, 19 Feb 2010 08:24:34 +0000</pubDate>
		<dc:creator>Karl Gilis</dc:creator>
				<category><![CDATA[Information architecture]]></category>
		<category><![CDATA[Methodology]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[user research]]></category>

		<guid isPermaLink="false">http://webusability-blog.com/?p=877</guid>
		<description><![CDATA[Web builders or information architects who claim they don't need to involve real users because 'they know what's best' are pretty pretentious. ]]></description>
			<content:encoded><![CDATA[<h1><strong>Do experts know everything?</strong></h1>
<p>10 years ago I thought so. More specifically: I thought <strong>I</strong> knew everything.</p>
<p>Surely my usability expertise, my deep knowledge of information architecture would be enough to find and solve all the usability issues on every possible website?</p>
<h1><strong>Without research you can never truly know your users</strong></h1>
<p>10 years of <a href="http://www.agconsult.be/en/usability/users.asp">user testing</a> have made me a bit more modest. Okay, a lot more modest. <a href="http://www.agconsult.be/en/usability/expert.asp">Expert knowledge</a> alone is not enough.</p>
<p>Does that mean I&#8217;m not a good usability expert? Hell no. I think I know more about <a href="http://www.agconsult.be/en/web-usability.asp">web usability</a> and <a href="http://www.agconsult.be/en/usability/informationstructure.asp">information architecture</a> than anyone else in Belgium. (Non-Belgian readers, please suppress that giggle.) Actually, that&#8217;s a lie: <a href="http://webusability-blog.com/about/els-aerts/">Els</a> knows more about it than I do. See, I told you I was modest.</p>
<p>And still, despite all of our combined expertise, we often say things like ‘That depends’, ‘We&#8217;ll have to ask your customers that&#8217; or &#8216;We&#8217;ll have to test that&#8217;.<span id="more-877"></span></p>
<h1><strong>Usability rules are not stone tablets</strong></h1>
<p>A lot of web designers and programmers resent those answers. They like it when everything is fixed. That makes it nice and easy.</p>
<p>Admittedly, Jakob Nielsen&#8217;s rules, the interface pattern libraries you see all around and even the usability tips we write on this blog, sometimes suggest it&#8217;s all black and white, clear-cut.</p>
<p>Wake up call: it isn&#8217;t. Usability isn&#8217;t that thing you read about in books. To fully understand usability, you have to see real users in action.</p>
<p>There are lots of rules and often those rules are right. But sometimes they&#8217;re also flexible, open for interpretation. Quite often the things that we as experts thought might cause problems end up not troubling users at all, while the things we thought wouldn&#8217;t be too much of a problem cause half of the test users to trip up.</p>
<p>Is that because we&#8217;re stupid? Because we&#8217;re not really experts after all?</p>
<p>I don&#8217;t think so. And our <a href="http://www.agconsult.be/en/references/">customers</a>, who gave us a client satisfaction score of 100% in our latest audit in 2009, obviously don&#8217;t think so either.</p>
<h1><strong>Content and structure are determined by your visitors</strong></h1>
<p>When it comes to your site&#8217;s information structure and your content, the rules don&#8217;t really help you much. They get more than a little vague.</p>
<p>A few examples:</p>
<ul>
<li>Use words that your visitors understand for your menu labels</li>
<li>Put the 3 to 5 things that matter most to your visitors above the page-fold on a detail page</li>
<li>Start every page and every paragraph with the most important information you&#8217;ve got</li>
</ul>
<p>While these rules are all true, they&#8217;re also very theoretical. Which words do your visitors understand? What exactly are those 3 to 5 most important things according to your visitors?</p>
<h1><strong>Pretentious</strong></h1>
<p>In all modesty, we think web builders or information architects who claim they don&#8217;t need to involve real users because &#8216;they know what&#8217;s best&#8217; are pretty pretentious.</p>
<p>Sure, those web builders&#8217; and information architects&#8217; common sense will probably keep their customers safe from all too big disasters. But is that really good enough?</p>
<h1><strong>User research gets you facts </strong></h1>
<p>Are you really so all-knowing that you know what people exactly want to know about a hotel, an airconditioing unit and an oil-free compressor? And a forklift, a handbag and a car loan?</p>
<p>Really? Wow, you must be making around 10.000 euro/hour. Congratulations!</p>
<p>In all fairness, nobody knows those things. The only way to find out what your visitors really want is by doing <a href="http://www.agconsult.be/en/usability/user-research.asp">user research</a>. That doesn&#8217;t have to be ridiculously expensive. You can do some of it yourself. A good online survey and interviews with potential or existing customers will already point you in the right direction.<br />
<a name="feiten"></a></p>
<h1><strong>Facts trump opinions</strong></h1>
<p>One of the biggest advantages of user research is that it gets you facts. The case for the information structure you present to your client is a whole lot stronger if you can base your decisions on facts rather than just your own opninion. Data from logfile analysis, survey results, user test videos &#8211; those are things that make compelling arguments, not your opinion.</p>
<p>Gathering facts is the main reason why we push clients to include user research in their project. Agreed, it costs a bit more when you&#8217;re doing it, but it sure saves time on meetings full of endless discussions based on nothing more than opinions.</p>
<h3>Related articles</h3>
<ul>
<li><a href="http://webusability-blog.com/webdesign-process-is-the-customer-king/">Webdesign process: is the customer king?</a></li>
<li><a href="http://webusability-blog.com/information-architecture-the-basics/">Information architecture: the basics</a></li>
</ul>
<h1>What do you think?</h1>
<p>Are we right or are we right? Feel free to disagree.</p>
]]></content:encoded>
			<wfw:commentRss>http://webusability-blog.com/experts-dont-know-everythin/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Webdesign process: is the customer king?</title>
		<link>http://webusability-blog.com/webdesign-process-is-the-customer-king/</link>
		<comments>http://webusability-blog.com/webdesign-process-is-the-customer-king/#comments</comments>
		<pubDate>Sun, 31 Jan 2010 14:30:43 +0000</pubDate>
		<dc:creator>Els Aerts</dc:creator>
				<category><![CDATA[Information architecture]]></category>
		<category><![CDATA[Methodology]]></category>
		<category><![CDATA[facts]]></category>
		<category><![CDATA[user research]]></category>

		<guid isPermaLink="false">http://webusability-blog.com/?p=794</guid>
		<description><![CDATA[Not the company that owns the website should be central in the webdesign process but the company's customers. Talk to them to find out what they want.]]></description>
			<content:encoded><![CDATA[<h1><strong>Is the customer king?</strong></h1>
<p>You&#8217;re probably thinking that should be a statement instead of a question. Well&#8230; yes, the customer is king. And no, he isn&#8217;t really. </p>
<p>One of the main reasons a lot of websites fail to deliver is because they&#8217;re made according to the specifications of the company that ordered it. Don&#8217;t get me wrong. It&#8217;s good for a web builder or usability expert to find out what the customer wants. But it&#8217;s not enough. </p>
<p>We tell most of our customers at the start of a usability project that it doesn&#8217;t really matter all that much what they think or want. </p>
<p>What we think doesn&#8217;t matter that much either.</p>
<h1>It&#8217;s not your customer&#8217;s opinion that counts, it&#8217;s his customers&#8217; opinion</h1>
<p>You don&#8217;t make a company&#8217;s website for that company. You make it for that company&#8217;s customers. </p>
<p>Their needs and expectations are what matters. A website can only be truly successful if it caters to the needs of its visitors, not to the needs of its owners or makers. </p>
<p>Finding out what visitors want is crucial if you want to base your <a href="http://www.agconsult.be/en/usability/functional-analysis-rfp.asp">functional analysis</a> and <a href="http://www.agconsult.be/en/usability/informationstructure.asp">information architecture</a> on facts rather than feelings.</p>
<h1>Companies know their customers</h1>
<p>Yeah, right.<span id="more-794"></span></p>
<p>That&#8217;s what I thought. But 10 years of experience have taught me that a lot of companies know surprisingly little about their customers. </p>
<p>Try it yourself if you don&#8217;t believe me. Ask your customer (or yourself if you&#8217;re a CEO, communication or marketing manager) questions like:</p>
<ul>
<li>Who visits your website?</li>
<li>Why do people visit your website?</li>
<li>Why do people buy your product and not your competitor&#8217;s?</li>
<li>Why do they buy product x and not product y of the same series?</li>
<li>What are your potential customers&#8217; 10 most frequently asked questions?</li>
</ul>
<p>It&#8217;s amazing how often companies don&#8217;t know the answers to these questions. Or how often the answers start with “I think” or “According to us”.</p>
<p>Which basically means &#8220;We don&#8217;t know&#8221;. Time for user research to make sure you can start your answers with &#8220;We know&#8221;.</p>
<h1>User research</h1>
<p>How do you find out what people want from a website? </p>
<p>That&#8217;s easy: you ask them. And you check what they&#8217;re already doing on your site.</p>
<p>A few user research methods we use:</p>
<ul>
<li><strong>Logfile analysis</strong><br />
Logfiles can tell you what people are doing on your website. They can&#8217;t tell you what they&#8217;d like to do or what they can&#8217;t do.</li>
<li><strong>Keyword analysis</strong><br />
Analysing the keywords people type into your search feature tells you what people are looking for on your site and which words they use.</li>
<li><strong>Customer contacts analysis</strong><br />
Ask everybody in your company who comes into contact with customers to keep track of the questions they ask so you know what the 10 most frequently asked questions are.</li>
<li><strong>Online survey</strong><br />
An online survey is a great way to find out more about your visitors&#8217; profile and what they&#8217;re looking for on your website. A short survey with the right questions still gets loads of responses.</li>
<li><strong>Interviews</strong><br />
Interviews with potential and existing customers are vital if you want to get details about what they really want from your website.</li>
<li><strong>User tests</strong><br />
User tests will show you what people like and dislike about your website and your competitors&#8217;.</li>
</ul>
<h1><strong>Is user research always interesting?</strong></h1>
<p>Absolutely. You always learn something new.</p>
<p>Of course you don&#8217;t always have to use all the methods we described. Our advice is to choose at least 1 analytical method (logfile analysis, keyword analysis or customer contacts analysis) and 1 other method. </p>
<p>Don&#8217;t get carried away with the number of people you interview or do user tests with either. Around 10 people is plenty, unless of course you have a huge website with loads of different target audiences.</p>
<h3><strong>Examples</strong></h3>
<ul>
<li><strong>Environmental government agency</strong><br />
The agency thought their website was mostly visited by 2 types of visitors:<br />
- Farmers and environmental professionals looking for scientific data.<br />
- Companies looking for information on environmental permits.<br />
Research showed these assumptions were wrong. Sure, 20% of visitors were companies and around 3% were farmers and environmental professionals. But about 75% of visitors were regular people looking for information on air and water quality in their area and tips on how to be environmentally friendly.</li>
</ul>
<p></p>
<ul>
<li><strong> Air conditioning manufacturer</strong><br />
Our customer thought the website was very important for engineering companies, architects, etc.<br />
Research showed these people rarely visited the website. The real visitors were end customers looking for information on air conditioning. And they weren&#8217;t too impressed with sales arguments like ‘titanium air filter’ and ‘only 69db’. Their main reasons to buy a particular air conditioning unit were things like ‘it&#8217;s really quiet&#8217; and &#8216;it fits with our decorating scheme&#8217;.</li>
</ul>
<p></p>
<ul>
<li><strong>Hospital</strong><br />
The hospital we worked for was convinced their website had to inform people about medical conditions and treatments. User research told a different story. People were mostly looking for contact information, phone numbers of doctors and visiting hours. As a matter of fact, more people used the website to look for information on the cafeteria than information about a medical condition or treatment.</li>
</ul>
<p></p>
<ul>
<li><strong>Scientific research institute</strong><br />
User research showed that the visitor profile was very different depending on the language version of the website. The Dutch version of the site was mostly visited by teachers, students and non-scientists, looking for general information or didactic material. The English version of the site was mostly visited by staff and scientists from other research institutes and industry, looking for information on specific research projects or scientists&#8217; contact details.</li>
</ul>
<h1><strong>So don&#8217;t talk to the customer?</strong></h1>
<p>Of course you should. Talking to your customer is always important.</p>
<p>But don&#8217;t just talk to the CEO or the web manager. Talk to people from all divisions of the company so you can find out what their expectations are about the website.  </p>
<p>And always, always check the company&#8217;s wishes and expectations against those of the people it&#8217;s all about: the website&#8217;s visitors.  </p>
<h1><strong>Conclusion: talk to your customer and his customers</strong></h1>
<p>What does all that talking get you? An excellent view on what the website should and shouldn&#8217;t do and what the visitors&#8217; top tasks are.</p>
<p>The end result: happy website visitors. Which in turn leads to a happy customer for you. </p>
<h1>Care to share your experiences?</h1>
<p>We&#8217;d love to hear from you.</p>
]]></content:encoded>
			<wfw:commentRss>http://webusability-blog.com/webdesign-process-is-the-customer-king/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

