<?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>Front to back &#187; Survival tactics</title>
	<atom:link href="http://fronttoback.org/category/survival-tactics/feed/" rel="self" type="application/rss+xml" />
	<link>http://fronttoback.org</link>
	<description>Your users experience it that way around.</description>
	<lastBuildDate>Tue, 25 May 2010 13:04:32 +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>4 ways to combat usability testing avoidance</title>
		<link>http://fronttoback.org/2010/01/20/4-ways-to-combat-usability-testing-avoidance/</link>
		<comments>http://fronttoback.org/2010/01/20/4-ways-to-combat-usability-testing-avoidance/#comments</comments>
		<pubDate>Wed, 20 Jan 2010 20:58:01 +0000</pubDate>
		<dc:creator>philbuk</dc:creator>
				<category><![CDATA[ForFlowThinkBlog]]></category>
		<category><![CDATA[Interaction design]]></category>
		<category><![CDATA[Survival tactics]]></category>

		<guid isPermaLink="false">http://fronttoback.org/?p=272</guid>
		<description><![CDATA[Working with users during the design process will untie project knots and boost team productivity and focus.  But there always seems to be an excuse for not testing.  Here are 4 ways to counter the excuses and make usability testing happen.
Excuse 1: &#8220;It&#8217;ll slow us down&#8221;
Finding users, building prototypes and working through hours [...]]]></description>
			<content:encoded><![CDATA[]]></content:encoded>
			<wfw:commentRss>http://fronttoback.org/2010/01/20/4-ways-to-combat-usability-testing-avoidance/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Design the stakeholder experience</title>
		<link>http://fronttoback.org/2009/08/20/design-the-stakeholder-experience/</link>
		<comments>http://fronttoback.org/2009/08/20/design-the-stakeholder-experience/#comments</comments>
		<pubDate>Thu, 20 Aug 2009 21:08:44 +0000</pubDate>
		<dc:creator>philbuk</dc:creator>
				<category><![CDATA[Interaction design]]></category>
		<category><![CDATA[Survival tactics]]></category>
		<category><![CDATA[User centred organisations]]></category>
		<category><![CDATA[User experience]]></category>

		<guid isPermaLink="false">http://fronttoback.org/2009/08/20/design-the-stakeholder-experience/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[]]></content:encoded>
			<wfw:commentRss>http://fronttoback.org/2009/08/20/design-the-stakeholder-experience/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Three blades to Occam&#8217;s Razor</title>
		<link>http://fronttoback.org/2009/04/23/three-blades-to-occams-razor/</link>
		<comments>http://fronttoback.org/2009/04/23/three-blades-to-occams-razor/#comments</comments>
		<pubDate>Thu, 23 Apr 2009 08:45:20 +0000</pubDate>
		<dc:creator>philbuk</dc:creator>
				<category><![CDATA[ForFlowThinkBlog]]></category>
		<category><![CDATA[Interaction design]]></category>
		<category><![CDATA[Survival tactics]]></category>

		<guid isPermaLink="false">http://fronttoback.org/2009/04/23/three-blades-to-occams-razor/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[]]></content:encoded>
			<wfw:commentRss>http://fronttoback.org/2009/04/23/three-blades-to-occams-razor/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
