What are some good habits for product managers?

Why do some friends find that after 1 or 2 years of becoming product managers (http://www.maiziedu.com/course/pm/), they find that they have not grown much or have entered a bottleneck and are unable to improve their technical capabilities. The problems that arise are specifically reflected in these situations: I know some points in product design, but when it comes to implementation, I can't connect these points well. I have done a lot of competitive product analysis and accumulated some materials, but I always feel that there is a problem in the product design. When I was using it, I couldn't use it. I felt that I knew the business logic very well, but when I actually encountered it, I couldn't accurately describe the problem. All of this confused me. Looking back now, I feel that there are a few habits that need PM: Special attention.

1: Form your own unique product design methodology
Collect and organize several mainstream methods of product design (http://www.maiziedu.com/course/pm/115-1118), find a method system that suits you, use actual projects to verify whether it is really suitable for you, and then continuously optimize and iterate This system breaks down the workflow, identifies key steps, and uses repeated practice to form its own unique methodology to thoroughly master these key points.
For example, when I am working on a gold buyback project, I am also constantly establishing, optimizing and iterating a set of backend system design methodologies, such as

Confirm business flow

Find key nodes

Build a business model (abstract business description)

User stories

Establish a conceptual model (a conceptual structure that reflects information needs, such as user permissions role table, UML diagram)

Logical model (prototype, document, field table)

These processes are the process of forming your own methodology

2: stay hungry stay foolish
I need to constantly maintain a strong thirst for knowledge and always have a humble attitude. Every month I will review my behavior during this period. I often feel that I am ignorant and arrogant. I always think that I have mastered most of the product design theories, and I am constantly Practice, so the mentality has expanded, unable to see one's own shortcomings, and magnifying one's own advantages. This is very fatal, because it will lead to complacency and loss of a calm and objective mentality.
Whenever I feel that I have this tendency, I will find some experts to ask if they have had the same experience and ask for their opinions. In terms of product design, since there are wheels, don’t go through it again yourself. , see how they handle it, and then keep alerting yourself.

3: Don’t do it just because competing products do it
​ ​ Continuing to tell a story, I remember that when I was working on Jinshengbao gold price reminder, I researched many trading apps. Finally, someone asked why it was designed like this. At that time, I answered without thinking: Because competing products are also designed in this way. I observed in the background that this kind of scene also happens in our team. Why is it designed like this? Because XXX, which ranks number one in the industry, is also designed in this way. Looking back now, it's so ridiculous.
This reminds me of my participation in the Chaos Research Society in April. Chen Erdong, the current engineering director of Twitter, said that Facebook conducted an A/B test on the homepage at that time, and then XX directly copied version A. As a result, FB used version B based on the data. The other party was very embarrassed. .
What I want to emphasize is, think more about why others do what they do (what the essence is). When you don’t understand why it is designed like this, stop and think clearly. The superficial appearance of what others do is not the reason why we must do it. , is competitive product research useful? Of course it is useful, because it will allow you to abstract some common rules, find differences, and conduct in-depth analysis based on business advantages, product features, user characteristics, and usage scenarios. When you do in-depth analysis, you will come up with some things that make you feel very Surprising conclusion.

This topic was reviewed and approved by Xiaobei on 2016-5-18 10:39