How to become a popular product manager 🌼
Today I saw a super interesting topic, I can not help but be happy ~
In addition to @Zhang SAN at the first time, I can’t help thinking:
As a product manager, how do I not get killed?
Considering that this is a matter of life and death, SO I invited my PM friends, we are all prodigal sons on the same boat, have to find a way together!
After three rounds of pushing and drinking, we finally put together the Product Manager’s Self-Cultivation.
How to become a popular product manager, according to our incomplete statistics, there are three main things to do.
Listen to me slowly:
1. Clear requirements
This first point is definitely the common call of design and development for product managers!
Before identifying requirements, it is important to know that clear requirements must come from a strong insight into users and markets, and that decisions should be made based on solving real problems, not what “they” say they want to do.
And even when you do encounter “they said,” you need to be able to go back and figure out why they said it.
Here brother Dao’s analytical thinking is reliable:
We need to learn to use the RTPA design framework, which is a contrarian hypothesis analysis that teaches us to use the thinking technique of assuming that the initial requirements are all wrong, that the problem doesn’t exist and you need to rediscover the problem. We should not start designing as soon as the demand side asks for a demand. We should ask why and investigate to find out the real problem. — By PMCAFF
Take a simple example: you cook at home every day and then one day your partner says, “Let’s go out to eat tomorrow!” At this point, the thinking of a good product manager is not to ask her: “where to eat?” “But to turn on your own initiative and explore: why do you want to eat out tomorrow? Why eat out? Why tomorrow?
So you see, being a lovable product manager requires not only listening, but also the ability to analyze and solve problems.
Listen to advice and make good decisions. Think twice before you move, indomitably!
Once you do that, your demand is pretty stable. The need not to change easily will create an atmosphere like this:
Second, detailed description
To be universally loved, it’s important to minimize the interaction between development and design at work and use visual, transferable expressions, as the saying goes, “Less talk, more love.”
After all, everyone’s voice goes like this:
-
A: “The most important thing is clarity of need! Define (not blur) exactly what needs to be done!”
-
B: “The product should think of all the details clearly, similar to the product data logic. Please don’t wait for me to find if else don’t know how to write.”
-
C: “Can submit clear, specific and concise documentation, even for small changes.”
-
D: “You’d better write on the prototype.”
☝ Thus, detailed requirements specification is of great importance.
The detailed description of output should mainly pay attention to the following three points:
-
Structured product prototypes
-
Flow chart with clear logic
-
The complete PRD is awesome
As luck would have it, here are three things we agreed on before we got too drunk:
Detailed specification of requirements must be accomplished with the help of efficient product tools.
Open the secret book page 8, on the book: copy RP!
Further down: Fast and efficient, free!
Continue: 👇👇👇
1. Support drawing structural prototype
Compared with some redesigned tools, Copy RP is actually a tool that pays more attention to product page structure and product function logic. After the requirements are determined and the functional modules are subdivided, we build our prototype framework on this basis, so that the produced prototype can reduce the frequency of repeated modification to the maximum extent.
(And what could be more endearing than not changing the requirements, not changing the page?)
2. Efficient prototype drawing method
If the structured prototype is to make the product function logic clearer, the interactive effect preset component, massive ICONS, high degree of freedom editing mode and other functions of Copy RP can help product managers quickly produce detailed hi-fi design draft.
This lightweight design, fast interactive prototyping, and more worthy of trying the operation of gameplay, should try: www.mockplus.cn/rp
Above template comes from: www.mockplus.cn/example/rp/… , click to try it now!
3, can open flow chart mode with one key
When we get to this point, we should do a more detailed business process review of each feature. For example, what validation should be done on the back end when the user completes input and submits. What to do with different inputs, what results to produce from different inputs, what values to return from different results, what pages to display.
All of these are best described by business flow chart + text to ensure logical integrity. A typical flowchart might look something like this:
However, in the prototype design of Copycat RP, a “flow chart” mode is specially provided. Not only can we draw the above business flow chart, but also for our page itself to carry out logical lines and text remarks.
And just click the icon on the left of the upper toolbar, you can open the flow chart mode, avoid new page, content expansion, very portable!
4. PRD documents can be synchronized
When it comes to PRD documents, this is the big one. When we write PRD documents, we usually export the RP design draft and flow chart into pictures and then put them into the document. So even if there are some minor changes in the design draft, you need to re-export the image and then update it to the PRD document.
This approach will directly lead to a surge in the number of teammates’ documents, which will attract people to like it! But if you use copycat’s PRD document function, you can save this troublesome modification step. Because the RP design draft and flow chart in the document can be automatically updated, but also support online review, it is very fragrant!
5. Free forever
If the document synchronization feature above is delicious, this is definitely the number one reason to recommend copycat RP with a conscience. Because it’s free: unlimited functionality, unlimited pages, unlimited duration!
So choose it to have no problem at all, after all, we do products out of the river’s lake, only pay attention to a rule: you do not accept my money, you are my big brother! And with copy RP prototype, a month can save 40 to 50 membership fees, so that we can stand up straight and hand rich to ask the waiter to add wine!
Three, elegant temperament
Please note, “temperament” this point, really not in my skin, but just need! Just need!!!!!
In particular, I’ve heard that in the development community, there’s a saying that goes,
Where does that quality come from? It is definitely not a big gold chain or a small gold watch, but the unique wisdom of our products:
1. Empathy
Empathy helps us better understand others, not just our users, but our teammates. Only by understanding them and identifying with them can you better connect yourself with your teammates, make reasonable schedules and plans, and make products that meet users’ needs.
2. Communication skills
Most of the time, most of the team members don’t understand why we need to do this and what the benefits are. This time we need to draw a big pie to tell the story, we need to tell teammates not only need to “do”, but also need to tell them “why”, let them know the meaning of doing so.
3. Sense of responsibility
By accountability, I don’t mean taking responsibility for your own affairs (because that’s the most basic professionalism). Rather, I mean being able to see problems that others don’t see and start solving them, and being able to reject unreasonable demands from your boss and business to pave the way for a team and a project.
4. Rules
A popular product manager must be big. We should not only have a keen intuition of the product, but also have the quality of humanistic care and a sense of social responsibility.
As we all know the dd take a taxi, even though we can’t deny it has changed our traditional way of travel, but in the process of product development, it from the beginning of the “kill”, no bottom line to suppress the driver and the interests of the users, then broke information leakage problem, makes a valuable product gradually to the collapse of word of mouth.
So if you want to be a popular product manager, you must speak the rules and be afraid. The secret book of the product has said: fear is not afraid to do without virtue, fearless is from its desire and to the disaster!
Last but not least. A good group of red envelopes, usually joking together, eat, share the five blessings, watering watering people, regardless of his development is design or product, who will not like it ~
At the end, how much do you remember?
Left out? Copy guest RP don’t forget!