Thinking in the workplace--technical thinking on the position of Product Manager (Part I)

Sometimes think, technical special cattle people will always do technology! After all, have been accustomed to their own technical circle. To come out of that circle, to consider the market, the operation, the industry ... A series of questions. It's the equivalent of jumping out of an advantage that you already have and how much you're not accustomed to. But recently, by chatting with some friends, I found out that for the job of product manager. And a more in-depth thinking.

From the market behavior backward inference technology research and development

The people who do the technology pay attention to rigorous, shred gap may affect the performance of the final product. As a product manager, what you have to think about is not just technology. In other words, for the technology, you can ask for details. But for some seemingly perverse market behavior, you can also pour out his technical advantage.

For example, the product manager in the auction analysis, why the other side of the product to use such a strategy to operate its products. For example: low-cost strategy, free strategy, building block package strategy and so on. From these market behaviors, it can be seen that they have a good understanding of the profit point of their own products. The internet era, after the pay and even upfront to hit the money to use the feeling of the utility of many. And if the other party to make such a marketing policy, it is bound to the technical threshold they will have their own insurmountable obstacles. There must be a reason behind what seems to be a more unusual thing.

User Requirements Analysis and product specification development

Technical staff will only consider how to make their own product character to do the best on the OK, but as a product manager to consider is how your product close to the user. In other words, the user's needs can be guided!

In the process of user demand analysis and research, you need to find out what are the core requirements of users? In general, three points is enough.  1, the user is that kind of user, is to B's also to C's user?  2, users will have a lot of demand, to distinguish between those are the most core, which can be guided, and what are the fake requirements? 3, how much do users want to pay for these new needs? The price here can be either time or money.

When you can analyze the above requirements, you can make the relevant product specifications. First of all, product manager if you are the first salesperson of this product. You have a lot of confidence in your product to sell, but your focus is not on sales. It is the continuous iteration after the product is formed.

Does the product manager want to see the customer?

On this issue, I have always understood that is not to see. Because after all, your product has not been formed, from the first-line sales, after-sale, operation and maintenance of the feedback from the problem will be many. More of these problems to statistical analysis, to find the product in favor of their direction. Personally feel that you can, as to say see customers this matter, only when you have the certainty of winning to see better. If you make a bad impression on your first meeting, it will have a big impact on your product's later sales.

Then the customer research, MVP stressed that most of the customer's needs can be guided. and how to use technical methods to express their views, there is how to communicate with customers. In a new era, personal feelings, communication and some things will be better. facilitates early communication. After all, it's a bit too expensive to talk to each other directly for the first time.

From a technical point of view a sort is the technical manager of the project manager of the:ceo> product manager. Product Manager It is better to know a little technology, understand some management, and understand some sales. Continuous learning process, you will also find that the product manager more is to think, think of a good idea, good planning to affect the upper layer to their own resources deployment. When a product manager has a certain technology, it can go down to control the final implementation of the project. It is also possible to avoid products that are out of sync with the original idea.

Well, the above is engaged in Product manager after the technical thinking, this is considered on the bar! Mainly write the main duties, next time write it down! Write a little more about how to communicate with the top leaders and coordinate the resources with other parts. In short, feel new job, new position is more challenging. With their original ideas completely different, is constantly learning, refueling!

This article is from the "Data Mining and Visualization" blog, reproduced please contact the author!

Thinking in the workplace--technical thinking on the position of Product Manager (Part I)