The question of prioritization of requirements is bound to be asked every time a product manager is recruited, and one of the answer keywords we hear the most must be the guy ROI, so how to quantify and reasonably evaluate this indicator Woolen cloth? bulk sms service Hope this article can give you some ideas. Excluding the company's strategic adjustment needs and online emergency bugs (bugs that affect users' use of core processes), let's talk about the controllable requirement prioritization of B-side product managers . Around the sorting of all these needs, there is no other, it is the evaluation of ROI, whichever has the highest return on investment, which one should be done first. Influencing factors Now, let's take a look at the factors that need to be considered in total: 1. In terms of bulk sms service investment Development cost (usually available) The solution design and development implementation cost to achieve this requirement are still relatively easy to estimate.
As long as there is an approximate solution design, an experienced development person in charge can still better estimate the approximate development bulk sms service cost (person/day). Purchase cost (if any) Some iterations or products need to cooperate with third parties, then this part involves docking and procurement, and the risk and cost of this part must also be taken into account. In fact, if you consider it rigorously, in addition to these input costs, you also need to consider the cost of training and promotion, but this is generally difficult to measure, and the impact is generally small, so I won't discuss it too much here. Taken together, the above is the input cost of a requirement or bulk sms service iteration. 2. In terms of income Customer benefit analysis (or type of demand): The solution to this demand is a new function that solves a real problem for the customer (it was impossible to do it before, but it is now done).
Or is it an improvement requirement, such as optimization of interaction and adjustment of the underlying architecture to help customers use the product bulk sms service more friendly. For B-end customers, experience is important, but more customers are willing to pay for functions. After all, function points are listed in the purchase contract by point. Number of users affected (number of feedback): How many users are affected by this demand? How often is the feedback? How many people need him? Of course, the importance of the customer to the company must also be considered here. For example, some large customers may be the only one who has raised a certain bulk sms service demand, but because the company attaches great importance to the customer, the priority of the demand naturally tops. Frequency of use of the function: After the requirements are realized, how often is the function used?