<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Why Good Projects Fail Anyway</title>
	<link>http://www.reformingprojectmanagement.com/2003/08/26/219/</link>
	<description>The magazine for the project age</description>
	<pubDate>Fri, 16 May 2008 19:42:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Joe Ely
        </title>
		<link>http://www.reformingprojectmanagement.com/2003/08/26/219/#comment-33</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2003/08/26/219/#comment-33</guid>
					<description>
        A story showing Alexander's principle.  

When I went to Purdue in the early 70s, the grounds crew never built sidewalks after a new building was put up.  Instead, they just sat back and looked to see where the footpaths developed (figuring, as well, that college kids were too grungy in those days to worry about mud on their shoes).  

Then, after seeing the footpaths which mapped for them the most efficient pathways, they then poured the sidewalks.  

This illustrates the concept pretty well.  Thanks!
      </description>
		<content:encoded><![CDATA[<p>A story showing Alexander&#8217;s principle.  </p>
<p>When I went to Purdue in the early 70s, the grounds crew never built sidewalks after a new building was put up.  Instead, they just sat back and looked to see where the footpaths developed (figuring, as well, that college kids were too grungy in those days to worry about mud on their shoes).  </p>
<p>Then, after seeing the footpaths which mapped for them the most efficient pathways, they then poured the sidewalks.  </p>
<p>This illustrates the concept pretty well.  Thanks!
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
