<?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: How to Succeed In A Startup</title>
	<atom:link href="http://www.bigdoor.com/blog/how-to-succeed-in-a-startup/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bigdoor.com/blog/how-to-succeed-in-a-startup/</link>
	<description>Free gamification platform that helps companies increase their traffic and revenue through social rewards</description>
	<lastBuildDate>Fri, 03 Feb 2012 21:02:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Kevin Lam</title>
		<link>http://www.bigdoor.com/blog/how-to-succeed-in-a-startup/#comment-40</link>
		<dc:creator>Kevin Lam</dc:creator>
		<pubDate>Fri, 25 Jun 2010 07:23:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.bigdoor.com/?p=735#comment-40</guid>
		<description>Great post Ben.  Biggest lesson (and hardest learned) for me was to stay focused.  As a fellow software engineer it&#039;s so easy to get distracted and start poking around in this technology and that technology.  The day I decided just to focus on X instead of X, Y, Z, A, B, C and 1, 2, 3 ... our productivity and self-satisfaction shot up. Not to mention our product improved in quality by leaps and bounds.

Second biggest is to be customer-obsessed. As a software engineer it&#039;s so easy to design and implement &quot;cool technologies&quot; the way we think we would like to use it and lose site of the actual end user, making them delighted to use your software. The typical approach is to design, implement and then shove it down the customer&#039;s throats and see how they like it. Some of the most successful companies I know take the opposite approach and they find out what customers want even before they write a single line of code and then design around fulfilling the customer&#039;s wants/needs.

Again, great post Ben.

--Kevin</description>
		<content:encoded><![CDATA[<p>Great post Ben.  Biggest lesson (and hardest learned) for me was to stay focused.  As a fellow software engineer it&#8217;s so easy to get distracted and start poking around in this technology and that technology.  The day I decided just to focus on X instead of X, Y, Z, A, B, C and 1, 2, 3 &#8230; our productivity and self-satisfaction shot up. Not to mention our product improved in quality by leaps and bounds.</p>
<p>Second biggest is to be customer-obsessed. As a software engineer it&#8217;s so easy to design and implement &#8220;cool technologies&#8221; the way we think we would like to use it and lose site of the actual end user, making them delighted to use your software. The typical approach is to design, implement and then shove it down the customer&#8217;s throats and see how they like it. Some of the most successful companies I know take the opposite approach and they find out what customers want even before they write a single line of code and then design around fulfilling the customer&#8217;s wants/needs.</p>
<p>Again, great post Ben.</p>
<p>&#8211;Kevin</p>
]]></content:encoded>
	</item>
</channel>
</rss>

