Forum Posts

Rojoni akter
Aug 03, 2022
In Welcome to the Forum
If the first two tricks are learned well, then it should not be difficult for R&D to take over the demand. However, during the review process, you may challenge email list the solution for this requirement. This may be because your plan is ill-considered, such as: Follow your feelings, a plan based entirely on your feelings Designers make plans, they can design how they want The scheme is very cool, but it does not consider feasibility and workload at all The required plan will be directly related to the investment of resources and the final data. Therefore, all product children's shoes, you must be responsible for the plan you got at the review meeting. You must not just take a plan and evaluate it. We must treat the plan. Be as cautious as choosing a marriage partner! There are thousands of plans, and nothing is necessarily right or wrong. The most important thing is to let everyone feel at the meeting that you are serious and responsible for your needs (or the same as marriage), rather than letting others think of you. Just take a set of plans and come out to fool people. Here are some tips for your reference: When making demands, you must do more research on competing products, ponder their design ideas, and compare their pros and cons. If possible, it is best to output a competitive product analysis report and display it at the meeting (if you can't do a competitive product report, you can click this ), so that everyone can be convinced. For large projects with high priority, from prototype to interaction to vision, try to output as many schemes as possible, and compare the advantages and disadvantages. At the meeting, we can show the finalized plan, but if there are alternatives before, when asked "why it is designed this way", the answer will be more confident, rather than blank. Avoid overdesigning. The manuscripts reviewed at the review meeting may be made by interaction designers or visual designers. Excellent designers tend to have more "romantic" and "artistic" ideas, or hope to be perfect. But this often consumes a large amount of work, so sometimes we can privately show the manuscript to R&D. If the workload is too large, we can cruelly reject the designer and suggest (beg) them to simplify the plan~ The same is true for some more complex product solutions. If you get the requirements for review at the meeting, and finally find that there is no feasibility at all, it will be a waste of effort. So if we have some unsure plan, we can first look for a good R&D to take a private look. If there is no good R&D, then disturb the R&D leader and ask TA to help assign a person~ Of course, these little tips are just icing on the cake. If your "personality" as a product manager is very reliable, the R&D team will naturally trust you and will not raise any big questions about your plan. After all, here On the other hand, you are more professional.
The third measure: take responsibility for the demand plan content media
0
0
2
 

Rojoni akter

More actions