<?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: Decision Making &#8211; Tips for implementation effectiveness</title>
	<atom:link href="http://barbvann.com/2009/10/decision-making-tips-for-implementation-effectiveness/feed/" rel="self" type="application/rss+xml" />
	<link>http://barbvann.com/2009/10/decision-making-tips-for-implementation-effectiveness/</link>
	<description>Transformative Leader of Business, People, and Information Technology</description>
	<lastBuildDate>Fri, 26 Feb 2010 00:59:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
	<item>
		<title>By: Decision Making &#171; Sapientia et Doctrina</title>
		<link>http://barbvann.com/2009/10/decision-making-tips-for-implementation-effectiveness/comment-page-1/#comment-107</link>
		<dc:creator>Decision Making &#171; Sapientia et Doctrina</dc:creator>
		<pubDate>Mon, 26 Oct 2009 04:14:08 +0000</pubDate>
		<guid isPermaLink="false">http://barbvann.com/?p=79#comment-107</guid>
		<description>[...] Read More    Tagged with: Decide, Decision, Decision Making   leave a comment    &#171; Be a person who can be&#160;trusted. [...]</description>
		<content:encoded><![CDATA[<p>[...] Read More    Tagged with: Decide, Decision, Decision Making   leave a comment    &laquo; Be a person who can be&nbsp;trusted. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Barb</title>
		<link>http://barbvann.com/2009/10/decision-making-tips-for-implementation-effectiveness/comment-page-1/#comment-88</link>
		<dc:creator>Barb</dc:creator>
		<pubDate>Thu, 22 Oct 2009 11:44:47 +0000</pubDate>
		<guid isPermaLink="false">http://barbvann.com/?p=79#comment-88</guid>
		<description>Saqib,
Thanks for adding to this post, you have provided great thoughts for consideration!</description>
		<content:encoded><![CDATA[<p>Saqib,<br />
Thanks for adding to this post, you have provided great thoughts for consideration!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Saqib Ali</title>
		<link>http://barbvann.com/2009/10/decision-making-tips-for-implementation-effectiveness/comment-page-1/#comment-82</link>
		<dc:creator>Saqib Ali</dc:creator>
		<pubDate>Wed, 21 Oct 2009 18:50:32 +0000</pubDate>
		<guid isPermaLink="false">http://barbvann.com/?p=79#comment-82</guid>
		<description>Barb,

Excellent post.

We often fall in the trap of re-evaluating decisions, which keeps us from executing upon it. I think the problem stems from lack of proper decision making tools and processes. Right now we exchange emails to come to a decision. However, email is where the information goes to die. The information that was used to come to decision, is lost in the threads in the Inbox. And once the decision has been made, it is transferred to PowerPoint for review by upper management. Fidelity is lost and details are left out in this translation from a threaded discussion to a PowerPoint slide.

The alternative is to use a wiki based platform, where a team can collaborate to formulate decision. But the problem with wiki, is the fluid nature of the platform. Once edits are made to a wiki page, it is almost impossible to tie the comments, thoughts, and input back to their author. Sure wikis provide a way to view  the linear history edit, but how many of us go back to look at the history of a wiki page?

What we need is a enterprise 2.0 style collaborative decision making software. This platform should allow teams members to collaboratively come to a decision by capturing input from each team member, and once a  decision has been reached, it should turn to a workflow for approval by upper management. Once approved, it should automatically be routed to the appropriate team for implementation. If changes are made to the decision, it should create a new workflow.

Saqib</description>
		<content:encoded><![CDATA[<p>Barb,</p>
<p>Excellent post.</p>
<p>We often fall in the trap of re-evaluating decisions, which keeps us from executing upon it. I think the problem stems from lack of proper decision making tools and processes. Right now we exchange emails to come to a decision. However, email is where the information goes to die. The information that was used to come to decision, is lost in the threads in the Inbox. And once the decision has been made, it is transferred to PowerPoint for review by upper management. Fidelity is lost and details are left out in this translation from a threaded discussion to a PowerPoint slide.</p>
<p>The alternative is to use a wiki based platform, where a team can collaborate to formulate decision. But the problem with wiki, is the fluid nature of the platform. Once edits are made to a wiki page, it is almost impossible to tie the comments, thoughts, and input back to their author. Sure wikis provide a way to view  the linear history edit, but how many of us go back to look at the history of a wiki page?</p>
<p>What we need is a enterprise 2.0 style collaborative decision making software. This platform should allow teams members to collaboratively come to a decision by capturing input from each team member, and once a  decision has been reached, it should turn to a workflow for approval by upper management. Once approved, it should automatically be routed to the appropriate team for implementation. If changes are made to the decision, it should create a new workflow.</p>
<p>Saqib</p>
]]></content:encoded>
	</item>
</channel>
</rss>

