<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/'><id>tag:blogger.com,1999:blog-7879107.post701841715861872074..comments</id><updated>2011-07-29T16:56:02.480-05:00</updated><category term='teamwork'/><category term='prodmgmt'/><category term='change management'/><category term='authority'/><category term='ethnography'/><category term='research'/><category term='prodmgmttalk'/><category term='austin'/><category term='customer development'/><category term='SME'/><category term='experience'/><category term='ux'/><category term='productcamp'/><category term='lean startup'/><category term='leadership'/><category term='requirement'/><category term='decision facilitation'/><category term='facilitation'/><category term='dormant problem'/><category term='scrum'/><category term='agile'/><category term='survey'/><category term='systems'/><category term='twitter'/><category term='sales'/><category term='persona'/><category term='innovation'/><category term='marketing'/><category term='market adoption'/><category term='incongruity theory'/><category term='career'/><category term='epic'/><category term='requirements'/><category term='user story'/><category term='prospect interview'/><category term='naming'/><category term='buying facilitation'/><category term='expert'/><category term='management'/><category term='brand'/><category term='talent'/><title type='text'>Comments on Cauvin: How to Prevent Product Paralysis</title><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://blog.cauvin.org/feeds/701841715861872074/comments/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7879107/701841715861872074/comments/default'/><link rel='alternate' type='text/html' href='http://blog.cauvin.org/2011/01/how-to-prevent-product-paralysis.html'/><author><name>Roger Cauvin</name><uri>https://profiles.google.com/109638091125955424339</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh6.googleusercontent.com/-nzecvI0g5lo/AAAAAAAAAAI/AAAAAAAAAAA/Lvt96kc38YQ/s512-c/photo.jpg'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>4</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-7879107.post-4841248589197318640</id><published>2011-01-05T14:22:17.073-06:00</published><updated>2011-01-05T14:22:17.073-06:00</updated><title type='text'>Joshua, you&amp;#39;re absolutely right about &amp;quot;hi...</title><content type='html'>Joshua, you&amp;#39;re absolutely right about &amp;quot;hidden influencers&amp;quot;.  Often, these influencers lie outside the product team, and their buy-in must also be facilitated.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7879107/701841715861872074/comments/default/4841248589197318640'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7879107/701841715861872074/comments/default/4841248589197318640'/><link rel='alternate' type='text/html' href='http://blog.cauvin.org/2011/01/how-to-prevent-product-paralysis.html?showComment=1294258937073#c4841248589197318640' title=''/><author><name>Roger L. Cauvin</name><uri>http://www.blogger.com/profile/08969779835314260680</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='24' height='32' src='http://1.bp.blogspot.com/_OJP2qnUyu7I/S8m3evwbNsI/AAAAAAAAAHg/X22qkc9Cml8/S220/Face+Shot+-+75+x+100.jpg'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://blog.cauvin.org/2011/01/how-to-prevent-product-paralysis.html' ref='tag:blogger.com,1999:blog-7879107.post-701841715861872074' source='http://www.blogger.com/feeds/7879107/posts/default/701841715861872074' type='text/html'/><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='blogger.itemClass' value='pid-1931156270'/></entry><entry><id>tag:blogger.com,1999:blog-7879107.post-3879061066594684609</id><published>2011-01-05T10:22:25.118-06:00</published><updated>2011-01-05T10:22:25.118-06:00</updated><title type='text'>Roger,

Great post and thanks for the mention!

I ...</title><content type='html'>Roger,&lt;br /&gt;&lt;br /&gt;Great post and thanks for the mention!&lt;br /&gt;&lt;br /&gt;I would add some emphasis to your point on how critical it is that the product manager understand how to influence change and decision facilitation to really be effective.  &lt;br /&gt;&lt;br /&gt;Also, they must really understand organizational dynamics to make sure that they are not only influencing the members of their team but the influences throughout the company.  &lt;br /&gt;&lt;br /&gt;In my experience, it is the hidden influencers that might not be directly involved in the upfront product decisions that if not sold on the direction can cause the biggest headaches down the road.&lt;br /&gt;&lt;br /&gt;Thanks again,&lt;br /&gt;&lt;br /&gt;Josh</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7879107/701841715861872074/comments/default/3879061066594684609'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7879107/701841715861872074/comments/default/3879061066594684609'/><link rel='alternate' type='text/html' href='http://blog.cauvin.org/2011/01/how-to-prevent-product-paralysis.html?showComment=1294244545118#c3879061066594684609' title=''/><author><name>Joshua Duncan</name><uri>http://www.blogger.com/profile/04751248141772230900</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://3.bp.blogspot.com/_KKEGsTP9RWU/TSN6z__eRvI/AAAAAAAAAAM/EtSm8MT9M4s/S220/jd.jpg'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://blog.cauvin.org/2011/01/how-to-prevent-product-paralysis.html' ref='tag:blogger.com,1999:blog-7879107.post-701841715861872074' source='http://www.blogger.com/feeds/7879107/posts/default/701841715861872074' type='text/html'/><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='blogger.itemClass' value='pid-680600476'/></entry><entry><id>tag:blogger.com,1999:blog-7879107.post-2322308497530795343</id><published>2011-01-04T19:10:05.968-06:00</published><updated>2011-01-04T19:10:05.968-06:00</updated><title type='text'>Thanks for the comment, Larry.

Totally agree that...</title><content type='html'>Thanks for the comment, Larry.&lt;br /&gt;&lt;br /&gt;Totally agree that internal change management is crucial to prevent product paralysis.  It&amp;#39;s important to keep in mind that &amp;quot;selling&amp;quot; a product roadmap isn&amp;#39;t sufficient.  There are important lessons to learn from Sharon Drew Morgen&amp;#39;s concept, &lt;a href="http://blog.cauvin.org/2010/08/what-is-buying-facilitation.html" rel="nofollow"&gt;Buying Facilitation(TM)&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;I&amp;#39;m not sure I see relevance of the product lifecycle.  At any point in the lifecycle, a product team is making strategic decisions about the product.  The decision to maintain but not significantly enhance a product is itself a strategic decision.  A subsequent decision to kill a product entirely is a strategic decision.  To be effective and fully executed, these decisions benefit from at least some of the approaches I&amp;#39;ve enumerated, right?</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7879107/701841715861872074/comments/default/2322308497530795343'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7879107/701841715861872074/comments/default/2322308497530795343'/><link rel='alternate' type='text/html' href='http://blog.cauvin.org/2011/01/how-to-prevent-product-paralysis.html?showComment=1294189805968#c2322308497530795343' title=''/><author><name>Roger L. Cauvin</name><uri>http://www.blogger.com/profile/08969779835314260680</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='24' height='32' src='http://1.bp.blogspot.com/_OJP2qnUyu7I/S8m3evwbNsI/AAAAAAAAAHg/X22qkc9Cml8/S220/Face+Shot+-+75+x+100.jpg'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://blog.cauvin.org/2011/01/how-to-prevent-product-paralysis.html' ref='tag:blogger.com,1999:blog-7879107.post-701841715861872074' source='http://www.blogger.com/feeds/7879107/posts/default/701841715861872074' type='text/html'/><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='blogger.itemClass' value='pid-1931156270'/></entry><entry><id>tag:blogger.com,1999:blog-7879107.post-7149960758542412858</id><published>2011-01-04T15:18:36.367-06:00</published><updated>2011-01-04T15:18:36.367-06:00</updated><title type='text'>Roger, good points but a good product manager shou...</title><content type='html'>Roger, good points but a good product manager should recognize when a company or product line is heading towards product paralysis early. Identifying some of the causes for this ahead of time might avoid a slow down or stoppage of forward momentum.  Signs that your are heading down this path would include a roadmap that looks like your first two indicators.  The good product manager is going to be guiding the direction and informing the team about where the market and the product need to be heading.  The sales process starts internally.  If you cannot convince you own team that there is a need for change, trying to convince your market is going to be an uphill battle. Change is never easy but is necessary.&lt;br /&gt;&lt;br /&gt;One other thought that you didn&amp;#39;t touch on was where in the product lifecycle are you?  This can greatly influence the next steps.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7879107/701841715861872074/comments/default/7149960758542412858'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7879107/701841715861872074/comments/default/7149960758542412858'/><link rel='alternate' type='text/html' href='http://blog.cauvin.org/2011/01/how-to-prevent-product-paralysis.html?showComment=1294175916367#c7149960758542412858' title=''/><author><name>Larry</name><uri>http://www.blogger.com/profile/06955719356259694710</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_7ARPyOiWcT0/SfoO6rpF6_I/AAAAAAAAAAM/a4L_Ad8MSVA/S220/larry.jpg'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://blog.cauvin.org/2011/01/how-to-prevent-product-paralysis.html' ref='tag:blogger.com,1999:blog-7879107.post-701841715861872074' source='http://www.blogger.com/feeds/7879107/posts/default/701841715861872074' type='text/html'/><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='blogger.itemClass' value='pid-1945252358'/></entry></feed>
