<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://msmvps.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>How not to make decisions</title><link>http://msmvps.com/blogs/sp/archive/2009/04/12/how-not-to-make-decisions.aspx</link><description>In the past week, I had a number of discussions about information securtity and technology in general. With colleagues, we identified few common patterns about decision-making in corporate environments - and those are case studies on how decisions shouldn&amp;#39;t</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40407.4157)</generator><item><title>re: How not to make decisions</title><link>http://msmvps.com/blogs/sp/archive/2009/04/12/how-not-to-make-decisions.aspx#1687324</link><pubDate>Mon, 13 Apr 2009 23:55:03 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:1687324</guid><dc:creator>Nhon Yeung</dc:creator><description>&lt;p&gt;I lot of it comes down to whether you have the time and money to invest in trying something new. Most organizations opt for the known and supported solutions hence you get the &amp;quot;we don&amp;#39;t support it as we do not know how it&amp;#39;ll behave&amp;quot; type scenarios. This hinders innovation and you end up with cookie cutter architectures which may not take full advantage of the technology. &lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://msmvps.com/aggbug.aspx?PostID=1687324" width="1" height="1"&gt;</description></item></channel></rss>