Recently, I feel that it has changed from technical management to product management , Or innovative products . however , How to make product innovation is a new knowledge for me , It is necessary to study deeply . This paper is mainly about flag, Record some personal immature ideas , As the basis of follow-up study notes .

in my opinion , Product innovation can apply the logic of scientific research ,“ Bold assumption , Careful proof ”, This paper is also my hypothesis of product innovation methodology .

Product innovation can be divided into the following four steps ：

1. Found that demand

Product innovation must first find demand , No matter what you feel , It was put forward by others . But the demand here is vague , And maybe it's just an example .

2. Demand assumption

First, sort out the requirements , Form clear demand assumptions .

Then infer the scope of the target user , That is, identify which users have this demand , This is also a hypothesis .

And then , Think about the value of this requirement to target users ？ The value of products depends on the value created by products for users . This is the third hypothesis .

Last , Think about how to achieve this requirement , What preconditions are there , What assumptions need to be tested .

It should be noted that the assumptions of requirements should be clear , The hole should be small .

3. Hypothesis testing

Hypothesis verification can have three levels .

3.1. Ask for hypothesis testing

The first level of hypothesis testing is to ask for , You can collect information from the Internet , You can also collect data through research and other means , Also include 1 Yes 1 User research .

Generally, the first requirement verification should be hypothesis verification in this form , Revise the hypothesis after verification , And form new hypotheses .2-3.1 The process may cycle many times .

3.2. Roadshow hypothesis verification

The second level of hypothesis verification is roadshow , It's a bit like 1 Yes 1 User research , The difference is that it goes with the product plan . The result of hypothesis verification is the continuous revision of assumptions and schemes . If you want to make a big correction to the hypothesis , You can go back to 2-3.1 Go in the cycle of .

3.3. MVP Formal hypothesis verification

The third level of hypothesis verification is product promotion , That is to make the product directly , To the market for verification . Hypothesis verification at this level especially requires that the gap of hypothesis should be small . That's what I understand MVP. If the promotion is not ideal , It may also need to be added to 2 To correct the hypothesis , Restart the whole process , But more is the revision at the product level - The cycle to market .

4. Demand landing

The implementation of demand can also be divided into two levels .

4.1. Scheme level landing

The first level is the scheme level , It usually happens in 3.1 and 3.2 Between . If 3.1 The verification is basically consistent with the hypothesis , Then you can enter the scheme level landing , Then take the scheme as the material to verify the roadshow hypothesis . Of course , Sometimes you can skip 3.1, also 4.1-3.2 The process may also be repeated .

4.2. Product level landing

The second level of landing is product level landing , It usually happens in 4.1 and 3.3 Between . When the scheme has undergone multiple rounds of verification and is basically mature , Product level landing can be carried out based on the scheme , Then you can go to 4.2 and 3.3 And back and forth , Keep pushing forward . If R & D efficiency is particularly high , The user base is very large , You can also skip 3.2 and 4.1.