Why product managers and designers make prototype design in different ways?
Product managers and designers somehow make prototypes in different ways.What are the differences and what effects do they have on the product in the end? How can they cooperate?
Generally, we have a clear and reasonable division of labor at work according to the different forms of products. In most cases, a product manager is mainly responsible for user needs management, planning, function screening, business model, business model exploration, iteration time planning, agile development and function point description.
As for web-end products, there won’t be many things about interaction. In addition, Product managers understand the functions very well. As a result, a product manager who is good at prototyping is definitely capable of making prototypes that facilitates the understanding of function points by the developers and also the time to communicate with the interaction designers. This helps a lot to improve the work efficiency.
As for mobile products, interaction design matters more. Product managers will encounter difficulties when trying to make interaction effects in details because they need to make a plan about various function points. The best choice is to have interaction designer to do the interactions in detail so that the product managers can focus on function planning. Although it takes some communication costs, the optimized interaction details will then reach a more professional level of user experience.
In summary, the difference between the product-manager-made prototypes and interaction-designer-made ones is the description of the details of the interaction and it depends on the complexity of the product to some extent. By the way, product managers should never stop improving theirs ability of understanding interaction, technology and even UI aesthetic to deal with more complex and acute accidents.
How to cooperate?
The first thing that product managers should do is make a mind-map. After the brainstorm, product managers can optimize the mind-map and draw the first sketch. You can Mockplus (Rapid Prototyping Tool) to make the medium-fidelity prototype. In his prototype, you need to list out the function points one by one. You don’t have to mention the details of the interaction details for they can be discussed later with the interaction designers. Be patient to explain every function points to the interaction designers clearly.
When the interaction designers understand the functions, they will begin to design the prototype according to their professional perception. As a product manager, I believe the soul of the product is built by the interaction designers and front-end designers.
When the prototype is finished, the product managers should voluntarily talk to the interaction designers to see if there is anything needs to be fixed. For specific functional details, product managers and the interaction designers should communicate to meet an agreement. After it is all done, you can handle the job to UI designers and programmers.
The enthusiasm of the product manager matters most in the whole process.
If the product manager is Steve Jobs, will he do the interaction design in a row?
In my opinion, the biggest advantage of Steve was that he understood and even mastered the detail of every product, and as a stubborn guy, he had faith in foreseeing the future of the product. Nearly all his subordinates are elites, so it’s not his job to do the interaction designs. However, as a leader, he is really special and he will directly tell designers the interaction they just made are shits. It is tough to understand him at first. But now I think it might be the secret of constantly improving a product.
Original site: zhihu
Original link: https://www.zhihu.com/question/19890069/answer/159...