Robby on Rails: The Technology of Dialoguethoughts.sort_by{|t| t[:topic]}.collect tag:www.robbyonrails.com,2005:TypoTypo2006-09-12T14:36:32-04:00Robby Russellurn:uuid:dbe5da89-c979-4086-8129-4673665ba5a62006-09-12T14:30:00-04:002006-09-12T14:36:32-04:00The Technology of Dialogue<p>In the essay, <a href="http://www.vision-nest.com/cbw/Dialogue.html">Dialogue and Organizational Transformation</a>, Glenna Gerard and Linda Teurfs outline the the <em>building blocks</em> of <a href="http://www.vision-nest.com/cbw/Dialogue.html#3"><span class="caps">THE TECHNOLOGY OF DIALOGUE</span></a>, which they suggests consists of:</p>
<ul>
<li>Suspension of Judgment</li>
<li>Identification of Assumptions</li>
<li>Listening</li>
<li>Inquiry and Reflection</li>
</ul>
<p>What makes dialogue different than conversation? According to <a href="http://www.gurteen.com/">David Gurteen</a>, <em>“dialogue is a disciplined form of conversation.”</em></p>
<p>Gurteen says that within dialogue<sup><a href="#fn1">1</a></sup>:</p>
<ul>
<li>You prefer a certain position but do not cling to it. </li>
<li>You are ready to listen to others.</li>
<li>Your mindset is not one of ‘convincing others that your way is right’ but of asking what you can learn from them.</li>
<li>It is recognizing that other people’s input will help you refine your own ideas or reveal your misconceptions.</li>
<li>It is not argument or debate. It is not win-lose. In dialogue all sides win by coming up with a more appropriate solution than a single person could ever have. It is win-win.</li>
</ul>
<p>When we first introduced Dialogue-Driven Development, Ryan Allen <a href="http://www.robbyonrails.com/articles/2006/08/02/dialogue-driven-development#comment-21737">responded with a brief overview</a> of how you might go about defining a <em>failed project</em>. His first bullet was, <em>“Miscommunication can lead to the implementation of the wrong solutions.”</em></p>
<p>It is our opinion that many of the problems that lead to <em>failed projects</em> can be solved through consistent and cooperative discourse. Much of this relies on each of us taking ownership of our commitment to encouraging healthy collaboration between developers, clients, and users.</p>
<p>Wikipedia <a href="http://en.wikipedia.org/wiki/Dialogue">currently describes dialogue</a> as, <em>“a reciprocal conversation between two or more persons.”</em></p>
<h3>Question</h3>
<p>What are some of the obstacles that you face when interacting with a diverse set of developers, clients, and users?</p>
<p id="fn1"><sup>1</sup> <a href="http://www.gurteen.com/gurteen/gurteen.nsf/id/km-dialogue">The Discipline of Dialogue by David Gurteen</a></p><p>In the essay, <a href="http://www.vision-nest.com/cbw/Dialogue.html">Dialogue and Organizational Transformation</a>, Glenna Gerard and Linda Teurfs outline the the <em>building blocks</em> of <a href="http://www.vision-nest.com/cbw/Dialogue.html#3"><span class="caps">THE TECHNOLOGY OF DIALOGUE</span></a>, which they suggests consists of:</p>
<ul>
<li>Suspension of Judgment</li>
<li>Identification of Assumptions</li>
<li>Listening</li>
<li>Inquiry and Reflection</li>
</ul>
<p>What makes dialogue different than conversation? According to <a href="http://www.gurteen.com/">David Gurteen</a>, <em>“dialogue is a disciplined form of conversation.”</em></p>
<p>Gurteen says that within dialogue<sup><a href="#fn1">1</a></sup>:</p>
<ul>
<li>You prefer a certain position but do not cling to it. </li>
<li>You are ready to listen to others.</li>
<li>Your mindset is not one of ‘convincing others that your way is right’ but of asking what you can learn from them.</li>
<li>It is recognizing that other people’s input will help you refine your own ideas or reveal your misconceptions.</li>
<li>It is not argument or debate. It is not win-lose. In dialogue all sides win by coming up with a more appropriate solution than a single person could ever have. It is win-win.</li>
</ul>
<p>When we first introduced Dialogue-Driven Development, Ryan Allen <a href="http://www.robbyonrails.com/articles/2006/08/02/dialogue-driven-development#comment-21737">responded with a brief overview</a> of how you might go about defining a <em>failed project</em>. His first bullet was, <em>“Miscommunication can lead to the implementation of the wrong solutions.”</em></p>
<p>It is our opinion that many of the problems that lead to <em>failed projects</em> can be solved through consistent and cooperative discourse. Much of this relies on each of us taking ownership of our commitment to encouraging healthy collaboration between developers, clients, and users.</p>
<p>Wikipedia <a href="http://en.wikipedia.org/wiki/Dialogue">currently describes dialogue</a> as, <em>“a reciprocal conversation between two or more persons.”</em></p>
<h3>Question</h3>
<p>What are some of the obstacles that you face when interacting with a diverse set of developers, clients, and users?</p>
<p id="fn1"><sup>1</sup> <a href="http://www.gurteen.com/gurteen/gurteen.nsf/id/km-dialogue">The Discipline of Dialogue by David Gurteen</a></p>