<?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: Why mind mapping software will go mainstream in 2009: The developer perspective</title>
	<atom:link href="http://mindmappingsoftwareblog.com/why-mind-mapping-software-will-go-mainstream-developer-perspective/feed/" rel="self" type="application/rss+xml" />
	<link>http://mindmappingsoftwareblog.com/why-mind-mapping-software-will-go-mainstream-developer-perspective/</link>
	<description>Your best resource for advice on mind mapping software</description>
	<lastBuildDate>Fri, 12 Mar 2010 16:51:36 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Wallace Tait</title>
		<link>http://mindmappingsoftwareblog.com/why-mind-mapping-software-will-go-mainstream-developer-perspective/comment-page-1/#comment-809</link>
		<dc:creator>Wallace Tait</dc:creator>
		<pubDate>Mon, 19 Jan 2009 05:03:19 +0000</pubDate>
		<guid isPermaLink="false">http://mindmappingsoftwareblog.com/?p=1963#comment-809</guid>
		<description>I&#039;ll ad to the VMBOK information and say: it simply won&#039;t work without input and feedback from professional Visual mappers and the mainstream developers.
Speaking with a developer colleague, I encouraged him to develop his own organizational BOK.  This is indeed the logical thing to do. A developers BOK translates into knowledge capital associated with their product.  Further, I would say: Any developer who has or decides to create a BOK that speaks of their existing software offerings, would understand the logic of their BOK being added to a VMBOK.

I firmly believe the VMBOK can be a home for numerous developers BOK&#039;s.  This would indeed benefit the potential for those who choose to be certified to a VMBOK in the future.

We have Phd, MB and other designations that fulfill the requirements of their respective BOK&#039;s, thus I don&#039;t see any reason why we can&#039;t prepare the future thought leaders (read whole brain thinkers) to be equipped with a recognized certification and designation as being a prepared and able Visual thinker.

Again, this can&#039;t happen without the active participation of professional Visual mappers and the mainstream developers.  The various BOK&#039;s that may act as modules that can be added to the VMBOK, thus enabling the availability of relevant developer information and training, aimed at the continuous improvement and development of VMBOK graduates.  The scope is wide and involves many approaches to Visual mapping.
Just my thoughts, but I wish these thoughts to challenge you to connect with us at info@visualmapper.org and become involved.</description>
		<content:encoded><![CDATA[<p>I&#8217;ll ad to the VMBOK information and say: it simply won&#8217;t work without input and feedback from professional Visual mappers and the mainstream developers.<br />
Speaking with a developer colleague, I encouraged him to develop his own organizational BOK.  This is indeed the logical thing to do. A developers BOK translates into knowledge capital associated with their product.  Further, I would say: Any developer who has or decides to create a BOK that speaks of their existing software offerings, would understand the logic of their BOK being added to a VMBOK.</p>
<p>I firmly believe the VMBOK can be a home for numerous developers BOK&#8217;s.  This would indeed benefit the potential for those who choose to be certified to a VMBOK in the future.</p>
<p>We have Phd, MB and other designations that fulfill the requirements of their respective BOK&#8217;s, thus I don&#8217;t see any reason why we can&#8217;t prepare the future thought leaders (read whole brain thinkers) to be equipped with a recognized certification and designation as being a prepared and able Visual thinker.</p>
<p>Again, this can&#8217;t happen without the active participation of professional Visual mappers and the mainstream developers.  The various BOK&#8217;s that may act as modules that can be added to the VMBOK, thus enabling the availability of relevant developer information and training, aimed at the continuous improvement and development of VMBOK graduates.  The scope is wide and involves many approaches to Visual mapping.<br />
Just my thoughts, but I wish these thoughts to challenge you to connect with us at <a href="mailto:info@visualmapper.org">info@visualmapper.org</a> and become involved.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wallace Tait</title>
		<link>http://mindmappingsoftwareblog.com/why-mind-mapping-software-will-go-mainstream-developer-perspective/comment-page-1/#comment-811</link>
		<dc:creator>Wallace Tait</dc:creator>
		<pubDate>Sat, 17 Jan 2009 02:09:54 +0000</pubDate>
		<guid isPermaLink="false">http://mindmappingsoftwareblog.com/?p=1963#comment-811</guid>
		<description>Yes! as I said in previous posts,&quot;Visual mapping as a term may become rather passe too&quot;.
Visual mapping though is being more widely used and accepted even in the Mind mapping communities.

Within business, when we use the term mapping, it can mean either flow charting, process or value stream mapping.
Using the term mapping just doesn&#039;t do it for me but I can accept it within the context of discussions with fellow Visual mappers.
Process mapping, Information mapping, Knowledge mapping et al; I certainly accept that &quot;Information mapping&quot; is more descriptive and meaningful to the arena that has been created around Visual mapping.
Graphical expressions of information and knowledge certainly has a wide scope.
Good points John.</description>
		<content:encoded><![CDATA[<p>Yes! as I said in previous posts,&#8221;Visual mapping as a term may become rather passe too&#8221;.<br />
Visual mapping though is being more widely used and accepted even in the Mind mapping communities.</p>
<p>Within business, when we use the term mapping, it can mean either flow charting, process or value stream mapping.<br />
Using the term mapping just doesn&#8217;t do it for me but I can accept it within the context of discussions with fellow Visual mappers.<br />
Process mapping, Information mapping, Knowledge mapping et al; I certainly accept that &#8220;Information mapping&#8221; is more descriptive and meaningful to the arena that has been created around Visual mapping.<br />
Graphical expressions of information and knowledge certainly has a wide scope.<br />
Good points John.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John England</title>
		<link>http://mindmappingsoftwareblog.com/why-mind-mapping-software-will-go-mainstream-developer-perspective/comment-page-1/#comment-810</link>
		<dc:creator>John England</dc:creator>
		<pubDate>Sat, 17 Jan 2009 01:41:26 +0000</pubDate>
		<guid isPermaLink="false">http://mindmappingsoftwareblog.com/?p=1963#comment-810</guid>
		<description>The VMBOK seems like a very good idea.
Is it the use of the word &#039;Visual&#039; causes some confusion in these discussions? We used to call ourselves (Mindsystems) &#039;The Visual Thinking Experts&#039; which while true did not really position us in the way we wanted. So what is wrong with the term &#039;Visual Mapping’? I believe the emphasis, as I have said elsewhere, should be on Information mapping. Many years ago I was involved in a military project on Information Mapping. While this had a difference focus than Visual mapping there are some important parallels. This was before laptops and even desktop computers so the focus was on paper. However to summarise, IM concerned such things as certain types of information always being presented in a prescribed format at a place you would expect it to be. A simple example is an address on a letter. My point is that if we thought of this issue more as an Information Mapping issue than a visual one ... would this make the developers path clearer? In other words if the focus was more on the ‘information’ with the visual aspect being secondary, perhaps some of the mist would clear. Please do not think that I consider the visual aspects unimportant ... they are CRITICAL. If is just that the information should be central and the visual presentation chosen according to the circumstances.</description>
		<content:encoded><![CDATA[<p>The VMBOK seems like a very good idea.<br />
Is it the use of the word &#8216;Visual&#8217; causes some confusion in these discussions? We used to call ourselves (Mindsystems) &#8216;The Visual Thinking Experts&#8217; which while true did not really position us in the way we wanted. So what is wrong with the term &#8216;Visual Mapping’? I believe the emphasis, as I have said elsewhere, should be on Information mapping. Many years ago I was involved in a military project on Information Mapping. While this had a difference focus than Visual mapping there are some important parallels. This was before laptops and even desktop computers so the focus was on paper. However to summarise, IM concerned such things as certain types of information always being presented in a prescribed format at a place you would expect it to be. A simple example is an address on a letter. My point is that if we thought of this issue more as an Information Mapping issue than a visual one &#8230; would this make the developers path clearer? In other words if the focus was more on the ‘information’ with the visual aspect being secondary, perhaps some of the mist would clear. Please do not think that I consider the visual aspects unimportant &#8230; they are CRITICAL. If is just that the information should be central and the visual presentation chosen according to the circumstances.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wallace Tait</title>
		<link>http://mindmappingsoftwareblog.com/why-mind-mapping-software-will-go-mainstream-developer-perspective/comment-page-1/#comment-808</link>
		<dc:creator>Wallace Tait</dc:creator>
		<pubDate>Sat, 17 Jan 2009 00:51:08 +0000</pubDate>
		<guid isPermaLink="false">http://mindmappingsoftwareblog.com/?p=1963#comment-808</guid>
		<description>As having direct involvement within the development of information management products and as co-founder of Visualmapper consultancy, I believe I can speak from the developer’s angle too.

I would say most developers have created excellent visual mapping products to enable data, process, information, knowledge and system improvement. Most of the products available to date have quite literally changed the way many within academia and businesses create, manage and exchange information.

If developers are using the term mind mapping, it begs the question; are you in the mind mapping business or the information management business?

Donald Maciver, the General Manager of Mind Genius based in Scotland is quoted as saying; “For mapping to go mainstream it requires a significant change in human behaviour”.

Agreeing with Donald’s quote, I would suggest a potential approach to enable Visual mapping to experience a mainstream infusion.

During mid 2008, I suggested to my fellow colleagues Arjen Ter Hoeve (Netherlands), Patrick Baker (New Zealand) and Brian Friedlander (USA) of a potential format for taking Visual mapping mainstream.
A free Visual mapping Body of Knowledge (VMBOK) may best serve this purpose. From within a body of knowledge, academic content and relevant knowledge could be extrapolated and compiled for potential future academic use.

So where do the developers fit into this?  I believe the developers are integral to the development, and continuous improvement of such a BOK.  This is where your organizational contributions to these endeavours can be preserved and realized. It is thus enabling you to continue to develop software with the confidence that a VMBOK delivers a knowledge base of the tools and techniques of visual mapping that represent your agendas.

Visual mapping includes but is not limited to Mind mapping, concept mapping, flow charting, argument mapping and much more, therefore we all have relevancy within a VMBOK.

My colleagues have already taken the initial steps of working together to establish the foundations of a VMBOK and would be extremely interested in your input and feedback regarding this initiative.  Your contribution and support, so please connect with us at: info@visualmapper.org

MAINSTREAM CAN HAPPEN IF WE MAKE IT SO.</description>
		<content:encoded><![CDATA[<p>As having direct involvement within the development of information management products and as co-founder of Visualmapper consultancy, I believe I can speak from the developer’s angle too.</p>
<p>I would say most developers have created excellent visual mapping products to enable data, process, information, knowledge and system improvement. Most of the products available to date have quite literally changed the way many within academia and businesses create, manage and exchange information.</p>
<p>If developers are using the term mind mapping, it begs the question; are you in the mind mapping business or the information management business?</p>
<p>Donald Maciver, the General Manager of Mind Genius based in Scotland is quoted as saying; “For mapping to go mainstream it requires a significant change in human behaviour”.</p>
<p>Agreeing with Donald’s quote, I would suggest a potential approach to enable Visual mapping to experience a mainstream infusion.</p>
<p>During mid 2008, I suggested to my fellow colleagues Arjen Ter Hoeve (Netherlands), Patrick Baker (New Zealand) and Brian Friedlander (USA) of a potential format for taking Visual mapping mainstream.<br />
A free Visual mapping Body of Knowledge (VMBOK) may best serve this purpose. From within a body of knowledge, academic content and relevant knowledge could be extrapolated and compiled for potential future academic use.</p>
<p>So where do the developers fit into this?  I believe the developers are integral to the development, and continuous improvement of such a BOK.  This is where your organizational contributions to these endeavours can be preserved and realized. It is thus enabling you to continue to develop software with the confidence that a VMBOK delivers a knowledge base of the tools and techniques of visual mapping that represent your agendas.</p>
<p>Visual mapping includes but is not limited to Mind mapping, concept mapping, flow charting, argument mapping and much more, therefore we all have relevancy within a VMBOK.</p>
<p>My colleagues have already taken the initial steps of working together to establish the foundations of a VMBOK and would be extremely interested in your input and feedback regarding this initiative.  Your contribution and support, so please connect with us at: <a href="mailto:info@visualmapper.org">info@visualmapper.org</a></p>
<p>MAINSTREAM CAN HAPPEN IF WE MAKE IT SO.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
