Change: The human element of R2O
![Image](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh2Gx6IC_kA9XR2NHGZyi-dC1GV_qDbM06941guogGxm4GkIWHks-LgOTR40Q-xqlsixfPKHLV4nWC6UoE1MOlVzlpmSPsGtTkNh6Dy9W7nPavhXanuif4tuhhagWaYndoScIlkniNzcO7O/s16000/j0178460.jpg)
From a product development perspective, the R2O process is complicated enough. But success is not attainable based solely on a good research idea, development cycle, and technical implementation. As part of the R2O process, it is also essential to make the case for organization-wide implementation and manage the change. Unlike normal product development, where the consumer ultimately determines the fate of the product through their purchase decision, the R2O process creates a deliverable that in some functional manner should change the workflow of the practitioner to strengthen the organization . And unlike the consumers, who openly embrace the change when they make their purchase decision, practitioners are asked accept whatever is implemented for their use organization-wide. Even with strong R2O principles at play, only a small subset of the practitioners are involved in the process through discussions, demonstrations, and testbeds before the coming change reaches implementation. Ch