Dealing with changes in IT project teams
Dealing with changes in IT project teams
Anyone who works in IT&C or knows the IT&C market acknowledges that it is very dynamic area, full of challenges and twists. This also means that any company that wants to succeed must make sure that every employee must be capable of adapting to changing situations very fast. The flip side is that with so many changes to deal with it is very easy to drift away from your plans and get yourself, the project or the entire organization into a difficult situation.
24 May 2016
2928
Other articles
How to incrementally migrate the data from RDBMS to Hadoop using Sqoop Incremental Last Modified technique?
How to implement Slowly Changing Dimensions(SCD) Type 2 in Spark?
How to incrementally migrate the data from RDBMS to Hadoop using Sqoop Incremental Append technique?
Why MongoDB don't fetch all the matching documents for the query fired
How to solve the issue of full disk utilization in HDFS Namenode
Can We Use HDFS as Back-up Storage?
How to do Indexing in MongoDB with Elastic Search? Part 1
How to do Indexing in MongoDB with Elastic Search? Part 2
How to store data on browser using NoSQL IndexedDB?
How to Apply MBTI in HR: Motivation for every day. Groups of People & their Motivations
Anyone who works in IT&C or knows the IT&C market acknowledges that it is very dynamic area, full of challenges and twists. This also means that any company that wants to succeed must make sure that every employee must be capable of adapting to changing situations very fast. The flip side is that with so many changes to deal with it is very easy to drift away from your plans and get yourself, the project or the entire organization into a difficult situation.
Managers can get into situations where it's pretty easy to go the wrong way when proposing or adapting to changes.
What are the risks?
Sometimes managers decide to keep a distance between their team and any change initiative – and any turmoil that may come with it. This is done for many reasons, be it lack of information or the fact that the news is negative, and managers want their teams to be protected and disturbed as little as possible. But the result of this unnecessarily protective behavior may surprise you. Instead of a climate of trust and focus on performance, people will experience a sense of uncertainty increased by a lack of information, where assumptions and word of mouth will replace normal communication. Not all people will ask their manager about what's going on and many will make backup plans if things should go wrong. Guess who will be surprised by their decision? In fact this behavior focuses people on getting information rather than performing in their daily tasks.
The second risk comes from assuming people will embrace change no matter what and that everybody will just adapt to the new situation. Lack of support is one of the reasons implementing changes in a team will fail.
Not having a plan or answers to provide, not to mention a high level of support for the new situation will only give unreasonable and unrealistic hopes on how the future will look like. The lack of competence in shifting from the current state to a new objective will trigger a sense of low self-trust.
What you can do
If you are managing a team in an IT environment takes note of following rules for managing change:
Dan Bruma
Specialist in Project Management, Soft Skills
Managers can get into situations where it's pretty easy to go the wrong way when proposing or adapting to changes.
What are the risks?
Sometimes managers decide to keep a distance between their team and any change initiative – and any turmoil that may come with it. This is done for many reasons, be it lack of information or the fact that the news is negative, and managers want their teams to be protected and disturbed as little as possible. But the result of this unnecessarily protective behavior may surprise you. Instead of a climate of trust and focus on performance, people will experience a sense of uncertainty increased by a lack of information, where assumptions and word of mouth will replace normal communication. Not all people will ask their manager about what's going on and many will make backup plans if things should go wrong. Guess who will be surprised by their decision? In fact this behavior focuses people on getting information rather than performing in their daily tasks.
The second risk comes from assuming people will embrace change no matter what and that everybody will just adapt to the new situation. Lack of support is one of the reasons implementing changes in a team will fail.
Not having a plan or answers to provide, not to mention a high level of support for the new situation will only give unreasonable and unrealistic hopes on how the future will look like. The lack of competence in shifting from the current state to a new objective will trigger a sense of low self-trust.
What you can do
If you are managing a team in an IT environment takes note of following rules for managing change:
- Clarity
- Rationale
- What doesn’t change
- What will stop
- Call for action
Dan Bruma
Specialist in Project Management, Soft Skills