<?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: Focus Your Efforts on Plan &#8220;A&#8221;</title>
	<atom:link href="http://www.leadershipandcommunity.com/2010/06/28/focus-your-efforts-on-plan-a/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.leadershipandcommunity.com/2010/06/28/focus-your-efforts-on-plan-a/</link>
	<description>Awareness, Development and Action in the Twin Cities</description>
	<lastBuildDate>Wed, 08 Feb 2012 21:43:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Nate Smith</title>
		<link>http://www.leadershipandcommunity.com/2010/06/28/focus-your-efforts-on-plan-a/comment-page-1/#comment-595</link>
		<dc:creator>Nate Smith</dc:creator>
		<pubDate>Thu, 01 Jul 2010 16:23:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.leadershipandcommunity.com/?p=1300#comment-595</guid>
		<description>Sheila,

Love it.  Here&#039;s an expansion on your thesis, as food for thought:

Plans, however static they  are before they commence, become organic thereafter.

The old military axiom, &quot;The moment the first bullet is fired, all plans are thrown out the window&quot;, is true because once things happen, things _change_.

Coming up with a secondary plan for a different set of static (because they haven&#039;t happened yet) variables is a waste of time.  If Plan A is the best plan, it&#039;s the only one worth going with because once the variables change ( and often they&#039;ve changed beyond anything you might have been able to predict given information on-hand during the planning stage), Plan A, Plan B, and however many other plans you layed out on nice white paper is so much garbage.  You kick off Plan A, and you are immediately, and automatically, working on a new Plan A given the new set of variables.

Coming up with multiple plans is a great way to show off how smart you are, but execution isn&#039;t only about being smart, it&#039;s about getting the bucket of water up the hill.  Go with your Plan A, and then keep driving when things change.  I&#039;ll cite an software development axiom I&#039;ve heard before, then shut up:  &quot;Launch early, and launch often.  Iterate.  Your customers will teach you what you never could have planned for.&quot;

Thanks for your post!

Nate Smith</description>
		<content:encoded><![CDATA[<p>Sheila,</p>
<p>Love it.  Here&#8217;s an expansion on your thesis, as food for thought:</p>
<p>Plans, however static they  are before they commence, become organic thereafter.</p>
<p>The old military axiom, &#8220;The moment the first bullet is fired, all plans are thrown out the window&#8221;, is true because once things happen, things _change_.</p>
<p>Coming up with a secondary plan for a different set of static (because they haven&#8217;t happened yet) variables is a waste of time.  If Plan A is the best plan, it&#8217;s the only one worth going with because once the variables change ( and often they&#8217;ve changed beyond anything you might have been able to predict given information on-hand during the planning stage), Plan A, Plan B, and however many other plans you layed out on nice white paper is so much garbage.  You kick off Plan A, and you are immediately, and automatically, working on a new Plan A given the new set of variables.</p>
<p>Coming up with multiple plans is a great way to show off how smart you are, but execution isn&#8217;t only about being smart, it&#8217;s about getting the bucket of water up the hill.  Go with your Plan A, and then keep driving when things change.  I&#8217;ll cite an software development axiom I&#8217;ve heard before, then shut up:  &#8220;Launch early, and launch often.  Iterate.  Your customers will teach you what you never could have planned for.&#8221;</p>
<p>Thanks for your post!</p>
<p>Nate Smith</p>
]]></content:encoded>
	</item>
</channel>
</rss>

