There is a very common situation here, that is, the requirements raised by some implementations are very simple. It is simply described in one sentence. This situation is generally understood by yourself based on experience. In fact, I don't recommend job function email list that product managers directly reject the need for a sentence. They must have their own thinking process. job function email list Then you can find the implementation for confirmation. If you don't understand it correctly, you need to clarify the requirements with the implementation again. Judging the rationality of demand is also a large part of my work.
Some hospitals have more individual job function email list needs. For us to do SAAS product model, we must consider whether the demand is reasonable. Otherwise, it is of little significance to create a function that is only used by one hospital. If it is a reasonable requirement, it is also necessary to consider whether to add configuration items. Because different hospitals have different scales and management, they can respond with different configuration items. The configuration items job function email list are also very particular. Whether it is for user configuration or hospital configuration depends on the scene. If the hospital needs unified management, it should be placed in the hospital configuration.
If it is based on the operating habits of different users, it should be configured according to the user. 3. My daily work - design scheme When designing a job function email list system, there will often be a variety of solutions. At this time, the optimal solution must be selected. The optimal solution must be able to meet the needs of customers and at the same time the cost is the job function email list smallest. Sometimes, in order to express, product managers will have complex designs and complicate simple problems. We try to avoid this, and many product managers advocate designing a feature with full consideration for future extensions.