<?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: Take a cautious approach to problem-solving</title>
	<atom:link href="http://www.goodproductmanager.com/2008/07/16/take-a-cautious-approach-to-problem-solving/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.goodproductmanager.com/2008/07/16/take-a-cautious-approach-to-problem-solving/</link>
	<description>A blog with tips on product management and related topics. Written by Jeff Lash, a product manager in St. Louis, MO</description>
	<lastBuildDate>Sun, 07 Mar 2010 10:14:56 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: David Locke</title>
		<link>http://www.goodproductmanager.com/2008/07/16/take-a-cautious-approach-to-problem-solving/comment-page-1/#comment-15712</link>
		<dc:creator>David Locke</dc:creator>
		<pubDate>Tue, 02 Dec 2008 20:01:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodproductmanager.com/?p=148#comment-15712</guid>
		<description>I can remember a situation that you could think of as a line. It was stopped. We were trying to get it started again. We spent the day focused on it, and we got nowhere. It wasn&#039;t until we went home and got some sleep. The answer was found in the shower. That&#039;s where a lag can be productive. It isn&#039;t sticking your head in the sand. 

The other lags will stem from dependencies. 

Another lag will be the one where you chase the quick fix, the intermediate fix, and then the final fix as you explore the problem space. There is no one right answer. There is no one right timeframe, or time to solution. It will depend on how accurate your fix needs to be, how much it can cost, and all the other constraints. The right solution would be wrong in other contexts.</description>
		<content:encoded><![CDATA[<p>I can remember a situation that you could think of as a line. It was stopped. We were trying to get it started again. We spent the day focused on it, and we got nowhere. It wasn&#8217;t until we went home and got some sleep. The answer was found in the shower. That&#8217;s where a lag can be productive. It isn&#8217;t sticking your head in the sand. </p>
<p>The other lags will stem from dependencies. </p>
<p>Another lag will be the one where you chase the quick fix, the intermediate fix, and then the final fix as you explore the problem space. There is no one right answer. There is no one right timeframe, or time to solution. It will depend on how accurate your fix needs to be, how much it can cost, and all the other constraints. The right solution would be wrong in other contexts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Berardinelli</title>
		<link>http://www.goodproductmanager.com/2008/07/16/take-a-cautious-approach-to-problem-solving/comment-page-1/#comment-15703</link>
		<dc:creator>Kevin Berardinelli</dc:creator>
		<pubDate>Tue, 02 Dec 2008 16:11:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodproductmanager.com/?p=148#comment-15703</guid>
		<description>I think the good product manager is one who is flexible in problem-solving techniques. Recognition of the root problem and any interdependencies is crucial from the get-go, and a good product manager should know when to stop the line for an immediate fix or look more strategically and use the problem as a developmental building block. So, I think you both (Emil and Jeff) are correct!</description>
		<content:encoded><![CDATA[<p>I think the good product manager is one who is flexible in problem-solving techniques. Recognition of the root problem and any interdependencies is crucial from the get-go, and a good product manager should know when to stop the line for an immediate fix or look more strategically and use the problem as a developmental building block. So, I think you both (Emil and Jeff) are correct!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emil Cardell</title>
		<link>http://www.goodproductmanager.com/2008/07/16/take-a-cautious-approach-to-problem-solving/comment-page-1/#comment-15697</link>
		<dc:creator>Emil Cardell</dc:creator>
		<pubDate>Tue, 02 Dec 2008 13:57:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodproductmanager.com/?p=148#comment-15697</guid>
		<description>I agree with you that people take the easy way out. But the problem is not waiting but how they solve the problem. 

Stop the line mentality makes it hard to only fix the easy problem because the line will be stop when the underlying problems starts to surface.</description>
		<content:encoded><![CDATA[<p>I agree with you that people take the easy way out. But the problem is not waiting but how they solve the problem. </p>
<p>Stop the line mentality makes it hard to only fix the easy problem because the line will be stop when the underlying problems starts to surface.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Lash</title>
		<link>http://www.goodproductmanager.com/2008/07/16/take-a-cautious-approach-to-problem-solving/comment-page-1/#comment-15679</link>
		<dc:creator>Jeff Lash</dc:creator>
		<pubDate>Tue, 02 Dec 2008 01:48:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodproductmanager.com/?p=148#comment-15679</guid>
		<description>I see your point, though I&#039;ve seen time and time again people fixing the symptoms without trying to diagnose the disease. Yes, it doesn&#039;t make sense, but it happens all the time. Often, this is because people jump to immediately solve the &lt;b&gt;easy&lt;/b&gt; problems -- which are often insignificant ones -- and ignore the &lt;b&gt;hard&lt;/b&gt; problems -- which are usually the really crucial ones -- simply because they are hard, time-consuming, expensive, or difficult to solve.</description>
		<content:encoded><![CDATA[<p>I see your point, though I&#8217;ve seen time and time again people fixing the symptoms without trying to diagnose the disease. Yes, it doesn&#8217;t make sense, but it happens all the time. Often, this is because people jump to immediately solve the <b>easy</b> problems &#8212; which are often insignificant ones &#8212; and ignore the <b>hard</b> problems &#8212; which are usually the really crucial ones &#8212; simply because they are hard, time-consuming, expensive, or difficult to solve.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emil Cardell</title>
		<link>http://www.goodproductmanager.com/2008/07/16/take-a-cautious-approach-to-problem-solving/comment-page-1/#comment-15676</link>
		<dc:creator>Emil Cardell</dc:creator>
		<pubDate>Mon, 01 Dec 2008 23:41:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodproductmanager.com/?p=148#comment-15676</guid>
		<description>Have to say that I don&#039;t agree with this at all. Sticking your head in the sand is never good, if you don&#039;t address the problems early they will grow. Small problems will become big ones. If you don&#039;t find the underlying problem when your solving a problem, then you need to look at new problem solving methods. 

I think Toyota and Lean methodology approach is much better. When you find a problem you stop the line and fix the problem so it never occurs again.</description>
		<content:encoded><![CDATA[<p>Have to say that I don&#8217;t agree with this at all. Sticking your head in the sand is never good, if you don&#8217;t address the problems early they will grow. Small problems will become big ones. If you don&#8217;t find the underlying problem when your solving a problem, then you need to look at new problem solving methods. </p>
<p>I think Toyota and Lean methodology approach is much better. When you find a problem you stop the line and fix the problem so it never occurs again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ohimor Innocent</title>
		<link>http://www.goodproductmanager.com/2008/07/16/take-a-cautious-approach-to-problem-solving/comment-page-1/#comment-14583</link>
		<dc:creator>Ohimor Innocent</dc:creator>
		<pubDate>Fri, 07 Nov 2008 15:39:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodproductmanager.com/?p=148#comment-14583</guid>
		<description>thanks on the tip on exploring strategic options rather than tactical</description>
		<content:encoded><![CDATA[<p>thanks on the tip on exploring strategic options rather than tactical</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bookmarks about Heat</title>
		<link>http://www.goodproductmanager.com/2008/07/16/take-a-cautious-approach-to-problem-solving/comment-page-1/#comment-14509</link>
		<dc:creator>Bookmarks about Heat</dc:creator>
		<pubDate>Wed, 05 Nov 2008 07:15:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodproductmanager.com/?p=148#comment-14509</guid>
		<description>[...] - bookmarked by 2 members originally found by XxMomsCutiexX on 2008-10-21  Take a cautious approach to problem-solving  http://www.goodproductmanager.com/2008/07/16/take-a-cautious-approach-to-problem-solving/ - [...]</description>
		<content:encoded><![CDATA[<p>[...] &#8211; bookmarked by 2 members originally found by XxMomsCutiexX on 2008-10-21  Take a cautious approach to problem-solving  <a href="http://www.goodproductmanager.com/2008/07/16/take-a-cautious-approach-to-problem-solving/" rel="nofollow">http://www.goodproductmanager.com/2008/07/16/take-a-cautious-approach-to-problem-solving/</a> &#8211; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 阿当说 &#187; 存档 &#187; 产品经理们，遇到Bug请别十万火急</title>
		<link>http://www.goodproductmanager.com/2008/07/16/take-a-cautious-approach-to-problem-solving/comment-page-1/#comment-10341</link>
		<dc:creator>阿当说 &#187; 存档 &#187; 产品经理们，遇到Bug请别十万火急</dc:creator>
		<pubDate>Wed, 06 Aug 2008 10:37:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodproductmanager.com/?p=148#comment-10341</guid>
		<description>[...] Lash 原文链接：Take a cautious approach to problem-solving 翻译：远骋       This entry was posted on Wednesday, August 6th, 2008 at 6:35 pm and is filed [...]</description>
		<content:encoded><![CDATA[<p>[...] Lash 原文链接：Take a cautious approach to problem-solving 翻译：远骋       This entry was posted on Wednesday, August 6th, 2008 at 6:35 pm and is filed [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 产品经理们，遇到Bug请别十万火急 -- 三秒改变世界</title>
		<link>http://www.goodproductmanager.com/2008/07/16/take-a-cautious-approach-to-problem-solving/comment-page-1/#comment-10281</link>
		<dc:creator>产品经理们，遇到Bug请别十万火急 -- 三秒改变世界</dc:creator>
		<pubDate>Tue, 05 Aug 2008 04:53:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodproductmanager.com/?p=148#comment-10281</guid>
		<description>[...] 本文译自&lt;Take a cautious approach to problem-solving&gt;，作者是Jeff Lash。 [...]</description>
		<content:encoded><![CDATA[<p>[...] 本文译自&lt;Take a cautious approach to problem-solving&gt;，作者是Jeff Lash。 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Locke</title>
		<link>http://www.goodproductmanager.com/2008/07/16/take-a-cautious-approach-to-problem-solving/comment-page-1/#comment-9518</link>
		<dc:creator>David Locke</dc:creator>
		<pubDate>Fri, 18 Jul 2008 19:28:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodproductmanager.com/?p=148#comment-9518</guid>
		<description>When a problem arises, we have our own orientation towards that problem in terms of time. Our time orientation may start out reactive, where we just have to fix the problem now, transition to predictive, and, we hope, ends up proactive where the problems that could happen have already been addressed. Peace of mind comes when we are acting proactively. 

Problems may also require a lag, in which you can&#039;t even think about the problem actively. The solution will come, so don&#039;t be affraid to wait. 

One dev organization brrought in a leader to change their processes. The changes were so gradual that the programmers where chomping at the bit to make the changes. Still, those changes came almost imperceptively. Adoption was never an issue. 

How many of the problems that we are reacting too have been known problems for quite a while?</description>
		<content:encoded><![CDATA[<p>When a problem arises, we have our own orientation towards that problem in terms of time. Our time orientation may start out reactive, where we just have to fix the problem now, transition to predictive, and, we hope, ends up proactive where the problems that could happen have already been addressed. Peace of mind comes when we are acting proactively. </p>
<p>Problems may also require a lag, in which you can&#8217;t even think about the problem actively. The solution will come, so don&#8217;t be affraid to wait. </p>
<p>One dev organization brrought in a leader to change their processes. The changes were so gradual that the programmers where chomping at the bit to make the changes. Still, those changes came almost imperceptively. Adoption was never an issue. </p>
<p>How many of the problems that we are reacting too have been known problems for quite a while?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shai</title>
		<link>http://www.goodproductmanager.com/2008/07/16/take-a-cautious-approach-to-problem-solving/comment-page-1/#comment-9480</link>
		<dc:creator>Shai</dc:creator>
		<pubDate>Thu, 17 Jul 2008 14:49:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodproductmanager.com/?p=148#comment-9480</guid>
		<description>I think this is great advice for life in general.  I am not sitting here waiting for my R&amp;D team to finish a build which is being delayed because they moved files around to clear space instead of just moving to the new storage server we got. Saved 5 minutes a week ago costing them 3 hours so far today. guess this is going to be a long weekend for the QA team.</description>
		<content:encoded><![CDATA[<p>I think this is great advice for life in general.  I am not sitting here waiting for my R&amp;D team to finish a build which is being delayed because they moved files around to clear space instead of just moving to the new storage server we got. Saved 5 minutes a week ago costing them 3 hours so far today. guess this is going to be a long weekend for the QA team.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2008-07-17 (Jarrett House North)</title>
		<link>http://www.goodproductmanager.com/2008/07/16/take-a-cautious-approach-to-problem-solving/comment-page-1/#comment-9464</link>
		<dc:creator>links for 2008-07-17 (Jarrett House North)</dc:creator>
		<pubDate>Thu, 17 Jul 2008 02:44:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodproductmanager.com/?p=148#comment-9464</guid>
		<description>[...] Take a cautious approach to problem-solving (Good Product Manager) Don&#8217;t solve all problems right away. Let them mellow. (tags: productmanagement) [...]</description>
		<content:encoded><![CDATA[<p>[...] Take a cautious approach to problem-solving (Good Product Manager) Don&#8217;t solve all problems right away. Let them mellow. (tags: productmanagement) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
