PLM Application Adoption - Global vs. Local

In the couple of years I have spent in helping the end users to adopt the PLM process supported with a PLM software application, I have learned some lessons in a hard way.  As I went through the hard way, however, I am able to touch the fundamentals with a deeper understanding.

First, the process of adoption is never a one side game.  The problem of representing a software vendor in the process of roll-out and adoption, as I often found, is that I have to follow instructions provided by the software vendor with strong perspective according to their understanding about the needs of the end users.  Unfortunately, software vendors wear the shoes of the software.  They are very clear about how the software should be working and they are constantly imagine the idea situation when all conditions are satisfied and the software is happy ever after.  Therefore, the assumption is, as long as my software runs perfectly without issue, the end user would be expected to be happy, too and very much willing to pick up and use the application.  As a result, the training program is designed to only show a happy system with a scope of functionalities covered.     It is just NOT enough.  No matter how much experience the trainer has, how well organized the training room is, it is just not enough.  The users would still be screaming at you.  What is missing is the other side of the game.

Second,  the human minds involved in this process are never one square mind.   

Third, the border lines between business and sysetm are never ever clear. 

The last but not the least, the clash between regional and global requirements can never be avoided.