<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments for QFD on the Web</title>
	<link>http://www.qfdweb.com</link>
	<description>Your online resource for all things QFD</description>
	<pubDate>Sat, 04 Sep 2010 23:21:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.3</generator>

	<item>
		<title>Comment on Submission Confirmation by Peter</title>
		<link>http://www.qfdweb.com/?page_id=19#comment-8</link>
		<author>Peter</author>
		<pubDate>Tue, 14 Aug 2007 04:08:16 +0000</pubDate>
		<guid>http://www.qfdweb.com/?page_id=19#comment-8</guid>
					<description>Justin - if you haven't already done so, you should check out Joseph Merts' article "&lt;a href="http://www.qfdonline.com/archives/when-to-say-when/" title="When to Say When" rel="nofollow"&gt;When to Say When&lt;/a&gt;" posted back in June.  He makes some pretty interesting comments about limiting requirements to a "magic number" or "rule of thumb".</description>
		<content:encoded><![CDATA[<p>Justin - if you haven&#8217;t already done so, you should check out Joseph Merts&#8217; article &#8220;<a href="http://www.qfdonline.com/archives/when-to-say-when/" title="When to Say When" rel="nofollow">When to Say When</a>&#8221; posted back in June.  He makes some pretty interesting comments about limiting requirements to a &#8220;magic number&#8221; or &#8220;rule of thumb&#8221;.</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Submission Confirmation by Fred</title>
		<link>http://www.qfdweb.com/?page_id=19#comment-9</link>
		<author>Fred</author>
		<pubDate>Sat, 14 Jul 2007 06:37:55 +0000</pubDate>
		<guid>http://www.qfdweb.com/?page_id=19#comment-9</guid>
					<description>It seems like it would be appropriate or helpful for tools to highlight or somehow indicate to users that the "whats" are not adequately being provided for or that the "hows" aren't actually helping any of the "whats". Knowing the aforementioned principles, it is still easy to miss these points while maintaining, using or just reading a QFD.</description>
		<content:encoded><![CDATA[<p>It seems like it would be appropriate or helpful for tools to highlight or somehow indicate to users that the &#8220;whats&#8221; are not adequately being provided for or that the &#8220;hows&#8221; aren&#8217;t actually helping any of the &#8220;whats&#8221;. Knowing the aforementioned principles, it is still easy to miss these points while maintaining, using or just reading a QFD.</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Changing the Orientation of Your QFD by Justin</title>
		<link>http://www.qfdweb.com/?p=12#comment-5</link>
		<author>Justin</author>
		<pubDate>Sun, 03 Jun 2007 18:40:27 +0000</pubDate>
		<guid>http://www.qfdweb.com/?p=12#comment-5</guid>
					<description>You mentioned that the column restrictions imposed by Excel, etc. may be too limiting for an HOQ.  I have been told that no HOQ should ever have more than 30 or 40 requirements in any of its lists in order to keep it maintainable.  Therefore, I really don't think that the column restrictions are much of an issue considering that Excel allows 256 columns.</description>
		<content:encoded><![CDATA[<p>You mentioned that the column restrictions imposed by Excel, etc. may be too limiting for an HOQ.  I have been told that no HOQ should ever have more than 30 or 40 requirements in any of its lists in order to keep it maintainable.  Therefore, I really don&#8217;t think that the column restrictions are much of an issue considering that Excel allows 256 columns.</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on QFD First Step: Determine Your Customer by Skid</title>
		<link>http://www.qfdweb.com/?p=10#comment-4</link>
		<author>Skid</author>
		<pubDate>Tue, 29 May 2007 05:21:54 +0000</pubDate>
		<guid>http://www.qfdweb.com/?p=10#comment-4</guid>
					<description>Great comments Joseph Merts... 
A problem I often see is that the stake holders are not sure who their customer is.  They get stuck in a loop of adding features and changing those features over and over again.  All because of the lack of focus, inability to choose, or fear to be wrong.  The stake holders have a hard time grasping the QFD process, but once they see and work through the exercise a new understanding is opened up and the product is able to move forward.</description>
		<content:encoded><![CDATA[<p>Great comments Joseph Merts&#8230;<br />
A problem I often see is that the stake holders are not sure who their customer is.  They get stuck in a loop of adding features and changing those features over and over again.  All because of the lack of focus, inability to choose, or fear to be wrong.  The stake holders have a hard time grasping the QFD process, but once they see and work through the exercise a new understanding is opened up and the product is able to move forward.</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on QFD First Step: Determine Your Customer by James</title>
		<link>http://www.qfdweb.com/?p=10#comment-3</link>
		<author>James</author>
		<pubDate>Sat, 26 May 2007 01:19:53 +0000</pubDate>
		<guid>http://www.qfdweb.com/?p=10#comment-3</guid>
					<description>Okay I have to disagree about the internal customers ruling the day.  I think that while there are legitimate internal customer issues they can't be "given the bull horn."  Example ... Beta Max vs. VHS.  If Sony would have listened more to the consumer and their desire to record programs they could have been the defacto standard.  Instead they listened to other internal forces (hollywood partners) and lost the market.</description>
		<content:encoded><![CDATA[<p>Okay I have to disagree about the internal customers ruling the day.  I think that while there are legitimate internal customer issues they can&#8217;t be &#8220;given the bull horn.&#8221;  Example &#8230; Beta Max vs. VHS.  If Sony would have listened more to the consumer and their desire to record programs they could have been the defacto standard.  Instead they listened to other internal forces (hollywood partners) and lost the market.</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on QFD First Step: Determine Your Customer by Mike</title>
		<link>http://www.qfdweb.com/?p=10#comment-2</link>
		<author>Mike</author>
		<pubDate>Sat, 26 May 2007 01:16:18 +0000</pubDate>
		<guid>http://www.qfdweb.com/?p=10#comment-2</guid>
					<description>We suffer from the issue of having a strong influence from internal customers but who are oft times out of touch with the consumers or decide features based on tradition.

You do make a good point about internal customers deciding the success of the project.    Some ideas have caused internal customers to sour on the product.  And so they believe it's not good or not on target...this gets spread around too much and the product is doomed before it reaches the consumers.  Dead before it's out the door.  

How can you educate your internal stake holders about what will make the product a smashing success?


Hopefully you can cover that in your next blog post.</description>
		<content:encoded><![CDATA[<p>We suffer from the issue of having a strong influence from internal customers but who are oft times out of touch with the consumers or decide features based on tradition.</p>
<p>You do make a good point about internal customers deciding the success of the project.    Some ideas have caused internal customers to sour on the product.  And so they believe it&#8217;s not good or not on target&#8230;this gets spread around too much and the product is doomed before it reaches the consumers.  Dead before it&#8217;s out the door.  </p>
<p>How can you educate your internal stake holders about what will make the product a smashing success?</p>
<p>Hopefully you can cover that in your next blog post.</p>
]]></content:encoded>
				</item>
</channel>
</rss>
