<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: On Information Architecture and user-testing &#8211; Part 2</title>
	<atom:link href="http://www.whatwasithinking.co.uk/2008/04/12/on-information-architecture-and-user-testing-part-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.whatwasithinking.co.uk/2008/04/12/on-information-architecture-and-user-testing-part-2/</link>
	<description>A Flash Development, Information Architecture, SEO &#38; Web Design Blog</description>
	<lastBuildDate>Sat, 06 Feb 2010 18:08:04 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Alex Luna</title>
		<link>http://www.whatwasithinking.co.uk/2008/04/12/on-information-architecture-and-user-testing-part-2/#comment-4459</link>
		<dc:creator>Alex Luna</dc:creator>
		<pubDate>Wed, 10 Jun 2009 09:38:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.whatwasithinking.co.uk/?p=25#comment-4459</guid>
		<description>Have you tried to simulate the situation of using the site with the client? If you have the time to do a mockup using a prototyper, that should be useful to show your point to the client.</description>
		<content:encoded><![CDATA[<p>Have you tried to simulate the situation of using the site with the client? If you have the time to do a mockup using a prototyper, that should be useful to show your point to the client.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alexanderrehm (Alexander Rehm)</title>
		<link>http://www.whatwasithinking.co.uk/2008/04/12/on-information-architecture-and-user-testing-part-2/#comment-3838</link>
		<dc:creator>alexanderrehm (Alexander Rehm)</dc:creator>
		<pubDate>Fri, 15 May 2009 06:50:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.whatwasithinking.co.uk/?p=25#comment-3838</guid>
		<description>On Information Architecture and User testing - defining a sitemap and wireframe:  http://tinyurl.com/6nr8xf</description>
		<content:encoded><![CDATA[<p>On Information Architecture and User testing &#8211; defining a sitemap and wireframe:  <a href="http://tinyurl.com/6nr8xf" rel="nofollow">http://tinyurl.com/6nr8xf</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: On Information Architecture and user-testing - Part 1 « WhatwasIthinking.co.uk</title>
		<link>http://www.whatwasithinking.co.uk/2008/04/12/on-information-architecture-and-user-testing-part-2/#comment-1830</link>
		<dc:creator>On Information Architecture and user-testing - Part 1 « WhatwasIthinking.co.uk</dc:creator>
		<pubDate>Mon, 16 Mar 2009 21:21:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.whatwasithinking.co.uk/?p=25#comment-1830</guid>
		<description>[...] Part 2 and part 3 are online [...]</description>
		<content:encoded><![CDATA[<div style="background: #F4F4EC;">
<p>[...] Part 2 and part 3 are online [...]</p>
</div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Timur</title>
		<link>http://www.whatwasithinking.co.uk/2008/04/12/on-information-architecture-and-user-testing-part-2/#comment-1218</link>
		<dc:creator>Timur</dc:creator>
		<pubDate>Tue, 27 Jan 2009 17:12:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.whatwasithinking.co.uk/?p=25#comment-1218</guid>
		<description>Wow! Thank you very much for this post!</description>
		<content:encoded><![CDATA[<p>Wow! Thank you very much for this post!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alexander Rehm</title>
		<link>http://www.whatwasithinking.co.uk/2008/04/12/on-information-architecture-and-user-testing-part-2/#comment-999</link>
		<dc:creator>Alexander Rehm</dc:creator>
		<pubDate>Sat, 13 Dec 2008 09:04:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.whatwasithinking.co.uk/?p=25#comment-999</guid>
		<description>Hi Joanne,

I understand completely where you are coming from. In a nutshell, you have prepared a prototype you feel meets the client&#039;s needs to great extent, yet you have now been told that the user&#039;s navigation and flow is being hindered by data-capture methods to actually get to the information the visitor wanted to come for in the first place. I have been in these situations now and then.

What I would do would be confronting the client at this stage and ask them exactly what their reasoning is behind stopping a user from accessing the exact information they came to the site for in the first place.

Let the client know you understand the reasons for data capture to increase their mailing lists or to have a more accurate feel for their target market, but argue that their plan will fail due to the fact that you - as the visitor - would be stumped by needing to enter your details for information that may be freely available on other, similar sites, thus risking losing a great number of visitors (and potential customers) at this stage. 

Maybe suggest a different way. Depending on the project you could make certain items (such as technical specifications or downloadable information) only available if you filled in a small form. This is very normal, as a visitor you have plenty of information to go on with, and if you need a bit more in-depth information then you need to sign up. 

If that does not work due to the product then maybe it would help working on having a little &quot;keep me updated&quot; box on the product pages along the lines of &quot;Would you like to receive more information and updates on this product? Please sign up here&quot;, that might do the trick as well.

Please let me know how you are getting on, and maybe &lt;a href=&quot;http://www.whatwasithinking.co.uk/2008/06/04/on-information-architecture-and-user-testing-part-3-usability-testing-and-accessibility-testing/&quot; rel=&quot;nofollow&quot;&gt;the third part of my article&lt;/a&gt; may come in handy as well in explaining your reasons for suggesting not to have sign-ups plastering a visitor&#039;s way :)</description>
		<content:encoded><![CDATA[<p>Hi Joanne,</p>
<p>I understand completely where you are coming from. In a nutshell, you have prepared a prototype you feel meets the client&#8217;s needs to great extent, yet you have now been told that the user&#8217;s navigation and flow is being hindered by data-capture methods to actually get to the information the visitor wanted to come for in the first place. I have been in these situations now and then.</p>
<p>What I would do would be confronting the client at this stage and ask them exactly what their reasoning is behind stopping a user from accessing the exact information they came to the site for in the first place.</p>
<p>Let the client know you understand the reasons for data capture to increase their mailing lists or to have a more accurate feel for their target market, but argue that their plan will fail due to the fact that you &#8211; as the visitor &#8211; would be stumped by needing to enter your details for information that may be freely available on other, similar sites, thus risking losing a great number of visitors (and potential customers) at this stage. </p>
<p>Maybe suggest a different way. Depending on the project you could make certain items (such as technical specifications or downloadable information) only available if you filled in a small form. This is very normal, as a visitor you have plenty of information to go on with, and if you need a bit more in-depth information then you need to sign up. </p>
<p>If that does not work due to the product then maybe it would help working on having a little &#8220;keep me updated&#8221; box on the product pages along the lines of &#8220;Would you like to receive more information and updates on this product? Please sign up here&#8221;, that might do the trick as well.</p>
<p>Please let me know how you are getting on, and maybe <a href="http://www.whatwasithinking.co.uk/2008/06/04/on-information-architecture-and-user-testing-part-3-usability-testing-and-accessibility-testing/" rel="nofollow">the third part of my article</a> may come in handy as well in explaining your reasons for suggesting not to have sign-ups plastering a visitor&#8217;s way <img src='http://www.whatwasithinking.co.uk/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joanne</title>
		<link>http://www.whatwasithinking.co.uk/2008/04/12/on-information-architecture-and-user-testing-part-2/#comment-998</link>
		<dc:creator>Joanne</dc:creator>
		<pubDate>Sat, 13 Dec 2008 08:50:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.whatwasithinking.co.uk/?p=25#comment-998</guid>
		<description>Hi Alexander, thank you very much for the article. I am currently trying to get my own prototype tested, but I am not entirely sure how to proceed...

I have worked on a prototype based on the client&#039;s brief, but half-way during the project some of the routes to get to the product have changed with a requirement to increase sign-ups - once you did a search and want to go to the product page you are asked to register your details for example. 

I am a bit at a loss here, as the original brief was very easy to follow, and I am now struggling trying to make sense of the prototype, simply because I as a user don&#039;t really want to proceed if that makes sense?

Joanne</description>
		<content:encoded><![CDATA[<p>Hi Alexander, thank you very much for the article. I am currently trying to get my own prototype tested, but I am not entirely sure how to proceed&#8230;</p>
<p>I have worked on a prototype based on the client&#8217;s brief, but half-way during the project some of the routes to get to the product have changed with a requirement to increase sign-ups &#8211; once you did a search and want to go to the product page you are asked to register your details for example. </p>
<p>I am a bit at a loss here, as the original brief was very easy to follow, and I am now struggling trying to make sense of the prototype, simply because I as a user don&#8217;t really want to proceed if that makes sense?</p>
<p>Joanne</p>
]]></content:encoded>
	</item>
</channel>
</rss>
