<?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: Management by conversation</title>
	<atom:link href="http://www.nehrlich.com/blog/2004/10/07/management-by-conversation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nehrlich.com/blog/2004/10/07/management-by-conversation/</link>
	<description>Eric Nehrlich, Unrepentant Generalist</description>
	<lastBuildDate>Thu, 09 Feb 2012 09:24:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: Dave</title>
		<link>http://www.nehrlich.com/blog/2004/10/07/management-by-conversation/comment-page-1/#comment-42443</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Wed, 09 May 2007 05:23:36 +0000</pubDate>
		<guid isPermaLink="false">/?p=122#comment-42443</guid>
		<description>(nods) I used to frequently describe my job as a series of exchanges where people would say &quot;I have a problem, X, with solution Y. What should I do?&quot;

And I would say &quot;Wait, wait, wait. Your problem is X?&quot; And they would nod.
And I would say &quot;And your solution is Y?&quot; And they would say &quot;Great, thanks!&quot; and run off.

And I&#039;ve become used to writing emails that go &quot;I don&#039;t really understand your question. You _might_ mean X, but you probably don&#039;t. You _might_ mean Y, but that would be stupid. You might mean Z... in fact you almost certainly do.&quot; then deleting that email and starting over with   &quot;Assuming you mean Z, the answer is blah.&quot;

But my favorite was when someone came to me with a proposed implementation to review and, after reviewing it, I said &quot;It looks OK to me, but you should run it by so-and-so as well, because he understands this stuff better than I do. For example, he will undoubtedly catch that error over there, which I missed.&quot;

Entirely sincerely.

My head is a strange and wondrous place.</description>
		<content:encoded><![CDATA[<p>(nods) I used to frequently describe my job as a series of exchanges where people would say &#8220;I have a problem, X, with solution Y. What should I do?&#8221;</p>
<p>And I would say &#8220;Wait, wait, wait. Your problem is X?&#8221; And they would nod.<br />
And I would say &#8220;And your solution is Y?&#8221; And they would say &#8220;Great, thanks!&#8221; and run off.</p>
<p>And I&#8217;ve become used to writing emails that go &#8220;I don&#8217;t really understand your question. You _might_ mean X, but you probably don&#8217;t. You _might_ mean Y, but that would be stupid. You might mean Z&#8230; in fact you almost certainly do.&#8221; then deleting that email and starting over with   &#8220;Assuming you mean Z, the answer is blah.&#8221;</p>
<p>But my favorite was when someone came to me with a proposed implementation to review and, after reviewing it, I said &#8220;It looks OK to me, but you should run it by so-and-so as well, because he understands this stuff better than I do. For example, he will undoubtedly catch that error over there, which I missed.&#8221;</p>
<p>Entirely sincerely.</p>
<p>My head is a strange and wondrous place.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Nehrlich, Unrepentant Generalist &#124;&#124; Thinking by talking &#124;&#124; April &#124;&#124; 2007</title>
		<link>http://www.nehrlich.com/blog/2004/10/07/management-by-conversation/comment-page-1/#comment-35587</link>
		<dc:creator>Eric Nehrlich, Unrepentant Generalist &#124;&#124; Thinking by talking &#124;&#124; April &#124;&#124; 2007</dc:creator>
		<pubDate>Sat, 14 Apr 2007 00:35:53 +0000</pubDate>
		<guid isPermaLink="false">/?p=122#comment-35587</guid>
		<description>[...] I had a teddy bear moment today. I was trying to debug something at work, got stuck, asked one of my coworkers to help me, explained the problem to him, and said &#8220;Oh, I see what&#8217;s going on&#8221; without them saying anything. I guess I should bring a teddy bear into work so that I can explain problems to it before bothering my coworkers. [...]</description>
		<content:encoded><![CDATA[<p>[...] I had a teddy bear moment today. I was trying to debug something at work, got stuck, asked one of my coworkers to help me, explained the problem to him, and said &#8220;Oh, I see what&#8217;s going on&#8221; without them saying anything. I guess I should bring a teddy bear into work so that I can explain problems to it before bothering my coworkers. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Nehrlich, Unrepentant Generalist &#124;&#124; But it&#8217;s just talking! &#124;&#124; March &#124;&#124; 2007</title>
		<link>http://www.nehrlich.com/blog/2004/10/07/management-by-conversation/comment-page-1/#comment-26505</link>
		<dc:creator>Eric Nehrlich, Unrepentant Generalist &#124;&#124; But it&#8217;s just talking! &#124;&#124; March &#124;&#124; 2007</dc:creator>
		<pubDate>Wed, 21 Mar 2007 03:27:55 +0000</pubDate>
		<guid isPermaLink="false">/?p=122#comment-26505</guid>
		<description>[...] Sometimes thinking through ideas out loud  is the only way the next step can be identified. Just by forcing their team members to articulate what&#8217;s going on, managers can often move people forward when they&#8217;re stuck in &#8220;blank page&#8221; syndrome or are procrastinating. My best manager (the coworker mentioned in that post actually) dropped by my desk once a week, in classic HP &#8220;management by walking around&#8221; fashion, to review what I&#8217;d done the past week, where I was stuck, and what I should get done the next week. It wasn&#8217;t any sort of formal meeting, but it helped me stay focused and gave me a chance to get unstuck. [...]</description>
		<content:encoded><![CDATA[<p>[...] Sometimes thinking through ideas out loud  is the only way the next step can be identified. Just by forcing their team members to articulate what&#8217;s going on, managers can often move people forward when they&#8217;re stuck in &#8220;blank page&#8221; syndrome or are procrastinating. My best manager (the coworker mentioned in that post actually) dropped by my desk once a week, in classic HP &#8220;management by walking around&#8221; fashion, to review what I&#8217;d done the past week, where I was stuck, and what I should get done the next week. It wasn&#8217;t any sort of formal meeting, but it helped me stay focused and gave me a chance to get unstuck. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

