<?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: Driving for Self, Driving for Other</title>
	<atom:link href="http://www.stevenlist.com/blog/2010/07/18/driving-for-self-driving-for-other/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.stevenlist.com/blog/2010/07/18/driving-for-self-driving-for-other/</link>
	<description>Thoughts on Agile software development, facilitation, communication, and relationships in the personal and professional worlds, from Steven &#34;Doc&#34; List</description>
	<lastBuildDate>Sun, 22 Jan 2012 18:20:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Tarek Abdelmaguid</title>
		<link>http://www.stevenlist.com/blog/2010/07/18/driving-for-self-driving-for-other/comment-page-1/#comment-3263</link>
		<dc:creator>Tarek Abdelmaguid</dc:creator>
		<pubDate>Tue, 20 Jul 2010 19:52:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevenlist.com/blog/2010/07/18/driving-for-self-driving-for-other/#comment-3263</guid>
		<description>Interesting analogy.
Since I&#039;ve been in similar situations, here are some ideas to seed the discussion:
- Announce the change. If people know something is coming, they&#039;ll be less surprised by it. I say less surprised, because some will still be surprised anyway: they will not understand what this changes means, or how it will affect them.
- Apply the change slowly. People will detect the change, and can start preparing for the full swing. They will also see what the change is, and will have a better understand of how it&#039;ll affect them.
- Listen for and encourage feedback. If the change is happening too fast, or causing discomfort, we can use this feedback to improve our approach.</description>
		<content:encoded><![CDATA[<p>Interesting analogy.<br />
Since I&#8217;ve been in similar situations, here are some ideas to seed the discussion:<br />
- Announce the change. If people know something is coming, they&#8217;ll be less surprised by it. I say less surprised, because some will still be surprised anyway: they will not understand what this changes means, or how it will affect them.<br />
- Apply the change slowly. People will detect the change, and can start preparing for the full swing. They will also see what the change is, and will have a better understand of how it&#8217;ll affect them.<br />
- Listen for and encourage feedback. If the change is happening too fast, or causing discomfort, we can use this feedback to improve our approach.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian</title>
		<link>http://www.stevenlist.com/blog/2010/07/18/driving-for-self-driving-for-other/comment-page-1/#comment-3259</link>
		<dc:creator>Adrian</dc:creator>
		<pubDate>Sun, 18 Jul 2010 18:04:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevenlist.com/blog/2010/07/18/driving-for-self-driving-for-other/#comment-3259</guid>
		<description>I think it&#039;s OK for folks to be surprised when we &quot;jink left&quot; in our unconscious agile &quot;driving&quot;. In fact, it may even be more educational to folks to feel the jolt first and then learn the &quot;why&quot; after the fact. The trick, I think, to mitigating the confusion and eliminating the frustration is to talk through the &quot;why&quot; as soon after the surprise as possible. To your point, I think, it requires a heightened sensitivity on our parts to predict the confusion and explain the differences without presuming that the passenger understands as instinctively as we do when &quot;going left&quot; is the correct maneuver.

Might be an interesting experiment to explain to my wife, the next time I&#039;m driving, why I do what I do... &quot;Honey, I just changed to the right lane because I saw a car in the distance that seems to be driving very fast behind me; I&#039;m just getting out of his way&quot;. Then again - it could drive her nuts. Yes. Then, it&#039;s settled. I&#039;ll try it.</description>
		<content:encoded><![CDATA[<p>I think it&#8217;s OK for folks to be surprised when we &#8220;jink left&#8221; in our unconscious agile &#8220;driving&#8221;. In fact, it may even be more educational to folks to feel the jolt first and then learn the &#8220;why&#8221; after the fact. The trick, I think, to mitigating the confusion and eliminating the frustration is to talk through the &#8220;why&#8221; as soon after the surprise as possible. To your point, I think, it requires a heightened sensitivity on our parts to predict the confusion and explain the differences without presuming that the passenger understands as instinctively as we do when &#8220;going left&#8221; is the correct maneuver.</p>
<p>Might be an interesting experiment to explain to my wife, the next time I&#8217;m driving, why I do what I do&#8230; &#8220;Honey, I just changed to the right lane because I saw a car in the distance that seems to be driving very fast behind me; I&#8217;m just getting out of his way&#8221;. Then again &#8211; it could drive her nuts. Yes. Then, it&#8217;s settled. I&#8217;ll try it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

