<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Boxes and Arrows: Comments by Melissa Huhn</title>
    <link>http://www.boxesandarrows.com/person/11339</link>
    <pubDate>Wed, 10 Oct 2007 15:07:38 GMT</pubDate>
    <description>Comments by Melissa Huhn</description>
    <item>
      <description>&lt;p&gt;I use this approach for process flows. I first learned about it at Process Mapping by Tube: &lt;a href="http://www.kaywebs.co.uk/process_maps.htm" rel="nofollow"&gt;http://www.kaywebs.co.uk/process_maps.htm&lt;/a&gt; (Michael Kay provides a guidebook explaining his approach, as well as some history on Mr. Beck and his map.) One of the main advantages is that the tube map is so accessible. Non-technical users find process diagrams in this format much less intimidating than the traditional boxes, diamonds, decision points, etc. I was mapping out an offline process that involved a number of non-technical users, and they embraced the diagram entusiastically&amp;#8212;it was such a pleasant surprise, to get so much interest and positive feedback about a process map!&lt;/p&gt;

	&lt;p&gt;Great article Patrick!&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/a-map-based-approach#content_12887</link>
      <guid>http://www.boxesandarrows.com/view/a-map-based-approach#content_12887</guid>
      <pubDate>Wed, 10 Oct 2007 15:07:38 GMT</pubDate>
      <author>Melissa Huhn</author>
    </item>
  </channel>
</rss>
