Business process carding and process, we should pay more attention to the rationality of business development in the process of combing business processes, because we must establish a clear understanding in all links in order to develop better. The following is business process combing and process sharing.
Business process carding and process 1 business process carding steps
First of all, by sorting out responsibilities, determine the process structure and directory.
By combing the responsibilities, the corresponding relationship between process and responsibility is determined, which lays a solid foundation for the following process description and process optimization. Through systematic comparison, the problems (such as missing, overlapping, etc.) in the responsibilities of various departments are found, which makes up for the possible process omissions in the process of decomposing the corresponding processes through responsibilities and provides opportunities for improving the responsibility system. Through system comparison, the problems of the system itself (such as system missing, outdated, etc.) are found.
Second, describe the process through job interviews.
In the process description stage, the main problem is the serious lack of systematicness, which mainly relies on branch processes to describe the division of labor in mining, and unique business processes describe the existing workflow. At this stage, the process descriptor is required to have a good sense of process control and risk management and a strong ability to summarize.
Thirdly, realize process optimization through process diagnosis.
System is an important basis and foundation for process diagnosis and optimization. Audit the process according to the system, find the inconsistency between the process and the system, identify opportunities for improvement or optimization, and give full play to the synergistic effect between the process system and the system management system.
Cross-departmental review of the process, review and improvement of various management systems, process diagnosis combined with control requirements and widely used process diagnosis technology, and process optimization according to the diagnosis results.
In the process optimization work, we should examine the process under the framework of the overall architecture, not only to ensure the integrity and smoothness of the process, but also to pay attention to the connection between the work steps of the process.
Technical means related to process diagnosis and optimization mainly include:
Process structure analysis, process link analysis, process node analysis, process management analysis, process management work organization
As a special project, process management should concentrate manpower for a period of time, and its main work contents include:
1. Establish the responsibility mechanism of process management. According to the department management responsibilities, define the departments and posts responsible for the process and establish the responsibility mechanism for business process management.
2. Sort out business processes and management systems. Sort out the business process, describe the basic steps, main risks and key control measures of the process, and clarify the rules and regulations.
3. Process modeling and system analysis. The application of business process management information system, the establishment of business process management model, systematic analysis of process elements, improve the main business processes.
4. Standardize business process management documents. In combination with the pilot, coordinate all departments, compile process management documents according to unified specifications, revise and improve rules and regulations, and issue them for implementation after being reviewed and approved according to company regulations.
Business process carding and process 2 1, business process carding
A: Basic knowledge of flow chart;
1, flow chart = process+chart, process is a series of logical relationships (including causality, time sequence, necessary conditions, input and output). The product manager must understand these logical relationships before putting forward the requirements. If it must be summed up in one sentence, "process is a summary of meeting the specific needs of users in a specific situation."
A chart is to present the logical relationship in your mind in the form of a graph, which has the characteristics of graphics and visualization. Because it is a graph, you can take it out and iterate when your logic needs to be modified, just like your version iteration. At the same time, because of the chart, it can be better preached to project members.
B: Why draw a flowchart?
1, help me sort out the logic.
When each of us thinks of a logic, we may not be able to think of all the details of this logic. If we draw a prototype in a hurry, we may do a lot of useless work. At this time, drawing a flowchart can help us sort out our logic. I suggest you draw this process on paper when you start sorting out the logic, because the advantage of doing so is that you can quickly present the logic in your mind on paper and it is convenient to modify it. After you draw it, you can draw it with professional tools and save it.
2, easy to preach and spread
The product manager needs to hold a review meeting and write a PRD document. At this time, if you have a clear flow chart, it is not only convenient for you to explain, but also convenient for you to understand the technology. At the same time, it is convenient for you to insert your own flowchart into the PRD document. When technology forgets the process, look at the process in the document, and you will know what the process is like, so you don't have to come to you repeatedly for confirmation.
3. Optimization iteration
For getting a logic, we may not be able to consider it so comprehensively. At this time, a clear flow chart is also convenient to record and modify.
At the same time, each version of the iterative flowchart may change accordingly. Through the comparative analysis of each version of the flow chart, we can know where the process optimization and product optimization are.
C: flow chart element definition;
Flowchart is a symbolic graphic language with its own specifications. Diamond represents judgment, distance represents specific operation behavior, and the starting point and ending point are represented by rounded corners.
For example:-Flowchart training;
D: Three main flow charts are designed in the product, namely business flow chart, task flow chart and page flow chart;
1, the business flow chart is to describe what those individuals have done under what conditions and what is the relationship between them. It is mainly divided into three aspects: ① Which subjects are involved? (2) what are the tasks of each subject? (3) How to contact all subjects?
It mainly includes which systems or role modules are involved in the process, which stages users use, and finally supplements them according to the user's operation process.
Take the drip behavior as an example:
System module: including front-end and background system; User roles: including user and driver roles.
Use stage: it can be roughly divided into user order stage, drip delivery stage and trip start-stop stage.
Eg- login registration:
For example: easy map software-user order-platform processing and distribution-driver order;
2. The task flow chart usually refers to the specific operation flow chart for determining a fixed entity in the business flow chart, which is usually a simplified version of the business flow chart.
3, page flow chart
Summary: the task flow chart pays attention to the interaction and logical relationship between different systems; The task flow chart focuses on a specific task operation process. For a product, it is particularly important to find the problems existing in the existing process, or to create a flow chart with strict logic and simple operation. The business flow chart combs out the presentation effects of different roles and different states according to the task flow chart, and the page flow chart is the condensed embodiment of the business flow chart.
Business process carding and process 3 1. Whether online or offline, it is necessary to completely restore the existing business processes.
Any business has its established process, whether it is online business or offline business, even if it has not been streamlined before, there must be a corresponding process, which can be expressed in a streamlined way based on the current business situation. In this process, you can't add your own understanding, and you can't draw a flow chart for granted. You must communicate and confirm with the business personnel to restore the actual business process to the greatest extent, otherwise it is easy to ignore the core link.
For example, in the common expense reimbursement process, there will be links of financial accounting audit and financial cashier payment. If we simply add these two links to the process without communicating with accountants, it will easily lead to one-sidedness in business understanding. Some companies have relatively simple business, and one audit is enough; Some businesses are complex and need to be reviewed twice:
Preliminary examination of financial accounting: mainly review the rationality of expense reimbursement items, whether they are within the scope allowed by the company and whether they meet the employee's reimbursement authority, and then submit them to the leader for approval.
Financial accounting audit: mainly audit the compliance of invoices, whether there are false reports, etc. , and then pay the cashier.
If the product function can meet the simple automatic verification of reimbursement items and reimbursement rights, it can be optimized for the first time. But if you don't sort it out, you may not find the points that need to be optimized in the original business process.
2. In the optimization design, besides the characteristics of the Internet, more business scenarios should be considered.
Many times when the Internet is mentioned, a concept called "disintermediation" will pop up, which was particularly popular in previous years. There is nothing wrong with de-intermediation itself. It is indeed the embodiment of the "link" of the Internet, but we should not only consider de-intermediation, but also consider the rationality of the business scenario. So many times, optimizing business processes is not necessarily a reduction link, but also an increase link.
The existence of offline business must have its rationality. Not all businesses can be easily subverted by internet plus. For example, K 12 online education products are difficult to bypass schools, which is determined by the system; It is difficult for online tutoring products to replace offline training institutions in a short time, because parents' knowledge of the Internet has not yet reached a good level of trust.
The business process is the same, and some links are inevitable. Even the same business will lead to different processes because of the different business entry points of each company. Therefore, it can't be optimized by normal business process design, and it needs to be combined with the actual needs of the business, unless you can push the business change according to the process you set.
Take the refund-only process (not involving returns) as an example. The simple business process is: user application-merchant review. As for the two links, the buyer can revise and resubmit according to the results of the business review, but we can't just consider this business scenario when optimizing the business process.
A. If the merchant keeps refusing, will the buyer keep revising and resubmitting? Obviously unreasonable, so buyers need to apply for platform intervention;
B, the buyer does not choose the platform to intervene, that is, it is constantly resubmitted, which is obviously unreasonable, so the merchant must also apply for platform intervention;
C. If the buyer applies for a partial refund, what about the remaining money or goods? This should consider the difference between applications before and after delivery;
D, ~ ~ ~ and so on, there are some other scenes to consider.
This will gradually improve the whole business process, not based on simple business realization, but aiming at the realization of business scenarios. The following flow chart is for reference, not perfect, and not suitable for all business processes that only refund.
When defining and designing the operation process, it is necessary to consider the user's operation scenarios and habits, and pay attention to the following points:
1, try to reduce the cognitive cost and learning cost of users, reduce the complexity of operation and improve the friendliness of operation.
In the description and guidance of copywriting, according to the characteristics of target users, we should reduce the use of technical terms and use vernacular descriptions, and pay attention to users' browsing habits and acceptance of common layouts and typesetting. Many established design methods can be adopted directly. To design a new operation method completely, it is necessary to consider the learning cost and acceptance of users.
Try to ensure that every operation has clear feedback, whether it is clicking or sliding, and clear result feedback will make users feel that the operation process is friendly. This point is often mentioned in many feedback designs and is also an important part of interaction design. Registration process and other commonly used account password information to fill in, the corresponding format requires that verification must be designed in the operation process.
2. For operations involving document status change, we should pay attention to the related influence and business control before and after the change.
Documents refer to similar orders, return orders, exchange orders, application forms, etc. These documents will circulate in the system, and the process of circulation will involve the change of document state, and each change of state is caused by user operation. In this case, first, we should consider the changes before and after the operation; Second, we should consider the related influence after the status change to see if it will affect other documents or business changes.
It generally involves the operation process of state change. In addition to defining the operation flow, there is also a state flow chart, which is the pre-position and post-position of each state change of a single document, and clearly defines the relationship between each state and the necessary factors of state change.
Process design can make you have a clear understanding of the business and user operation process, so that there will be no leakage of requirements and pages when designing functions. Moreover, it can make the product manager know the business more thoroughly, and it doesn't take too much time to sort out the business. If you start drawing the prototype directly, it is easy to miss the page, and it is not easy for others to understand your prototype.
At this point, the conceptual design, functional design and process design have all been explained. These three links are the process of rationalizing the realization of requirements on the basis of requirements analysis, which can make product managers have a clear outline of requirements, and then begin to refine them. As product managers, many small partners will ignore these three links and start drawing prototypes directly after receiving the demand. No matter how good the prototype design skills are, if you don't understand the business, you will eventually become a prototype drawing machine, and your growth and promotion will be slower.
In the early stage of accumulating experience and cultivating the ability to make products, you should do every link well. When you are proficient, you will find that your analytical ability will improve rapidly and naturally grow faster.