Designer and product manager who is important

The product/design circle often has a discussion of whether it is important to the designer or important to the product manager.

The product manager will think that the product functions are theirs, and even some interactions are drawn by them. The designer just draws the picture again.

The designer believes that the product manager’s own logic is unclear, and the designers help him sort through the process, analyze the user, and then output high-quality design drawings.

After working for a while, I found that the importance should be sorted as follows:

Product Managers who are proficient in business and experience > Designers who are proficient in business and experience > Product managers who are proficient in business experience > Proficient in designing unskilled designers > Product managers or designers who are not proficient

Therefore, it does not exist which position is necessarily more important. What is important is who is more proficient.

Let’s use a common product manager as a reference to demonstrate the scenarios in which different levels of designers communicate with the same product manager.

1. Weak Designer VS Product Manager

The most junior designer, who is a drawing tool, does not think deeply and lead.

PM: We have to do a blah blah blah function, you need a mockup here. This is roughly the case, put three tabs, respectively blah blah blah, and then the content is blah blah blah.

Designer: Ok. [Nod agree, then start to immerse yourself in the picture, into the infinite details]

|
[Draw a good picture to PM]
|

PM: I didn’t tell you clearly. This should be like this. I have to modify it. The process over there is refined, add a blah blah blah.

Designer: Ok. [Follow the changes, occasionally some design questions will be raised, but most of them are just the buttons to put the left or right, the big size or the small point.]

|
[Modified to PM, PM took it to development, found some problems in the development process]
|

PM: Sorry, we found some problems when we developed them. We need to modify them again. This is blah blah blah.

Designer: Oh, ok. [Follow the revision, there is no way, development can not be done only compromise]

|
[I don’t know what to do after the final draft, I don’t know what the online product development is, I don’t know how the user is using it.]

2. Ordinary Designer VS Product Manager

Ordinary designers will follow the process to produce a good design.

PM: We have to do a blah blah blah function, you need a mockup here. This is roughly the case, put three tabs, respectively blah blah blah, and then the content is blah blah blah.

Designer: Ok, but you shouldn’t put three tabs. These three parts are not too many. You can merge them into one page and separate them with the title, because each page will lose some users, and the tabs will be converted. Relatively low.

PM: Well, it makes sense, then you can say it.

Designer: Well, ok. [Silly, then immersed in drawing]

|
[Draw a good picture to PM]
|

PM: I didn’t tell you clearly, the business logic has been revised, here is a fine-tuning, blah blah blah.

Designer: Ok. However, this logic is a bit complicated. We can split it into several steps, let ordinary users go through the normal process, and users who need advanced operations give complex interfaces. What do you think?

PM: Yes, yes, I am bothering you.

Designer: Nothing. [buried picture]

|
[Modified to PM, PM took it to development, found some problems in the development process]
|

PM: Sorry, we found some problems when we developed them. We need to modify them again. This is blah blah blah.

Designer: Oh, ok. [Some technical issues can be compromised, and some have to push the technology to achieve full functionality]

|
[After finalizing, wait until the product is tested before going online, go to the development to do design verification]

3. Powerful Designer VS Product Manager

A powerful designer will grasp the demand and lead the design, rather than being led by the product manager.

PM: We have to do a blah blah blah function, you need a mockup here. This is roughly the case, put three tabs, respectively… [interrupted by designer]

Designer: Wait a minute, you first tell me what the background of the project is and what the goal is. [Master background information]
PM: Oh, we found through this research that the user has not met the requirements. This product iteration needs to add this function. In the future, we will enrich the functions and make our products become a platform of blah blah blah.

Designer:OK。

PM: So we mainly do blah blah blah this function, mainly let the user to blah blah blah, need to add a button on a certain page, click to perform blah blah blah operation.

Designer: Yes. So what we want to achieve in this issue is to add a blah blah blah editing and display area, users can use blah blah blah, the goal is to increase the number of users, let our products become a platform-level product. [Refining and summarizing the content of PM’s over-detailed content into the content of the strategic layer, ensuring that the strategic layer is correct, and then forgetting the details of the PM, and re-deriving the information structure and interaction of the page from the strategic layer]

PM: That’s right. Can you see if you can put a button here and click on the blah blah blah operation?

Designer: Actually, our problem is not simply adding a button. You see, we have to complete the leap from tool-based products to platform-based products. We need to strengthen the blah blah blah function and weaken the blah blah blah function. This page can be used with this. Make an integration and then take this feature out.

PM: Well, it makes sense, then change it as you said.

Designer: Ok. [Start drawing, confirm communication many times before finalizing]

|
[Draw a good picture to PM]
|

PM: Ok, thank you. [No modification or minor modification]

|
[Product manager took it to development and found some problems in the development process]
|

PM: Sorry, we found some problems when we developed them. We need to modify them again. This is blah blah blah.

Designer: Oh, then we changed to this kind of solution, which can reduce the development cost and avoid the current technical problems. [In-depth understanding of technology implementation]

|
[After finalizing, design verification before the product goes online, and often pay attention to data performance and user feedback after the product goes online]

4. More powerful designers VS Product Manager

Grasp the final demand and push back the product realization.

Designer: We found that users have such a need, want to launch such a design, you can help us push it.

PM: Ok.

—— End ——

—————————————–

I am Baoling, an unrestricted designer.

If you like my article, please forward it to your friends. Also welcome to follow my WeChat public account BaolingUX