<?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 for uxcube.com</title>
	<atom:link href="http://www.uxcube.com/blog/?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://www.uxcube.com/blog</link>
	<description>website optimisation and design</description>
	<lastBuildDate>Thu, 09 Oct 2008 13:22:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>Comment on Consistency, ConSIStency, ConSisTENCY&#8230; by Steph</title>
		<link>http://www.uxcube.com/blog/?p=7&#038;cpage=1#comment-8</link>
		<dc:creator>Steph</dc:creator>
		<pubDate>Thu, 09 Oct 2008 13:22:30 +0000</pubDate>
		<guid isPermaLink="false">http://sonyal1.wordpress.com/2006/10/03/consistency-consistency-consistency/#comment-8</guid>
		<description>I just wrote an article on consistency, this might be interesting to you:
http://girldev.wordpress.com/2008/10/08/consistency/

Nice job!
Steph</description>
		<content:encoded><![CDATA[<p>I just wrote an article on consistency, this might be interesting to you:<br />
<a href="http://girldev.wordpress.com/2008/10/08/consistency/" rel="nofollow">http://girldev.wordpress.com/2008/10/08/consistency/</a></p>
<p>Nice job!<br />
Steph</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on barriers to usability by sonyal1</title>
		<link>http://www.uxcube.com/blog/?p=48&#038;cpage=1#comment-59</link>
		<dc:creator>sonyal1</dc:creator>
		<pubDate>Wed, 21 May 2008 19:43:40 +0000</pubDate>
		<guid isPermaLink="false">http://sonyal1.wordpress.com/2007/08/22/barriers-to-usability/#comment-59</guid>
		<description>It can be a tricky one to win people over and I can only advise some usability testing. This doesn’t have to be lab-based or indeed expensive. I can recommend Steve Krug’s book Don’t make me think – a common sense approach to usability. Although is a few years old it does have a useful section about informal usability testing.

Even informal testing can provide invaluable insight into how; users use software, find ways round things that maybe confusing them or even how users can be unaware that they are not using it as intended.

In my last project I was undertaking a heuristic-based review and on a particular function something didn’t seem quite right - I wasn’t sure how I could convince my audience that there was a problem so I asked a few colleagues in my office to have a go at completing a particular task. In this instance this was extremely useful, as 3 out 4 didn’t successfully complete it when they thought they had. The remaining person did successfully complete the task after trying 5 times. This confirmed my fears but also gave me a bit more credence to my argument when reporting back. When I did report back those that thought they understood usability and how it was achieved were very surprised but also started to listen. It was no longer my view vs. theirs it was facts that they had to deal with. This also helped keep the discussions much more objective.

This was also leverage to get some formal usability testing done, which has also furthered their understanding.

I hope this helps.</description>
		<content:encoded><![CDATA[<p>It can be a tricky one to win people over and I can only advise some usability testing. This doesn’t have to be lab-based or indeed expensive. I can recommend Steve Krug’s book Don’t make me think – a common sense approach to usability. Although is a few years old it does have a useful section about informal usability testing.</p>
<p>Even informal testing can provide invaluable insight into how; users use software, find ways round things that maybe confusing them or even how users can be unaware that they are not using it as intended.</p>
<p>In my last project I was undertaking a heuristic-based review and on a particular function something didn’t seem quite right &#8211; I wasn’t sure how I could convince my audience that there was a problem so I asked a few colleagues in my office to have a go at completing a particular task. In this instance this was extremely useful, as 3 out 4 didn’t successfully complete it when they thought they had. The remaining person did successfully complete the task after trying 5 times. This confirmed my fears but also gave me a bit more credence to my argument when reporting back. When I did report back those that thought they understood usability and how it was achieved were very surprised but also started to listen. It was no longer my view vs. theirs it was facts that they had to deal with. This also helped keep the discussions much more objective.</p>
<p>This was also leverage to get some formal usability testing done, which has also furthered their understanding.</p>
<p>I hope this helps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on barriers to usability by cranley</title>
		<link>http://www.uxcube.com/blog/?p=48&#038;cpage=1#comment-58</link>
		<dc:creator>cranley</dc:creator>
		<pubDate>Wed, 07 May 2008 14:33:59 +0000</pubDate>
		<guid isPermaLink="false">http://sonyal1.wordpress.com/2007/08/22/barriers-to-usability/#comment-58</guid>
		<description>Your post is right on the money.  At my last job, Usability = Easy &lt;i&gt;and&lt;/i&gt; Flashy... Usability was also dictated by the CEO, somebody who had excellent vision but didn&#039;t understand what, exactly, Usability it or, worse, &lt;i&gt;how&lt;/i&gt; its achieved.

The product in question is over 8 years old, and the shoot-from-the-hip &quot;usability&quot; decisions started to add up such that, when they brought me in (as a software developer, not a UI/UX expert) I was actually floored at how horrible the thing was to use.  There was no consistency, no UI guidelines, no flow (in fact, &quot;by design&quot;, every screen had so much stuff crammed into it that it was impossible to visually guide the user).  The thing was a complete mess, but everybody else had been so indoctrinated, and understood the underlying functionality and business goals, that they couldn&#039;t see the mess that was in front of them.

Tried as I might I was unable to convince the key people that we needed to take a different approach.  My question to you is, what advice do you have for people in organizations that want to make a UI/UX difference, but are facing the people that don&#039;t (or can&#039;t) see the problems that you see?  How do you get the ball rolling?  How do you &quot;win them over&quot;?  Are some organizations too entrenched to make the shift?

Thanks - great post!</description>
		<content:encoded><![CDATA[<p>Your post is right on the money.  At my last job, Usability = Easy <i>and</i> Flashy&#8230; Usability was also dictated by the CEO, somebody who had excellent vision but didn&#8217;t understand what, exactly, Usability it or, worse, <i>how</i> its achieved.</p>
<p>The product in question is over 8 years old, and the shoot-from-the-hip &#8220;usability&#8221; decisions started to add up such that, when they brought me in (as a software developer, not a UI/UX expert) I was actually floored at how horrible the thing was to use.  There was no consistency, no UI guidelines, no flow (in fact, &#8220;by design&#8221;, every screen had so much stuff crammed into it that it was impossible to visually guide the user).  The thing was a complete mess, but everybody else had been so indoctrinated, and understood the underlying functionality and business goals, that they couldn&#8217;t see the mess that was in front of them.</p>
<p>Tried as I might I was unable to convince the key people that we needed to take a different approach.  My question to you is, what advice do you have for people in organizations that want to make a UI/UX difference, but are facing the people that don&#8217;t (or can&#8217;t) see the problems that you see?  How do you get the ball rolling?  How do you &#8220;win them over&#8221;?  Are some organizations too entrenched to make the shift?</p>
<p>Thanks &#8211; great post!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Google mini error by Ceej McQueen</title>
		<link>http://www.uxcube.com/blog/?p=44&#038;cpage=1#comment-57</link>
		<dc:creator>Ceej McQueen</dc:creator>
		<pubDate>Thu, 23 Aug 2007 09:33:00 +0000</pubDate>
		<guid isPermaLink="false">http://sonyal1.wordpress.com/2007/06/20/google-mini-error/#comment-57</guid>
		<description>You are not alone. We use Google mini to provide the search facility on several websites. It is implemented by means of a proxy - i.e. the GM box itself is not publicly facing. Instead, we send the query via our websites requesting the results in xml with no dtd. This enables tight integration. Anyway, we have experienced a problem when trying to query it for results - we received the same error message: &#039;The underlying connection was closed: Unable to connect to the remote server&#039;. The only method of bringing it back was to pull the plug out! When it came back the index had been emptied and we still got the same error message. Upon forcing a recrawl of all our sources Google mini came fully back to life. However, currently I am none the wiser as to what happened....</description>
		<content:encoded><![CDATA[<p>You are not alone. We use Google mini to provide the search facility on several websites. It is implemented by means of a proxy &#8211; i.e. the GM box itself is not publicly facing. Instead, we send the query via our websites requesting the results in xml with no dtd. This enables tight integration. Anyway, we have experienced a problem when trying to query it for results &#8211; we received the same error message: &#8216;The underlying connection was closed: Unable to connect to the remote server&#8217;. The only method of bringing it back was to pull the plug out! When it came back the index had been emptied and we still got the same error message. Upon forcing a recrawl of all our sources Google mini came fully back to life. However, currently I am none the wiser as to what happened&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why we should take care when using image icons for menu items by sonyal1</title>
		<link>http://www.uxcube.com/blog/?p=29&#038;cpage=1#comment-39</link>
		<dc:creator>sonyal1</dc:creator>
		<pubDate>Fri, 29 Jun 2007 10:33:29 +0000</pubDate>
		<guid isPermaLink="false">http://sonyal1.wordpress.com/2007/04/25/why-we-should-take-care-when-using-image-icons-for-menu-items/#comment-39</guid>
		<description>I urge caution when using icons as a means of navigation as they are often open to misinterpretation and so from a usability point of view can interfere with a positive user experience.
The primary goals of a labelling/navigation system whether formed of icons or text are to:

Communicate effectively
- cause the right association for the user
Communicate efficiently
-don&#039;t take up too many cognitive resources

In deciding whether to use icons you should consider who your audience are and what type of tasks they are expected to complete on your website. For example, an ecommerce business relies on users completing transactions through their website. If users are unsure of the meaning of an icon and it is not clear what to click next to complete a transaction, they are likely to feel frustrated and anxious about whether they should handover their credit card details.

However, they are not always bad. If the purpose of your site is for fun, then there is less need to be concerned. They can be useful for more efficient use of space and are generally more effective alongside or with embedded text. The general rule would be to use icons that are simple and universal… don’t try to be too clever :-)
Hope this helps.</description>
		<content:encoded><![CDATA[<p>I urge caution when using icons as a means of navigation as they are often open to misinterpretation and so from a usability point of view can interfere with a positive user experience.<br />
The primary goals of a labelling/navigation system whether formed of icons or text are to:</p>
<p>Communicate effectively<br />
- cause the right association for the user<br />
Communicate efficiently<br />
-don&#8217;t take up too many cognitive resources</p>
<p>In deciding whether to use icons you should consider who your audience are and what type of tasks they are expected to complete on your website. For example, an ecommerce business relies on users completing transactions through their website. If users are unsure of the meaning of an icon and it is not clear what to click next to complete a transaction, they are likely to feel frustrated and anxious about whether they should handover their credit card details.</p>
<p>However, they are not always bad. If the purpose of your site is for fun, then there is less need to be concerned. They can be useful for more efficient use of space and are generally more effective alongside or with embedded text. The general rule would be to use icons that are simple and universal… don’t try to be too clever <img src='http://www.uxcube.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /><br />
Hope this helps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Consistency, ConSIStency, ConSisTENCY&#8230; by sonyal1</title>
		<link>http://www.uxcube.com/blog/?p=7&#038;cpage=1#comment-7</link>
		<dc:creator>sonyal1</dc:creator>
		<pubDate>Fri, 06 Oct 2006 09:00:01 +0000</pubDate>
		<guid isPermaLink="false">http://sonyal1.wordpress.com/2006/10/03/consistency-consistency-consistency/#comment-7</guid>
		<description>I have seen the use of colours to denote areas/sections and this can work quite well. One thing to becareful of is to ensure that you don&#039;t use colour to convey information as this would go against accessibility guidelines as many people have some form of colour blindness. If you use colour it is important that you also ensure that each section is clearly labelled.

One that doesn&#039;t use different colours and one that I think works quite well is http://www.brighton.ac.uk</description>
		<content:encoded><![CDATA[<p>I have seen the use of colours to denote areas/sections and this can work quite well. One thing to becareful of is to ensure that you don&#8217;t use colour to convey information as this would go against accessibility guidelines as many people have some form of colour blindness. If you use colour it is important that you also ensure that each section is clearly labelled.</p>
<p>One that doesn&#8217;t use different colours and one that I think works quite well is <a href="http://www.brighton.ac.uk" rel="nofollow">http://www.brighton.ac.uk</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Consistency, ConSIStency, ConSisTENCY&#8230; by Flo</title>
		<link>http://www.uxcube.com/blog/?p=7&#038;cpage=1#comment-6</link>
		<dc:creator>Flo</dc:creator>
		<pubDate>Thu, 05 Oct 2006 13:10:04 +0000</pubDate>
		<guid isPermaLink="false">http://sonyal1.wordpress.com/2006/10/03/consistency-consistency-consistency/#comment-6</guid>
		<description>What about the use of colors/images on a website to denote areas/sections?

I think that both have their individual merits but, care should be taken so as not to confuse/detract from the content/message.</description>
		<content:encoded><![CDATA[<p>What about the use of colors/images on a website to denote areas/sections?</p>
<p>I think that both have their individual merits but, care should be taken so as not to confuse/detract from the content/message.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

