In the previous article, I described what some product managers are doing from the actual work of my own product experience, and also summarized some of the things that product managers should do; but they are all described from the overall direction of product managers, for some work. The details of the process are not elaborated.
In this article, I will share the process of a requirement that I have experienced from being proposed by a customer to the final implementation, and see what a requirement has gone through and finally becomes a function in the product.
This is the flow chart from the country email list proposal to the realization of the requirement I described. We will start the following article based on this flow chart:
After the design of our new version of the operating room anesthesia information system was completed, a tertiary hospital officially launched our system as the first customer. The simple standard operation flow chart of our system is as follows:
During the use, the director of the anesthesiology department put forward an idea for the surgical procedure of the system: "Hopefully we can have a secondary surgery function in addition to this standard surgical procedure, and enable it to identify and record that the patient is a secondary surgery. surgery patients.”
Our system's previous approach to a patient's secondary surgery was to recreate the surgery request and proceed as a new surgery. There will be two surgical records of the patient in the system, both of which exist in the form of independent operations, which will ensure that each surgical procedure is standard.
If the second operation is associated with the first operation, the original standard operation process of the system will be broken. For example, a patient should be in the end of the operation, but the next state is the beginning of the operation; after this requirement is proposed by the director, our The on-site implementation personnel decided that the existing functions could not be used on site to solve the problem, so they reported it to our business department.
2. Demand analysis
After receiving the customer's demand, the business department sent the demand to our product department.
We mainly analyze this demand from three aspects:
Whether the requirement will affect the acceptance of the project;
the client's influence;
the market conditions of the demand;
Through the requirement analysis, it is firstly determined whether the demand response is not responsive and if the response is only for the customer or included in the product standard version.
1. Will the requirement affect the acceptance of the project?
We participated in the meeting of the implementation team to communicate with the customer's needs. During this period, when we mentioned the need for secondary surgery, we once again confirmed with the customer that this situation does exist in the actual business of their hospital, and she mainly wanted to use this function to strengthen the operating room. Management practices for secondary surgery.
We feel that the attitude of hospital management is still very concerned about this demand, which is a strong expectation and will affect customer satisfaction.