Change Management: Focus on the People11 Apr 2017
Attempting to introduce new methods, policies or practices into an organization meets one, clear obstacle: resistance to change. Behaviour as natural for humans as breathing the air and very tricky to remove, due to the way our minds are wired to stray from the unknown and stick to once set ways.
The crucial thing to keep in mind when introducing a change is to oversee it throughout. If you're concerned about good results of shifting to a new paradigm, policy, system etc. - announcing it and expecting implementation is - by far - not enough. There needs to be an administration scheme in place, thanks to which teams will be prepared and aware of the nature of changes introduced before they happen.
Management also must have means of addressing outright reluctance to changes, and be sure that these means will not brake the team and company apart.
If you were to visualize a successful change introduction process, it should include the following:
- Having everyone aware of the adjustments being implemented since before the process started
- Appointing a few representatives and ambassadors of the change from among the team
- Building a support network for the foreseeable issues and questions
- Crucially - ensuring excellent communication flow between all part-takers through process duration.
Preparing for people being difficult
Now, that you've devised a plan and are hoping to work through it step by step, one thing you should be aware of is that most people will resist the change and some will outright boycott it - thereby inflaming others' moderate resistance.
An answer to the problem is not pointing fingers and assigning blame, but having a tool-set ready for working with these people, in particular - trying to identify the groups of largest resistance even before they speak up and presenting them with a simple work-plan, that weaves the changes into their current workflow.
It's normally easy to identify who will be among the resisting parties, by looking at people who:
- Stand a chance of feeling that more work will be expected from them in particular
- Were always advocating loudly for the old ways or vividly opposing the new ones when they were discussed
- Have been highly successful while working along the current lines of action.
Reaching out to these employees and providing an actionable plan can eliminate a lot of the potential bad attitude for a new paradigm, before this attitude spreads among all team members.
Reinforcing and monitoring changes
Bringing in a new set of requirements does not end with calming down the resistance, though this is indeed the toughest job. There is also a need to ensure the new policy or model are being followed after the initial weeks - you need to check up on whether the change has stuck.
The actual way to do this will highly depend on what the new demands brought in, some changes can be checked for by monitoring the process flow, others by sending dummy-test requests, others need to be explored in documentation.
Tracking down the results
From a practical point of view, you will need some way of managing dates and ticking off checkpoints, as well as of comparing statistical data from before and after the change.
We recommend using Kanban Tool's built-in Analytics, which make comparison of lead times and system throughputs effortless, also giving you access to the details of what the team are working on throughout the day. This allows for easy week-to-week comparison of what portion of time the changed aspects of their job was taking before and after modification, hence helping to validate the change in general.
Depending on your organization size and nature, introducing a change will either be "just difficult" or "very difficult", and this is why none of the time spent on preparing for it is wasted. Final tips:
- Don't try to introduce a change that you know is not possible to implement
- Spend a lot of time choosing the right people to act as change managers and change support - the success of your change implementation lies largely on their hands
- Use a reliable scheduling and analysing tool to monitor the results and actions
- Focus on how the team are reacting and feeling throughout the process, their attitudes and knowing that they're being cared for will be the make or brake of a success.
Global Search has Arrived!09 Mar 2017
We are happy to introduce an all-powerful, comprehensive and quick global search functionality. As hinted by global - the function allows to s...
When "Must Go Agile" Is Just a Face of Deeper Issues?21 Feb 2017
Agile can be controversial - it has its clear enthusiasts and vivid mockers. What does not help the situation are groups of people who use a call t...
Checklist Templates Are Now Available!06 Feb 2017
We've just added a great new Power-Up, with which you will be able to have a number of pre-set checklists. Thanks to this, you will be able to make...
Agile for a Small Business17 Jan 2017
You'd think that small businesses are Agile by default, simply because of scale of their operation. But it's not necessarily the case, and more oft...
Bringing Agile into Non-Tech Environments04 Jan 2017
Agile originated in a technical work environment and its likely still its main performance stage. However, that doesn't mean Agile cannot bring...
Happy Holidays!22 Dec 2016
Kanban Tool Team are wishing you Joyful & Happy Holidays and a prosperous New Year!
Solving the Working from Home Conundrum13 Dec 2016
If, despite best efforts, you are still getting stuck on social media while trying to do actual work - consider these, less obvious methods of ...
Agile Marketing Anyone?23 Nov 2016
It's not surprising that Agile development has spread to marketing. In a fast-paced environment, software development and marketing, along with...
Is Agile Good for People?16 Nov 2016
We know now for sure that Agile is a tested, proven and recommended methodology of organizing work and introducing change to an office environment....