Inscrivez-vous ou connectez-vous pour rejoindre votre communauté professionnelle.
Think that by doing this you can reduce the number of workers so that the overheads will reduce.
Firstly you have to realise that employees hearing automation over manual process which is synonymous to job loss is going to send employees into a spin and on a major Resist till the End war cry.
As a Project Manager in an IT solutions provider whenever we had meetings management once they got over the cost shock were eager to go ahead - employees on the other hand becomes extremely resistant to participation in the User Requirement State - thinking that if they didn't tell the Solution providers everything, they'd still have their job security - this is a no win situation in reality.
So my approach was always go down to the grassroots and LISTEN to what they are saying and understand what their REAL and FICTIONAL concerns are.
I often found that when I went into my first URS meeting I'd always be met with hostility - oh here's the person who is going to make me lose my job. But by engaging with the employees, listening to their daily challenges in their manual process and finding out the bottlenecks and being able to relate how the proposed automation will free up this much time for them to focus on the more important things helped.
Also the fact the if management actively engaged with employees prior to a role out of any OA solutions, where their input and ideas were incorporated - you find a decrease in the resistance and even an excitable interest to see the fruits of their input rolled out.
It's actually engaging in a bit of covert conversion and role reversal where employee feels they have a say in how they do their job on the OA gives ownership and responsibility.
Good luck
