Follow Prem Kamble on Google+!
Managers Don't Need IT Skills - They Need 'Behavioral IT' Skills
Summary: Behavioral IT is a new term coined by Prem Kamble. It is important for all Managers, particularly CEOs, CXOs and Department Heads. What is Behavioural IT? Is it a new field of study within IT, or is it a skill? Well, it is both, argues Prem Kamble. Managers can heave a sigh of relief as they really don't need to know IT. Managers need to know Behavioral IT. They need not harbor that inherent fear of IT, nor the painful thought "I do not know IT".
"Behavioral Finance" and "Behavioral Economics" are relatively new topics of study in the areas of Finance and Economics respectively. They explore the impact of human behavior and psychology on decisions like investment and spending.
There is a scope for a whole new area of study and research which I call "Behavioural IT". Information Technology or IT is not all technology. People are an important part of this technology game. It is very well understood that software development is a people intensive activity unlike a manufacturing activity where machines are involved. But what is not very well appreciated is the role that people at all levels of an organization play during the implementation of software, a step which is the last mile without which no IT activity can be complete. Implementation impacts much larger groups of people as software gets rolled out to reach all the users in the company. Attitudes, mindset, beliefs, misconceptions, fears and behavior of people at all levels play a significant role in the success and failure of this phase of an IT project.
IT is the primary driver of change in businesses today. And people naturally and strongly resist change. Behavioral IT is a study of behavioural aspects of particpants and stake holders in an IT Implementation that can make a difference between success and failure of the project in any company. Alternately, Behavioral IT skills are the skills required by all managers to manage people and processes impacted by rapid IT-Driven Change.
Before I put up this page in my website, I did a google search on "Behavioral IT" to check if anyone has defined this term. I did not find any relevant entry. Now (Nov 2012), my page (this page you are reading) shows up as the first entry in google search output. In fact this is the only relevant entry as all other entries do not exactly match the search term "Behavioral IT". It appears that no one has used or defined this term. If I am the first to use this term, it becomes my responsibility to define this term as clearly as possible. So let me try to define it in this article. Though I have been working and writing on this topic for long, I have not called it "Behavioral IT" before. Being my first penned thoughts on defining this term, they may be incomplete and to some extent unstructured. I am sure a more precise definition will evolve as I refine this article, hopefully with the help of useful comments and feedback from you, the reader.
Whereas there is enough emphasis so far on the behavioral issues in the software development process, what has been relatively ignored is what typically gets left out in most IT projects - the last mile, i.e., the actual transition from the old system to the new computerized system. We call it the implementation and user acceptance of the new system. In an IT project, the last mile is the most important and most difficult part of the journey. This last step is important because a failure at this stage would obviously imply a higher loss of resources and time, having spent the time and resources already on the development of the IT project. Usually the maximum number of people are involved in the IT project during implementation. Moreover, the maximum variety of people (right from clerical and executive level to CEOs) are involved during this phase. A failure at this stage implies higher stress and lower morale for maximum number of people.
Unfortunately, most IT Professionals lack the skill to see a project through the last mile. They are comfortable doing all the technical preparatory work for IT projects in the cool comforts of their offices, but fail miserably when it comes to implementing systems in the tense, heated environment of vested interests, personal preferences and rigid mental-emotional make of people affected by the IT-driven change.
Behavioral aspects are very important in the implementation phase not simply because more people are involved, but because people are expected to do what they resist most, i.e. change their way of working. People naturally resist change and complex behavioral patterns come to surface, which the IT Transition manager or Implementer has to overcome to succeed. It involves people's attitudes, fears, dogmas, mental paradigms, misconceptions, resistance to change and various human character traits. A software solution may look excellent when demonstrated on the computer screen. But if is not accepted and adopted by the end users, all the effort, time and money spent on the project is wasted. And the wastage is huge, looking at the amount of unimplemented systems in companies and over 70% failures in ERP implementations.
I did an extensive search on the web on people issues of IT. Most of the papers written so far deal with Human Computer Interface, Interface design, collaboration, people issues in software development, etc. (and of late, on the impact of social media on people's behavior). If at all behavioral aspects have been studied in IT, they are with respect to two main areas of IT - behavioral issues in software development phase or development project management, and behavioral aspects in man-machine interface. There is very little work done on behavioral issues during the Implementation phase. Whereas researchers have gone as far as neuro science to localize the functionality of the brain areas that impact Technology Adoption (a field of study called NeuroIT), not much research is done on the behavioral aspects that are at play during the most people-centric stage of IT project, that is, the stage of IT implementation.
would therefore define Behavioral IT as Behavioral aspects of IT driven
transitions, particularly the stage of implementation when there is maximum
people involvement and also maximum project risk due to behavioral traits, attitudes and fears
of people. This is the stage when people's behavior is most unpredictable as
they are in the most uncomfortable and vulnerable state - that of change. Change causes
considerable stress, and the implementation stage is the stage of nailing the change (and hence the stage of maximum
upheaval and turmoil).
Definition of Behavioral IT
Behavioral IT as an Essential Managerial Skill
Behavioral IT is a special skill essential for all managers to succeed in this IT Driven world. Managers don't need to know IT, they only need to know Behavioral IT. Behavioral IT provides an avenue for managers to acquire just the right IT skills which they need, without knowing technology. Behavioral IT as a skill is discussed in this article.
Behavioral IT Framework of Implementation
Behavioral IT can be defined as a field of IT that proposes people-based theories to study the causes of success and failure of Software implementation projects. Within Behavioral IT, it is assumed that the success or failure of IT projects do not merely depend on the technical issues as is commonly believed, but largely due to people's attitude, mindset, beliefs, mental conditioning, concepts and misconceptions about IT. Hence a Framewrok can be developed with focus on people to successfully implement IT projects. I call it the "Behavioral IT Framework of IT and ERP Success". This Framework is not included in this article and is described separately in another article. (Click here to read)
Understanding "Behavioral IT" Skills
A good way to understand "Behavioral IT" is to look at the typical behavior or traits of managers who display "Behavioral IT Skills" in contrast to managers who do not have the same skills. Knowledge of Behavioral IT, in fact, is the key to personal success of all managers. Behavioral IT skills are particularly important for Department Heads and CEOs who are the primary drivers of change in IT Projects.Department Heads/ Managers with Behavioral IT Skills:
In contrast, Department Heads/ Managers who lack Behavioral IT skills
The same is true for CEOs.
Behavioral IT aware CEOs:
Whereas CEOs who are not Behavioral IT aware:
The Way Forward
Since not much work has been done in this important aspect of IT, it is important to start with educating senior management on Behavioral IT and its importance in the success of IT Projects. Behavioral IT skills are required by all managers, irrespective of their function, as all managers need to use IT to speed and streamline their processes. Behavioral IT skills are also required by CEOs and Heads of departments, because they play key roles in the success or failure of an IT project. It is an irony that most seminars and courses on Change Management do not even touch upon managing IT-Driven change, which is the primary driver of change today. With this need in mind, some seminars have been designed for senior managers. Please click here to see more details about these seminars.
It is important that this skill is imparted right at the entry stage or at management education stage so that young managers enter the corporate world equipped to manage people behavior under IT-Driven Change. Hence, it is recommended that courses on Behavioral IT be introduced in the management curriculum. A course on Behavioral IT has been designed for MBA students, which could well be the first of its kind in the world! This course has been delivered at IIM, Indore. Click here for details of the course or write to me for details.
Comments? Feedback? Click here
(Keywords: Behavioral IT,Computer,Implementation,IT Best Practices,Infotech,CIO,People Issues in IT,Human aspects of IT,Psychology of Change, Software Professional,Psychology,Behavioural IT,Behavioral aspects of Information Systems,IT management,Change Management,Prem Kamble)
Behavioral IT® Model of Successful IT Implementations
Copyright © 2012 Prem Kamble