As a product manager, how to conceive an APP?
How to conceive an app", the more specific question should be "how to discover a need and conceive a solution for the product as an app".
The specific strategy is to make bold assumptions, Be careful to verify.
What is a bold assumption?
First of all, you must have a keen eye to discover the needs and pain points, and discover the pain points of certain groups of people by observing life.
If you find it, do you have an idea for a subversive solution? If your idea is just "better", then I suggest it. Think again, or give up this field and find other needs. You know, what can beat Rising Antivirus is not better Rising Antivirus, but free 360 Antivirus; what can beat Nokia is not a camera with higher pixels. , a faster Nokia with a flashier casing, but an all-around revolutionary iPhone
OK, now you find a real need, and your idea is "different", not better. , then you can list the needs, existing pain points and your solutions together. Then communicate in detail with your peers and peers and simply verify it with common sense.
At this time, you may find out. There is something subtly inappropriate about your solution (if you don't feel this way, maybe you believe in yourself too much). Thinking more deeply, it is actually because it contains some assumptions, some unverified assumptions.
For example, when conceiving Momo’s idea, Tang Yan must have considered the following assumptions:
Young people (target group) all have a need to meet strangers.
p>Young people (target group) show their photos and other information to strangers and feel safe
Young people are more willing to communicate with strangers nearby, thereby leading to relationships. Offline.
When Tang Yan thinks about these issues, he first starts from himself. Assuming that these premises are confirmed, the Momo product can be built.
How to verify carefully?
After you put forward some hypotheses, you can conduct some small-scale interviews to directly find your target users and communicate directly. If your ideas are verified, you can go further. Conduct a larger-scale questionnaire survey.
Remember, you cannot deliberately lead users to lean towards your plan at this time, or take it for granted that your assumptions are the reality. Otherwise, you will not be able to do so until you build the product. It turns out that none of the assumptions are valid, your so-called painful pain points are just itches, and the rigid needs you mentioned are all false needs.
If you can do this step seriously, objective investigation of the target audience. A statistical result shows that more than 60% of the results are in favor of your original idea, which preliminarily verifies your hypothesis.
Then you can continue to the next step and think about whether this product can be best implemented with an App solution. :
Many people I have contacted want to make whatever product they conceive into an App, without thinking about whether App is the best way to implement the product, or a trial and error method.
What usage scenarios is the App suitable for?
Application environments with high performance requirements.
High frequency startup and usage requirements.
Applications with complex interactive logic.
Those with low network requirements, or using apps that can significantly reduce data usage.
The cost of making an app is many times different from that of making a mobile website. I saw someone say that he wanted to make an app for repairing water pipes and connecting toilets. The most obvious problem is the second one. I may not use an O2O app for repairing water pipes and toilets once a year, so why should I install an app that may not be activated more than once a year?
Nowadays, there are so many implementation solutions, and WeChat public accounts can already solve many problems. Why do we still need to write apps for two platforms?
If you have examined these questions and think you still want to make an App,
If you are the boss, then think about the following points:
Market analysis. Think about whether this market can support the growth of your product, and who are the current competitors in this market. In what ways can your product cut into the edge of this market? After all, the success rate of edge attacks is 37%, while the success rate of frontal assault is only 6%.
Business model. How will your product make money in the future? Do you want to think about whether you will fall into the Moji Weather style cycle of "trying your best to be a user, but ultimately unable to monetize"?
Promote. You work hard and finally release an app. If it doesn't become a hit, then you have only achieved 10% of the product. So how to promote it next? Is it a Meituan that needs to become popular to grow, or is it a force-promoting Meituan that can generate value by spending money to buy users? So if it's the latter, are there enough funds to promote this App? In the final analysis, it depends on whether this industry and this product are driven by creativity or money, and whether your team has enough relevant resources to complete the project.
If you have thought through all the issues, please gather your strength to complete the first version of your App as soon as possible.
If you are a PM under your boss, you need to write a BRD (Business Requirement Document) on the above issues to convince him.
As for how to draw a prototype, first use paper to draw a sketch, then use Axure to refine it, and do some interaction, and that’s it. Don’t do some fancy high-fidelity.