<?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: Problems Are Everywhere</title>
	<atom:link href="http://tynerblain.com/blog/2008/05/21/problems-are-everywhere/feed/" rel="self" type="application/rss+xml" />
	<link>http://tynerblain.com/blog/2008/05/21/problems-are-everywhere/</link>
	<description>Software product success.</description>
	<lastBuildDate>Sun, 12 Feb 2012 19:10:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2008/05/21/problems-are-everywhere/comment-page-1/#comment-380685</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Sat, 31 May 2008 15:08:24 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/?p=682#comment-380685</guid>
		<description>Thanks Vinodh, and welcome to Tyner Blain!

I&#039;ll add that while of immediately obvious value to product companies, this may be more distinctly valuable as the &quot;secret sauce&quot; of an IT department.  Ideally, a company&#039;s IT department will be focused on enabling business capabilities - as opposed to self-defining as a cost-center that does what is needed.

When you infuse the product-centric perspective of defining problems, you enable your IT department to drive innovation, and your company to develop distinctive competencies that can make it more competitive.</description>
		<content:encoded><![CDATA[<p>Thanks Vinodh, and welcome to Tyner Blain!</p>
<p>I&#8217;ll add that while of immediately obvious value to product companies, this may be more distinctly valuable as the &#8220;secret sauce&#8221; of an IT department.  Ideally, a company&#8217;s IT department will be focused on enabling business capabilities &#8211; as opposed to self-defining as a cost-center that does what is needed.</p>
<p>When you infuse the product-centric perspective of defining problems, you enable your IT department to drive innovation, and your company to develop distinctive competencies that can make it more competitive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vinodh Nandakumar</title>
		<link>http://tynerblain.com/blog/2008/05/21/problems-are-everywhere/comment-page-1/#comment-377649</link>
		<dc:creator>Vinodh Nandakumar</dc:creator>
		<pubDate>Mon, 26 May 2008 10:35:53 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/?p=682#comment-377649</guid>
		<description>Makes a lot of sense and great business value, especially if you are a product company trying to build something on your own. 
I really like 37signals approach to this, Getting real is a great read for any product manager!</description>
		<content:encoded><![CDATA[<p>Makes a lot of sense and great business value, especially if you are a product company trying to build something on your own.<br />
I really like 37signals approach to this, Getting real is a great read for any product manager!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Product Managers: The One Number You Should Know While Prioritizing Requirements : Product Management Insights</title>
		<link>http://tynerblain.com/blog/2008/05/21/problems-are-everywhere/comment-page-1/#comment-375230</link>
		<dc:creator>Product Managers: The One Number You Should Know While Prioritizing Requirements : Product Management Insights</dc:creator>
		<pubDate>Thu, 22 May 2008 07:50:15 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/?p=682#comment-375230</guid>
		<description>[...] couple of excellent posts in the blogosphere this week emphasized that you should consider customer problems solved and value added to customers while deciding which requirements/features to implement in your next [...]</description>
		<content:encoded><![CDATA[<p>[...] couple of excellent posts in the blogosphere this week emphasized that you should consider customer problems solved and value added to customers while deciding which requirements/features to implement in your next [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

