<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.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>Don't walk in with a problem until you have a solution</title><link>http://blogs.msdn.com/nickmalik/archive/2006/07/01/653640.aspx</link><description>Enterprise Architecture is a source of chaos, obstacles, and high-level fights. Any organization that has an EA team is saddled with inefficiency and cannot possibly make an agile decision. They are smart people, who can be used on other ways much more</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Technical Related Notes  &amp;raquo; Blog Archive   &amp;raquo; links for 2006-07-02</title><link>http://blogs.msdn.com/nickmalik/archive/2006/07/01/653640.aspx#654493</link><pubDate>Sun, 02 Jul 2006 18:39:49 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:654493</guid><dc:creator>Technical Related Notes  » Blog Archive   » links for 2006-07-02</dc:creator><description>PingBack from &lt;a rel="nofollow" target="_new" href="http://technote.thedeveloperside.com/?p=27"&gt;http://technote.thedeveloperside.com/?p=27&lt;/a&gt;</description></item><item><title>re: Don't walk in with a problem until you have a solution</title><link>http://blogs.msdn.com/nickmalik/archive/2006/07/01/653640.aspx#655959</link><pubDate>Tue, 04 Jul 2006 14:45:24 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:655959</guid><dc:creator>Asim Hanif</dc:creator><description>Hi there!&lt;br&gt;&lt;br&gt;&amp;quot;Don't walk in with a problem until you have a solution&amp;quot; - I think this statement is a good one, but very difficult to achieve in reality. We Enterprise Architects are often organizied in a central department and our aim with EA is to focus on holistisc cross-organisation and long term interests. One of our job is to review and give support to the decentralizied development departments. Our focus is EA and we can therefor not give solutions to project- and systemspecific problems (=solution architecture). The specific solution of problems and projects are decentralizied and our collegaues out there are much better then us to solute those problems. We have not deep and specific tech. competences to do that. We can poiint out problems and challenges, but the real solution must be done decentralizied at the projects with our reviews.&lt;br&gt;&lt;br&gt;</description></item><item><title>re: Don't walk in with a problem until you have a solution</title><link>http://blogs.msdn.com/nickmalik/archive/2006/07/01/653640.aspx#656046</link><pubDate>Tue, 04 Jul 2006 18:13:11 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:656046</guid><dc:creator>NickMalik</dc:creator><description>Hello Asim,&lt;br&gt;&lt;br&gt;It is true that it is up to the development project teams to fix technical problems. &amp;nbsp;However, from a pure governance point of view, a valuable EA program is not focused solely on technical problems. &amp;nbsp;Most of the problems that we will bring to the table to strategic alignment problems, and those are much harder to fix. &amp;nbsp;In that case, we not only point out the problem, but for those project teams that have never fixed a problem like this before, we need to provide as many specifics as possible to assist in solving them.</description></item><item><title>re: Don't walk in with a problem until you have a solution</title><link>http://blogs.msdn.com/nickmalik/archive/2006/07/01/653640.aspx#658156</link><pubDate>Thu, 06 Jul 2006 21:38:31 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:658156</guid><dc:creator>Piyush</dc:creator><description>Sometimes the key insight is sensing the problem and defining it properly. Enterprise Architects can certainly help do that even if they don't bring a solution. I'd go far enough to say that the best Architects I've seen have been better at defining problems in a simple way rather than crackerjack solutionheads.</description></item><item><title>re: Don't walk in with a problem until you have a solution</title><link>http://blogs.msdn.com/nickmalik/archive/2006/07/01/653640.aspx#664622</link><pubDate>Thu, 13 Jul 2006 19:21:58 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:664622</guid><dc:creator>Asim Hanif</dc:creator><description>I am much agreeing in Piyush&amp;#180;s statement. The often situation in projectrelated challanges is that the problems are not veldefined. In this case it is good that we Enterprise Architects can come from outside and see and define the problem objectively. Regards Asimblogged.com</description></item><item><title>Enterprise Architecture and Being Solution Oriented</title><link>http://blogs.msdn.com/nickmalik/archive/2006/07/01/653640.aspx#676166</link><pubDate>Mon, 24 Jul 2006 04:19:46 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:676166</guid><dc:creator>Patrick Altman</dc:creator><description> Nick Malik hits the nail right on the head with this post.&amp;amp;amp;nbsp; This doesn&amp;amp;amp;rsquo;t just apply to architects...</description></item></channel></rss>