<?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: SpeechUsability</title>
	<atom:link href="http://paul-blunden.com/2008/06/08/speechusability/feed/" rel="self" type="application/rss+xml" />
	<link>http://paul-blunden.com/2008/06/08/speechusability/</link>
	<description>Thoughts about the future of customer experience</description>
	<pubDate>Sat, 22 Nov 2008 02:12:51 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John Hibel</title>
		<link>http://paul-blunden.com/2008/06/08/speechusability/#comment-27</link>
		<dc:creator>John Hibel</dc:creator>
		<pubDate>Thu, 04 Sep 2008 06:02:21 +0000</pubDate>
		<guid isPermaLink="false">http://blunden.wordpress.com/?p=66#comment-27</guid>
		<description>There are indeed a few small firms in the U.S. who focus on IVR usability.  I wish there were more.  I recently had dinner with a college roommate I hadn't seen in fifteen years.  We shared a laugh because he was now an executive at a tobacco company and I was an executive at an IVR company.  We couldn't decide whether it was worse to sell cancer sticks or to trap callers in inescapable IVR menus.  Both could lead to a premature and potentially painful death.  I had to explain that IVR technology isn't the problem- it is the proliferation of systems with poor usability design that creates those legendary customer experiences that turn into the butt of many jokes (I tried use tobacco lingo so he could understand.)  In many cases this happens because usability is either ignored or tacked on the tail end of a development project when it's too late to make anything more than minor tweaks in response to user feedback.  I strongly recommend engaging usability professionals and having them closely involved throughout the development process if you want to create an IVR user experience that puts the cancer sticks to shame! 

I apologize for being horribly late with this comment...but I just stumbled across your blog and enjoyed your posts, Paul.  

John Hibel (PSS)</description>
		<content:encoded><![CDATA[<p>There are indeed a few small firms in the U.S. who focus on IVR usability.  I wish there were more.  I recently had dinner with a college roommate I hadn&#8217;t seen in fifteen years.  We shared a laugh because he was now an executive at a tobacco company and I was an executive at an IVR company.  We couldn&#8217;t decide whether it was worse to sell cancer sticks or to trap callers in inescapable IVR menus.  Both could lead to a premature and potentially painful death.  I had to explain that IVR technology isn&#8217;t the problem- it is the proliferation of systems with poor usability design that creates those legendary customer experiences that turn into the butt of many jokes (I tried use tobacco lingo so he could understand.)  In many cases this happens because usability is either ignored or tacked on the tail end of a development project when it&#8217;s too late to make anything more than minor tweaks in response to user feedback.  I strongly recommend engaging usability professionals and having them closely involved throughout the development process if you want to create an IVR user experience that puts the cancer sticks to shame! </p>
<p>I apologize for being horribly late with this comment&#8230;but I just stumbled across your blog and enjoyed your posts, Paul.  </p>
<p>John Hibel (PSS)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
