<?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: The practice of Dialogue Mapping &#8211; Part 2</title>
	<atom:link href="http://www.cleverworkarounds.com/2009/09/16/the-practice-of-dialogue-mapping-part-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cleverworkarounds.com/2009/09/16/the-practice-of-dialogue-mapping-part-2/</link>
	<description>After much frustration, it seems DEFAULT is the way to go...</description>
	<lastBuildDate>Thu, 02 Feb 2012 17:45:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: FileCraft</title>
		<link>http://www.cleverworkarounds.com/2009/09/16/the-practice-of-dialogue-mapping-part-2/comment-page-1/#comment-58052</link>
		<dc:creator>FileCraft</dc:creator>
		<pubDate>Thu, 04 Nov 2010 09:35:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.cleverworkarounds.com/?p=1583#comment-58052</guid>
		<description>This is a delightful and I think realistic story that may make sense to many people.
Compendium is pretty enough, but I like indented outline form which captures this in less than 25 lines of text with any editor and is trivial to email around or develop further in a wiki. With a shared editor, experienced groups might be able to multi-task to take some strain off the single recording secretary. I’ve never seen that work at all, but I like the idea.
I use Q, A, Pro, and Con as the qualifier/header for each line. For links to other material, I use Ref. For included explanatory stuff, I use Note.</description>
		<content:encoded><![CDATA[<p>This is a delightful and I think realistic story that may make sense to many people.<br />
Compendium is pretty enough, but I like indented outline form which captures this in less than 25 lines of text with any editor and is trivial to email around or develop further in a wiki. With a shared editor, experienced groups might be able to multi-task to take some strain off the single recording secretary. I’ve never seen that work at all, but I like the idea.<br />
I use Q, A, Pro, and Con as the qualifier/header for each line. For links to other material, I use Ref. For included explanatory stuff, I use Note.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CleverWorkarounds &#187; The practice of Dialogue Mapping &#8211; Part 3</title>
		<link>http://www.cleverworkarounds.com/2009/09/16/the-practice-of-dialogue-mapping-part-2/comment-page-1/#comment-16184</link>
		<dc:creator>CleverWorkarounds &#187; The practice of Dialogue Mapping &#8211; Part 3</dc:creator>
		<pubDate>Mon, 21 Sep 2009 15:21:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.cleverworkarounds.com/?p=1583#comment-16184</guid>
		<description>[...] in the real-world. To recap, in part 1, I provided a brief overview of Dialogue Mapping and in part 2, I described a common real world usage scenario that we perform fairly often as SharePoint [...]</description>
		<content:encoded><![CDATA[<p>[...] in the real-world. To recap, in part 1, I provided a brief overview of Dialogue Mapping and in part 2, I described a common real world usage scenario that we perform fairly often as SharePoint [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

