<?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:rssFeedStyles="http://www.lerougeliet.com/ns/rssFeedStyles#"

	>
<channel>
	<title>
	Comments on: Five ways to make and execute a great plan	</title>
	<atom:link href="https://berkonomics.com/?feed=rss2&#038;p=4759" rel="self" type="application/rss+xml" />
	<link>https://berkonomics.com/?p=4759&#038;utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=five-ways-to-make-and-execute-a-great-plan</link>
	<description>Dave Berkus&#039; business insights</description>
	<lastBuildDate>Mon, 08 Nov 2021 21:15:50 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0</generator>
	<item>
		<title>
		By: Michael O'Daniel		</title>
		<link>https://berkonomics.com/?p=4759&#038;cpage=1#comment-153229</link>

		<dc:creator><![CDATA[Michael O'Daniel]]></dc:creator>
		<pubDate>Mon, 08 Nov 2021 21:15:50 +0000</pubDate>
		<guid isPermaLink="false">https://berkonomics.com/?p=4759#comment-153229</guid>

					<description><![CDATA[I would add a couple more steps. And BTW actively soliciting and acting upon feedback, and reporting the steps taken in response to the feedback, is indeed critical and, Bravo! for including that in two different configurations (Provide feedback loops, Listen to complaints etc.).

What any plan or project also needs are:

1. An ongoing communications process so that everyone affected is kept apprised of milestones reached or not reached, and the gaps that still need to be closed to reach the milestones. This is also a good time to ask for additional feedback, e.g. we thought we were on the right path, but we&#039;re coming up short, so how can we correct that?

A broad-based communications process is important. Even if responsibility for the plan or project only dwells within one department, if you step back and look at your overall organizational structure, you&#039;ll recognize that there are other departments affected as well. So it&#039;s important to keep them in the loop.

2. A &quot;gated process,&quot; meaning that until one step of the plan has been completed, and signed off on by whoever is charged with doing so, no one has permission to advance to the next step until the current step has been successfully completed. And the accent is on &quot;successfully&quot; rather than merely &quot;completed.&quot; For example, training is a particular area where completion often takes precedence over success. &quot;Yeah, we completed the training, here&#039;s the manual,&quot; instead of &quot;Here&#039;s what our trainees knew previously, and here&#039;s what [this percentage of them] they know now, here are the gaps that still need to be closed, and here&#039;s how we&#039;re going to do that.&quot;

The gated process is necessary to keep the plan or the project on the right path toward success. A common temptation is to say &quot;We didn&#039;t quite complete that step, but we&#039;ve got to move on, so we&#039;ll come back and fix it later.&quot; And then guess what? It never gets fixed. Plan or project deadlines can and should be adjusted to ensure successful completion of each step rather than trying to meet a deadline just for the sake of meeting the deadline. The challenge is to balance the urgency of meeting an often artificial deadline with the measured approach to making the plan or project a success.]]></description>
			<content:encoded><![CDATA[<p>I would add a couple more steps. And BTW actively soliciting and acting upon feedback, and reporting the steps taken in response to the feedback, is indeed critical and, Bravo! for including that in two different configurations (Provide feedback loops, Listen to complaints etc.).</p>
<p>What any plan or project also needs are:</p>
<p>1. An ongoing communications process so that everyone affected is kept apprised of milestones reached or not reached, and the gaps that still need to be closed to reach the milestones. This is also a good time to ask for additional feedback, e.g. we thought we were on the right path, but we&#8217;re coming up short, so how can we correct that?</p>
<p>A broad-based communications process is important. Even if responsibility for the plan or project only dwells within one department, if you step back and look at your overall organizational structure, you&#8217;ll recognize that there are other departments affected as well. So it&#8217;s important to keep them in the loop.</p>
<p>2. A &#8220;gated process,&#8221; meaning that until one step of the plan has been completed, and signed off on by whoever is charged with doing so, no one has permission to advance to the next step until the current step has been successfully completed. And the accent is on &#8220;successfully&#8221; rather than merely &#8220;completed.&#8221; For example, training is a particular area where completion often takes precedence over success. &#8220;Yeah, we completed the training, here&#8217;s the manual,&#8221; instead of &#8220;Here&#8217;s what our trainees knew previously, and here&#8217;s what [this percentage of them] they know now, here are the gaps that still need to be closed, and here&#8217;s how we&#8217;re going to do that.&#8221;</p>
<p>The gated process is necessary to keep the plan or the project on the right path toward success. A common temptation is to say &#8220;We didn&#8217;t quite complete that step, but we&#8217;ve got to move on, so we&#8217;ll come back and fix it later.&#8221; And then guess what? It never gets fixed. Plan or project deadlines can and should be adjusted to ensure successful completion of each step rather than trying to meet a deadline just for the sake of meeting the deadline. The challenge is to balance the urgency of meeting an often artificial deadline with the measured approach to making the plan or project a success.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
