This article summarizes several considerations for sharing common processes, and presents several situations that can be judged as sharing common processes. 1. Why consider sharing? Foreword: The commonality that the author understands is that there is similar content, either logically similar or front-end pages are similar. You can directly share without changing it at all, or you can merge the processes and optimize the existing processes before sharing. The current OA system basically has a process engine, and the creation process is simple and fast, and it is often much faster to create a new process than to change the process. The creation process is so fast, why consider sharing? 1.1 User operations are repetitive and cumbersome Almost every company has an OA system, and OA is used by all employees of the company. If the interface and operation of multiple processes are almost the same, it will create the illusion of repetition for employees. If they are shared, it will not only simplify employee operations, but also Reduce learning costs and training costs. 1.2 Single data and no use value
A company with a large scale of personnel has many departments and processes, and information between departments is not smooth. Maybe A has a process, and B has a similar process, but they do not know each other. Although the creation process is fast, the PM has to plan sms marketing service the product reasonably, and from the perspective of the integrator, he needs to give the demander some reference and suggestions to reduce redundant single data. 1.3 Infrequent use, affecting page layout The longer the system is in use, the more processes, some of which are simple in design and used infrequently.