Become a good product manager: Let go of the function

Article Description: Product managers, please put some of the features on your hands.

If you want to be an incompetent product manager, publish all of your features immediately. Immediately show all the cool features you have on hand to the world. The only thing you need to do is to be as quick as possible and publish as much as you can. Because when the user first uses the product, if cannot see all function, we will have the possibility to lose these users. While some feature users don't really care, users will be happy to sift through the extra features that they think are valuable.

Suppose you have an ambition to be a good product manager, some features can be put aside. When a product is first released, it does make sense to include enough function points, but in the next release, there are reasonable reasons to delay the release of some Non-core features:

1. Users cannot handle and familiarize themselves with too many functions at once. for new products, extremely easy to appear too many function points, users can not focus on the product of the most core functions of the situation. Too much non-core functionality, instead, allows users to shift their focus away from the core functionality of the product. Users are attracted to those unimportant features, ignoring the real added value of the product. Need to know, each additional new function point, must provide a certain amount of time to allow users to adapt and familiar.

2. at the beginning of the product, fewer function points give you a chance to capture more value. Some "blockbuster" products release all of the best feature points at the first release, resulting in continuous upgrades and improvements that are not available during the next iteration of the product. In many cases, a certain range of solutions can be achieved through a phased overlay version. If all of the most valuable features are released in one release, the idea of bringing more product value to the company through price promotion and modular expansion is challenging. On the contrary, only the core function of the 1.0 version, has enough to prove the value of the product and the user's acceptance. This will pave the way for you to build better, more rational product layouts, get more value from users, and make it easier to lock out potential users. With the development of products, the initial "slim" products, for the late function of the increase and price increase to provide more flexibility.

3. Functional phased implementation , the product can be based on market feedback rapid response and on this basis to adjust the new function. In product management, there is a law-tomorrow you will know a lot more than you did yesterday (you always know much tomorrow than you did yesterday). This is like a lot of features that you think are important before the release of the product, and may not be necessary after the release. Retain some of the functionality in the early stages, but also benefit from user feedback. Once users start using and contacting your product, they will not only provide feedback on the product's existing functionality, but more importantly, give feedback on features you don't currently have. Before you think of a very important function, you will find that the user does not feel important. All sorts of "fancy" ideas that you wouldn't expect at all will flow from your users. Based on the real scene of user feedback, help you identify the direction of the product development and modify your product layout. At the same time, you can put more effort into more valuable functions, rather than wasting on a bunch of worthless features.

With the product manager of product function expansion, a product of the future function of reasonable expectations can lay a solid foundation for the development of products. However, product management is a marathon, not a sprint. Product managers need to focus on the overall development and long-term success. In contrast to all the potentially valuable features of a one-time release product, the product manager should provide only core functionality at the first release to market the product as quickly as possible.

Retain part of the function bar! Only in this way, product managers can better establish a convincing product layout, in the development of maintaining a leading position in the market before the change to prepare everything.

PS: For users, they are not using the product, but a problem solution. So what is the core requirement (I prefer to use the term "basic requirements")? Is the use of product subtraction, when any one of the reduced functionality is not enough to allow your products to help users solve the problem, the product has the function is the most basic and indispensable function, that is, the core function. Any product, in fact, should help users to solve their problems in a more efficient and convenient way. When the product has not been able to provide this most essential function, look back at the original product and the original intention, may be able to rediscover and find direction. In fact, in addition to the function needs us to slow down, we also need to learn and the bug to live in peace. Not every bug needs to be resolved immediately, put a bug that is not very serious, do not interrupt the development of the developer constantly, so it will backfire. Finally, maybe lost the watermelon, Penny Wise.