<?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"
	>
<channel>
	<title>Comments on: Delegating Like a Pro in 10 Easy Steps!</title>
	<atom:link href="http://vervecoaching.com/delegating-like-a-pro-in-10-easy-steps/feed/" rel="self" type="application/rss+xml" />
	<link>http://vervecoaching.com/delegating-like-a-pro-in-10-easy-steps/</link>
	<description>Expert Coaching for Entrepreneurs, Small Business Executives &#38; Aspiring Leaders</description>
	<pubDate>Thu, 04 Dec 2008 04:40:46 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Ellis Cohen</title>
		<link>http://vervecoaching.com/delegating-like-a-pro-in-10-easy-steps/#comment-40185</link>
		<dc:creator>Ellis Cohen</dc:creator>
		<pubDate>Sat, 17 May 2008 14:29:08 +0000</pubDate>
		<guid isPermaLink="false">http://vervecoaching.com/?p=237#comment-40185</guid>
		<description>I really like the notion of asking the person if you can count on them not just to do the job, but to do it as you asked.  Of course, even if they answer yes, there will be plenty of cases when they don't -- perhaps because they didn't allocate time to get the job done, or because they didn't understand something and didn't want to look bad, so they didn't ask.  Reports really do help here -- and the ones that are vague or ambiguous are your wake-up call to go get more information.  And still things don't work out -- there's a mismatch in understanding assumptions, or techniques or goals which sometimes don't get discovered until too late.

It's tempting (if you don't just give up and do things yourself, as Kelly notes) to immediately think about improving or adding reports and other processes, and sometimes that is the right thing to do.  But it's equally important to improve reflection and communication -- to create a culture where the people you delegate to think about whether they've got the assumptions, techniques and goals right, raise their own questions, and discuss them with each other and with you.  Of course, creating that culture could be a whole other article.</description>
		<content:encoded><![CDATA[<p>I really like the notion of asking the person if you can count on them not just to do the job, but to do it as you asked.  Of course, even if they answer yes, there will be plenty of cases when they don&#8217;t &#8212; perhaps because they didn&#8217;t allocate time to get the job done, or because they didn&#8217;t understand something and didn&#8217;t want to look bad, so they didn&#8217;t ask.  Reports really do help here &#8212; and the ones that are vague or ambiguous are your wake-up call to go get more information.  And still things don&#8217;t work out &#8212; there&#8217;s a mismatch in understanding assumptions, or techniques or goals which sometimes don&#8217;t get discovered until too late.</p>
<p>It&#8217;s tempting (if you don&#8217;t just give up and do things yourself, as Kelly notes) to immediately think about improving or adding reports and other processes, and sometimes that is the right thing to do.  But it&#8217;s equally important to improve reflection and communication &#8212; to create a culture where the people you delegate to think about whether they&#8217;ve got the assumptions, techniques and goals right, raise their own questions, and discuss them with each other and with you.  Of course, creating that culture could be a whole other article.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
