Standardized management, standardized management of ways of doing things

1. Classification of standardized management: the importance and frequency of "things".

(1) Importance of things: An enterprise has many things, some are important and some are not. The importance of everything is different, and the degree of management according to the importance is also different.

(2) Frequency of events: Some things happen every day and some things happen for a long time. The frequency of occurrence is different, so is the degree of management.

(3) Regular events: things that happen frequently, that is, events with high frequency, belong to regular events and are brought into standardized management.

(4) Abnormal events: Incidents that occur occasionally or with low frequency belong to abnormal events and are included in the exception management.

2. The principle of designing "doing things" is simple, complete and effective.

(1) In the management of design specifications, certain principles must be observed, namely simplicity, integrity and effectiveness. The system designed according to this principle will have efficient application and smooth operation.

(2) Simplicity: Simple things are easy to achieve, and you can play easily and effectively. Simple design can distinguish responsibilities and grasp key points.

(3) Integrity: Necessary control is indispensable. Without them, there will be loopholes, and there will be big loopholes. Therefore, integrity means everything in management.

(4) Effective: The designed management means or procedures and steps should be effective and can achieve the goal. Don't manage for the sake of management, and turn management into something redundant.

(5) Matching with the positioning of enterprises: each enterprise has its own positioning, its own goals, its own products, its own resource richness and its own particularity. The management specification of the design should match this.

3. Standardize the file category and architecture of management.

(1) Procedural document: a standardized and pre-designed workflow described by a document, which generally spans multiple posts and departments and runs through the whole process of one thing.

(2) Operation documents: standardized and pre-designed steps described by documents, generally consisting of multiple actions. Is it part of the program or the details?

(3) Table: The table used in the process of program operation is not only the guide and carrier of operation, but also the record carrier of process information.

(4) Administrative system: It forces and constrains people's behavior, and stipulates what people can do, what they should do, what they can't do, and the punishment that illegal systems should receive.

(5) Target document: a document describing the target, implementation steps, evaluation methods, process records, etc.

4. Management norms for special events.

Principle (1): Exceptions are rare and accidental. Generally, there is no document to specify how to do it, but when dealing with it, we must follow a principle, that is, "power and responsibility are consistent, and advantages are sought and disadvantages are avoided."

(2) Similar powers and responsibilities: every exception will have an impact. Generally, which department will be affected will be handled by leaders with equal powers and responsibilities. If it affects the production department, it will be handled by the production department manager, and if it affects the whole factory, it will be handled by the general manager. If the leader cannot determine the scope of its influence, the incident will be pushed to a higher level for further handling.

(3) Seek advantages and avoid disadvantages: when dealing with exceptional events, we should deal with them in a direction that is beneficial to the enterprise, not in a direction that is harmful or unfavorable to the enterprise.

(4) Disposal: If you encounter an exception outside the file system, you should immediately know the whole state of the matter, and then evaluate whether it is within your own authority. If not, you should report to the superior leader. Until the disposal is completed by leaders with similar powers and responsibilities.

(5) Report: After the disposal of abnormal events is completed, the disposer shall report the situation to the superior leader.