<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Conversational Antipatterns on Message Boards</title><link>http://blogs.msdn.com/b/nickmalik/archive/2012/06/22/conversational-antipatterns-on-message-boards.aspx</link><description>Architects argue.&amp;#160; I have, over the past year, spent a good bit of time on LinkedIn Message boards.&amp;#160; I’ve watched a lot of people argue.&amp;#160; I’ve learned a great deal about Enterprise Architecture, and a few things about myself, as I’ve compared</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Conversational Antipatterns on Message Boards</title><link>http://blogs.msdn.com/b/nickmalik/archive/2012/06/22/conversational-antipatterns-on-message-boards.aspx#10323246</link><pubDate>Sat, 23 Jun 2012 21:05:04 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10323246</guid><dc:creator>Peter Murchland</dc:creator><description>&lt;p&gt;Nick&lt;/p&gt;
&lt;p&gt;Wonderful contribution - the work of a real architect - recognising patterns and assessing supportive vs destructive behaviours associated with use of these patterns, offering in an open and invitational way the opportunity for future improved performance. &amp;nbsp;I should not expect less from a leading practitioner!!&lt;/p&gt;
&lt;p&gt;What spoke to me in this was a number of my own learnings from similar experiences, and some underlying principles which support the gaining of greater value from the patterns.&lt;/p&gt;
&lt;p&gt;Firstly, I would have to point out that I have learned more through honestly and openly addressing any of the challenges I have received to my latest thinking and ideas. &amp;nbsp;Principle 1 - be open, be honest, be true to yourself, and be willing to admit being wrong&lt;/p&gt;
&lt;p&gt;I find that people respond better if I provide constructive critique ie, I describe my issues and concerns and offer an alternate articulation rather than simply telling them that they are wrong. &amp;nbsp;Principle 2 - offer constructive critique&lt;/p&gt;
&lt;p&gt;I keep on finding that there is not a single right answer. &amp;nbsp;There are multiple perspectives, and not just two the right one and the wrong one. &amp;nbsp;The latter is what is often articulated and created. &amp;nbsp;It polarises people rather than bringing them together to a shared understanding and commitment. &amp;nbsp;Principle 3 - and not or&lt;/p&gt;
&lt;p&gt;A former colleague told me that his boss said communication is what other people hear, not what you say. &amp;nbsp;If someone responds in a manner you don&amp;#39;t expect, then consider the possibility that they did not appreciate your intended meaning and that there is an obligation on you to communicate it again in a different and hopefully clearer way. &amp;nbsp;Here we need to recognise that language can be our worst enemy - that which we choose to use may fail to communicate our intended meaning. &amp;nbsp;Principle 4 - take responsibility for clear communication&lt;/p&gt;
&lt;p&gt;If I am engaging with 10 people, then there are ten different mental models at play. &amp;nbsp;Each is dynamic, potentially changing with each interaction. &amp;nbsp;Hopefully, they become more aligned through interaction and provide the basis for shared understanding and better collaboration. &amp;nbsp;it is important to honour each of the mental models at play and the people who own them. &amp;nbsp;Principle 5 - offer respect and reciprocity&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10323246" width="1" height="1"&gt;</description></item></channel></rss>