Previously we discussed why it's important to keep limited number of integrations. Today we would like to introduce you the second tip which will help you to implement a P2P digital solution successfully.
Shall we wait until everything is ready then presenting it to the end users? No!
It's not a matter of perfectionism, at least not in this case. We have seen companies waiting until everything is almost ready before finally starting to engage the end users. What happened is that people simply didn't recognize it and feel less satisfied with the new system. About 70% of transformation initiatives fail, mostly resulting in a lack of buy-in and engagement from the employees. When the transformation fails, it takes much more time to rebuild, redesign and reengage the users. The investment of time and effort are wasted unworthily. Therefore our advice for you is to start showing the system to end user as soon as possible, don't wait until it's perfect (it's never perfect). The reason why this tip is crucial is because change takes time. A change in the daily operations, especially in the tool or system people use, may be considered as a much greater change for them. While it's all about repetition, the earlier we start showing the system to end users, the higher chance they will buy-in more easily.
Besides, early identification of leaders, super users and change champions is key to appropriately prepare them to lead the change of this scale and complexity. By engaging these key stakeholders earlier, we increase the chance to ensure a smooth and sustainable transition of people's mindsets.
In the coming months, we will publish our learning and recommendation for each tip bi-weekly based on real-life cases. Please follow us to ensure that you receive the latest updates!
- Keep the number of interfaces limited
- Start showing the system to end user as soon as possible, don't wait until it's perfect (it's never perfect)
- Keep the buying channels design simple, standardized and flexible
- Be bold and honest to encourage more single POs creation
- Giving user more access of the system in the beginning instead of in the end of the project
- Avoid (notification) email overload
- Don't overkill the non-preferred supplier but keep some of them to enhance user experience
- Don't lose sight of your company culture