Jun 19, 2022
In Welcome to the Food Forum
In the previous article, we talked about the overall plan for designing B-end products from 0 to 1. Interested friends can read my "5000-word long text: B-end products from 0 to 1, product solutions + cases". Today, we continue to talk about detailed solutions and analyze how product managers can develop their own solution capabilities. 1. Structure and main points of the detailed plan category email list The overall plan mainly describes the product value, overall process category email list and structure. On the one hand, it is convenient to report to the senior management of the company and customers; on the other hand, it is also convenient for product managers to understand each other's work and improve the efficiency of communication and collaboration. The detailed plan needs to analyze the needs of each module and clarify the success indicators, and then explain the solution through text descriptions category email list and flow charts, and finally the page design and related logic descriptions . For large B-end products, the detailed solution may need to be broken down to multiple product managers to complete. For a complete detailed category email list plan, the following needs to be included: demand analysis Clear success metrics Program key points Scheme process Prototype Next, we explain one by one. 2. Demand analysis Although we have analyzed the detailed requirements in the business research section. We consider that reasonable requirements are the cornerstone of successful products, and we also consider the need to promise the reliability of category email list requirements to development, testing and other departments. Therefore, we can elaborate on the rationality of the requirements in the detailed scheme. In addition to the description of key requirements, we need category email list to clarify three points: Is it a fake demand? Is the current version required? Is it a personalized requirement? For pseudo-demand, we need to uphold the "spirit of the end" and ask a few more whys. In addition, there are some requirements that may be true requirements, but the value is very low, and needs to be comprehensively considered to evaluate the priority . For example, a customer may wish.