Thursday, September 08, 2011

How do you see your profession changing?

Am referring to your profession not your job.

To set the context, Am going to talk only about functions only within Enterprise IT (CIO organization).

You may be a Project Manager, Architect, Vice-President - Operations, Compliance Officer, Quality Assurance Provider, Accountant, HR, Developer - There are chances that your stakeholders might have added new expectations to your function without your notice!.

Let me quote few examples.

1. There is no dearth of discussion around the topic of Enterprise Architecture & Enterprise Architects. People across networks keep debating about the pros and cons of this Role all the time. Recently, there was an article published from Zapthink on some of those provocative topics - What will it take for enterprise architecture to become a profession?. And Why nobody is doing enterprise architecture?.

2. Forrester has been publishing some very interesting research on Why do some Strategic Roles fail?. The roles include Enterprise Architects, PMO, Planning, Relationship Management, Vendor Management etc.

3. TechTarget predicting the future roles of Enterprise IT with the advent of Software-as-a-Service. It predicts Enterprise IT would dwindle and become a Service Broker rather than a Solution Constructor. With this change, it claims coding/development functions will become less important and eventually transition to IT Service companies/Product Companies.

4. The emergence of new roles such as Data Scientists may be a threat for some and opportunity for others.

If Strategic functions have these challenges, one may get an impression that Operational functions are safe haven! Not Really! :-)

5. Rakesh Khurana of Princeton University argues whether management itself can be considered as a profession. That's startling!. Of course, the context of this perspective is not specific to Enterprise IT. It applies to General management across industries.

What do we mean by Profession? Making a function as a Profession requires codifying the practices and enforcing the code of conduct for practitioners. (e.g. Medicine, Law). A Job provides a channel to deliver the standard functions of a Profession.

Why is this issue important for Enterprise IT? Because, its the only unit within the organization that gets continuously disrupted both with emerging technologies and changing business needs!. Enterprise IT needs to balance the expectations of being a rock-solid infrastructure provider to business enabler and innovative technology solution partner.

In progressive organizations, the disruptions in the demand/supply chains of Enterprise IT (be it business stakeholders on the demand side or IT service providers/technology vendors on the supply side) will call for profound changes in individual functions within the unit!.

Let's face it!. Functions in Enterprise IT are moving targets!. The solution is to continuously deliver "value" in current function and stay alert!. To stay alert, it is required to understand the movements/disruptions a lot more better in terms of its direction, velocity & impact and respond appropriately and timely!.

1 comment:

Venky said...

Interesting thoughts. Considering the amount of rapid change happening, would enterprise IT architecture move towards emergent design? With the advent of Web, firms are beginning to go by Emergent strategy, taking their baby steps aligned with their ecosystem? As we move slowly towards a perfect Cloud, wouldn't there be need for the architecture to be emergent, in sync with the current state of the ecosystem? Would love to hear your thoughts..