For example: after the product design is completed and after entering the development, you may encounter technical questions about why you want to develop this function, can you combine several functions into one whatsapp database function and so on. If you can’t go back to the business scenario, go back to the scenario where the user uses the product, and can’t answer and communicate questions from the perspective of the user’s usage whatsapp database scenario, then in many cases, communication will be unsmooth and product advancement will be blocked. 2.
Think back to the beginning We often say that in the process of specific work, product managers often spend more time thinking than drawing prototypes and writing documents, which is a more reasonable time allocation. Thinking about whatsapp database what? There are a lot of things to think about, but one of them must be very important, that is: go back to the scene, go back to the origin to think, think about what kind of problem the user whatsapp database has encountered and what problem needs to be solved in what scenario, not based on the business scenario.
The needs of the people are all imaginary needs behind closed doors. In other words: the business scenario is the origin of the product's downward design. If this work is not done well, the products designed later may have little use value. 3. Thinking in the whole scene, so that the needs are not missed If we say that when we analyze the whatsapp database scene and find the demand, we think about where is where, instead of thinking from the overall framework. It is easy to cause omissions in demand, and the product cannot form a whatsapp database closed loop. Since the sorting out of business scenarios is so important, what should be done? Here, I will talk about the following 5 aspects: