What about IT cultivating a relationship with marketing where a lot of innovative ideas orginate? Or even with sales or support folks in the field who know what it takes to close more deals and keep customers happy....just a thought. Seems like those are relationships are rarely explore. I know some IT hate marketing because they are always, among other things, pushing. But they often know their markets extremely well.
Last week I was interacting with a number of technologists where we were discussing the need for organizations to be more agile and the implications this may have on an organization’s architecture efforts in general and enterprise architecture in particular.
The same pressures shifting the needs of the business are present where business and technology meet and should affect the creation and use of architecture work products. Much can be learned from what’s happening in the agile development space, and applied to architecture:
Since the first of the year, I’ve been giving a presentation on embracing technical trends for organizations – what strategists need to think about to address the needs of their organizations. At the end of the material, I include a summary of takeaway points. Since I haven’t posted anything to this site for a while, I thought I’d share them and see what kind of reaction develops:
This week I was working on a presentation for the ISSIP Service Futures SIG titled: Service Futures and Drivers of Change. Part of the presentation included a discussion of megatrends – the industry independent trends that will shape our lives in the future and their effect on business decision making.
Last month, I attended the MIT CIO Symposium focused on the transformational CIO. At the event I ran into John Dodge (of this site). John said I hadn’t posted much recently so I thought I’d pass along a brief summary of the panels I attended:
I was in a discussion the other day about the state of automation and IT. We started talking using a quadrant chart (much favored by consulting organizations today), that had an axis for data and one for process that looked something like this.