<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>3 Simple Rules &#187; Performance Management</title>
	<atom:link href="http://www.3simplerules.com/category/performance-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.3simplerules.com</link>
	<description>Over 80 years of research</description>
	<lastBuildDate>Tue, 01 Apr 2008 22:08:06 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>After Action Reviews &#8211; keeping them simple</title>
		<link>http://www.3simplerules.com/2008/03/the-after-action-reviews-keeping-them-simple/</link>
		<comments>http://www.3simplerules.com/2008/03/the-after-action-reviews-keeping-them-simple/#comments</comments>
		<pubDate>Sun, 09 Mar 2008 09:32:57 +0000</pubDate>
		<dc:creator>Bruce</dc:creator>
				<category><![CDATA[Behaviour]]></category>
		<category><![CDATA[Performance Management]]></category>

		<guid isPermaLink="false">http://www.3simplerules.com/?p=46</guid>
		<description><![CDATA[Seven years ago we were introduced to the concept of an After Action Review and&#160;we have been using it ever since.&#160; The purpose of the tool is just like it sounds, to review the action that has just happened.&#160; The tool&#160;was created by&#160;the US military about 20 years ago.&#160;&#160;If you search for it in google&#160;you [...]]]></description>
			<content:encoded><![CDATA[<p><img height="152" alt="" hspace="10" src="http://www.3simplerules.com/images/afteraction.jpg" width="200" align="right" vspace="10" border="10" />Seven years ago we were introduced to the concept of an <a href="http://en.wikipedia.org/wiki/After_Action_Review">After Action Review</a> and&nbsp;we have been using it ever since.&nbsp; The purpose of the tool is just like it sounds, to review the action that has just happened.&nbsp; The tool&nbsp;was created by&nbsp;the <a href="http://www.au.af.mil/au/awc/awcgate/army/tc_25-20/chap1.htm">US military</a> about 20 years ago.&nbsp;&nbsp;If you search for it in <a href="http://www.google.co.uk/search?hl=en&amp;q=after+action+review&amp;btnG=Google+Search&amp;meta=">google</a>&nbsp;you will find quite a few documents most of which go into all the finer details of how to conduct the review, examples of which can be found <a href="http://35.8.109.2/resources/TC25-20AARs.pdf">here</a> and <a href="http://pdf.dec.org/pdf_docs/PNADF360.pdf">here</a>.&nbsp; </p>
<p>A core part of what we do as a business is to simplify tools and techniques so that people can get most of a tool&#8217;s&nbsp;benefit without all the usual overhead.&nbsp; What we are sharing with you here is&nbsp;a simplified approach to&nbsp;the after action review.&nbsp; We have also identified the&nbsp;few critical behaviours that&nbsp;you&nbsp;need to focus on&nbsp;during the review&nbsp;and have provided an explanation of why this approach aids learning.</p>
<p><strong><em>The Approach<br /></em></strong>&nbsp;<br />Tell the team that you want to set aside 5 to 10 minutes right after a meeting to hold an After Action Review.&nbsp; Use the following set of questions to conduct the review; </p>
<blockquote>
<p>What result did you expect?</p>
<ul>
<li>What went well? </li>
<li>What didn&#8217;t go so well? </li>
<li>What would you do differently next time? </li>
</ul>
</blockquote>
<p>The <em>result</em> question sets the context for answering the other questions.</p>
<p><strong><em>The Leverage</em></strong></p>
<p>As the person asking the questions you&nbsp;need to be sure not to over react to any of the responses you receive.&nbsp;&nbsp; Take a minute before the review starts&nbsp;to think about&nbsp;one thing you want them to learn.&nbsp; Having thought about a learning point you are ready to begin asking the questions.&nbsp; <em>Remember, once you ask a question shut up, listen and let them do the talking.</em>&nbsp; </p>
<p>Getting people to engage in acts of self reporting is a very powerful learning technique.&nbsp;&nbsp;The &quot;<em>What didn&#8217;t go so well?</em>&quot; question contains the leverage.&nbsp; Most of the time they will know what didn&#8217;t work and will have some idea of what they could have done differently.&nbsp;&nbsp; Once&nbsp;they have found something that is worth improving you should conclude the meeting.&nbsp; Don&#8217;t try to over reach by drilling into them&nbsp;with loads of additional questions.&nbsp; By keeping the session brief and relaxed there is the potential for these reviews to become very reinforcing.</p>
<p><strong><em>Why it creates learning</em></strong></p>
<p>If you think about the interaction you will recognise that you didn&#8217;t have to point out what went wrong, they were able to figure it out themselves.&nbsp; Research has shown that we are far more likely to do something we choose compared to something that is imposed upon us.&nbsp; The things to do differently next time were chosen by&nbsp;them not you.</p>
<p>Make sure the review happens right after the event, this will capture the feedback while everyone&#8217;s memory is still fresh.&nbsp; Holding the review&nbsp;creates the opportunity for learning but it is <em>your&nbsp;behaviour of listening and not over reacting</em> that&nbsp;ensures the learning occurs.</p>
<p>Give it a try and let us know how it went.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.3simplerules.com/2008/03/the-after-action-reviews-keeping-them-simple/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Hole Management: Getting Started with Plan vs. Actual</title>
		<link>http://www.3simplerules.com/2007/09/hole-management-getting-started-with-plan-vs-actual/</link>
		<comments>http://www.3simplerules.com/2007/09/hole-management-getting-started-with-plan-vs-actual/#comments</comments>
		<pubDate>Sat, 08 Sep 2007 19:51:41 +0000</pubDate>
		<dc:creator>Bruce</dc:creator>
				<category><![CDATA[Performance Management]]></category>

		<guid isPermaLink="false">http://www.3simplerules.com/?p=45</guid>
		<description><![CDATA[Getting yourself out of a hole means getting started with performance management.&#160; Pull together a plan and tracking your progress against that plan. The plan represents the work you need to accomplish over a period of time.&#160; A typical approach is to break the work down into a set of deliverables.[1]&#160; Count the number of [...]]]></description>
			<content:encoded><![CDATA[<p>Getting yourself out of a hole means getting started with performance management.&nbsp; Pull together a plan and tracking your progress against that plan.</p>
<p><span id="more-45"></span></p>
<p>The plan represents the work you need to accomplish over a period of time.&nbsp; A typical approach is to break the work down into a set of deliverables.<sup><a id='note-45-1' href='#footnote-45-1'>[1]</a></sup>&nbsp; Count the number of deliverables you will have to produce by day, week or month.&nbsp; Then put it on a graph and begin to track your progress.</p>
<p></p>
<p><img width="500" height="253" src="http://www.3simplerules.com/images/planvactual.png" alt="" /></p>
<p>A simple Plan vs. Actual graph is a great tool for focusing a team on what needs to get done.&nbsp; It is easy to see what you intended to do and what you actually did.&nbsp; Your ability to change your performance occurs at the rate of measurement;</p>
<ul>
<li>Monthly and you have to wait months to see the change </li>
<li>Weekly and you have to wait weeks to see the change </li>
<li>Daily and you will only need days to see the change </li>
</ul>
<p>Think about it from an improvement opportunity perspective.&nbsp; Monthly means you have 12 opportunities a year to make adjustments using data, weekly &#8211; 52 times a year, and daily 260 times a year.</p>
<p>If you are the leader then your job is to create the environment for the team to deliver the plan.&nbsp; If the team isn&#8217;t delivering then they should be coming to you asking for things such as;</p>
<ul>
<li>More time</li>
<li>More money or people</li>
<li>or they can&#8217;t recover</li>
</ul>
<p>If this isn&#8217;t happening then you haven&#8217;t created an environment where they can give you bad news.<sup><a id='note-45-2' href='#footnote-45-2'>[2]</a></sup></p>
<p>A mentor of mine, Charlie Remsen, always said; &quot;Begin with the end in mind.&quot;&nbsp; Set out with a plan of what you need to deliver, measure your progress, adjust as necessary and chances are you deliver more that if you hadn&#8217;t tracked your progress.</p>
<p><a href="http://www.3simplerules.com/docs/plan-actual.zip"><img width="20" height="20" alt="" src="http://www.3simplerules.com/docs/download.png" /> Template for Plan vs. Actual Graph</a><br />&nbsp;</p>
<ol class='footnotes'>
	<li id='footnote-45-1'><a href='#note-45-1'>&uarr;1</a> A deliverable is just like it sounds, something that you &quot;deliver&quot; to someone else.&nbsp; These deliverables should make sense for the context of your business.&nbsp;&nbsp; For example drawings, approvals, assessments or other such things. </li>
	<li id='footnote-45-2'><a href='#note-45-2'>&uarr;2</a> If you don&#8217;t take bad news well then you won&#8217;t get any. </li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.3simplerules.com/2007/09/hole-management-getting-started-with-plan-vs-actual/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
