More damned if you don’t
Monday, July 21st, 2008For the last several weeks, there’s been a lot of blog discussion about a Burton Group report on SOA “success” or the apparent lack of it.
An interesting thread of commentary has broken out about the role of CIOs in the success or failure of next-generation application development in business. David Linthicum suggests that CIOs are “…very different animals from company to company.” And Scott Wilson thinks CIOs are in a “delicate position” when it comes to adopting new technologies, balancing needs to progress versus reliable service delivery.
For us, it’s simpler: it’s much more dangerous — bordering on suicidal — to let the fear of change become the rationale for continued stasis. That’s why Burton reports that companies get better results with newly hired CIOs. The new guy has a honeymoon period in which he or she can do the unthinkable. (Marketing execs in software companies are almost as perishable as CIOs. We are often brought in to “fix” the previous guy’s reluctance to change.)
But at the end of the day, a change in leadership doesn’t change the underlying reality that the whole IT organization — from the developer in his cube to the CIO — just isn’t scared enough.
Sure, they’re a little bit scared: “If we have to change, we run a risk.” But it’s the wrong thing they’re afraid of…the wrong fear.
What’s a fossil? Something that stood still long enough to get buried, then wedged into rock to be cooked by pressure over time until it disappears. That’s what developers, analysts, business owners and CIOs are doing: letting the small fear of change become comfortable enough to crowd out the large, more important fear of being fossilized.
And that’s a whole lot scarier. For the business…for individuals.
If this sounds like a wake-up call to developers to lose more sleep at night over why they keep finding reasons not to move to services-based apps, it is. If you think we are saying that enterprise architects should be put on a multi-step program to recovery from PowerPoint architectures, we are. If you think we are suggesting the CIO is more damned if he doesn’t implement today’s visual orchestration systems, you’ve got it.




