I came across this article / blog piece while out surfing yesterday which essentially covers off '10 new IT rules' for the sceptical / amused in an 'oh for xxxxs sake' kind of way at the IT world in general. My favorite was actually #1—the CIO should come from the business. Why? Well we've been talking about the results from a major project we just completed this week (much more on this soon) and one of the areas we got to discussing is an issue which I think the vendor community merrily skipped over some time ago—the bit where they explained to their customers why all this 'service stuff' was actually rather useful for them as a common language to help them find those pesky incremental benefits from their IT that will help them get some of that nice competitive advantage instead of meandering along quite ordinarily thanksverymuch… and then read the above article and thought of course… whack a business guy into the CIO seat and problem solved—business guys get services… give him a few weeks and the entire organisation will…

At my second 'reading of other peoples stuff' session before i hit the sack I find James Gov and others chatting about devolving responsibility down the IT hierarchy (or not) and again, I thought good old #1's got that one licked too—the 'business CIO' wouldn't get all funny about letting those that know what they are doing get on with doing it (within the realms of some kind of over-arching common goal of course) because thats what senior business guys do—they delegate and devolve responsibility and dont get funny (well usually) about people taking the initiative and generally care more about how the business is doing. I'll hopefully talk a little more coherantly about more of this stuff in good time, and little earlier in the evening too.

so there… I surfed round in a circle today, liked something I read this morning and still liked it as I turn in to bed… which is more than I can say most days.