<?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: Four VUI Lessons from Social Web Design Pitfalls</title>
	<atom:link href="http://www.vuidesign.net/four-vui-lessons-from-social-web-design-pitfalls.htm/feed" rel="self" type="application/rss+xml" />
	<link>http://www.vuidesign.net/four-vui-lessons-from-social-web-design-pitfalls.htm</link>
	<description>Interface Design Lessons From The World Around Us</description>
	<lastBuildDate>Thu, 25 Feb 2010 15:09:02 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: eolvera</title>
		<link>http://www.vuidesign.net/four-vui-lessons-from-social-web-design-pitfalls.htm/comment-page-1#comment-353</link>
		<dc:creator>eolvera</dc:creator>
		<pubDate>Fri, 15 Jun 2007 17:45:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.vuidesign.net/four-vui-lessons-from-social-web-design-pitfalls.htm#comment-353</guid>
		<description>Absolutely. But like you said, the current tuning methods aren&#039;t very efficient (compared to the almost immediate feedback you get from most website tuning tools) and require a significant amount of human intervention. But one of the things I suggest is maybe looking at other parameters that can be obtained automatically from the system (e.g. In-grammar rates, Accuracy rates, Confidence scores) and creating custom tracking mechanisms to measure whether a certain caller was successful or not at completing a certain tasks, so that the call flows themselves can dynamically adapt based on these results (results which can then be reviewed and analyzed during a full tuning)</description>
		<content:encoded><![CDATA[<p>Absolutely. But like you said, the current tuning methods aren&#8217;t very efficient (compared to the almost immediate feedback you get from most website tuning tools) and require a significant amount of human intervention. But one of the things I suggest is maybe looking at other parameters that can be obtained automatically from the system (e.g. In-grammar rates, Accuracy rates, Confidence scores) and creating custom tracking mechanisms to measure whether a certain caller was successful or not at completing a certain tasks, so that the call flows themselves can dynamically adapt based on these results (results which can then be reviewed and analyzed during a full tuning)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IanRae</title>
		<link>http://www.vuidesign.net/four-vui-lessons-from-social-web-design-pitfalls.htm/comment-page-1#comment-352</link>
		<dc:creator>IanRae</dc:creator>
		<pubDate>Fri, 15 Jun 2007 16:16:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.vuidesign.net/four-vui-lessons-from-social-web-design-pitfalls.htm#comment-352</guid>
		<description>#3 is a big issue with speech apps.  It&#039;s not just that post-deployment tuning is essential.  It&#039;s the way apps can be failing and no one knows about it.  Unless someone is monitoring completion rates, the system can be failing silently.  I blogged about this at (http://silentsoftware.blogspot.com/2006/08/you-cant-tune-silence.html), and suggested a temporary tuning mode that adjusts the recognition thresholds to force more confirmations, allowing the app to log the rejected values.</description>
		<content:encoded><![CDATA[<p>#3 is a big issue with speech apps.  It&#8217;s not just that post-deployment tuning is essential.  It&#8217;s the way apps can be failing and no one knows about it.  Unless someone is monitoring completion rates, the system can be failing silently.  I blogged about this at (<a href="http://silentsoftware.blogspot.com/2006/08/you-cant-tune-silence.html)" rel="nofollow">http://silentsoftware.blogspot.com/2006/08/you-cant-tune-silence.html)</a>, and suggested a temporary tuning mode that adjusts the recognition thresholds to force more confirmations, allowing the app to log the rejected values.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
