<?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: The problem with learning reviews…</title>
	<atom:link href="http://www.theproposalguys.com/2006/04/26/the-problem-with-learning-reviews%e2%80%a6/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.theproposalguys.com/2006/04/26/the-problem-with-learning-reviews%e2%80%a6/</link>
	<description>Jon and B.J.&#039;s Proposal Blog</description>
	<lastBuildDate>Tue, 17 Jan 2012 20:30:46 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: BJ</title>
		<link>http://www.theproposalguys.com/2006/04/26/the-problem-with-learning-reviews%e2%80%a6/comment-page-1/#comment-5</link>
		<dc:creator>BJ</dc:creator>
		<pubDate>Fri, 05 May 2006 20:47:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.theproposalguys.com/2006/04/26/the-problem-with-learning-reviews%e2%80%a6/#comment-5</guid>
		<description>AND - leave us not forget that reviewing the process - the planning, management, team, milestones and such - is critical as well (Those who know both Jon and I will know that Jon leans a bit to the front side of the process - that being the business aspects - while I lean a bit more towards the process side - that being proposal management, etc.

Too often, in my experience, the focus of a learning review is entirely on the business aspects. 

Discovering, capturing and taken actions on all the areas Jon mentions is critical .

But if the way you produce proposals isn&#039;t reviewed, and to Jon&#039;s point, action isn&#039;t taken, then how will the process ever improve (and how will you ever get out of the &#039;Late nights, cold pizza&#039; syndrome.

I divide a learning review into three areas - the Strategy (every thing related to the &#039;sell&#039;), the Document (the proposal itself) and the Plan (every thing related to producing the proposal)</description>
		<content:encoded><![CDATA[<p>AND &#8211; leave us not forget that reviewing the process &#8211; the planning, management, team, milestones and such &#8211; is critical as well (Those who know both Jon and I will know that Jon leans a bit to the front side of the process &#8211; that being the business aspects &#8211; while I lean a bit more towards the process side &#8211; that being proposal management, etc.</p>
<p>Too often, in my experience, the focus of a learning review is entirely on the business aspects. </p>
<p>Discovering, capturing and taken actions on all the areas Jon mentions is critical .</p>
<p>But if the way you produce proposals isn&#8217;t reviewed, and to Jon&#8217;s point, action isn&#8217;t taken, then how will the process ever improve (and how will you ever get out of the &#8216;Late nights, cold pizza&#8217; syndrome.</p>
<p>I divide a learning review into three areas &#8211; the Strategy (every thing related to the &#8217;sell&#8217;), the Document (the proposal itself) and the Plan (every thing related to producing the proposal)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

