Editor's Guide: Newcomers who have just entered the industry will always encounter such a situation: although they have considered comprehensively, they will always encounter various problems during development. When drawing prototypes, many usage scenarios are often missed. How should we improve them? We discussed this issue with our friends at Tiantianwen, let's see what they have to say~
As a product manager, you are business email list either drawing prototypes or on the road to drawing prototypes.
As a newcomer, you will always encounter this situation:
After drawing the prototype and reviewing it, I thought there was no problem, but when it came to front-end and back-end development, there would still be various problems or some situations that I didn’t expect.
Why is this happening? Is it my own incompetence or is it normal? What needs to be improved?
In response to this question, we started a discussion at Tiantian. Let's see what our friends have to say~
1. Start with yourself
After getting the requirements, don't draw the prototype immediately, the first step is to confirm the understanding of the requirements; on the basis of confirming the understanding of the requirements, conduct demand research and competitive product analysis, complete the competitive product analysis and required research, and then draw a function list and business flow chart , and draw the prototype at the end; the prototype is the last step and a very important one, and you can't rush for success.
Whether the product requirements document is considered comprehensively will directly affect the subsequent development progress and the effect of implementation.