Skip to main content

Mind the Gap not the Name

As mentioned in my post ESB for an Orphan, Business & IT alignment is one of SOA's Value Propositions. Do we need also to change the name of Information Technology (IT) to another name reflecting IT's new role as Business related technology?
George F. Colony, Forrester Research founder, Chairman of the Board and Chief Executive Officer thinks it should be changed to Business Technology (BT).

About three years ago, he posted his view in Forrester Research's Web site and initiated a very interesting discussion. Forrester's analysts and other IT or BT experts presented their views and their comments on George Colony's view. Some participants agreed with him, while other suggested other new names replacing IT. Surely, some participants thought IT should remain the name for IT. I do think that the issue was not resolved and therefore I am posting again my opinion. Comments are welcomed.

My Opinion titled: Mind the Gap not the Name

I read George Colony's view and the comments to it. The only agreement is no agreement about what a new name for IT should be if any.
The real issue is the gap between IT and Business. George Colony is right: Business can not function without IT, but IT is also a main obstacle to business growth due to no Business and IT alignment and the current inflexible IT architectures.
I think that in the past we (IT people) focused on new technologies and architectures (and perhaps new names and acronyms) instead of servicing the business requirements.

based on many clients' organizations, is that we (IT people) can do more in order to reduce the gap. In my opinion, SOA, if properly implemented, would reduce the gap for the long term.

As far as the less important naming is concerned I have no acronym to offer.
If a new acronym would emerge the following elements could be part of it:
Information, Processes, Services.
I agree with Phil Murphy and others that Business should not be a part of that acronym.

Should Technology be part of it?
I am not sure.
Technology is a broader term referring to other non IT technologies, which may be essential for some business segments (e.g. Mechanical Engineering technologies in Automobile or Airplane industries).


Labels:

Comments

Post a Comment

Popular posts from this blog

The mainframe: still alive and kicking

Recently, I was interviewed by  Pcon   (unfortunately the link points to an Hebrew only site) as part of debriefing on Legacy Systems.  Pcon is an Israeli company investigating IT topics by quoting professional articles and interviewing experts. They publish the results of the investigations including practical recommendations. This post is mainly about topics raised by me during the interview, but not included in the debriefing, which will be published.    What are Legacy Systems? The term Legacy Systems refers to old application systems and/or veteran technologies still in use.  Usually, the term Legacy Systems is associated with: 1. Mainframe Hardware e.g. IBM System z and its Operating Systems or Proprietary Servers and Operating Systems such as HP Alpha and OpenVMS Operating System, IBM AS/400 and OS/400   Operating System. 2. Development and Production Environments, e.g. COBOL , Natural and DBMS systems such as Adabas  ...
16 comments
Read more

Will Business and IT Aligned?

For decades we are talking about closing the gap between business and IT , but the gap is still as wide as it was. In the beginning of the ERP era, we focused on aligning Business Processes and Core Systems, but in most enterprises we failed. SOA was the next alignment promise: defining the SOA Services in Business boundaries instead of Technical boundaries, should narrow the gap. However, despite of SOA Business Value ( Agility and Reuse )  in most enterprises,  the large Business-IT Gap remained as large as it was.  The IT Community aimed at the next alignment attempt: SOA is technical and BPM is its Business related complement.  Will the current BPM based alignment attempt succeed? I do not know, but Nick Heath's article  titled: Stop doing what the vendors tell you, CIOs told , published in  Tech Republic , suggests that the root of the problem is not Technological .   Stop Doing What the vendors Tell You Nick Heath's article is based ...
11 comments
Read more

Vendors Survival: Will Software AG Survive until 2019?

This post is another post in the Vendors Survival series following posts on Microsoft , Google , HP , Sun and EMC . On July 14 th Software AG and IDS Scheer announced that Software AG is going to take over IDS Scheer . The intended acquisition is an opportunity to add another post in my Vendors Survival posts series. A brief history of Software AG Mainframe products Software AG is larger than any German software company except SAP . It was established in the Mainframe age (in 1969). I worked with many customers, who used and some of them are still using, its two flagship products Adabas and Natural . Although these products support many platforms, their main platform is IBM Mainframe. Adabas is a database and Natural is a development environment. Like other pairs of Database and Development Environment in the mainframe environment (e.g. Ideal and Datacom , Mantis and Supra) build by the same vendor, they are tied together. As a result, although it is possible t...
8 comments
Read more