<?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/"
	xmlns:rssFeedStyles="http://www.lerougeliet.com/ns/rssFeedStyles#"

	>
<channel>
	<title>
	Comments on: Don’t rest until you test!	</title>
	<atom:link href="https://berkonomics.com/?feed=rss2&#038;p=3017" rel="self" type="application/rss+xml" />
	<link>https://berkonomics.com/?p=3017&#038;utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=dont-rest-until-you-test</link>
	<description>Dave Berkus&#039; business insights</description>
	<lastBuildDate>Wed, 19 Jul 2017 16:31:43 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		By: Kent Deines		</title>
		<link>https://berkonomics.com/?p=3017&#038;cpage=1#comment-109374</link>

		<dc:creator><![CDATA[Kent Deines]]></dc:creator>
		<pubDate>Wed, 19 Jul 2017 16:31:43 +0000</pubDate>
		<guid isPermaLink="false">https://berkonomics.com/?p=3017#comment-109374</guid>

					<description><![CDATA[I couldn&#039;t agree more. I have been embarrassed more than once. We always tested our products before we shipped them and still shipped product that didn&#039;t work when the customer got it. Even though we tested and tested, we missed problems. 

Sometimes we took a shortcut that hid the problem.  Often the shortcut is unrealized at the time. (Using a lab power supply and not the battery the customer used. Opps.) Other times we didn&#039;t think to test it that way. (Shallow water and slow moving boat. Either one ok, together, no good.) Then there is a whole class of low probably issues. Most units don&#039;t show the problem or nobody is aware of it. Sometimes it becomes easy to see only when you get a flash of understanding that allows you to carefully design the right experiment. Only then it becomes painfully obvious. A wonderful problem is when a customer dreams up a new application and an opps pops up. 
If you are lucky enough to have, what I call, Consenting-Adult-Customers, that that you can help test your product, it is wonderful. These are customers that you are comfortable showing your dirty, holey under ware to along with your products that don&#039;t quite work the way they should. They will work with you to identify and fix your mistakes and not hold it against you and later become your advocate. They usually have experience that tells them, that, of course you are screwed up, but it is normal, human and ok. Treat these people very well.  

At screening meetings I ask, &quot;What are you going to do when you find out that it doesn&#039;t work on Thursdays when the moon is full?&quot; You will have a disaster, I guarantee it. I want to see if they thought about it and have a plan for it. In the end, it is really all management can do.]]></description>
			<content:encoded><![CDATA[<p>I couldn&#8217;t agree more. I have been embarrassed more than once. We always tested our products before we shipped them and still shipped product that didn&#8217;t work when the customer got it. Even though we tested and tested, we missed problems. </p>
<p>Sometimes we took a shortcut that hid the problem.  Often the shortcut is unrealized at the time. (Using a lab power supply and not the battery the customer used. Opps.) Other times we didn&#8217;t think to test it that way. (Shallow water and slow moving boat. Either one ok, together, no good.) Then there is a whole class of low probably issues. Most units don&#8217;t show the problem or nobody is aware of it. Sometimes it becomes easy to see only when you get a flash of understanding that allows you to carefully design the right experiment. Only then it becomes painfully obvious. A wonderful problem is when a customer dreams up a new application and an opps pops up.<br />
If you are lucky enough to have, what I call, Consenting-Adult-Customers, that that you can help test your product, it is wonderful. These are customers that you are comfortable showing your dirty, holey under ware to along with your products that don&#8217;t quite work the way they should. They will work with you to identify and fix your mistakes and not hold it against you and later become your advocate. They usually have experience that tells them, that, of course you are screwed up, but it is normal, human and ok. Treat these people very well.  </p>
<p>At screening meetings I ask, &#8220;What are you going to do when you find out that it doesn&#8217;t work on Thursdays when the moon is full?&#8221; You will have a disaster, I guarantee it. I want to see if they thought about it and have a plan for it. In the end, it is really all management can do.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
