<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>

<channel>
	<title>ActionMap Waves</title>
	<link>http://blog.actionmap.com</link>
	<description>Accelerate Solutions Development</description>
	<pubDate>Wed, 16 Jul 2008 21:40:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3</generator>
	<language>en</language>
			<item>
		<title>Why Existing Categories Don&#8217;t Provide the Breakthrough</title>
		<link>http://blog.actionmap.com/2007/10/12/csd_gap_center/</link>
		<comments>http://blog.actionmap.com/2007/10/12/csd_gap_center/#comments</comments>
		<pubDate>Fri, 12 Oct 2007 23:00:06 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[02.  The Missing Ingredient - Knowledge Processing]]></category>

		<guid isPermaLink="false">http://blog.actionmap.com/2007/10/12/csd_gap_center/</guid>
		<description><![CDATA[The bottleneck:  long cycles of meetings and communications for business/technology process development, used to bridge the gap between:


 

Separate knowledge and interests


=&#62;  and  &#60;=     


Stakeholder alignment on detailed processes and plans



Why don&#8217;t existing categories of solutions provide a breakthrough?
Briefly, free-form collaboration does not have sufficient analytic power or direction, decision support produces too narrow a perspective, process modeling is too rigid [...]]]></description>
			<content:encoded><![CDATA[<p><strong>The bottleneck:  long cycles of meetings and communications for business/technology process development, used to bridge the gap between:</strong></p>
<table>
<tr>
<td width="20"> </td>
<td width="150">
<p align="right"><strong>Separate knowledge and interests</strong></p>
</td>
<td width="70" vAlign="middle">
<p align="center"><strong>=&gt;  and  &lt;=</strong>     </p>
</td>
<td width="200">
<p align="left"><strong>Stakeholder alignment on detailed processes and plans</strong></p>
</td>
</tr>
</table>
<p><strong>Why don&#8217;t existing categories of solutions provide a breakthrough?</strong></p>
<p>Briefly, free-form collaboration does not have sufficient analytic power or direction, decision support produces too narrow a perspective, process modeling is too rigid and analytic, and project planning requires too many un-affirmed assumptions and pre-buy-in commitments.</p>
<p>A hypothetical option is to combine pre-existing tools from among these different categories. However, in terms of net impact on the bottleneck in the market today, this is largely a consultant’s dream and a customer’s nightmare.</p>
<p>At the center of the problem is the fact that the activity of bridging the above gap is effectively the same activity as “people communicating to agree on what to do together”. In everyday situations of relatively low complexity, this activity uses a natural fusion of natural human abilities for “collaboration”, “decision support”, “process modeling” and “project planning”. That’s where this work is done.</p>
<p>Simply put, the work is -knowledge- processing, not information processing. Knowledge is the result of that fusion of collaboration (peer confirmation and interest gauging), decision support (analytic review of the facts), process modeling (context and flow logic), and project planning (understanding what actions can be taken).</p>
<p>What a person “knows” about the external world, they know through a fusion of all of these cognitive modes at the same time.</p>
<p>To test this assertion, find something not entirely personal that you feel that you strongly “know” that does not include one of these modes.</p>
<p>In the current business environment, when a situation becomes more complicated, this natural human activity is sub-divided into the separate activities of “collaboration”, “decision support”, “process modeling” and “project planning”, and supported with predominantly non-overlapping “information” tools.</p>
<p>These tools work effectively in their own domains. However, by virtue of specialization, they have lost the ability to fully support the natural ability of people to “communicate to agree on what to do together”.</p>
<p>As a result, when people use these tools in group meetings, they don’t end up “knowing”. And when they don’t “know” they don’t produce alignment on detailed processes and plans. Instead, they produce the conclusion: “Let’s look at it again a next week”. Or for better or worse, “Let’s go ahead with what we’ve got”.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.actionmap.com/2007/10/12/csd_gap_center/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Add Comments for &#8220;Collaborative Solutions Development - Overview&#8221;</title>
		<link>http://blog.actionmap.com/2007/10/01/cpd_ovr_comm/</link>
		<comments>http://blog.actionmap.com/2007/10/01/cpd_ovr_comm/#comments</comments>
		<pubDate>Mon, 01 Oct 2007 20:28:04 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[01. Collaborative Solutions Development (CSD) Overview]]></category>

		<guid isPermaLink="false">http://blog.actionmap.com/2007/10/01/cpd_ovr_comm/</guid>
		<description><![CDATA[Please use this post to add comments about the main article, &#8220;Collaborative Solutions Development - Overview&#8221;.
]]></description>
			<content:encoded><![CDATA[<p>Please use this post to add comments about the main article, &#8220;Collaborative Solutions Development - Overview&#8221;.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.actionmap.com/2007/10/01/cpd_ovr_comm/feed/</wfw:commentRss>
		</item>
		<item>
		<title>CSD in Business / IT Alignment</title>
		<link>http://blog.actionmap.com/2007/09/29/cpd_bizit_02/</link>
		<comments>http://blog.actionmap.com/2007/09/29/cpd_bizit_02/#comments</comments>
		<pubDate>Sat, 29 Sep 2007 07:00:40 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[BITA Article]]></category>

		<guid isPermaLink="false">http://blog.actionmap.com/2007/09/28/cpd_bizit_01/</guid>
		<description><![CDATA[A CHALLENGE OF MOVING TARGETS
Business / IT Alignment is fundamentally a challenge of moving targets: technical innovation and business change. Accordingly, better Business / IT Alignment depends primarily on more/better/faster on-going planning between business and IT.
The core challenge in Business / IT Alignment is that this planning must focus on business/technology processes, ranging from division-wide [...]]]></description>
			<content:encoded><![CDATA[<p><em><strong>A CHALLENGE OF MOVING TARGETS</strong></em></p>
<p>Business / IT Alignment is fundamentally a challenge of <strong>moving targets</strong>: technical innovation and business change. Accordingly, better Business / IT Alignment depends primarily on more/better/faster <strong>on-going planning</strong> between business and IT.</p>
<p>The core challenge in Business / IT Alignment is that <strong>this planning must focus on business/technology processes</strong>, ranging from division-wide operations models to detailed training and implementation plans.</p>
<p>Because of this, the <strong>primary bottleneck activity</strong> in Business / IT Alignment is <strong>collaborative solutions development.</strong>  And The bottleneck <strong>resource</strong> in this activity is &#8220;collaborative solutions development capability&#8221;.  That is, the ability to lead, contribute to and participate in <strong>group process knowledge sharing, design, implementation planning and consensus-building</strong>.</p>
<p>There is <strong>no substitute</strong> for these human activities, capabilities and results: <strong>where this capability is lacking, Business / IT Alignment falters.</strong></p>
<p><strong><em>A Major Bottleneck in IT Value Delivery</em></strong></p>
<p>The focus of collaborative solutions development is bridging the gap between separate knowledge and interests and agreed upon activities, models and plans.</p>
<table>
<tr>
<td width="20"> </td>
<td width="150">
<p align="right"><strong>Separate knowledge and interests</strong></p>
</td>
<td width="70" vAlign="middle">
<p align="center"><strong>=&gt;  X  &lt;=</strong>     </p>
</td>
<td width="200">
<p align="left"><strong>Stakeholder alignment on detailed processes and plans</strong></p>
</td>
</tr>
</table>
<p>This is a <strong>major bottleneck</strong> in innovation and IT in general.</p>
<p>The main symptom of this bottleneck is <strong>long cycles of meetings and communications</strong> in which information and consensus are gradually and often painfully and incompletely assembled.</p>
<p>The overall impact of this bottleneck is <strong>billions of dollars a year in cost, risk, error and delay</strong> in IT projects, along with matching frustration, conflict and stress, stalled innovation and progress, and lost opportunity.</p>
<p>And, <strong>failed Business / IT Alignment.</strong></p>
<p><strong><em>An Opportunity for the Seriously Ambitious</em></strong></p>
<p>The challenge here is four part:</p>
<p>1) &#8220;collaborative solutions development&#8221; is such a widely used activity that it <strong>lacks a focus for improving its performance.</strong></p>
<p>2) there are no <strong>highly effective, widely distributed solutions</strong> for supporting collaborative solutions development. <strong>(&#8221;What is the name of the market leader?&#8221;)</strong></p>
<p>3) The capabilities of particularly talented individuals or high performance teams are generally <strong>not highly transportable, flexible or scalable.</strong></p>
<p>4) <strong>Market attention is diffused and distracted</strong> by a myriad of solutions in the categories of collaboration, decision-support, process modeling and project planning that <strong>only partly address</strong> the above gap without significantly shortening the long cycles of meetings and communications.</p>
<p><strong><em>The Need for a New Solutions Category</em></strong></p>
<p>In my weblog article at <a href="http://blog.actionmap.com/">http://blog.actionmap.com/</a>, I make the case that &#8220;collaborative sooutions development&#8221; needs to be <strong>a new product and service category</strong>. That&#8217;s what it&#8217;s going to take to focus attention on the need for <strong>better tools for collaborative solutions development</strong>.</p>
<p><strong><em>The Action Point</em></strong></p>
<p>Why is Business / IT Aligment so difficult? Because it is largely a matter of matter of <strong>hard work</strong>. However, if it&#8217;s truly important, it&#8217;s time to identify and bear down on the <strong>right</strong> work.</p>
<p>My assertion is that the best action point for improved Business/IT Alignment is <strong>increasing collaborative solutions development capability</strong>.</p>
<p>In my weblog article I describe why this is a matter of <strong>strategic competitive importance</strong> and offer <strong>starting points</strong> for accomplishing it.</p>
<p><strong><em>A Scorecard for Readiness</em></strong></p>
<p>One of these starting points is a <strong>scorecard</strong> for evaluating your organization&#8217;s (and your personal) readiness to increase capability for collaborative solutions development. The scorecard is located at: <a href="http://www.actionmap.com/050_ScoreSumm.html">http://www.actionmap.com/050_ScoreSumm.html</a>.</p>
<p><strong><em>Conclusion</em></strong></p>
<p>Business / IT Alignment is primarily a challenge of <strong>moving targets</strong>, that involve business/technology processes.</p>
<p>The only way to keep up with this work is <strong>more/better/faster collaborative planning.</strong></p>
<p>The critical constraining resource for this work is <strong>collaborative solutions development capability.</strong></p>
<p>The market currently has <strong>no highly effective, widely used solution</strong> to support this capability.</p>
<p>Organizations that want to increase Business/IT Alignment need to <strong>demand and/or build better solutions</strong> for this capability.</p>
<p>The <strong>starting point</strong> is to get clear about the <strong>strategic importance </strong>of collaborative solutions development. The case for this is made at <a href="http://blog.actionmap.com/">http://blog.actionmap.com/cpd_ovr/cpd_strategic/</a>.</p>
<p>A <strong>scorecard </strong>for your organization&#8217;s readiness to do this work is available at <a href="http://www.actionmap.com/050_ScoreSumm.html">http://www.actionmap.com/050_ScoreSumm.html</a>.</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p>Comments:  Please review and add comments regarding this current post at: <a href="http://blog.actionmap.com/2007/10/02/cpd_bizit_comments/">Add Comments to &#8220;CPD in Business/IT Alignment</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.actionmap.com/2007/09/29/cpd_bizit_02/feed/</wfw:commentRss>
		</item>
		<item>
		<title>CSD in HRD / Org Change / Training / Recruiting</title>
		<link>http://blog.actionmap.com/2007/09/28/cpd_hr_ph/</link>
		<comments>http://blog.actionmap.com/2007/09/28/cpd_hr_ph/#comments</comments>
		<pubDate>Fri, 28 Sep 2007 22:35:17 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[080 HRD / Org Change / Training / Recruiting]]></category>

		<guid isPermaLink="false">http://blog.actionmap.com/2007/09/28/cpd_hr_ph/</guid>
		<description><![CDATA[Placeholder for CSD in HR
]]></description>
			<content:encoded><![CDATA[<p>Placeholder for CSD in HR</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.actionmap.com/2007/09/28/cpd_hr_ph/feed/</wfw:commentRss>
		</item>
		<item>
		<title>CSD in Six Sigma / Lean</title>
		<link>http://blog.actionmap.com/2007/09/28/cpd_ssl_ph/</link>
		<comments>http://blog.actionmap.com/2007/09/28/cpd_ssl_ph/#comments</comments>
		<pubDate>Fri, 28 Sep 2007 20:51:21 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[070 Six Sigma / Lean]]></category>

		<guid isPermaLink="false">http://blog.actionmap.com/2007/09/28/cpd_ssl_ph/</guid>
		<description><![CDATA[Placeholder for CSD in Six Sigma / Lean
]]></description>
			<content:encoded><![CDATA[<p>Placeholder for CSD in Six Sigma / Lean</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.actionmap.com/2007/09/28/cpd_ssl_ph/feed/</wfw:commentRss>
		</item>
		<item>
		<title>CSD in Systems Engineering</title>
		<link>http://blog.actionmap.com/2007/09/28/cpd_se_ph/</link>
		<comments>http://blog.actionmap.com/2007/09/28/cpd_se_ph/#comments</comments>
		<pubDate>Fri, 28 Sep 2007 20:50:42 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[040 Systems Engineering]]></category>

		<guid isPermaLink="false">http://blog.actionmap.com/2007/09/28/cpd_se_ph/</guid>
		<description><![CDATA[Placeholder for CSD in Systems Engineering
]]></description>
			<content:encoded><![CDATA[<p>Placeholder for CSD in Systems Engineering</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.actionmap.com/2007/09/28/cpd_se_ph/feed/</wfw:commentRss>
		</item>
		<item>
		<title>CSD in Complex Selling (Internal and External)</title>
		<link>http://blog.actionmap.com/2007/09/28/cpd_sales_ph/</link>
		<comments>http://blog.actionmap.com/2007/09/28/cpd_sales_ph/#comments</comments>
		<pubDate>Fri, 28 Sep 2007 20:46:04 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[060 Complex Selling (Internal and External)]]></category>

		<guid isPermaLink="false">http://blog.actionmap.com/2007/09/28/cpd_sales_ph/</guid>
		<description><![CDATA[Placeholder for CSD in Complex Selling
]]></description>
			<content:encoded><![CDATA[<p>Placeholder for CSD in Complex Selling</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.actionmap.com/2007/09/28/cpd_sales_ph/feed/</wfw:commentRss>
		</item>
		<item>
		<title>CPD in Project Management</title>
		<link>http://blog.actionmap.com/2007/09/28/cpd_pm_ph/</link>
		<comments>http://blog.actionmap.com/2007/09/28/cpd_pm_ph/#comments</comments>
		<pubDate>Fri, 28 Sep 2007 20:44:43 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[020 Project Management]]></category>

		<guid isPermaLink="false">http://blog.actionmap.com/2007/09/28/cpd_pm/</guid>
		<description><![CDATA[Placeholder for CPD in Project Management
]]></description>
			<content:encoded><![CDATA[<p>Placeholder for CPD in Project Management</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.actionmap.com/2007/09/28/cpd_pm_ph/feed/</wfw:commentRss>
		</item>
		<item>
		<title>CSD in BPM</title>
		<link>http://blog.actionmap.com/2007/09/28/cpd_bpm_ph/</link>
		<comments>http://blog.actionmap.com/2007/09/28/cpd_bpm_ph/#comments</comments>
		<pubDate>Fri, 28 Sep 2007 20:43:30 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[050  Business Process Management]]></category>

		<guid isPermaLink="false">http://blog.actionmap.com/2007/09/28/cpd_bpm/</guid>
		<description><![CDATA[Placeholder for CSD in BPM
]]></description>
			<content:encoded><![CDATA[<p>Placeholder for CSD in BPM</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.actionmap.com/2007/09/28/cpd_bpm_ph/feed/</wfw:commentRss>
		</item>
		<item>
		<title>CSD in BPR</title>
		<link>http://blog.actionmap.com/2007/09/28/cpd_bpr_ph/</link>
		<comments>http://blog.actionmap.com/2007/09/28/cpd_bpr_ph/#comments</comments>
		<pubDate>Fri, 28 Sep 2007 17:26:54 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[030 Business Process Reengineering]]></category>

		<guid isPermaLink="false">http://blog.actionmap.com/2007/09/28/26/</guid>
		<description><![CDATA[Placeholder for CSD in BPR
]]></description>
			<content:encoded><![CDATA[<p>Placeholder for CSD in BPR</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.actionmap.com/2007/09/28/cpd_bpr_ph/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
