<?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 only way to do a handover	</title>
	<atom:link href="https://lobsterpot.com.au/blog/2006/12/19/the-only-way-to-do-a-handover/feed/" rel="self" type="application/rss+xml" />
	<link>https://lobsterpot.com.au/blog/2006/12/19/the-only-way-to-do-a-handover/</link>
	<description></description>
	<lastBuildDate>Mon, 27 Jul 2009 06:29:04 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		By: Theresa Glenister		</title>
		<link>https://lobsterpot.com.au/blog/2006/12/19/the-only-way-to-do-a-handover/#comment-177</link>

		<dc:creator><![CDATA[Theresa Glenister]]></dc:creator>
		<pubDate>Mon, 27 Jul 2009 06:29:04 +0000</pubDate>
		<guid isPermaLink="false">/blogs/robfarley/archive/2006/12/19/the-only-way-to-do-a-handover.aspx#comment-177</guid>

					<description><![CDATA[Does anyone have a department handover template?]]></description>
			<content:encoded><![CDATA[<p>Does anyone have a department handover template?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: robfarley		</title>
		<link>https://lobsterpot.com.au/blog/2006/12/19/the-only-way-to-do-a-handover/#comment-176</link>

		<dc:creator><![CDATA[robfarley]]></dc:creator>
		<pubDate>Wed, 20 Dec 2006 01:41:19 +0000</pubDate>
		<guid isPermaLink="false">/blogs/robfarley/archive/2006/12/19/the-only-way-to-do-a-handover.aspx#comment-176</guid>

					<description><![CDATA[But that&#039;s why you should practise. And anything that you find needs to be communicated outside the documentation should then be added to the documentation so that everything is known.

Wikis can help here too, of course.]]></description>
			<content:encoded><![CDATA[<p>But that&#8217;s why you should practise. And anything that you find needs to be communicated outside the documentation should then be added to the documentation so that everything is known.</p>
<p>Wikis can help here too, of course.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Yasas		</title>
		<link>https://lobsterpot.com.au/blog/2006/12/19/the-only-way-to-do-a-handover/#comment-175</link>

		<dc:creator><![CDATA[Yasas]]></dc:creator>
		<pubDate>Wed, 20 Dec 2006 00:28:06 +0000</pubDate>
		<guid isPermaLink="false">/blogs/robfarley/archive/2006/12/19/the-only-way-to-do-a-handover.aspx#comment-175</guid>

					<description><![CDATA[I agree with what you say in general, but I feel that really does not solve the problem fully. Even though you document what you do, the chances are high that you miss the tiny little points that you consider are not important, obvious or already known by the new guy. These are the exact points that you would miss during a verbal handover or a typical semi-documented handover.
So, in my opinion, it has to be a combination of all those that would be used. All or most (depending the situation) of the hand-over methods such as documentation, peer working, verbal, emails, casual chats, sharing all the info available, introducing to all possible contact points etc. have to be done.
I personally had the same experience that you have had. When I left the previous employer, they allocated a new person quickly, but the new person left after few months! Due to the panic, they could not find the best match for the role, but sent the available one directly to the deep-end, obviously the pressure and the ask would have been too much. So, this proves that apart from all the above mentioned methods, it is important to find the best match for the role even though there can be practical situations which are truly difficult.
 ]]></description>
			<content:encoded><![CDATA[<p>I agree with what you say in general, but I feel that really does not solve the problem fully. Even though you document what you do, the chances are high that you miss the tiny little points that you consider are not important, obvious or already known by the new guy. These are the exact points that you would miss during a verbal handover or a typical semi-documented handover.<br />
So, in my opinion, it has to be a combination of all those that would be used. All or most (depending the situation) of the hand-over methods such as documentation, peer working, verbal, emails, casual chats, sharing all the info available, introducing to all possible contact points etc. have to be done.<br />
I personally had the same experience that you have had. When I left the previous employer, they allocated a new person quickly, but the new person left after few months! Due to the panic, they could not find the best match for the role, but sent the available one directly to the deep-end, obviously the pressure and the ask would have been too much. So, this proves that apart from all the above mentioned methods, it is important to find the best match for the role even though there can be practical situations which are truly difficult.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Kibble the wonder Ox and his trusty sidekick Grim Reaper		</title>
		<link>https://lobsterpot.com.au/blog/2006/12/19/the-only-way-to-do-a-handover/#comment-174</link>

		<dc:creator><![CDATA[Kibble the wonder Ox and his trusty sidekick Grim Reaper]]></dc:creator>
		<pubDate>Tue, 19 Dec 2006 14:39:16 +0000</pubDate>
		<guid isPermaLink="false">/blogs/robfarley/archive/2006/12/19/the-only-way-to-do-a-handover.aspx#comment-174</guid>

					<description><![CDATA[&lt;p&gt;The same applies for promotion and not just with handover. If you share information with colleagues freely (as I know you do) then not only is handover a much simpler and smaller task, but your value as a knowledgable and capable employee is obvious at all times. Coupled with the documentation of howtos or knowledgebases identifying small but useful aspects of daily work this makes you an easy target for promotion. Conversely, the guy who hides all &#039;the secrets&#039; is seen as such and because nobody understands what he does and nobody else can do his job, he&#039;s kept exactly where he is. Often these people are actually incompetent, one of the &#039;qualities&#039; they are trying to hide.&lt;/p&gt;]]></description>
			<content:encoded><![CDATA[<p>The same applies for promotion and not just with handover. If you share information with colleagues freely (as I know you do) then not only is handover a much simpler and smaller task, but your value as a knowledgable and capable employee is obvious at all times. Coupled with the documentation of howtos or knowledgebases identifying small but useful aspects of daily work this makes you an easy target for promotion. Conversely, the guy who hides all &#8216;the secrets&#8217; is seen as such and because nobody understands what he does and nobody else can do his job, he&#8217;s kept exactly where he is. Often these people are actually incompetent, one of the &#8216;qualities&#8217; they are trying to hide.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
