<?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>UsabilityOne Blog &#187; Photo Friday</title>
	<atom:link href="http://blog.usabilityone.com/category/photo-friday/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.usabilityone.com</link>
	<description>Usability, design and technology</description>
	<lastBuildDate>Mon, 30 Aug 2010 01:57:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Photo Friday: More lift controls</title>
		<link>http://blog.usabilityone.com/2010/04/photo-friday-more-lift-controls/</link>
		<comments>http://blog.usabilityone.com/2010/04/photo-friday-more-lift-controls/#comments</comments>
		<pubDate>Thu, 22 Apr 2010 21:00:15 +0000</pubDate>
		<dc:creator>Chris Gray</dc:creator>
				<category><![CDATA[Photo Friday]]></category>
		<category><![CDATA[Lift]]></category>
		<category><![CDATA[photo]]></category>
		<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://blog.usabilityone.com/?p=402</guid>
		<description><![CDATA[Image showing poor usability of lift which has resulted from poor implementation.]]></description>
			<content:encoded><![CDATA[<p>Jo and I stepped into this lift last week and just had to take a photo.  Where is the right facing button going to take us??  I guess it goes to show that implementation is so important.<img class="aligncenter" title="lift button" src="http://farm5.static.flickr.com/4013/4539122511_3587055e01.jpg" alt="" width="250" height="333" /></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.usabilityone.com/2010/04/photo-friday-more-lift-controls/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Photo Friday: Clear lift control</title>
		<link>http://blog.usabilityone.com/2010/04/photo-friday-clear-lift-control/</link>
		<comments>http://blog.usabilityone.com/2010/04/photo-friday-clear-lift-control/#comments</comments>
		<pubDate>Thu, 08 Apr 2010 21:03:49 +0000</pubDate>
		<dc:creator>Chris Gray</dc:creator>
				<category><![CDATA[Photo Friday]]></category>
		<category><![CDATA[photo]]></category>
		<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://blog.usabilityone.com/?p=320</guid>
		<description><![CDATA[Photo of a lift control which was highly intuitive and usable.]]></description>
			<content:encoded><![CDATA[<p>Lifts can, at times, be confusing.  Is street level &#8217;0&#8242; or &#8217;1&#8242;? Did I enter the building on &#8216;G&#8217; or &#8216;B&#8217;?  Jo and I saw this example whilst visiting the Department of Justice on Wednesday.  And immediately took a snap.<img class="aligncenter" src="http://farm5.static.flickr.com/4004/4480675928_c998da9d28.jpg" alt="good example of lift controls" width="500" height="375" /></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.usabilityone.com/2010/04/photo-friday-clear-lift-control/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Photo Friday: Unconventional conventional doors</title>
		<link>http://blog.usabilityone.com/2010/03/photo-friday-unconventional-conventional-doors/</link>
		<comments>http://blog.usabilityone.com/2010/03/photo-friday-unconventional-conventional-doors/#comments</comments>
		<pubDate>Thu, 25 Mar 2010 21:10:33 +0000</pubDate>
		<dc:creator>Chris Gray</dc:creator>
				<category><![CDATA[Photo Friday]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[usability photo]]></category>

		<guid isPermaLink="false">http://blog.usabilityone.com/?p=283</guid>
		<description><![CDATA[door usability including a photo]]></description>
			<content:encoded><![CDATA[<p><img class="aligncenter" title="Confusing door" src="http://farm3.static.flickr.com/2770/4441903494_8b40008949.jpg" alt="Confusing door" width="500" height="386" />Doors are often used as examples of good and bad design. As in, &#8220;Handles are for pulling etc.&#8221;</p>
<p>Last week I came across these doors and was a little confused.  Upon looking at the photo, it is clear how each door operates.  My confusion may have been a &#8216;user issue&#8217; but it did defy my expectation that double doors open in the same direction.  Is it me or the doors?</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.usabilityone.com/2010/03/photo-friday-unconventional-conventional-doors/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Photo Friday: Hold or Hang Up?</title>
		<link>http://blog.usabilityone.com/2010/03/photo-friday-hold-or-hang-up/</link>
		<comments>http://blog.usabilityone.com/2010/03/photo-friday-hold-or-hang-up/#comments</comments>
		<pubDate>Thu, 18 Mar 2010 23:37:12 +0000</pubDate>
		<dc:creator>Jo Squire</dc:creator>
				<category><![CDATA[Design Issues]]></category>
		<category><![CDATA[Photo Friday]]></category>
		<category><![CDATA[usability photo]]></category>

		<guid isPermaLink="false">http://blog.usabilityone.com/?p=268</guid>
		<description><![CDATA[Unintuitive icons lead to poor device design impacting the user experience of a telephone system.]]></description>
			<content:encoded><![CDATA[<p><img class="alignnone" title="Unintuitive Hold icon" src="http://farm5.static.flickr.com/4069/4441951802_f77a7fc937.jpg" alt="Unintuitive Hold icon on phone" width="500" height="375" /></p>
<p>When on an important client call it can be quite stressful figuring out which button to use to place the call on hold and avoid rudely hanging up on the person. No matter how many times I&#8217;ve taken calls using this phone, time and time again I get confused . So much so that I&#8217;ve had to create my own work around for the device by placing a sticky note on the phone.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.usabilityone.com/2010/03/photo-friday-hold-or-hang-up/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Photo Friday: Temperature, high or low?</title>
		<link>http://blog.usabilityone.com/2010/03/photo-friday-temperature-high-or-low/</link>
		<comments>http://blog.usabilityone.com/2010/03/photo-friday-temperature-high-or-low/#comments</comments>
		<pubDate>Thu, 11 Mar 2010 20:00:08 +0000</pubDate>
		<dc:creator>Chris Gray</dc:creator>
				<category><![CDATA[Photo Friday]]></category>
		<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://blog.usabilityone.com/?p=215</guid>
		<description><![CDATA[Photo of fridge cooling control]]></description>
			<content:encoded><![CDATA[<div class="wp-caption aligncenter" style="width: 510px"><img title="Fridge control" src="http://farm5.static.flickr.com/4064/4398848683_d88be50192.jpg" alt="Fridge control" width="500" height="375" /><p class="wp-caption-text">Fridge control</p></div>
<p>Last night the fish in the fridge froze, so I attempted to increase the temperature .  Then I was faced with the options of &#8216;high cool&#8217; or &#8216;low cool&#8217;.  In terms of temperature, I am familiar with warm or cold, even high or low, but not high cool or low cool. Is high cool, extra cold, or the higher end of the cold spectrum?</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.usabilityone.com/2010/03/photo-friday-temperature-high-or-low/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Photo Friday: Yeah, thanks for that!</title>
		<link>http://blog.usabilityone.com/2010/03/photo-friday-yeah-thanks-for-that/</link>
		<comments>http://blog.usabilityone.com/2010/03/photo-friday-yeah-thanks-for-that/#comments</comments>
		<pubDate>Fri, 05 Mar 2010 05:00:19 +0000</pubDate>
		<dc:creator>Owen Hodda</dc:creator>
				<category><![CDATA[Photo Friday]]></category>
		<category><![CDATA[buttons]]></category>
		<category><![CDATA[Press to operate]]></category>
		<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://blog.usabilityone.com/?p=202</guid>
		<description><![CDATA[If you must write help documentation, ensure it is needed. And actually helpful.]]></description>
			<content:encoded><![CDATA[<p><img class="alignnone" title="Push to operate" src="http://farm3.static.flickr.com/2702/4388576119_da42ceb120_o.jpg" alt="" width="455" height="354" /></p>
<p>If you must write help documentation, ensure it is needed. And actually helpful.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.usabilityone.com/2010/03/photo-friday-yeah-thanks-for-that/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Photo Friday (on Monday): Press Up to Go Up</title>
		<link>http://blog.usabilityone.com/2010/03/photo-friday-on-monday-press-up-to-go-up/</link>
		<comments>http://blog.usabilityone.com/2010/03/photo-friday-on-monday-press-up-to-go-up/#comments</comments>
		<pubDate>Sun, 28 Feb 2010 23:58:42 +0000</pubDate>
		<dc:creator>Owen Hodda</dc:creator>
				<category><![CDATA[Photo Friday]]></category>
		<category><![CDATA[Elevator]]></category>
		<category><![CDATA[Lift]]></category>
		<category><![CDATA[Sign]]></category>

		<guid isPermaLink="false">http://blog.usabilityone.com/?p=187</guid>
		<description><![CDATA[“We shouldn’t assume that the general viewing public is an idiot” Joshua Davis (via InspireUX)]]></description>
			<content:encoded><![CDATA[<p><img src="http://nightapesdream.com/wp-content/uploads/2008/08/press-up-to-go-up.png" alt="" width="648" height="487" /></p>
<p>“We shouldn’t assume that the general viewing public is an idiot”</p>
<p>Joshua Davis (via <a onclick="javascript:pageTracker._trackPageview('/outgoing/www.inspireux.com/2008/04/16/dont-assume-the-general-viewing-public-is-an-idiot/');" href="http://www.inspireux.com/2008/04/16/dont-assume-the-general-viewing-public-is-an-idiot/" target="_blank">InspireUX</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.usabilityone.com/2010/03/photo-friday-on-monday-press-up-to-go-up/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Photo Friday: Kaffe, Coffi, Kahve&#8230;</title>
		<link>http://blog.usabilityone.com/2010/02/photo-friday-kaffe-coffi-kahve/</link>
		<comments>http://blog.usabilityone.com/2010/02/photo-friday-kaffe-coffi-kahve/#comments</comments>
		<pubDate>Fri, 19 Feb 2010 05:15:38 +0000</pubDate>
		<dc:creator>Owen Hodda</dc:creator>
				<category><![CDATA[Photo Friday]]></category>
		<category><![CDATA[buttons]]></category>
		<category><![CDATA[Coffee]]></category>
		<category><![CDATA[coffee machine]]></category>
		<category><![CDATA[Usability Tip]]></category>

		<guid isPermaLink="false">http://blog.usabilityone.com/?p=156</guid>
		<description><![CDATA[There are some serious coffee drinkers in the UsabilityOne office, and a number of us are fairly fussy about our coffees too. So when our new coffee machine arrived we were keen to fiddle with the settings and configure it just the way we like it. Several weeks later, we still haven&#8217;t worked out how [...]]]></description>
			<content:encoded><![CDATA[<p>There are some serious coffee drinkers in the UsabilityOne office, and a number of us are fairly fussy about our coffees too. So when our new coffee machine arrived we were keen to fiddle with the settings and configure it just the way we like it.</p>
<p><img class="alignnone" title="Coffee Machine Control Panel" src="http://farm3.static.flickr.com/2737/4369756940_63beeef682_o.jpg" alt="Coffee Machine Control Panel" width="500" height="375" /><br />
Several weeks later, we still haven&#8217;t worked out how to do that. We do know how to change the language on the menu though.</p>
<p>When designing an interface, design for the most likely and frequent activities your users will undertake.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.usabilityone.com/2010/02/photo-friday-kaffe-coffi-kahve/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
