Let’s talk about the process of the project from 0 to 1

As the saying goes, there are more projects and more problems. Products are used to solve problems. So what problems will you encounter during the project? Write them down and record those routines. I also hope to communicate with you and tell you how you solve them.

1. Early stage of the project --- product (strategic level) planning, demand collection stage

In the early stage of a product, there is generally a demand collection stage. So where do the demands come from? The sources of demand include those proposed by the leadership, user opinions from the business department, operation department, customer service department, etc., and those proposed by people inside and outside the company. Adjustments that need to be made through data analysis, adjustments to the basic framework at the product business level, product reconstruction, etc. are all sources of demand. In this process, many problems will be faced. First, the demands proposed by the leadership. The demands of the leadership often have two directions.

[[207267]]

One is the general direction of what function to make or what kind of platform to make. Another direction is that the process at the interaction layer is not smooth, the color is not good, the button position is not good, and so on. We internally call it "fine-tuning requirements" hahahaha. For me, the general direction of adjustment will generally follow the leadership. Because the leadership knows the forefront of the industry best. Even if the leadership makes the wrong decision, we have to follow it. Because we also have to try and make mistakes. Keep trying this market. For the other direction, I usually go back and quietly collect data to analyze which ones can be improved by version and iteration step by step. Secondly, the requirements put forward by the business department are always from their own perspective, or they can't say for sure, just look at what others are doing in the market and we want what we want.

You can't figure out whether this is suitable for the current development of your company, and you can't wait to use the function I told you today tomorrow. You said that you are a product coordinator, what do you do? Then you have to have the ability to control and judge the overall situation. You have to judge what can be done and what cannot be done. There are other needs such as the operation department, customer service department, etc. You have to distinguish the project levels according to the company's strategic needs, project needs, and product needs. Let me talk about the general project classification of 5 levels, which is enough.

2. Product design stage---prototype design, business process diagram design

During the design phase, the product needs prototype and business, and the product flow chart are produced. This process is a process of repeated communication, confirmation, and adjustment. Disputes will arise in this process. This function is not what I want, it is not right here, it should not be done this way, all of which are problems. At this time, you need to have enough product experience, a lot of similar product thinking, and have seen the practices of similar products on the market. For example, the business wants this function but it is not complicated to do and it is difficult to do. What should I do? Is there another way? Take a practical example. Our customer return visit system wants to return a customer in a few days. I want to return the customer again after two or three days. I want an automatic prompt. After my own analysis, the customer management system on the market actually needs a return visit plan list function to solve it.

3. The demand prototype is basically determined. The following is the design of the interaction level of the visual draft

At this stage, I will have some debates with the designer about opinions and practices. If conditions permit, I can do user research and A/B testing. If there is data support, I can do it according to the data results. In fact, I have always been a "you say you have your reasons, the woman has her reasons" when it comes to design and interaction. The best thing is to listen to the user's opinions.

4. After the high-fidelity prototype is produced, it is the development stage

At this stage, you need to have PRD documents and high-fidelity prototypes to communicate with developers and explain the requirements. At this stage, developers need to evaluate what kind of technical framework and technical language these requirements should adopt. What if you encounter a problem that this function cannot be done, is difficult to do, or takes a long time to implement? As a product, you need to promote and make the product.

First of all, you should have some knowledge of technical knowledge. Before the demand review meeting, you should first examine whether the function logic is reasonable and whether the function really needs to be changed. During the demand review meeting, when everyone is looking at your business process diagram, product framework diagram, and demand prototype, use a third-party tone to narrate the requirements and learn to tell stories. Never say that I think this function is very simple, and have less personal subjective consciousness. Use more data support and user opinions to lead the demand. Some product managers who come from development backgrounds are prone to make such mistakes. You can you do IT, right?

5. Project testing phase---testing by professional testers and testing by all staff

The product will also encounter some problems in the testing phase. Sometimes the requirements will change during the testing phase, which is the most troublesome thing. It will also be encountered during the development process. Especially the changes in requirements encountered during the development process, these requirements should be treated in two parts. See which requirements can be added if the development progress permits, and which major changes cannot be added. Can they be added in the next iteration?

At this time, we should carefully review the early demand research, user research, visual design, and interaction. Have we done user research? If there are mistakes in the research process, it means that the early direction is wrong. Generally, do not add big requirements in the testing phase, otherwise the project will be in a state of endless modification. It is better to go online early to verify the requirements and make further iterations and improvements.

At this stage, you will encounter some problems, such as what to do if the effect does not meet the actual needs, which will make you angry. Pay attention to node control and node quality assessment and acceptance during the project process. Avoid entering the next stage of the project in an out-of-control state, otherwise the project will be in an awkward situation of not knowing when it can be launched.

6. After the project is launched, the product has entered the user use stage

Some products do not conduct user demand research in the early stage. Some users of the products will give feedback that the process path is not right, bugs, etc. Pay attention to collecting user feedback and data indicator feedback. Some product functions have been added, but the user usage rate is not high, and users cannot be more activated. Then we have to reflect whether the entrance is too deep and users are not easy to find. Or the threshold is set too high. Make timely adjustments. Written in *** Projects are not only full of problems. As the person in charge of the product, you have to face all kinds of problems and know a little bit about all kinds of skills.

Be good at coordination and communication. Look at and describe problems from an objective perspective. There is no problem that cannot be solved. Talk it out, don't be too picky. It's all for work. It's all from the same pot. If something goes wrong, you have to deal with it alone. It's just that as a product, you are just a representative. If something goes wrong, you will bear it. If there is glory, it belongs to the team. It's not just you. In the process of product project development, you will face various problems. Only by thinking about various problems in advance, we have to talk about risk point management in the project development process. I won't talk about this this time. If there is a problem, we will solve it. Don't talk about other things.