When I originally made the outline, I named this part of the content as "My Product Methodology" at first. After sorting it out, I feel that it is not worthy of being called a methodology. It can only be said to be a review of some experiences, skills and working methods. A summary is email list made from eight aspects: business needs analysis, user research, needs analysis management, product design, project promotion, product iteration, team management, and learning methods.
In the product from 0 to 1, the product manager should first contact the concept of a business prototype. At this time, a standard business model has not been formed, and our team does not know what to do next. What we need to do is an analysis of business models and business needs.
Although the business model and business direction should be considered more by the boss, I think that as a product manager, you should have a basic business sense, and at least be able to judge how a business model makes money.
The business prototype I mentioned here is also the most primitive demand prototype and the first stage of demand analysis.
Enterprises need to deeply cultivate a field, and so do people. You have been in a certain industry for a long time, you are an expert, you can find some problems and form a business prototype.
Of course, the objective condition of industry experience is difficult to achieve with shortcuts or methodologies. It can only be learned, practiced, and accumulated. But interest is different, there are ways to quickly accumulate.
QQ groups and Tieba are good things. As long as you can think of it, no matter how weird the crowd is, you can find it in it. Then what needs to be done is to know more, interact more, and participate more in activities.
②The collision of brainstorming ideas
Many people resent frequent meetings and nonsense. However, product managers must not be disgusted. They have a wider range of hobbies and more nonsense. Many good ideas are often pulled out of nonsense.