<?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"
	>
<channel>
	<title>Comments on: There He Was&#8230; Gone</title>
	<atom:link href="http://www.errantdreams.com/ardor/2007/05/05/there-he-was-gone/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.errantdreams.com/ardor/2007/05/05/there-he-was-gone/</link>
	<description>"Science is the study of what is. Engineering builds what will be." -- Theodore von Karman</description>
	<pubDate>Tue, 07 Oct 2008 13:37:57 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Cian</title>
		<link>http://www.errantdreams.com/ardor/2007/05/05/there-he-was-gone/#comment-45</link>
		<dc:creator>Cian</dc:creator>
		<pubDate>Mon, 05 May 2008 15:34:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.errantdreams.com/ardor/2007/05/05/there-he-was-gone/#comment-45</guid>
		<description>I really like those rules a lot. The ones I would add are ones that I have had issues with, and generally affect the larger organization. If you have these problems in a small company you are in real trouble.
1. Incent everyone to work toward a common goal.
2. Don't create systems with conflicting objectives and then ask/expect people to be team players.
3. Either have managers who have the authority to make decisions, or take out a bunch of layers.
4. Don't stop listening to the people that actually do the work.</description>
		<content:encoded><![CDATA[<p>I really like those rules a lot. The ones I would add are ones that I have had issues with, and generally affect the larger organization. If you have these problems in a small company you are in real trouble.<br />
1. Incent everyone to work toward a common goal.<br />
2. Don&#8217;t create systems with conflicting objectives and then ask/expect people to be team players.<br />
3. Either have managers who have the authority to make decisions, or take out a bunch of layers.<br />
4. Don&#8217;t stop listening to the people that actually do the work.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
