The timeline can be divided into quarters, but there are basically certain mistakes in what to do in each quarter. The first half is from a business perspective. Starting, the second half is from the perspective of platform construction. Of course, product planning is not something that can be explained in a few simple sentences. Generally speaking, product planning is to make the product go on with goals and paths in the future, and product planning will also follow the market. Changes are constantly adjusting. When doing product planning, we also need to weigh the resources at hand. For the above-mentioned product, these three steps are taken together.
There is a team of 180 people, and basically all of them come up in a month, but if you only have a few people or A team of more than a dozen people cannot cover all the scenes at once. Another product planning is not only to split requirements to complete within the planning time, but also to require certain KPIs or OKRs. For the production and research team, the KPI is more likely to be the realization of how many business requirements are completed, and the results. But as a product manager not only to do product design, but also to have certain Phone Number List requirements for business indicators. In this product, it is the offline team that actually generates value.
What the online product needs to do is to 'open source and reduce expenditure'. 'Open source' refers to optimizing service processes, improving user experience, increasing brand influence, retaining users' stickiness, and 'saving expenditure'. 'It is to improve personnel efficiency and reduce construction costs. demand analysis At this point, we need to conduct a more detailed demand analysis. Lao Wang intends to conduct some analysis on the user applet as an example. As for the other parts, let's turn it over for a while. After all, this is just a chestnut. It's really time-consuming to say that one person analyzes and designs it all.