No, no,no. Our factory girl appeared today.
Imagined product works
After detailed data analysis, user research and demand analysis, N user requirements are finally summarized, and after careful value evaluation, product requirements are output, connecting all business parties and partners, and everyone hits it off and advances quickly.
Actual product work
Eight of the ten needs are what the boss should do, not only to convince himself to do it, but also to do it well and produce reasonable value. After 180 rounds of pressure and efforts with partners. If the progress is slow and the online effect is not good, the boss will question "your ability is not good"
Imagined product works
R&D, the test and operation are your younger brother. As the core members of the project, everyone will think in one place, work hard in one place, make up for each other's needs, make the needs perfect, and do them quickly and well.
Actual product work
Project extension, looking for products; The function is not easy to use, looking for products; Have users consult and find products; There are problems on the Internet, and it's all the fault of the product. Kill the product, sacrifice to heaven, and all problems will be solved.
Imagined product works
Doing data analysis, writing documents, drinking coffee, urging project members to make progress and chatting on WeChat every day, the perfect day has passed.
Actual product work
Eight meetings a day, ten hours of meetings, all business parties take turns to make efforts, you have your schedule, I have my priority, no one will obey, no one will let go. In the dead of night, you can finally discredit and write a demand, and you will be "destroyed". I can only go home and fight with my computer on my back until dawn.
Imagined product works
At the time of reporting, the project data performance exceeded expectations, the value was clear, the boss valued it, and the promotion and salary increase were upgraded all the way.
Actual product work
Of the ten projects in a year, eight have sunk into the sea, and many others have failed. Various partners complain that the existence of products is a waste of people and money. Fortunately, a project has produced results, which is also due to the good guidance of the boss, the good design of the development architecture and the good operation strategy. Product? What is the use of the microphone in the product?
Haha, after listening to the above, if you think it is acceptable, then congratulations, you are a real product person with a strong heart, which is the most important element of the product. Don't be nervous, just follow the trend, and you will encounter scenes at work, imaginary and actual. As the product ability becomes stronger and stronger, the experience becomes richer and richer, the parties become more familiar, and life will develop more and more imaginatively (if you know how to handle things and relationships, you won't hide under the covers and cry in the dead of night).
In addition to the above "follow the trend and laugh at yourself", I have several suggestions for Xiaobai who wants to switch to product manager. For example, it is very important to cultivate the basic knowledge of products from 0 to 1
For example, in my daily meeting, I was responsible for the iteration and optimization of three versions of the product, and went through the whole process of product design/development/testing/online, switching back and forth in a refined state every day:
1. 1 version online stage: online demand follow-up, and a demand pool collates data &; Feedback regression iteration optimization
2. The second edition is under development. Test stage: attached table 1. Communicate product details with RD, copy and sort out buried points.
3. Version 3 is in the design stage: requirements investigation-MRD compiles the details of an interactive communication product-requirements review.
As an old social worker, my job needs to connect N roles, such as communicating with students of R&D/ design/operation/testing/customer service/products. At first, I was very uncomfortable and had some social deaths. Now I can take over and communicate well. I found that while doing my job well, 80% of my work is docking, which are two situations I often face and my shallow thinking.
RD said I couldn't meet this demand.
1) clarify the real meaning behind it: I really can't/can't or can't do it.
2) The root cause of the phenomenon: technology/schedule/time cost/development/difficulty/expectation/benefit.
3) When there is a dispute, give a solution quickly.
4) In essence, how to make RD do more: keep the same relationship/interests.
Interaction: I think this requirement is well designed:
1) How to answer the approval idea?
2) What's the answer if you don't agree with this idea?
Of course, the premise of not being argued is to improve your product ability, so you still have a lot of room for improvement.
Disadvantages:
1) keep exhaustive thinking: when writing MRD, logic should exhaust mutual exclusion and think of the most complete solution.
2) Prioritize things: According to the matching roles and subsequent versions, arrange the things to be done every week and make a table.
3) Do a good job in project management: the promotion of requirements needs the cooperation of multiple roles, and discharge the ddl of the docking roles according to their own ddl to avoid delaying their own affairs.
4) Reporting key nodes: periodically feed back the status of important nodes, and timely feed back the intermediate status for long-term requirements to prevent thinking deviation.
In fact, I said so much, mainly to tell you not to deify any work. Capitalists are not fools and will not pay you much more than the value of your work to hire you. There are ups and downs in life, and the most important thing is to go uphill forever ~