For product managers, most of the day-to-day revolves around requirements - communicating requirements, implementing them, etc. So for bulk sms service the content of requirements, if you have a correct understanding, I believe it will be of great help to the subsequent implementation. The original intention of writing this article is to combine my methodology with the thinking in the actual project, so that I can sort out my knowledge system when doing the review, and at the same time I can share it with you, and I hope to point out my knowledge system Let's discuss the possible deficiencies in it. (We are a non-profit e-commerce platform. When I give examples, I will avoid some places that involve internal company decisions or privacy secrets) I think it's important bulk sms service to understand what the needs are first? Then where will the demand come from? What to do if you dig your own needs?
How should I record the demand when it comes? How to analyze after recording? How to verify after analysis? How to sort after verification? So my bulk sms service requirements methodology consists of seven parts: understanding of requirements, source of requirements, mining of requirements, recording of requirements, analysis of requirements, verification of requirements, and prioritization of requirements . This article is about understanding, sourcing, mining and documenting requirements An understanding of needs What is demand? There are many dimensions in which requirements can be classified, but I think we should start with the source, that is, from the standpoint, it can be divided into user needs and company needs . The needs we generally refer to bulk sms service are the needs of users , but the needs of the company cannot be ignored. 1. Use the KANO model to understand user needs
According to the KANO model, user needs can be divided into basic needs (pain points: users are conscious) , expected needs (itch points: users bulk sms service may be conscious) , exciting needs (exciting points: users may be unconscious), and indifferent needs, reverse need. (network map, invaded and deleted) A. Basic needs: The functions and services that users think your product should have, and these functions can basically meet their needs; without these functions, user satisfaction will be greatly reduced. B. Expected requirements: Users may not be able to describe in detail, but can roughly imagine what they need, so they hope to provide functions and services; if such requirements are met or performed well, user satisfaction will be significant Increase. C. Excited needs: Users may generally be unaware. At this time, once unexpected functions or services can be bulk sms service provided, surprises can be generated. Mining such needs can greatly improve user satisfaction, thereby increasing user loyalty.