If you want to change a workplace, the workers need to help drive it. They need to understand the change, why it's needed, and how it helps them and the company. They need to help shape the details.
This means that you don't just spring a new computer system on them one day and provide them with a couple of hours of training. This means, as you develop the system, you also develop simulators, and you allow groups of users to try them out (even at the beginning of the project, where functionality is minimum). Get their feedback, and incorporate that into the design. There are no excuses to not iterate, especially if you consider yourself "agile."
Finally, when the system is ready, you don't just tell the users to do everything with the new system, especially if they are under a time crunch. Have both systems side by side, and start by letting them work a few, simple tasks through the new system. Let them naturally shift over their workload to the new system as they get comfortable.
These are all covered by my Strategic Simplicity® Framework, CLOUD:
Change simplicity
Language simplicity
Operational simplicity
User simplicity
Decision simplicity
© 2024 Praveen Puri
