Methodology of big factory: how to draw a perfect business flow chart?

Business flow chart is the most commonly used in product dog work, but it is also the most easily overlooked. The business flow chart is like scrambled eggs with tomatoes in the product industry. Everyone can fry, but not everyone can fry delicious. This paper will interpret how to draw a qualified business flow chart from two aspects.

Everything has a process, just like you fry a dish, you need to buy food, choose vegetables, wash vegetables, stir-fry and plate. For example, if we want to design a user registration function, the path that users need to take is the registration process.

In product design, the business flow chart is a process document, just like the architectural drawings of our building. Product design is process design in simple English. All product requirements must have a flow chart, otherwise problems will easily occur. If you want to be a qualified product manager, you must have the ability to draw a flow chart, so that your ability with R&D PK will be greatly improved when the requirements are reviewed. If there is no problem with your flowchart, there will be no problem with the following page flowcharts, prototypes, requirements documents and requirements review.

First of all, the important thing is: what to do and what is the goal of users coming in?

Second, users: What kind of users will take this process?

Third, information: From beginning to end, how did this data run?

Fourth, how to deal with the problem?

Let me analyze the business flow chart of Netease snail reading login function:

The problem is that the user has to complete the login process, and the goal of his coming in is to log in to Netease snail learning.

Users are old users who want to log in, and new users generally have to go through the registration process.

Information, enter Netease mobile phone account and mobile phone number, enter password or verification code, and finally log in successfully.

What about the abnormality? Enter whether the mobile phone number is 1 1 digit. If not, hint: Please enter the correct mobile phone number. If it is a verification code login, enter the graphic verification code, and the background will judge whether it is correct. If it is not correct, the SMS verification code cannot be obtained. Tip: If it is correct, get the SMS verification code, enter the SMS verification code, and then check whether the SMS verification code is correct. If it is not correct, give a hint.

There are many children's shoes that have just entered the industry, and they like to draw colorful business processes, and the shapes of the flow charts are also varied. For example, a lovely colleague of mine is like this. Asked why she painted it like this, she said, how beautiful it is. Your painting like that is too monotonous (I look calm).

So how to draw a business flow chart in a standardized way? Below I list some common business process symbols and their meanings:

Let's leave now. Netease snail reading-Netease mobile phone account? Taking registration as an example, how to draw a single channel business flow chart.

The first step is to clarify what users need to complete: users need to register with their mobile phone accounts, and the task is to complete the registration process.

The second step is to clarify what is the beginning and what is the end: the beginning is to enter the mobile phone number, and the end is the end.

The third step is to define the sequence of the process, which determines the quality of the user experience: the sequence is to click on Netease mobile phone account-enter verification code-judge whether it has been registered, if not, enter graphic verification code-get mobile phone verification code-enter verification code, and finally register successfully. This is basically a core process.

The fourth step, what exceptions will occur, and what should I do if these exceptions occur? The exception is whether the mobile phone number has been registered and whether it is correct. Whether the graphic verification code is correct. Whether the SMS verification code is correct and expired. There are two different dimensions. If it is wrong, go back to the step of re-filling the verification code. If it expires, get the verification code again.

Step 5: Optimize and adjust your business flow chart: For example, when users click "Netease Mobile Account", do they need to check "Agree to the Terms of Service and Privacy" by default, or do they need to check it themselves? Of course, the default check here is better, which reduces the user's operation steps.

Step six, output your flow chart, combine your own working methods, and output it to a document or prototype or email.

The complicated process is difficult to express clearly, so it is necessary to split the roles here. Swim chart is used to make complex business flow chart, which can highlight the logical relationship between user operation, back-end system and front-end page, and how to operate it.

First, analyze the key logic of the function: see who participates in the function, what role these people play and what they want to do. Different roles have different tasks to complete.

Second, define users and tasks: define all participating users and systems, and the system also acts as a participating role. What is the relationship between these participants, is it a superior-subordinate relationship or an upstream-downstream relationship? What is the ultimate goal of all participants?

Third, clear the starting and ending path: in each functional module, there is generally only one starting and ending. If there are too many endings, it means that users will be dumbfounded. Some functional processes need to distinguish time periods, such as running errands, which are divided into pre-order, in-order and after-order.

Fourth, determine the functional modules and core paths: which functional modules will participate in this process, and the core flow direction in the process must be clear. If the core process is not clear, users will be confused.

Fifth, constantly adjust the order of the optimization flow chart and merge the abnormal flow: consider the abnormal flow clearly and make it as detailed as possible.

6. There is a basis for the merger or split process: first complex, then simple, first addition, then subtraction, sort out everything that can be thought of, and then investigate related products for merger analysis.

1. Flowcharts should be uniform in shape, color and font size, and each flowchart should start and end. There can only be one beginning in a flowchart, and there can be multiple endings, but not more than three.

2. The flow chart should be injected from the left or upper end of the shape, flowed out from the right or lower end, arranged from left to right and from top to bottom, and the connecting lines should not cross.

3. Unless there is a judgment, the arrow of the flowchart cannot have a callback, and each judgment has only two results: Yes and No. ..

Windows system can use: Axure rp9, Visio, Mindjet? MindManager？ 20 19, etc. , you can use MAOS systems: Axure rp9, OmniGraffle 7, My Draw, Edraw, etc. , and some online, such as Process On, MindFlow, AsciiFlow and so on.