Why can't designers design what product managers want?

The most common and acute contradiction between the product manager and the designer is that the designer puts the article that has spent a lot of effort in front of the product manager. After reading the product, I feel very unfamiliar and beyond expectation, said: "What is this ".

. Not to mention who is right or who is wrong, but it is very hard, but why is it always so embarrassing.

The best cooperation in the world is actually your hands and your head. How do you think about your head, how do you paint your hands, and the ugly old man Ding also feels very kind. Grace is my good work (Star eyes ). It will be a little troublesome when two people work together. Because, let the "designer's hand" be precisely controlled by the "Product Manager's head". Every time I finish drawing a picture, I feel that it is unrealistic to adjust the agility when I continue to draw or make mistakes.

The downside is that some communications have many drawbacks. Only by solving these problems can the team sing in harmony."Same dream".

 

I. products do not realize that what we want to talk about is actually a story.

A common product manager can directly write "add a repost button on the feed" in the requirement document to indicate the reason for reprinting ". This method of description is actually a concrete solution. Then, this document containing dozens of requirements described in this way will be posted to the internal requirement management website or sent to the designer via email.

Designers often find this document quite wrong. Ah, I can't help it. I want to save money for disaster recovery. Then take the requirement document and modify it on the existing interface. However, we often find that there are many conflicts in details about these specific solutions. As a result, the designer first needs to reverse yy the user requirements behind this function, and then tries to find a new solution in the cracks that do not conflict with various details. Show this article to the product, and the product will be stunned and say "What is this ...". (--#),(--')

In fact, many product managers have not figured out their biggest value points. As a product manager, what should be done most is to discover the various requirements that users do not know how to meet in their lives, and then entrust these challenging and valuable user needs to the resource team to help solve the problem.This requirement should be expressed in a life-like and story-telling manner as much as possible, and has nothing to do with any specific solutions.This wayDesigners can clearly understand what problems they want to solve, and the design has a starting point. It is also the starting point given by the product manager.. Therefore, the baton delivered by the product manager is a good story to express the user's difficulties.

The core content of a story should include: <what kind of people> <under what circumstances> <what needs to be met>

 

2. text is not the best way to tell stories

Everyone has heard of the joke that "buy a pound of Steamed Stuffed bun after work. If you see watermelon, buy one. When a product uses words to express its own ideas, a lot of information will be distorted. When the designer receives these words, he will reverse the idea of the product. What he imagined is another story.

Both the back of napkin and frog Collective Action Toolkit provide a more expressive way to tell stories. Such as drafts, cartoons, and videos can all be used to express user needs. This is more efficient than text, and the probability of misunderstanding is also low.

We often say that this text is very graphic, but I think not all product managers can write this text, why don't I use a picture to tell a story directly? :) I will not write it, either of which is correct.

 

3. Designers did not confirm their understanding as early as possible

The designer has taken the holy promise from the product manager, but there is also a risk point, that is, he thinks he understands the will of the product adult, but it is not all at all. The best way isDesigners can immediately repeat their understanding in a language or more visual way to the product manager.. Otherwise, you will buy a steamed stuffed bun after you meet the watermelon seller.

What a designer is best at is to embody abstract things. Now that you have such a skill, you can also draw a picture in person rather than rush back to your seat immediately. Here, you can demonstrate how users can solve their needs in the future. You can understand the product immediately. The best way to keep your eyes on the wrong path is to open your eyes as soon as possible and make sure you are in the big direction.

 

4. design has not released multiple designs

The product manager said that he had used both learning and singing, told a good story, and set a precise starting point for the next design. The following shows the designer's face.

What is the most effective solution for a user's pain points, in fact, it is very confused (point to the competitor's product interface and say "I just want a page like this", so let's not talk about it ). This requires the designer to be able to think differently and try to explore various promising methods. In this way, there may be more innovative breakthroughs.

In fact, product managers are under a lot of pressure. They want to bet on their own career prospects to ask investors for manpower (well, designers and engineers) material resources to realize an unknown dream. If a designer can code out a batch of solutions and tell the product manager which one you want to pick and which one you want to see is the best, it will undoubtedly help the product manager improve his/her confidence ).

I hope this article will help our product managers and designers have less quarrel with each other. We are one of the best.