Work OS adoption is exposing inconsistent business processes
I am the Director of Business Applications, and I am responsible for the implementation of a Work OS which seeks to bring together project management, service requests, approvals, and operations. Rather than having uniform processes, though, each department has its own way of doing something. Even for basic actions like employee onboarding and purchase approvals, the process used will depend on the department.
Thanks to the Work OS, these inconsistencies are now obvious, and management expects us to standardize everything before we roll out the implementation. The problem we face is balancing the need for standardization against the needs of the departments.
To anyone that has implemented a Work OS across a number of departments, did you standardize processes before adoption or did you find that the platform helped you to identify the systems in nine over time? What approach led to the least disruption for the company?