Thanks for the comment, Kelly Barner.
I think it is fair to say that you are not the only one who hates change. I guess most people (if not everyone) answers “no” when asked to change. Especially when, as you rightly say, they are given no proper explanations / reasons (i.e. consideration).
Without spoiling what is coming in part 3 and 4 — 😜…here are a couple of things that are more or less obvious (and typical mistakes) that applies to many Procurement tech. projects:
- Lack of meaning: this is the “why” you are talking about. It has several levels: company (business case, ROI…) and individuals.
- View of such projects as being solely technical (solution, features…) when they are actual all about people (change management, motivation, adoption…). This has a huge impact on the design of the project.
- Too fast, too soon. This induces a focus on “doing” and not on preparing enough the project / case.
Also, and to conclude (and going back to your “I hate change”), yes, most people hate change but the way they respond to it is what matters. Most people will just be passive and follow the flow. Cynicism aside, a natural tendency of “change leaders” is to try to convince everybody. It is a waste of time and energy. It is much better to focus on the people who are ready to give the change a try. Once they demonstrate that it works, the majority, who is passive, will follow.