<?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: Market of One</title>
	<atom:link href="http://myownpirateradio.com/2006/03/08/market-of-one/feed/" rel="self" type="application/rss+xml" />
	<link>http://myownpirateradio.com/2006/03/08/market-of-one/</link>
	<description>Oshoma Momoh's personal blog</description>
	<pubDate>Thu, 04 Dec 2008 02:08:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rob Gagnon</title>
		<link>http://myownpirateradio.com/2006/03/08/market-of-one/#comment-139</link>
		<dc:creator>Rob Gagnon</dc:creator>
		<pubDate>Tue, 14 Mar 2006 21:24:02 +0000</pubDate>
		<guid isPermaLink="false">http://myownpirateradio.com/2006/03/08/market-of-one/#comment-139</guid>
		<description>This was what sucked me into technology in the 1990s in the firstplace. I had a vision that the internet allowed you manufacture goods the world never saw before because of it's unique qualities.

I beleive that a smart organization treats each user as a live relationship of feedback (in a cellular sense) and by watching and interacting you can have them tell you specifically what they want and you can deliver specifically what they want. It's not wood, metal or plastic (long horizon) with Web 2.0 you can literally ask a visitor: What do want? How should it look? What features? and out of the primordial soup of code create what they need, functions and form factor that suits them: A perfect product. Then as their use increases and more limitations are revealed by the user, the app grows and adapts to their needs (in real time).

It means looking at applications in a different way. We adopted a view of "event based computing" for our platform develpment that essentially said "they'll tell us what they want, we just have to have the ability to listen". I am a  retailer from way back, you never made money from stocking what you want, you made money from selling things people want.

Unfortunately, this isn't a terribly good way to raise funding.. it's too vague. Money loves little clean boxes with sides, ends and tops.

Rob</description>
		<content:encoded><![CDATA[<p>This was what sucked me into technology in the 1990s in the firstplace. I had a vision that the internet allowed you manufacture goods the world never saw before because of it&#8217;s unique qualities.</p>
<p>I beleive that a smart organization treats each user as a live relationship of feedback (in a cellular sense) and by watching and interacting you can have them tell you specifically what they want and you can deliver specifically what they want. It&#8217;s not wood, metal or plastic (long horizon) with Web 2.0 you can literally ask a visitor: What do want? How should it look? What features? and out of the primordial soup of code create what they need, functions and form factor that suits them: A perfect product. Then as their use increases and more limitations are revealed by the user, the app grows and adapts to their needs (in real time).</p>
<p>It means looking at applications in a different way. We adopted a view of &#8220;event based computing&#8221; for our platform develpment that essentially said &#8220;they&#8217;ll tell us what they want, we just have to have the ability to listen&#8221;. I am a  retailer from way back, you never made money from stocking what you want, you made money from selling things people want.</p>
<p>Unfortunately, this isn&#8217;t a terribly good way to raise funding.. it&#8217;s too vague. Money loves little clean boxes with sides, ends and tops.</p>
<p>Rob</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://myownpirateradio.com/2006/03/08/market-of-one/#comment-138</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Wed, 08 Mar 2006 19:47:01 +0000</pubDate>
		<guid isPermaLink="false">http://myownpirateradio.com/2006/03/08/market-of-one/#comment-138</guid>
		<description>PS notice this cycle is happening with his own product ;)</description>
		<content:encoded><![CDATA[<p>PS notice this cycle is happening with his own product <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://myownpirateradio.com/2006/03/08/market-of-one/#comment-137</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Wed, 08 Mar 2006 19:45:55 +0000</pubDate>
		<guid isPermaLink="false">http://myownpirateradio.com/2006/03/08/market-of-one/#comment-137</guid>
		<description>Funny, I was thinking about your Attention post &#38; questions while I watched Seth Godin in this talk the other day:
  http://video.google.com/videoplay?docid=-6909078385965257294
It's 45 min long and probably valuable for 1/2 of that time (sucks that you can't skip around in video &#38; still comprehend the whole, like you can in text :( )

For example from the video: good engineering (your first point) gives you an opening to a conversation with your target user (your second point).  But I don't think he's worried about the "echo chamber" effect because the point of the conversation is specifically to spark that user into having a conversation - about your product - with other people.  So you're tunnelling very narrowly to reach the excitable user but counting on him to escape the echo chamber.

His suggested cycle:
- build something interesting
- tell people about it
- let them start conversations about it themselves
- get permission to tell them more things later

This isn't an echo chamber, it's resonance ...</description>
		<content:encoded><![CDATA[<p>Funny, I was thinking about your Attention post &amp; questions while I watched Seth Godin in this talk the other day:<br />
  <a href="http://video.google.com/videoplay?docid=-6909078385965257294" rel="nofollow">http://video.google.com/videoplay?docid=-6909078385965257294</a><br />
It&#8217;s 45 min long and probably valuable for 1/2 of that time (sucks that you can&#8217;t skip around in video &amp; still comprehend the whole, like you can in text <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> )</p>
<p>For example from the video: good engineering (your first point) gives you an opening to a conversation with your target user (your second point).  But I don&#8217;t think he&#8217;s worried about the &#8220;echo chamber&#8221; effect because the point of the conversation is specifically to spark that user into having a conversation - about your product - with other people.  So you&#8217;re tunnelling very narrowly to reach the excitable user but counting on him to escape the echo chamber.</p>
<p>His suggested cycle:<br />
- build something interesting<br />
- tell people about it<br />
- let them start conversations about it themselves<br />
- get permission to tell them more things later</p>
<p>This isn&#8217;t an echo chamber, it&#8217;s resonance &#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
