<?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:go='http://ns.gigaom.com/'
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 on: 10 Reasons Why Documentation is a Startup Secret Sauce</title>
	<atom:link href="http://gigaom.com/2008/04/08/10-reasons-why-documentation-is-a-startup-secret-sauce/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2008/04/08/10-reasons-why-documentation-is-a-startup-secret-sauce/</link>
	<description></description>
	<lastBuildDate>Fri, 10 Feb 2012 21:40:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Why We Need Documentation? &#171; . : toYatoYa : .</title>
		<link>http://gigaom.com/2008/04/08/10-reasons-why-documentation-is-a-startup-secret-sauce/#comment-198456</link>
		<dc:creator><![CDATA[Why We Need Documentation? &#171; . : toYatoYa : .]]></dc:creator>
		<pubDate>Thu, 06 Nov 2008 04:28:16 +0000</pubDate>
		<guid isPermaLink="false">http://foundread.com/?p=684#comment-198456</guid>
		<description><![CDATA[[...] http://gigaom.com/2008/04/08/10-reasons-why-documentation-is-a-startup-secret-sauce/ [...]]]></description>
		<content:encoded><![CDATA[<p>[...] <a href="http://gigaom.com/2008/04/08/10-reasons-why-documentation-is-a-startup-secret-sauce/" rel="nofollow">http://gigaom.com/2008/04/08/10-reasons-why-documentation-is-a-startup-secret-sauce/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dr. S. V. Ranade</title>
		<link>http://gigaom.com/2008/04/08/10-reasons-why-documentation-is-a-startup-secret-sauce/#comment-198455</link>
		<dc:creator><![CDATA[Dr. S. V. Ranade]]></dc:creator>
		<pubDate>Sun, 13 Apr 2008 12:24:47 +0000</pubDate>
		<guid isPermaLink="false">http://foundread.com/?p=684#comment-198455</guid>
		<description><![CDATA[I am running a small web design company in India and have similar problems in effective management and marketing. I realised for the first time importance and need of documentation.  I shall adopt your method and ask all my staff to do the same.Thanks for the tips.]]></description>
		<content:encoded><![CDATA[<p>I am running a small web design company in India and have similar problems in effective management and marketing. I realised for the first time importance and need of documentation.  I shall adopt your method and ask all my staff to do the same.Thanks for the tips.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marko</title>
		<link>http://gigaom.com/2008/04/08/10-reasons-why-documentation-is-a-startup-secret-sauce/#comment-198454</link>
		<dc:creator><![CDATA[Marko]]></dc:creator>
		<pubDate>Fri, 11 Apr 2008 05:01:01 +0000</pubDate>
		<guid isPermaLink="false">http://foundread.com/?p=684#comment-198454</guid>
		<description><![CDATA[Yep, this is the main gimmick of &quot;The E-Myth.&quot; Think of your business as a potential franchise, and document it in such a way that you could in theory bring in all new people, give them the docs and a few days training, go on a yearlong vacation, and the business would still work.



A side effect of this is that you can hire inexperienced (i.e., cheap) staff.



It&#039;s also the &quot;Is it a job or a business?&quot; test. You can sell businesses, but not jobs.



Your&#039; restatement was much better than the book, which is terribly written and frustrating. Why don&#039;t you write a book?]]></description>
		<content:encoded><![CDATA[<p>Yep, this is the main gimmick of &#8220;The E-Myth.&#8221; Think of your business as a potential franchise, and document it in such a way that you could in theory bring in all new people, give them the docs and a few days training, go on a yearlong vacation, and the business would still work.</p>
<p>A side effect of this is that you can hire inexperienced (i.e., cheap) staff.</p>
<p>It&#8217;s also the &#8220;Is it a job or a business?&#8221; test. You can sell businesses, but not jobs.</p>
<p>Your&#8217;restatement was much better than the book, which is terribly written and frustrating. Why don&#8217;t you write a book?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shiva</title>
		<link>http://gigaom.com/2008/04/08/10-reasons-why-documentation-is-a-startup-secret-sauce/#comment-198453</link>
		<dc:creator><![CDATA[Shiva]]></dc:creator>
		<pubDate>Wed, 09 Apr 2008 05:15:53 +0000</pubDate>
		<guid isPermaLink="false">http://foundread.com/?p=684#comment-198453</guid>
		<description><![CDATA[I am sure all the people working in QA/QC or some form of process will be happy to read this.]]></description>
		<content:encoded><![CDATA[<p>I am sure all the people working in QA/QC or some form of process will be happy to read this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sakin</title>
		<link>http://gigaom.com/2008/04/08/10-reasons-why-documentation-is-a-startup-secret-sauce/#comment-198452</link>
		<dc:creator><![CDATA[Sakin]]></dc:creator>
		<pubDate>Wed, 09 Apr 2008 04:16:43 +0000</pubDate>
		<guid isPermaLink="false">http://foundread.com/?p=684#comment-198452</guid>
		<description><![CDATA[Documentation is very important for company startups as it lays down the strategic objectives/goals of the company leading to the company vision. Documentation also helps you to keep in track of your progress and achievements. It improves the work efficiency and quality.



But be aware too much of documentation will prevent innovation which is very important to become competitive and successful in this global competitive market. Documents also make your associate more followers then the leaders.



So, my conclusion is that keep documentation flexible enough so that there is room for innovation. Find out which task need to be fully documented and which need to be flexible. Make a strategy and succession plan for it. For example: It can be like this: Write step-by-step documents for the routine and daily works to improve efficiency and quality. But always make flexible documents for company strategies, plans, objectives and goals which needs to be evolved as the situation demands.]]></description>
		<content:encoded><![CDATA[<p>Documentation is very important for company startups as it lays down the strategic objectives/goals of the company leading to the company vision. Documentation also helps you to keep in track of your progress and achievements. It improves the work efficiency and quality.</p>
<p>But be aware too much of documentation will prevent innovation which is very important to become competitive and successful in this global competitive market. Documents also make your associate more followers then the leaders.</p>
<p>So, my conclusion is that keep documentation flexible enough so that there is room for innovation. Find out which task need to be fully documented and which need to be flexible. Make a strategy and succession plan for it. For example: It can be like this: Write step-by-step documents for the routine and daily works to improve efficiency and quality. But always make flexible documents for company strategies, plans, objectives and goals which needs to be evolved as the situation demands.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam</title>
		<link>http://gigaom.com/2008/04/08/10-reasons-why-documentation-is-a-startup-secret-sauce/#comment-198451</link>
		<dc:creator><![CDATA[Adam]]></dc:creator>
		<pubDate>Tue, 08 Apr 2008 23:45:21 +0000</pubDate>
		<guid isPermaLink="false">http://foundread.com/?p=684#comment-198451</guid>
		<description><![CDATA[This is one of the central messages of the book, &quot;The E-Myth Revisited.&quot; &quot;E&quot; as in entrepreneur. It&#039;s a great read, and I recommend it to anybody who is serious about starting their own company and being successful.



The author calls what you have described as the &quot;Franchise effect.&quot;]]></description>
		<content:encoded><![CDATA[<p>This is one of the central messages of the book, &#8220;The E-Myth Revisited.&#8221; &#8220;E&#8221; as in entrepreneur. It&#8217;s a great read, and I recommend it to anybody who is serious about starting their own company and being successful.</p>
<p>The author calls what you have described as the &#8220;Franchise effect.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith Barrows - StarPilot : Getting started for the long haul...</title>
		<link>http://gigaom.com/2008/04/08/10-reasons-why-documentation-is-a-startup-secret-sauce/#comment-198450</link>
		<dc:creator><![CDATA[Keith Barrows - StarPilot : Getting started for the long haul...]]></dc:creator>
		<pubDate>Tue, 08 Apr 2008 17:19:18 +0000</pubDate>
		<guid isPermaLink="false">http://foundread.com/?p=684#comment-198450</guid>
		<description><![CDATA[[...] framework - not once but 5 times so far.&#160; I just read an article on Found/Read titled 10 Reasons Why Documentation is a Startup Secret Sauce.&#160; Believe me, not having the documentation extends my time on the order of 10 or 20 times when [...]]]></description>
		<content:encoded><![CDATA[<p>[...] framework &#8211; not once but 5 times so far.&#160; I just read an article on Found/Read titled 10 Reasons Why Documentation is a Startup Secret Sauce.&#160; Believe me, not having the documentation extends my time on the order of 10 or 20 times when [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2008-04-08 &#171; Brent Sordyl&#8217;s Blog</title>
		<link>http://gigaom.com/2008/04/08/10-reasons-why-documentation-is-a-startup-secret-sauce/#comment-198449</link>
		<dc:creator><![CDATA[links for 2008-04-08 &#171; Brent Sordyl&#8217;s Blog]]></dc:creator>
		<pubDate>Tue, 08 Apr 2008 15:38:48 +0000</pubDate>
		<guid isPermaLink="false">http://foundread.com/?p=684#comment-198449</guid>
		<description><![CDATA[[...] 10 Reasons Why Documentation is a Startup Secret Sauce 9) Documentation signals that you are a professional and someone who cares enough about what they do to write it down and analyze it. They will be proud to work for you. (tags: documentation) [...]]]></description>
		<content:encoded><![CDATA[<p>[...] 10 Reasons Why Documentation is a Startup Secret Sauce 9) Documentation signals that you are a professional and someone who cares enough about what they do to write it down and analyze it. They will be proud to work for you. (tags: documentation) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dtenner</title>
		<link>http://gigaom.com/2008/04/08/10-reasons-why-documentation-is-a-startup-secret-sauce/#comment-198448</link>
		<dc:creator><![CDATA[dtenner]]></dc:creator>
		<pubDate>Tue, 08 Apr 2008 12:56:57 +0000</pubDate>
		<guid isPermaLink="false">http://foundread.com/?p=684#comment-198448</guid>
		<description><![CDATA[I think you should draw a line between documenting information and documenting plans and expectations. Writing down thing like a business plan or a development plan fits your description very well and is indeed worth doing at every stage of a company. But at the other end of the spectrum, documenting, say, the process by which you log in to your company&#039;s bank account to make a payment has very little value early on in the life of a company.



Not all documentation is equal. The key is to document the right things and ignore the rest. How do you tell what the right things are? Well, experience helps. If you got shafted by not having documented it before, you&#039;ll probably make sure it&#039;s documented in the future!]]></description>
		<content:encoded><![CDATA[<p>I think you should draw a line between documenting information and documenting plans and expectations. Writing down thing like a business plan or a development plan fits your description very well and is indeed worth doing at every stage of a company. But at the other end of the spectrum, documenting, say, the process by which you log in to your company&#8217;s bank account to make a payment has very little value early on in the life of a company.</p>
<p>Not all documentation is equal. The key is to document the right things and ignore the rest. How do you tell what the right things are? Well, experience helps. If you got shafted by not having documented it before, you&#8217;ll probably make sure it&#8217;s documented in the future!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anders Toxboe</title>
		<link>http://gigaom.com/2008/04/08/10-reasons-why-documentation-is-a-startup-secret-sauce/#comment-198447</link>
		<dc:creator><![CDATA[Anders Toxboe]]></dc:creator>
		<pubDate>Tue, 08 Apr 2008 09:15:40 +0000</pubDate>
		<guid isPermaLink="false">http://foundread.com/?p=684#comment-198447</guid>
		<description><![CDATA[Documentation is great for routine-based businesses - like the one you describe -&gt; answering emergency calls. It might actually be the key here, as you describe, although it sounds like it&#039;s the process of defining and standardizing your processes that was what benefitted you - not the documentation itself.



I believe it&#039;s important to stress that in more creativity oriented companies - like software companies - documentation can be a stopper. My belief tells me that documentation should only be written down if is has a purpose, which it clearly did in your case. Documentation for the sake of documentation will only lead to bureaucracy and a comprehensive compilation of documents that constantly screams to be updated. In the latter case, your company might suffer from the infamous &quot;death by documentation&quot;...]]></description>
		<content:encoded><![CDATA[<p>Documentation is great for routine-based businesses &#8211; like the one you describe -&gt; answering emergency calls. It might actually be the key here, as you describe, although it sounds like it&#8217;s the process of defining and standardizing your processes that was what benefitted you &#8211; not the documentation itself.</p>
<p>I believe it&#8217;s important to stress that in more creativity oriented companies &#8211; like software companies &#8211; documentation can be a stopper. My belief tells me that documentation should only be written down if is has a purpose, which it clearly did in your case. Documentation for the sake of documentation will only lead to bureaucracy and a comprehensive compilation of documents that constantly screams to be updated. In the latter case, your company might suffer from the infamous &#8220;death by documentation&#8221;&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Get your commitments on paper &#8212; Battling It Solo</title>
		<link>http://gigaom.com/2008/04/08/10-reasons-why-documentation-is-a-startup-secret-sauce/#comment-198446</link>
		<dc:creator><![CDATA[Get your commitments on paper &#8212; Battling It Solo]]></dc:creator>
		<pubDate>Tue, 08 Apr 2008 07:57:23 +0000</pubDate>
		<guid isPermaLink="false">http://foundread.com/?p=684#comment-198446</guid>
		<description><![CDATA[[...] now I may. After reading &#8216;10 Reasons Why Documentation is a Startup Secret Sauce&#8217; from FoundRead, I&#8217;m convinced that the idea about writing things down is excactly right. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] now I may. After reading &#8216;10 Reasons Why Documentation is a Startup Secret Sauce&#8217; from FoundRead, I&#8217;m convinced that the idea about writing things down is excactly right. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

