<?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>User Experience NZ</title>
	<atom:link href="http://www.userexperience.co.nz/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.userexperience.co.nz</link>
	<description>Observing, exploring and discussing UX in New Zealand</description>
	<lastBuildDate>Mon, 05 Jul 2010 08:12:31 +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>UX research. Making every minute count</title>
		<link>http://www.userexperience.co.nz/2010/07/ux-research-making-every-minute-count/</link>
		<comments>http://www.userexperience.co.nz/2010/07/ux-research-making-every-minute-count/#comments</comments>
		<pubDate>Mon, 05 Jul 2010 08:12:31 +0000</pubDate>
		<dc:creator>Nick</dc:creator>
				<category><![CDATA[Design research]]></category>
		<category><![CDATA[Number 8 wire]]></category>
		<category><![CDATA[UX methods]]></category>
		<category><![CDATA[User research]]></category>

		<guid isPermaLink="false">http://www.userexperience.co.nz/?p=474</guid>
		<description><![CDATA[
Facilitating ‘face to face’ interviews with your clients’ customers is central to UX research. It’s also one of the most difficult of all UX skills to develop.
Valuable insights can be generated and captured during each session but you’re often having to cover a lot of ground in the time allocated.
After hundreds of these sessions I [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignleft size-full wp-image-476" title="ux-research-interview-clock" src="http://www.userexperience.co.nz/wp-content/uploads/2010/07/ux-research-interview-clock.jpg" alt="ux-research-interview-clock" width="455" height="238" /></p>
<p>Facilitating ‘face to face’ interviews with your clients’ customers is central to UX research. It’s also one of the most difficult of all UX skills to develop.</p>
<p>Valuable insights can be generated and captured during each session but you’re often having to cover a lot of ground in the time allocated.</p>
<p>After hundreds of these sessions I still find myself so deeply immersed in observing the participant’s experience of the product that it’s easy to lose track of these precious minutes, dwelling on one activity or area of focus at the expense of another.</p>
<p>I thought I’d share this very simple tool to help keep track of time and make the most of every minute of these sessions. It’s basically a modified clock face.</p>
<p>Grab yourself a wall clock and cut out a new paper face. Cut a slit from the edge to the centre so it can be slipped around the arms of the clock. Mark and name your time allocations on the new face.<br />
At the beginning of each session, just wind the minute hand back to the start and you’re on your way.</p>
<p>For a 90 minute session mark the segments on a spiral going inward, like in the picture of this one I used recently. Oh, and I removed the hour and second hands too.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.userexperience.co.nz/2010/07/ux-research-making-every-minute-count/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Tune in to customer behaviour, or you&#8217;re buggered</title>
		<link>http://www.userexperience.co.nz/2010/06/tune-in-to-customer-behaviour-or-youre-buggered/</link>
		<comments>http://www.userexperience.co.nz/2010/06/tune-in-to-customer-behaviour-or-youre-buggered/#comments</comments>
		<pubDate>Mon, 31 May 2010 20:38:24 +0000</pubDate>
		<dc:creator>Nick</dc:creator>
				<category><![CDATA[Behaviours]]></category>
		<category><![CDATA[Customer experience]]></category>
		<category><![CDATA[Insights]]></category>
		<category><![CDATA[New Zealand]]></category>

		<guid isPermaLink="false">http://www.userexperience.co.nz/?p=459</guid>
		<description><![CDATA[
With technology and the way we consume all types of media advancing at a blinding pace, following changes in behaviours, motivations and expectations of customers plays a critical part in informing and providing a great user experience.
It’s nice to think we kiwis are up to date when it comes to technology and that our media [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignleft size-full wp-image-463" title="Process from an ethnographic study to understand media use in early adopters." src="http://www.userexperience.co.nz/wp-content/uploads/2010/06/Media-use-ethnography.jpg" alt="Process from an ethnographic study to understand media use in early adopters." width="455" height="110" /><br />
With technology and the way we consume all types of media advancing at a blinding pace, following changes in behaviours, motivations and expectations of customers plays a critical part in informing and providing a great user experience.</p>
<p>It’s nice to think we kiwis are up to date when it comes to technology and that our media providers are armed with this rich customer insight, but in a weekend radio show some TV folk discussed <a title="MP3 audio file from Radio New Zealand Morning Report." href="http://podcast.radionz.co.nz/mnr/mnr-20100528-0852-Challenges_ahead_for_New_Zealand_as_50th_anniversary_looms-048.mp3">the future of TV in NZ</a>.</p>
<p>TV3 have this to say:</p>
<blockquote><p>“TV companies have not yet cottoned-on to the internet generation&#8217;s wavelength.</p>
<p>We haven’t caught up with them yet … with their understanding of technology… their understanding of the process.</p>
<p>The world is SO different and <strong>I’m buggered if I know</strong> how we respond to that&#8221;.</p></blockquote>
<p>mmm, Well &#8230;now I’m not so sure.</p>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow: hidden;"><!--[if gte mso 9]><xml> <o:OfficeDocumentSettings> <o:RelyOnVML /> <o:AllowPNG /> </o:OfficeDocumentSettings> </xml><![endif]--><!--[if gte mso 9]><xml> <w:WordDocument> <w:View>Normal</w:View> <w:Zoom>0</w:Zoom> <w:TrackMoves /> <w:TrackFormatting /> <w:PunctuationKerning /> <w:ValidateAgainstSchemas /> <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid> <w:IgnoreMixedContent>false</w:IgnoreMixedContent> <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText> <w:DoNotPromoteQF /> <w:LidThemeOther>EN-US</w:LidThemeOther> <w:LidThemeAsian>X-NONE</w:LidThemeAsian> <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript> <w:Compatibility> <w:BreakWrappedTables /> <w:SnapToGridInCell /> <w:WrapTextWithPunct /> <w:UseAsianBreakRules /> <w:DontGrowAutofit /> <w:SplitPgBreakAndParaMark /> <w:DontVertAlignCellWithSp /> <w:DontBreakConstrainedForcedTables /> <w:DontVertAlignInTxbx /> <w:Word11KerningPairs /> <w:CachedColBalance /> <w:UseFELayout /> </w:Compatibility> <m:mathPr> <m:mathFont m:val="Cambria Math" /> <m:brkBin m:val="before" /> <m:brkBinSub m:val=" " /> <m:smallFrac m:val="off" /> <m:dispDef /> <m:lMargin m:val="0" /> <m:rMargin m:val="0" /> <m:defJc m:val="centerGroup" /> <m:wrapIndent m:val="1440" /> <m:intLim m:val="subSup" /> <m:naryLim m:val="undOvr" /> </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"   DefSemiHidden="true" DefQFormat="false" DefPriority="99"   LatentStyleCount="267"> <w:LsdException Locked="false" Priority="0" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Normal" /> <w:LsdException Locked="false" Priority="9" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="heading 1" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9" /> <w:LsdException Locked="false" Priority="39" Name="toc 1" /> <w:LsdException Locked="false" Priority="39" Name="toc 2" /> <w:LsdException Locked="false" Priority="39" Name="toc 3" /> <w:LsdException Locked="false" Priority="39" Name="toc 4" /> <w:LsdException Locked="false" Priority="39" Name="toc 5" /> <w:LsdException Locked="false" Priority="39" Name="toc 6" /> <w:LsdException Locked="false" Priority="39" Name="toc 7" /> <w:LsdException Locked="false" Priority="39" Name="toc 8" /> <w:LsdException Locked="false" Priority="39" Name="toc 9" /> <w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption" /> <w:LsdException Locked="false" Priority="10" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Title" /> <w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font" /> <w:LsdException Locked="false" Priority="11" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtitle" /> <w:LsdException Locked="false" Priority="22" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Strong" /> <w:LsdException Locked="false" Priority="20" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Emphasis" /> <w:LsdException Locked="false" Priority="59" SemiHidden="false"    UnhideWhenUsed="false" Name="Table Grid" /> <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text" /> <w:LsdException Locked="false" Priority="1" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="No Spacing" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 1" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 1" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 1" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 1" /> <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision" /> <w:LsdException Locked="false" Priority="34" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="List Paragraph" /> <w:LsdException Locked="false" Priority="29" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Quote" /> <w:LsdException Locked="false" Priority="30" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Quote" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 1" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 1" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 1" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 1" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 1" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 2" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 2" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 2" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 2" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 2" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 2" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 2" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 2" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 2" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 3" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 3" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 3" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 3" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 3" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 3" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 3" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 3" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 3" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 4" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 4" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 4" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 4" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 4" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 4" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 4" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 4" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 4" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 5" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 5" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 5" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 5" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 5" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 5" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 5" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 5" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 5" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 6" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 6" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 6" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 6" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 6" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 6" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 6" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 6" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 6" /> <w:LsdException Locked="false" Priority="19" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis" /> <w:LsdException Locked="false" Priority="21" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis" /> <w:LsdException Locked="false" Priority="31" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference" /> <w:LsdException Locked="false" Priority="32" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Reference" /> <w:LsdException Locked="false" Priority="33" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Book Title" /> <w:LsdException Locked="false" Priority="37" Name="Bibliography" /> <w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading" /> </w:LatentStyles> </xml><![endif]--><!--  /* Font Definitions */  @font-face 	{font-family:"Cambria Math"; 	panose-1:2 4 5 3 5 4 6 3 2 4; 	mso-font-charset:1; 	mso-generic-font-family:roman; 	mso-font-format:other; 	mso-font-pitch:variable; 	mso-font-signature:0 0 0 0 0 0;} @font-face 	{font-family:Calibri; 	panose-1:2 15 5 2 2 2 4 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:swiss; 	mso-font-pitch:variable; 	mso-font-signature:-1610611985 1073750139 0 0 159 0;}  /* Style Definitions */  p.MsoNormal, li.MsoNormal, div.MsoNormal 	{mso-style-unhide:no; 	mso-style-qformat:yes; 	mso-style-parent:""; 	margin-top:0cm; 	margin-right:0cm; 	margin-bottom:10.0pt; 	margin-left:0cm; 	line-height:115%; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Calibri","sans-serif"; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:"Times New Roman"; 	mso-fareast-theme-font:minor-fareast; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} .MsoChpDefault 	{mso-style-type:export-only; 	mso-default-props:yes; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:"Times New Roman"; 	mso-fareast-theme-font:minor-fareast; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} .MsoPapDefault 	{mso-style-type:export-only; 	margin-bottom:10.0pt; 	line-height:115%;} @page Section1 	{size:612.0pt 792.0pt; 	margin:72.0pt 72.0pt 72.0pt 72.0pt; 	mso-header-margin:36.0pt; 	mso-footer-margin:36.0pt; 	mso-paper-source:0;} div.Section1 	{page:Section1;} --><!--[if gte mso 10]> <mce:style><!   /* Style Definitions */  table.MsoNormalTable 	{mso-style-name:"Table Normal"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	mso-style-noshow:yes; 	mso-style-priority:99; 	mso-style-qformat:yes; 	mso-style-parent:""; 	mso-padding-alt:0cm 5.4pt 0cm 5.4pt; 	mso-para-margin-top:0cm; 	mso-para-margin-right:0cm; 	mso-para-margin-bottom:10.0pt; 	mso-para-margin-left:0cm; 	line-height:115%; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Calibri","sans-serif"; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin;} --> <!--[endif]--></p>
<p class="MsoNormal"><span lang="EN-GB">With technology and the way we consume this media advancing at a blinding pace, following changes in behaviours, motivations and expectations of customers plays a critical part in informing and providing a great user experience. </span></p>
<p class="MsoNormal"><span lang="EN-GB">It’s nice to think we kiwis are up to date when it comes to technology and that our media providers are armed with this rich customer insight, but in a weekend radio show some TV folk discussed the future of TV in NZ. Well…now I’m not so sure.</span></p>
<p class="MsoNormal"><span lang="EN-GB">TV3 have this to say<span style="color: red;"> “TV companies have not yet cottoned on to the internet generations wavelength”</span></span></p>
<p class="MsoNormal"><span style="color: red;" lang="EN-GB">“We haven’t caught up with them yet … with their understanding of technology… their understanding of the process. The world is SO different and I’m buggered if I know how we respond to that.</span></p>
</div>
]]></content:encoded>
			<wfw:commentRss>http://www.userexperience.co.nz/2010/06/tune-in-to-customer-behaviour-or-youre-buggered/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
<enclosure url="http://podcast.radionz.co.nz/mnr/mnr-20100528-0852-Challenges_ahead_for_New_Zealand_as_50th_anniversary_looms-048.mp3" length="1522688" type="audio/mpeg" />
		</item>
		<item>
		<title>Apology, or invitation. What’s your message?</title>
		<link>http://www.userexperience.co.nz/2010/05/apology-or-invitation-what%e2%80%99s-your-message/</link>
		<comments>http://www.userexperience.co.nz/2010/05/apology-or-invitation-what%e2%80%99s-your-message/#comments</comments>
		<pubDate>Sun, 23 May 2010 20:33:43 +0000</pubDate>
		<dc:creator>Nick</dc:creator>
				<category><![CDATA[Customer experience]]></category>
		<category><![CDATA[Observations]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[User research]]></category>

		<guid isPermaLink="false">http://www.userexperience.co.nz/?p=443</guid>
		<description><![CDATA[
If this were a checkout operator speaking to you, which would you think  was most friendly and helpful?
Two signs; Same context, audience and purpose. More design effort has gone into one, but it is the choice of words here which has the most impact on the message they convey.
So when it comes to fine [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignleft size-full wp-image-442" title="Are you being served?" src="http://www.userexperience.co.nz/wp-content/uploads/2010/05/customer-touchpoint-messagi.jpg" alt="Are you being served?" width="455" height="196" /></p>
<p><strong>If this were a checkout operator speaking to you, which would you think  was most friendly and helpful?</strong></p>
<p>Two signs; Same context, audience and purpose. More design effort has gone into one, but it is the choice of words here which has the most impact on the message they convey.</p>
<p>So when it comes to fine tuning a digital user interface, why is there such a focus on graphic interaction design elements, often tweaked to the nearest pixel with less importance given to copy and messaging?</p>
<p>Refreshingly, a recent website usability project came from the opposite angle. My client had accepted they were <a title="A previous blog post explaining the curse of getting too close to your project." href="http://www.userexperience.co.nz/2009/03/a-aign-your-user-experience-needs-a-reality-check/">deeply immersed in the technical nature of their product </a>and their way of communicating it was out-of-whack with terms their target market would relate to.</p>
<p>The team realised that regardless how perfectly their visual design and site architecture presented their product, it was the words they used to communicate their product which would make it fly…. Or not.</p>
<p>Working with a <a title="Techical copywriter who understands UX and Interface Design." href="http://www.taylfin.com/">technical copywriter</a> we were able to identify phrases which really resonated with people, which to avoid and critically, what copy should be ‘front and centre’ to engage and convert potential customers.</p>
<p>During the flow of research participants, we made copy changes on the fly, gaining immediate reaction to provide a rapid cycle of improvement.</p>
<p>As well as taking us down the path of making sense and talking people’s language, it was a strong lesson to get rid of that ‘lorem ipsum’ placeholder text as early as possible when getting feedback from customers.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.userexperience.co.nz/2010/05/apology-or-invitation-what%e2%80%99s-your-message/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Skype takes the hassle out of remote usability</title>
		<link>http://www.userexperience.co.nz/2010/05/skype-takes-the-hassle-out-of-remote-usability/</link>
		<comments>http://www.userexperience.co.nz/2010/05/skype-takes-the-hassle-out-of-remote-usability/#comments</comments>
		<pubDate>Sun, 09 May 2010 19:57:31 +0000</pubDate>
		<dc:creator>Nick</dc:creator>
				<category><![CDATA[Customer experience]]></category>
		<category><![CDATA[Design research]]></category>
		<category><![CDATA[Empathy]]></category>
		<category><![CDATA[New Zealand]]></category>
		<category><![CDATA[UX methods]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[User research]]></category>

		<guid isPermaLink="false">http://www.userexperience.co.nz/?p=427</guid>
		<description><![CDATA[Remote research brings cultural relevance to usability findings, providing the kinds of insights which can only be gained by being there…virtually at least.
I recently ran some remote website usability sessions for a Kiwi startup whose main customer is in the U.S.A. &#8230; sure, &#8216;isolation breeds innovation&#8217; and all that, but when your customers are on [...]]]></description>
			<content:encoded><![CDATA[<p>Remote research brings cultural relevance to usability findings, providing the kinds of insights which can only be gained by being there…virtually at least.</p>
<p>I recently ran some remote website usability sessions for a Kiwi startup whose main customer is in the U.S.A. &#8230; sure, &#8216;isolation breeds innovation&#8217; and all that, but when your customers are on the other side of the world, it’s vital that  your product connects with them.</p>
<p>A fun project, but choosing which software to run during the sessions was a headache… There’s a boggling number of <a title="25 Remote usability tools for your confusing perusal" href="http://remoteusability.com/tools/">services to choose from</a> (25 on this link) and there’s no clear winner.</p>
<p>After some experimenting, I went with Skype and it did the job nicely.<br />
Here are some benefits over paid and more sophisticated software I&#8217;ve used previously:</p>
<ul>
<li>It’s easy to recruit participants who already use Skype</li>
<li>Familiarity means no learning curve for you or participants</li>
<li>No install means no wasting valuable session time setting-up</li>
<li>Sending links and files is instant with built-in messaging</li>
<li>It’s possible to make contact with participants prior to the session</li>
<li>It’s free, so that’s hard to argue with</li>
</ul>
<p>During the sessions, I was able to video chat with the participant for a while, then fire up <a title="Apparently this is a seldomly used feature of Skype" href="http://www.skype.com/intl/en-us/features/allfeatures/screensharing/">Skype’s screen-sharing tool</a>, so I could observe their movements on the website while  hearing their thoughts and reactions etc.</p>
<p>Skype’s screen-sharing only works between two computers so if you have clients observing, this will have to be through an external monitor (Make sure they are sitting out of view of your webcam and preferably out of earshot).</p>
<p>The project generated rich insights and shaped the design process moving forward.<br />
I’d definitely use Skype for this again, but would love to hear from anyone who’s used anything else with success.</p>
<p>I also had Adobe Connect recommended …anyone tried that?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.userexperience.co.nz/2010/05/skype-takes-the-hassle-out-of-remote-usability/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Keeping it ‘old school’ with Diary Studies</title>
		<link>http://www.userexperience.co.nz/2010/04/keeping-it-%e2%80%98old-school%e2%80%99-with-diary-studies/</link>
		<comments>http://www.userexperience.co.nz/2010/04/keeping-it-%e2%80%98old-school%e2%80%99-with-diary-studies/#comments</comments>
		<pubDate>Mon, 05 Apr 2010 20:24:25 +0000</pubDate>
		<dc:creator>Nick</dc:creator>
				<category><![CDATA[Customer experience]]></category>
		<category><![CDATA[Design research]]></category>
		<category><![CDATA[UX methods]]></category>
		<category><![CDATA[User research]]></category>

		<guid isPermaLink="false">http://www.userexperience.co.nz/?p=413</guid>
		<description><![CDATA[I’m always looking for better ways to understand customer behaviour and the experiences customers have in their own context, out in the wild.
There are some interesting ‘digital ethnography’ tools on the market, using web and mobile channels to capture, collate and filter all this stuff as it occurs in the field.
http://www.myservicefellow.com
http://www.thethinkingshed.co.uk
http://www.7daysinmylife.com
Impressive technology, but ‘whizz-bang’ isn’t [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignleft size-full wp-image-418" title="user-experience-diary-study" src="http://www.userexperience.co.nz/wp-content/uploads/2010/04/user-experience-diary-study.jpg" alt="user-experience-diary-study" width="455" height="207" />I’m always looking for better ways to understand customer behaviour and the experiences customers have in their own context, out in the wild.</p>
<p>There are some interesting ‘digital ethnography’ tools on the market, using web and mobile channels to capture, collate and filter all this stuff as it occurs in the field.</p>
<p><a href="http://www.myservicefellow.com">http://www.myservicefellow.com</a><br />
<a href="http://www.thethinkingshed.co.uk">http://www.thethinkingshed.co.uk</a><br />
<a href="http://www.7daysinmylife.com">http://www.7daysinmylife.com</a></p>
<p>Impressive technology, but <strong>‘whizz-bang’ isn’t always the answer</strong>. I stuck to the traditional pen and paper approach for a diary study recently and am I’m pleased I did.</p>
<p><span style="color: #808080;">For the uninitiated, diary studies in UX are a qualitative research method where participants record events, interactions, attitudes etc. in diary format over days or weeks. They are a great way to study customer behaviours in the context using a product or service over time, as opposed to during a 60 minute usability-style interview.</span></p>
<p>In my study for example, I was interested in how and where people used a portable device in their day to day activities and how well it performed in each situation</p>
<p>Here are some ways I feel <strong>the old-school method holds its’ own</strong>:</p>
<p><strong>It’s human</strong><br />
No learning curve, no teething problems. Paper and pen doesn’t require login details, needs almost no instructions, is ultra portable, and doesn’t rely on web or mobile coverage. Participants don’t have to think about or remember anything other than jotting down their thoughts.</p>
<p><strong>It’s flexible</strong><br />
Photos are great, and really help to add context, but I’m always amazed at how pictorial some people make their diary notes. Sketching and doodling on a blank sheet of paper is always going to win over an online text-entry box.</p>
<p><strong>‘till the fat lady sings</strong><br />
The real gems from these studies emerge in the exit interview with each participant. When they&#8217;re looking back over their own handwriting, these paper diaries transport people back to those moments in time, where you can access the rich detail needed to paint the full picture.</p>
<p><strong>It’s immersive</strong><br />
I love the process of pinning-up diary data around a room.<br />
Having met each participant, built rapport and empathy, this is somehow retained when you’re surrounded in their scrawl. All those attitudes and responses pop back in your mind, help you get into their character, see things through their eyes and in relation to their context.</p>
<p>When the right type of project comes along, I’ll give the ‘digital ethnography’ tools a shot, but until then, I know I’ve got paper.</p>
<p>Even so …I’d love to hear from someone who’s run an ethno project using any of these tools.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.userexperience.co.nz/2010/04/keeping-it-%e2%80%98old-school%e2%80%99-with-diary-studies/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>User Centred Design, for the long haul.</title>
		<link>http://www.userexperience.co.nz/2010/03/user-centred-design-for-the-long-haul/</link>
		<comments>http://www.userexperience.co.nz/2010/03/user-centred-design-for-the-long-haul/#comments</comments>
		<pubDate>Sun, 07 Mar 2010 19:14:04 +0000</pubDate>
		<dc:creator>Nick</dc:creator>
				<category><![CDATA[Design research]]></category>
		<category><![CDATA[Innovation]]></category>
		<category><![CDATA[Insights]]></category>
		<category><![CDATA[New Zealand]]></category>
		<category><![CDATA[UX methods]]></category>
		<category><![CDATA[User Centered Design]]></category>

		<guid isPermaLink="false">http://www.userexperience.co.nz/?p=401</guid>
		<description><![CDATA[
During a 9 month project with IDEO, Air New Zealand took a user centred approach to improve seating design for their long haul services. They built full scale prototypes of cabin interiors to carry out design research, evaluating seating and service concepts with real passengers.
The project began in 2007 with a goal of understanding passenger [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignleft size-full wp-image-402" title="air-new-zealand-user centred design of seating." src="http://www.userexperience.co.nz/wp-content/uploads/2010/03/air-new-zealand-ideo-ucd.jpg" alt="air-new-zealand-user centred design of seating." width="455" height="205" /></p>
<p>During a 9 month project with IDEO, Air New Zealand took a user centred approach to improve seating design for their long haul services. They built full scale prototypes of cabin interiors to carry out design research, evaluating seating and service concepts with real passengers.</p>
<p>The project began in 2007 with a goal of understanding passenger needs during long haul flights. Following extensive interviewing of passengers and flight attendants, a design team built seat concepts from polystyrene and cardboard.</p>
<p>Paid actors, as well as customers sat (or lay) through three hour research sessions simulating the in-flight experience. The actors were included to enhance the sense of realism, in addition to engine noise and full cabin service.</p>
<p><img class="alignleft size-full wp-image-403" title="air-new-zealand-ideo-design research" src="http://www.userexperience.co.nz/wp-content/uploads/2010/03/air-new-zealand-ideo-ucd1.jpg" alt="air-new-zealand-ideo-design research" width="455" height="194" /></p>
<p>Finding a point of difference is a challenge for airlines. While Qantas’ recent design efforts focussed on the aesthetic, commissioning Marc Newson to add a layer of style to the A380 interior, Air New Zealand choose to tackle the challenge from the customer’s viewpoint, leaving style out of the question until the functionality was humming.</p>
<p>As well as researching the way passengers used the seating concepts, a ‘fresh eyes’ approach was taken when selecting a design team. Air New Zealand opted to work with industrial designers who had ergonomics experience, but were new to airline seating, avoid preconceptions, maximising  freedom to take risks and innovate.</p>
<p>A groundbreaking three year project with User Centred Design at the heart, resulting in true innovation based on fresh thinking and real customer insight.</p>
<p>What a dream project.</p>
<p><a href="http://www.futuretakingflight.com/#/the-design-story">Watch an unexpectedly cheesy 2min video which will give you some glimpses into the process.</a></p>
<p><a href="http://www.futuretakingflight.com/#/home">View the website created to showcase the new seating types</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.userexperience.co.nz/2010/03/user-centred-design-for-the-long-haul/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>The tip of the User Experience iceberg</title>
		<link>http://www.userexperience.co.nz/2010/03/the-tip-of-the-user-experience-iceberg/</link>
		<comments>http://www.userexperience.co.nz/2010/03/the-tip-of-the-user-experience-iceberg/#comments</comments>
		<pubDate>Sun, 28 Feb 2010 21:07:04 +0000</pubDate>
		<dc:creator>Nick</dc:creator>
				<category><![CDATA[Customer experience]]></category>
		<category><![CDATA[Interactions]]></category>
		<category><![CDATA[New Zealand]]></category>
		<category><![CDATA[Observations]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[User Experience]]></category>

		<guid isPermaLink="false">http://www.userexperience.co.nz/?p=393</guid>
		<description><![CDATA[Some websites provide more of an experience than others, but the number of web agencies and even individuals who offer User Experience in their list of ‘services’ indicates there’s a chunk of lip-service being paid to what has become an almost industry-specific buzzword.
Although many techniques and approaches to UX have been honed and made popular [...]]]></description>
			<content:encoded><![CDATA[<p>Some websites provide more of an experience than others, but the number of web agencies and even individuals who offer User Experience in their list of ‘services’ indicates there’s a chunk of lip-service being paid to what has become an almost industry-specific buzzword.</p>
<p>Although many techniques and approaches to UX have been honed and made popular during online projects, if New Zealand businesses associate User Experience only with making a well considered website, the power of taking a user-centred approach will be diluted and practitioners risk limited uptake from business in the design/research/strategy of their other channels and customer touch-points.</p>
<p>There’s so much more ground to cover and value to offer away from the web and I hope I’m not alone in my ideal that businesses and organisations should involve customers in the planning and design of all facets they interact with, on and offline, physical and virtual.</p>
<p>Tell me I’m not alone…</p>
]]></content:encoded>
			<wfw:commentRss>http://www.userexperience.co.nz/2010/03/the-tip-of-the-user-experience-iceberg/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>When less is less and more is too much.</title>
		<link>http://www.userexperience.co.nz/2010/01/when-less-is-not-more-and-more-is-too-much/</link>
		<comments>http://www.userexperience.co.nz/2010/01/when-less-is-not-more-and-more-is-too-much/#comments</comments>
		<pubDate>Sun, 24 Jan 2010 21:09:59 +0000</pubDate>
		<dc:creator>Nick</dc:creator>
				<category><![CDATA[Behaviours]]></category>
		<category><![CDATA[Design research]]></category>
		<category><![CDATA[Insights]]></category>
		<category><![CDATA[Observations]]></category>
		<category><![CDATA[User Centered Design]]></category>
		<category><![CDATA[User research]]></category>

		<guid isPermaLink="false">http://www.userexperience.co.nz/?p=376</guid>
		<description><![CDATA[This Honda trunk-lid has been simplified and streamlined so much that the owner has crudely screwed on a &#8216;hardware store&#8217; handle to make it easier to use.
This Mazda door entry has gone the other way by adding complexity; a key-code entry, which looked to me like it had never been touched, whereas the standard key-hole [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignleft size-full wp-image-377" title="Honda. Door handles optional" src="http://www.userexperience.co.nz/wp-content/uploads/2010/01/honda-door-handle.jpg" alt="Honda. Door handles optional" width="455" height="200" />This Honda trunk-lid has been <strong>simplified and streamlined</strong> so much that the owner has crudely screwed on a &#8216;hardware store&#8217; handle to make it easier to use.</p>
<p><img class="alignleft size-full wp-image-378" title="Mazda. Where is the 'forgot pin' button?" src="http://www.userexperience.co.nz/wp-content/uploads/2010/01/mazda-door-handle.jpg" alt="Mazda. Where is the 'forgot pin' button?" width="455" height="200" />This Mazda door entry has gone the other way by <strong>adding complexity;</strong> a key-code entry, which looked to me like it had never been touched, whereas the standard key-hole had seen plenty of action.</p>
<p><strong>Less features or more?</strong><br />
Your new product needs a point of difference in a crowded market, but there’s a fine balance between adding features and taking them away.</p>
<p><strong>The</strong><strong> key to this balance lies in how useful and intuitive it is for the end user</strong>.<br />
In these examples, the product teams have gone out of their way to either simplify or complicate a conventional and accepted way to open a car door, at great cost to the carmaker, and with no benefit for the end user.<br />
<strong>So, how can you tell which way to go?</strong></p>
<ul>
<li> When does more become too much, and less not enough?</li>
<li>At what point does the investment your customer has to make in adapting their behaviour to a new design outweigh its benefits?</li>
<li>Exactly how minimal can you go when stripping back those features to make your customer use your product without having to think about it?</li>
</ul>
<p><strong>User research</strong><br />
We can get a good feel for where this balance lies by watching the way people use existing products and prototypes of new ones, gaining an understanding of what they need and don’t need, what works for them and what doesn&#8217;t.<br />
If either of these two carmakers had spent time watching their customers use a prototype of these products they would never have made it to market.</p>
<p>…or perhaps Honda just wanted to sell <strong>door-handles as a premium accessory?</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://www.userexperience.co.nz/2010/01/when-less-is-not-more-and-more-is-too-much/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Picture, or thousand words?</title>
		<link>http://www.userexperience.co.nz/2010/01/picture-or-thousand-words/</link>
		<comments>http://www.userexperience.co.nz/2010/01/picture-or-thousand-words/#comments</comments>
		<pubDate>Sun, 10 Jan 2010 09:04:18 +0000</pubDate>
		<dc:creator>Nick</dc:creator>
				<category><![CDATA[Design research]]></category>
		<category><![CDATA[UX methods]]></category>
		<category><![CDATA[User Centered Design]]></category>
		<category><![CDATA[User research]]></category>

		<guid isPermaLink="false">http://www.userexperience.co.nz/?p=366</guid>
		<description><![CDATA[Outcomes of UX research projects can be difficult to put in a nutshell, and a bullet pointed list sometimes just does not cut it.
As well as the usual deliverables emerging from a brief, I sometimes add a rich picture as a visual summary. These often originate from doodles generated while I’m trying to figure out [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.bowmast.com"><img class="alignleft size-full wp-image-367" title="design-research-process" src="http://www.userexperience.co.nz/wp-content/uploads/2010/01/design-research-process.jpg" alt="design-research-process" width="455" height="191" /></a>Outcomes of UX research projects can be difficult to put in a nutshell, and <strong>a bullet pointed list sometimes just does not cut it</strong>.</p>
<p>As well as the usual deliverables emerging from a brief, I sometimes <strong>add a rich picture as a visual summary</strong>. These often originate from doodles generated while I’m trying to figure out relationships or flow between elements of a process etc.</p>
<p>What starts out as a way for me to make sense of a complex landscape often grows into <strong>an important tool to communicate</strong> this to client teams.</p>
<p>The ability of these info-graphics to engage people often amazes me, with <strong>the drawing sometimes becoming the focal point </strong>of discussion, receiving more attention and air time than the agreed deliverable.</p>
<p>This week my consultancy website <a title="Bowmast Consulting. User Experience &amp; Design Research" href="http://www.bowmast.com">www.bowmast.com</a> turned <strong>10 years old</strong> so I gave it a refresh.<br />
Out of my doodles came a drawing attempting to summarise <strong>the design research process as I see it.</strong><br />
It’s on the<a href="http://www.bowmast.com" target="_blank"> home page</a> if you fancy a gander.</p>
<p><strong>Happy Twenty-Ten to you all.</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://www.userexperience.co.nz/2010/01/picture-or-thousand-words/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Air New Zealand listens to customers. Or do they?</title>
		<link>http://www.userexperience.co.nz/2009/10/air-new-zealand-listens-to-customers-or-do-they/</link>
		<comments>http://www.userexperience.co.nz/2009/10/air-new-zealand-listens-to-customers-or-do-they/#comments</comments>
		<pubDate>Mon, 26 Oct 2009 04:37:25 +0000</pubDate>
		<dc:creator>Nick</dc:creator>
				<category><![CDATA[Customer experience]]></category>
		<category><![CDATA[Insights]]></category>
		<category><![CDATA[New Zealand]]></category>
		<category><![CDATA[User Experience]]></category>

		<guid isPermaLink="false">http://www.userexperience.co.nz/?p=340</guid>
		<description><![CDATA[
A UK based Air New Zealand campaign highlights the attitude and friendliness of cabin crew as something uniquely kiwi.  The idea for the campaign was apparently inspired by a passenger’s tweet;

… but given that the tweeter is a London-based digital marketing consultant who’s own website has a page of  “10 reasons why you should engage [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.youtube.com/watch?v=EyoiOUiAJ3o&amp;feature=related"><img class="alignleft size-full wp-image-343" title="Watch campaign clip on YouTube" src="http://www.userexperience.co.nz/wp-content/uploads/2009/10/air-new-zealand-personality1.jpg" alt="Watch campaign clip on YouTube" width="455" height="190" /></a></p>
<p>A UK based Air New Zealand campaign highlights the attitude and friendliness of cabin crew as something uniquely kiwi.  The idea for the campaign was apparently inspired by a passenger’s tweet;</p>
<p><img class="alignleft size-full wp-image-350" title="air-new-zealand-tweet" src="http://www.userexperience.co.nz/wp-content/uploads/2009/10/air-new-zealand-tweet1.jpg" alt="air-new-zealand-tweet" width="455" height="42" /></p>
<p>… but given that the tweeter is a London-based digital marketing consultant who’s own website has a page of  “10 reasons why you should <a title="Link to the Tweeter's website and 10 reasons page" href="http://www.deviceteam.com/index.php?option=com_content&amp;view=article&amp;id=103&amp;Itemid=66 " target="_blank">engage your customers</a> in an online conversation”</p>
<p>…I’ll let <strong>you be the judge</strong> of how genuine this is.</p>
<p>Customer blogs and tweets about your product can act as a great barometer of how your customers perceive your product or service.</p>
<p>With most airlines competing on price, this campaign shows <strong>Air New Zealand as being responsive to customer feedback, and focused on the in-flight passenger experience.</strong></p>
<p>When you look at the <strong>dozens of touch-points involved in a travel experience</strong>; research, planning, booking, in-airport routines, transfers and accommodation details that sandwich the actual flight, it can almost dwarf the on-board component of the passenger experience. Especially for short flights.</p>
<p>An Airline I worked with in the UK carried out an <strong>‘Experience evaluation’ seeing and measuring the entire process through a customer viewpoint;</strong> from the inspiration to take the trip, right through to uploading your photos when you’re home. By identifying which of the touch-points work well and which ones frustrate passengers, these airlines can <strong>identify ways to improve the passenger experience.</strong></p>
<p>This ‘personality allowed’ campaign is aimed at long haul flights where the actual flight is likely to be the memorable aspect, hopefully blanking your memory of the queues at immigration and perhaps even something worth shouting, or tweeting about.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.userexperience.co.nz/2009/10/air-new-zealand-listens-to-customers-or-do-they/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
