<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for Ooga Labs</title>
	<atom:link href="http://blog.oogalabs.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.oogalabs.com</link>
	<description>Ooga Labs</description>
	<lastBuildDate>Fri, 26 Feb 2010 21:37:53 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Passionate Beliefs, Loosely Held by LitoR</title>
		<link>http://blog.oogalabs.com/2009/12/22/passionate-beliefs-loosely-held/#comment-453</link>
		<dc:creator>LitoR</dc:creator>
		<pubDate>Fri, 26 Feb 2010 21:37:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.oogalabs.com/?p=180#comment-453</guid>
		<description>Very well said...

Exactly the reason why in a TEAM there is no &quot;I&quot;.

And it&#039;s really hard to get stuck with a group where the &quot;I&quot; abounds, get&#039;s you nowhere =(</description>
		<content:encoded><![CDATA[<p>Very well said&#8230;</p>
<p>Exactly the reason why in a TEAM there is no &#8220;I&#8221;.</p>
<p>And it&#8217;s really hard to get stuck with a group where the &#8220;I&#8221; abounds, get&#8217;s you nowhere =(</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Advisor Compensation Gap by Bryan White</title>
		<link>http://blog.oogalabs.com/2009/05/12/the-advisor-compensation-gap/#comment-451</link>
		<dc:creator>Bryan White</dc:creator>
		<pubDate>Thu, 25 Feb 2010 16:28:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.oogalabs.com/index.php/2009/05/12/the-advisor-compensation-gap/#comment-451</guid>
		<description>I have just formed a start up and I have not raised any funds at this time.  However, I have befreinded a retired president/CEO of the industry that my start up is in.  We meet, he is very qualified, very well respected by his peers but when we talked about compensation, he asked for defeered compensation until we were funded and 10% equity for moderate involvement and up to 20% equity for heavy involvement.  Is this typical at this early stage of a start up?   It seems like alot, equity amount that is to me- please let me know your thoughts?</description>
		<content:encoded><![CDATA[<p>I have just formed a start up and I have not raised any funds at this time.  However, I have befreinded a retired president/CEO of the industry that my start up is in.  We meet, he is very qualified, very well respected by his peers but when we talked about compensation, he asked for defeered compensation until we were funded and 10% equity for moderate involvement and up to 20% equity for heavy involvement.  Is this typical at this early stage of a start up?   It seems like alot, equity amount that is to me- please let me know your thoughts?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Fast, Good AND Cheap by George Rebane</title>
		<link>http://blog.oogalabs.com/2009/12/23/fast-good-and-cheap/#comment-417</link>
		<dc:creator>George Rebane</dc:creator>
		<pubDate>Wed, 13 Jan 2010 18:40:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.oogalabs.com/?p=205#comment-417</guid>
		<description>The original form of this dictum (used forever in the systems development world) is &#039;Performance, Cost, Schedule - pick any two&#039;.</description>
		<content:encoded><![CDATA[<p>The original form of this dictum (used forever in the systems development world) is &#8216;Performance, Cost, Schedule &#8211; pick any two&#8217;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Personal Character in Product Development by Marc Siegel</title>
		<link>http://blog.oogalabs.com/2009/12/23/personal-character-in-product-development/#comment-410</link>
		<dc:creator>Marc Siegel</dc:creator>
		<pubDate>Fri, 08 Jan 2010 18:57:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.oogalabs.com/?p=192#comment-410</guid>
		<description>Oops, I left out the juiciest part, the article&#039;s link:  
http://www.startuplessonslearned.com/2009/10/real-customer-advisory-board.html</description>
		<content:encoded><![CDATA[<p>Oops, I left out the juiciest part, the article&#8217;s link:<br />
<a href="http://www.startuplessonslearned.com/2009/10/real-customer-advisory-board.html" rel="nofollow">http://www.startuplessonslearned.com/2009/10/real-customer-advisory-board.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Personal Character in Product Development by Marc Siegel</title>
		<link>http://blog.oogalabs.com/2009/12/23/personal-character-in-product-development/#comment-409</link>
		<dc:creator>Marc Siegel</dc:creator>
		<pubDate>Fri, 08 Jan 2010 17:31:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.oogalabs.com/?p=192#comment-409</guid>
		<description>Hello James,
Right on!  A key to improvement is the willingness to look honestly within. A positive attitude greatly helps to persevere in making difficult changes. These truths hold for human personality as well as software products. As a product manager, I always found my best tool was a pair of large ears, willing to hear what customers were saying without being defensive. 

As companies/products mature, formalizing a feedback loop with Customer Advisory Boards can help. This article describes one enlightened example.
Best of luck.
Marc</description>
		<content:encoded><![CDATA[<p>Hello James,<br />
Right on!  A key to improvement is the willingness to look honestly within. A positive attitude greatly helps to persevere in making difficult changes. These truths hold for human personality as well as software products. As a product manager, I always found my best tool was a pair of large ears, willing to hear what customers were saying without being defensive. </p>
<p>As companies/products mature, formalizing a feedback loop with Customer Advisory Boards can help. This article describes one enlightened example.<br />
Best of luck.<br />
Marc</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Kevin Rose — Silicon Valley’s first Tom Cruise? by Leonel Dilda</title>
		<link>http://blog.oogalabs.com/2007/07/18/keven-rose-silicon-valleys-first-tom-cruise/#comment-406</link>
		<dc:creator>Leonel Dilda</dc:creator>
		<pubDate>Thu, 07 Jan 2010 22:53:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.oogalabs.com/index.php/2007/07/18/keven-rose-silicon-valleys-first-tom-cruise/#comment-406</guid>
		<description>I read that he that he wanted do a Neighbours cameo :O. Sounds a bit dodgy to me. There&#039;s a part of me that kind of wishes this is true lol.</description>
		<content:encoded><![CDATA[<p>I read that he that he wanted do a Neighbours cameo :O. Sounds a bit dodgy to me. There&#8217;s a part of me that kind of wishes this is true lol.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Fast, Good AND Cheap by Dave McClure</title>
		<link>http://blog.oogalabs.com/2009/12/23/fast-good-and-cheap/#comment-398</link>
		<dc:creator>Dave McClure</dc:creator>
		<pubDate>Fri, 01 Jan 2010 11:39:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.oogalabs.com/?p=205#comment-398</guid>
		<description>actually, i don&#039;t think it&#039;s impossible to build fast, good, AND cheap, however i DO think it&#039;s difficult to prioritize all 3 at the same time (or even 2, really). 

most things are built with only 1 of these as priorities, with possibly a 2nd constraint as a minimum rqmt. (ex: PayPal was pretty crappy at first, and was PRIMARILY built with an emphasis on viral distribution (Fast &amp; Cheap), while maintaining basic functional use as a payment mechanism, and while limiting overall system fraud activity to a manageable % (not Good, but Good Enough).

thus, while Twitter is arguably fast, good, &amp; cheap now, it certainly wasn&#039;t great when it started, and it wasn&#039;t very fast either (and not very reliable at all, as noted by almost everyone).  it was built cheap &amp; simple, and because it did it well *enough*, it was good (enough).

at the same time, most of Apple and Amazon products were built with GOOD as primary emphasis, and Cheap ENOUGH as the constraint... and perhaps some rqmts on speed, altho not clear they have as much focus there.

anyway, agreed that we shouldn&#039;t let narrow-minded thinking rule the day when aiming for breakthrough products &amp; services, but probably good to have a clear primary emphasis, along with secondary constraints.

my .02,</description>
		<content:encoded><![CDATA[<p>actually, i don&#8217;t think it&#8217;s impossible to build fast, good, AND cheap, however i DO think it&#8217;s difficult to prioritize all 3 at the same time (or even 2, really). </p>
<p>most things are built with only 1 of these as priorities, with possibly a 2nd constraint as a minimum rqmt. (ex: PayPal was pretty crappy at first, and was PRIMARILY built with an emphasis on viral distribution (Fast &amp; Cheap), while maintaining basic functional use as a payment mechanism, and while limiting overall system fraud activity to a manageable % (not Good, but Good Enough).</p>
<p>thus, while Twitter is arguably fast, good, &amp; cheap now, it certainly wasn&#8217;t great when it started, and it wasn&#8217;t very fast either (and not very reliable at all, as noted by almost everyone).  it was built cheap &amp; simple, and because it did it well *enough*, it was good (enough).</p>
<p>at the same time, most of Apple and Amazon products were built with GOOD as primary emphasis, and Cheap ENOUGH as the constraint&#8230; and perhaps some rqmts on speed, altho not clear they have as much focus there.</p>
<p>anyway, agreed that we shouldn&#8217;t let narrow-minded thinking rule the day when aiming for breakthrough products &amp; services, but probably good to have a clear primary emphasis, along with secondary constraints.</p>
<p>my .02,</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Fast, Good AND Cheap by mel</title>
		<link>http://blog.oogalabs.com/2009/12/23/fast-good-and-cheap/#comment-396</link>
		<dc:creator>mel</dc:creator>
		<pubDate>Wed, 30 Dec 2009 00:00:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.oogalabs.com/?p=205#comment-396</guid>
		<description>It&#039;s not the tech that&#039;s the point of the post, it&#039;s the means. 

Bureaucrats justifying mediocracy. Place markers building their little empire. Mel Conway explained it in 1968.

I&#039;m a scrum master. To me scrum is the only rational way to control chaotic projects; that&#039;s software to you. 

The good, fast and cheap is a natural consequence of scrum&#039;s focus on ROI.</description>
		<content:encoded><![CDATA[<p>It&#8217;s not the tech that&#8217;s the point of the post, it&#8217;s the means. </p>
<p>Bureaucrats justifying mediocracy. Place markers building their little empire. Mel Conway explained it in 1968.</p>
<p>I&#8217;m a scrum master. To me scrum is the only rational way to control chaotic projects; that&#8217;s software to you. </p>
<p>The good, fast and cheap is a natural consequence of scrum&#8217;s focus on ROI.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Fast, Good AND Cheap by Rajesh</title>
		<link>http://blog.oogalabs.com/2009/12/23/fast-good-and-cheap/#comment-394</link>
		<dc:creator>Rajesh</dc:creator>
		<pubDate>Tue, 29 Dec 2009 19:17:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.oogalabs.com/?p=205#comment-394</guid>
		<description>James,

You are comparing apples and oranges.

The common thread in your &quot;Slow, Expensive, Good&quot; examples is that there is more to the product/service (technical complexity, financial regs., logistics whatever) that what you see from a user&#039;s standpoint.  

The &quot;Fast Cheap Good&quot; is all WYSIWYG (mostly) and largely web/mobile applications that piggy-back on other infrastructure.

No excuses for the crappy stuff...

I would bet that something like SquareUp would take time to build given all the regulations and infrastructure that needs to be built. Some things can only be built so fast (good or crappy).

-Rajesh</description>
		<content:encoded><![CDATA[<p>James,</p>
<p>You are comparing apples and oranges.</p>
<p>The common thread in your &#8220;Slow, Expensive, Good&#8221; examples is that there is more to the product/service (technical complexity, financial regs., logistics whatever) that what you see from a user&#8217;s standpoint.  </p>
<p>The &#8220;Fast Cheap Good&#8221; is all WYSIWYG (mostly) and largely web/mobile applications that piggy-back on other infrastructure.</p>
<p>No excuses for the crappy stuff&#8230;</p>
<p>I would bet that something like SquareUp would take time to build given all the regulations and infrastructure that needs to be built. Some things can only be built so fast (good or crappy).</p>
<p>-Rajesh</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Fast, Good AND Cheap by jamescurrier</title>
		<link>http://blog.oogalabs.com/2009/12/23/fast-good-and-cheap/#comment-393</link>
		<dc:creator>jamescurrier</dc:creator>
		<pubDate>Tue, 29 Dec 2009 06:14:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.oogalabs.com/?p=205#comment-393</guid>
		<description>Fast, Good and Cheap:  Facebook, Twitter, Bebo, FourSquare, Groupon, MySpace, Fickr, PhotoBucket, Texas Hold &#039;Em on FB (which lead to Zynga), (lil) Green Patch on FB (which launched the social gaming category and could have lead to Zynga), and then the Web 1.0 winners like CraigsList, Match.com, Monster, and eBay.

Slow, expensive and good: Amazon, Google, everything Apple, the F8 platform on FB.

Slow, expensive and crappy: most other stuff, like Zune, A9, all of KPCB&#039;s stealth companies, all of EA&#039;s attempts at social gaming on FB, LinkedIn (even though it won through lack of competition), all of Yahoo&#039;s startup attempts in the last 3 years.</description>
		<content:encoded><![CDATA[<p>Fast, Good and Cheap:  Facebook, Twitter, Bebo, FourSquare, Groupon, MySpace, Fickr, PhotoBucket, Texas Hold &#8216;Em on FB (which lead to Zynga), (lil) Green Patch on FB (which launched the social gaming category and could have lead to Zynga), and then the Web 1.0 winners like CraigsList, Match.com, Monster, and eBay.</p>
<p>Slow, expensive and good: Amazon, Google, everything Apple, the F8 platform on FB.</p>
<p>Slow, expensive and crappy: most other stuff, like Zune, A9, all of KPCB&#8217;s stealth companies, all of EA&#8217;s attempts at social gaming on FB, LinkedIn (even though it won through lack of competition), all of Yahoo&#8217;s startup attempts in the last 3 years.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
