How to build a great product 7-Product Mission verification method

Product Mission Verification method

Assuming that you can now use your established product intuition to apply the "three bucket model" to your industry, you can easily (and correctly) classify the function points into different barrels, and you are already better than most product managers. But that's not enough. You need to know that this method is actually flawed in some way:

• If you are simply classifying functional points by a speculative intuition, you will easily be persuaded by the rhetoric of another voice in your mind to make the right decision after making a mistake.
• When you build the product, you are bound to hands every big and small decision, because others simply have nothing to guide them.
• Your siege Lions will be frustrated because they will assume that your decision to speculate is unfounded.
• Before the product comes out you will need a lot of other people to help you-journalists, investors, potential employees, and customers. It will be very difficult to persuade these people, because the decisions you make are intuitive.

A good way to solve these problems is to define your product mission. You can think of it as a function that accepts a function point as a parameter and then returns a value that is one of the three casks. The definition of a good function must be concise, readable, and reusable. Ideally, after reading this product mission, most members of your team will be able to classify function points into the corresponding barrels as you would.

Here's what we think of as a productive, humorous product mission definition for RETHINKDB:

Database Tools should be the same as Magic
Provide developers with the coveted development tools to help them build real-time and data-driven Web applications to surprise and wonder. And to create a great software PRODUCT process to bring pure interest and simplification.

On the surface, these two sentences actually seem to be saying nothing, but if you dig deeper, this product mission is actually full of information. It tells people that what we're building is a database product; It tells people that we first treat the product as a development tool, which eases the tensions between developer-related features (such as the query language of the database) and functions related to software operation (such as monitoring). Be aware that all of our gamechagners levels of functionality revolve around solving developers ' problems. We consider the function point of the database how to run the function as showstopper level. The mission of this product resolves our expectations of how users should use RETHINKDB (which is used to build real-time, data-driven network applications). This product mission also gives you an idea of how much we can achieve (surprise and magic) for a particular feature. It's not enough for developers to be good enough. These people spend a lot of time on our products every day-we need to make them feel good in the process. The product's mission also implies that we will accept more complex implementations to make life easier for our users. It leads us to the ability for developers to write new, rather than already existing, applications. It has a sense of self and embodies a healthy sense of humor that we have as a team. This gives the public a general understanding of what kind of team we are.

With this product mission, we can use it to verify the various feature points proposed. On top of that, with some team-sharing knowledge, our team members are able to classify function points independently in a broadly consistent way.

It took us three years to figure out what kind of plane we were doing before thinking about the product's mission. If we were to define this mission on the first day, our development time could be half-reduced, maybe more. When you build a product, the product mission should be the first thing you need to fix. If you have a mental model that is good enough to write a product mission that will inspire all of your company, other things will naturally be solved.

——— finished ———-

English Original: http://www.defmacro.org/2013/09/26/products.html
Make/Translator: Slava akhmechet/Heaven Zhuhai Branch Rudder
Public Number: Techgogogo
Csdn:http://blog.csdn.net/zhubaitian

How to build a great product 7-Product Mission verification method