<?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: The Chinese Menu &#8212; Product Development	</title>
	<atom:link href="https://themusingsofthebigredcar.com/the-chinese-menu-product-development/feed/" rel="self" type="application/rss+xml" />
	<link>https://themusingsofthebigredcar.com/the-chinese-menu-product-development/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=the-chinese-menu-product-development</link>
	<description>53 years and 204,000 miles of business, CEO, leadership, startup, political, military wisdom</description>
	<lastBuildDate>Sun, 10 Aug 2014 18:43:00 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.9.11</generator>
	<item>
		<title>
		By: JLM		</title>
		<link>https://themusingsofthebigredcar.com/the-chinese-menu-product-development/#comment-1579</link>

		<dc:creator><![CDATA[JLM]]></dc:creator>
		<pubDate>Sun, 10 Aug 2014 18:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://themusingsofthebigredcar.com/?p=3571#comment-1579</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://themusingsofthebigredcar.com/the-chinese-menu-product-development/#comment-1578&quot;&gt;James Ferguson @kWIQly&lt;/a&gt;.

.
In many instances it does not matter from which direction folks come to solve the problem.


It is the process oriented and structural implications which provides order to what can at times be disorderly and chaotic thought processes.


As things get progressively more complex, the ability to approach subsets of the problem in an orderly manner reduces the friction created by trying to blend operational, development, marketing, pricing considerations.


How does one eat an elephant?


One bite/bit at a time?


Stay well, friend.


BRC
.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://themusingsofthebigredcar.com/the-chinese-menu-product-development/#comment-1578">James Ferguson @kWIQly</a>.</p>
<p>.<br />
In many instances it does not matter from which direction folks come to solve the problem.</p>
<p>It is the process oriented and structural implications which provides order to what can at times be disorderly and chaotic thought processes.</p>
<p>As things get progressively more complex, the ability to approach subsets of the problem in an orderly manner reduces the friction created by trying to blend operational, development, marketing, pricing considerations.</p>
<p>How does one eat an elephant?</p>
<p>One bite/bit at a time?</p>
<p>Stay well, friend.</p>
<p>BRC<br />
.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: James Ferguson @kWIQly		</title>
		<link>https://themusingsofthebigredcar.com/the-chinese-menu-product-development/#comment-1578</link>

		<dc:creator><![CDATA[James Ferguson @kWIQly]]></dc:creator>
		<pubDate>Sun, 10 Aug 2014 16:05:00 +0000</pubDate>
		<guid isPermaLink="false">http://themusingsofthebigredcar.com/?p=3571#comment-1578</guid>

					<description><![CDATA[Hi @JLM,


Although the mapping from product dev to pricing structure is arguably obvious (as in pay for what you get) - It helped us to invert this.  Finding MVP (from a huge range of possibilities) without wasting time was for us about the lowest common denominator. On its own it is almost useless (so not an obvious MVP) because it takes a set of skills to deploy that aren&#039;t common amongst clients but as it is itself a persuasive functionality that feels like it &quot;should&quot; sit at the core of any proposition, and because some people will use it alone and others want it with extras - it outlines a clear entry level differentiator.


TLDR; - Thanks useful !]]></description>
			<content:encoded><![CDATA[<p>Hi @JLM,</p>
<p>Although the mapping from product dev to pricing structure is arguably obvious (as in pay for what you get) &#8211; It helped us to invert this.  Finding MVP (from a huge range of possibilities) without wasting time was for us about the lowest common denominator. On its own it is almost useless (so not an obvious MVP) because it takes a set of skills to deploy that aren&#8217;t common amongst clients but as it is itself a persuasive functionality that feels like it &#8220;should&#8221; sit at the core of any proposition, and because some people will use it alone and others want it with extras &#8211; it outlines a clear entry level differentiator.</p>
<p>TLDR; &#8211; Thanks useful !</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
