The stronger the function, the better?

The stronger the function, the better.

In the laboratory LIMs system, because of the personalization difference, it is very difficult to train a fixed "product". In the process of gradually improving the product, with the demand of more and more customers, but also because of the need for market promotion, each family is emphasizing my function more and more powerful. Of course, this is also when we are dealing with this matter, the original attitude, or unconsciously was pulled to this line. There is always a constant increase in functionality that attempts to take into account various possibilities. For example: The following figure is in 2005, we are in the old LIMs version of the partial background settings page, then adopted the C/s architecture.

Market people like this kind of things, which makes him more confident. Can confidently tell the customer: My function is very powerful.

The customer might also like something like this, and he would feel: my money seems to be worth the comparison. At least it looks like so many features. Note: This is also just a background setting, with each set item changing, and the combination of changes resulting in more possibilities. And the functional differences of the foreground. 】

Powerful and better. When we were designing a new generation of lab LIMs, the project team was rethinking the issue. Of course, one of the basic ideas of reflection is: the idea of agile development. Everyone is affected by the 37Single. As for the right and wrong, and whether it should be used in the field of software such as LIMs, that is another topic.

It's not powerful. Perhaps, for example: For most features a customer is not used, he needs to pay for it. For inexperienced system administrators, it is estimated that he is dizzy when looking at these tabs, increased training costs for administrators and users, increased training costs for project implementation engineers, and a team of Test members who worked hard, but let him try to exhaust these combinations, test and verify that it is no problem, the workload can be imagined, A slight negligence bug must be saved, the project group to the later maintenance code is more and more difficult ... Wait a minute.

Another point of view, the function is not enough "powerful", or say the function is relatively single. Can you sell the product? Will the customer buy it.

We try to find a balance between "powerful" and "concise", which is one of the most painful problems encountered by the project team. Of course, we want our customers to be able to perceive our efforts in our new generation B/S version of the lab LIMs system. It should be more concise and easier to use, while maintaining the necessary functionality. Perhaps, we need a lot of "black box".

Do you have any good ideas?