<?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"
	>
<channel>
	<title>Comments on: Frequently Urgent</title>
	<atom:link href="http://www.productbehavior.com/archive/frequently-urgent/feed" rel="self" type="application/rss+xml" />
	<link>http://www.productbehavior.com/archive/frequently-urgent</link>
	<description>Tell me about it.
</description>
	<pubDate>Fri, 05 Dec 2008 01:31:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Expressed And Implied &#124; Product Behavior</title>
		<link>http://www.productbehavior.com/archive/frequently-urgent#comment-109</link>
		<dc:creator>Expressed And Implied &#124; Product Behavior</dc:creator>
		<pubDate>Fri, 25 Apr 2008 13:36:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.productbehavior.com/?p=135#comment-109</guid>
		<description>[...] little more on Frequency and Urgency, which I wrote about last week. Clearly, using such a tool helps designers to prioritize the [...]</description>
		<content:encoded><![CDATA[<p>[...] little more on Frequency and Urgency, which I wrote about last week. Clearly, using such a tool helps designers to prioritize the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://www.productbehavior.com/archive/frequently-urgent#comment-108</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Wed, 23 Apr 2008 11:58:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.productbehavior.com/?p=135#comment-108</guid>
		<description>Sure. The changing relationship between user and product necessarily shifts the Kano model around, as the definitions of "needs" and "satisfaction" change over time. The Frequency/Urgency model can help the whole QFD process by demonstrating the need to include both "on the shelf" requirements and "after a year of use" requirements.</description>
		<content:encoded><![CDATA[<p>Sure. The changing relationship between user and product necessarily shifts the Kano model around, as the definitions of &#8220;needs&#8221; and &#8220;satisfaction&#8221; change over time. The Frequency/Urgency model can help the whole QFD process by demonstrating the need to include both &#8220;on the shelf&#8221; requirements and &#8220;after a year of use&#8221; requirements.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: khalil</title>
		<link>http://www.productbehavior.com/archive/frequently-urgent#comment-107</link>
		<dc:creator>khalil</dc:creator>
		<pubDate>Mon, 21 Apr 2008 11:05:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.productbehavior.com/?p=135#comment-107</guid>
		<description>Interesting. 
This could be merged with the Kano model.
http://en.wikipedia.org/wiki/Kano_model
what do you think?</description>
		<content:encoded><![CDATA[<p>Interesting.<br />
This could be merged with the Kano model.<br />
<a href="http://en.wikipedia.org/wiki/Kano_model" rel="nofollow">http://en.wikipedia.org/wiki/Kano_model</a><br />
what do you think?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
