Truly reliable product action from the forefront of the user needs

Article Description: listening to the voice of the user, basically is that part of the very likes of active feedback problem minority. Just listen to the general. Allow irreplaceable technical resources to address the functionality that most users need. As to how to determine whether certain feedback is a big demand, the product manager's ability problem.

Long time no serious summary of recent product experience. Accumulated a lot of themes, all in the high intensity of the work of the rhythm of the grinding lost. Even the book does not look lazy people, if you do not form a summary of the habit, the TMD finished, it becomes a product manager of the garbage products.

It's over. 1: Careful use of design methods to solve the problem of demand.

After discovering the problems in the product, the role of the product manager should at least be to find out the needs behind these problems and translate it to everyone and ourselves. The role of interaction designer, should be based on the requirements of the interpretation and measurement of the problem, put forward the corresponding solution. But what is the real situation? Sometimes, the project is tight, there is no condition and time to do complete user research or testing, several people together to make a decision, a few people who pat the head are not reliable. Sometimes, the demand is ambiguous, the competition product analysis several other product's practice, then parody, several is taken to analyze the product is not reliable.

None of this is advisable. It is advisable, either, to eventually convince yourself of 100% reasons, or to make a quick trial mistake in a low-cost, low coupling way. To clear follow-up, can not be confused online.

There is a misconception that you should not be fooled by the seemingly still-good design. If the demand is not clear, and then the appropriate design, but also a trap, resulting in more and more function to do one of the traps.

2: Don't waste too much energy on a few users.

Listening to the voice of the user, basically is that part of the very likes of active feedback problem minority. Just listen to the general. Allow irreplaceable technical resources to address the functionality that most users need. As to how to determine whether certain feedback is a big demand, the product manager's ability problem.

The Problem 3: Don't forget the core experience because of the flashy features .

If it is a mailbox, NB and the capacity of the network disk function, also can not be compared with the speed of mailbox. If it is an album, and then NB of the album template, can not compare to upload speed pictures. First of all, the core experience to achieve the ultimate, do not be competing products gaudy auxiliary function to frighten.

The problem 4: data is sometimes not so important.

If it is not the electricity dealer or Tens user quantity product, cannot take the data to influence oneself and the team's product movement. A qualified product manager with good knowledge of demand should have basic judgment, from product experience and intuitive sense of the field to a relatively simple product at the beginning of development. The data should play its proper role.

5: Do not ignore the technical backbone of the product recommendations.

Although the technical male looks basically to be in front of own computer, the muddle-through Pats the code. But the reliable technology, the most solution of the product behind the data structure and implementation logic. When a product manager translates requirements into functions and submits them to development, it is most likely to save time costs and reduce the risk of implementation, and is a discussion with technology. Discuss how new features fit into existing logic, and whether or not to expand new requirements in the future. Often have a bright technical advice, make the function more logical aesthetic, more economical to achieve cost.

In other words, knowing more technology and developing technical thinking, product managers are more likely to be NB and reliable. I particularly enjoy the process of discussing the way the technology is implemented with the engineers.

It's over. 6: The nature of the operating-driven product

Truly reliable product movements, from the forefront of the user needs. Users need not rely on the user to shout out, is to someone to soak in the user to find the line. The product manager has to do the job and run it. A person who runs away from operations and only functions, is basically an interactive designer.

Shameless said, this work can only be done by product managers, pure editing, operation, and can not be extracted from the operation and translation of the reliable demand, a mess of 1.0 of media, portal products is a typical counter example.

Overall, the product manager is not Superman, can not escape so many traps, overcome so many problems. So a product group, a few tacit understanding of the product together, more secure.