Many companies balk at enterprise architecture because they feel that the returns doesn't necessarily justify the investment, but then again, most companies have never really done enterprise architecture before nor do they know how to really invest or do it right. But that's a theme for a different blog post. Rather the issue is many companies feel that they can continue doing what they are doing now and do arch Many companies balk at enterprise architecture because they feel that the returns doesn’t necessarily justify the investment, but then again, most companies have never really done enterprise architecture before nor do they know how to really invest or do it right. But that’s a theme for a different blog post. Rather the issue is many companies feel that they can continue doing what they are doing now and do architecture at some point in the future. In essence, they are saying that there’s no time (or money) to do things right now, but there’s time to do it over and over again. If you think about that, it doesn’t make any sense. Why would a company have time to do things right in the future if it’s just digging the hole deeper? The answer is typically spun around budget issues, and even office politics. The connection is that on Thursday, this is one of the key issues we’re discussing at our Practical SOA for Financial Services event in London, and will be a recurring theme for all our sessions. It’s not sufficient to know about SOA, but companies have to know to do things right before they just go back and do things over. The truth is that delaying “the fix” just costs more money. More than you think, when you do the analysis. I’m constantly surprised how much is wasted around ineffective and static architectures that are not able meet the needs of business. The solution is complex, but with a bit of work doable, within most organizations. You just have to have the desire to fix things once and for all. Software Development