Users only feel your services through software, so the best service is the most important thing.
Software (functions and forms) that are separated from services is useless. It is better to introduce the service to introduce the software. Software is part of the service. Software serves industrial needs. Services can directly bring value to users. You may need to arrange and combine the functions to obtain the service. Functions are not directly oriented, and services are not directly valuable, so they are not the ultimate goal. "What can I do with this ?", Users often ask this question. "What can we do" should be directly presented to users. If the user does not directly feel it, it means that the service is not attached to the user.
Before that, the value that the service can bring to users also needs to be carefully determined. The previous question "What can I do with this" applies the service as "this" and is also applicable. The answer should be value. Whether this value is important to users can also ask this question again.
If you can make sense three times, it is reasonable. (Whether it works well or not. Sometimes it requires a considerable review, and perhaps an iteration and exploration phase .)
Should a service be hidden behind the value? It should not be reversed. A service has some value in it.
[Principle] the software as a whole must clearly reflect as much fundamental value as possible. The service is in the form and is encapsulated by the software itself. The function is used to encapsulate components supporting services and should not be directly presented to users. For users, services are positive (UI), values are overcast, and functions are invisible. OK.
When users cannot do anything, they have to make a decision. The more direct the better.
Each software should be clearly analyzed and defined in terms of its functions, services, and values. Then check whether the above principles are met. [Analysis Method] Ask a question, give an answer, and then judge the answer: 1. What value does it bring to the user? 2. What services do users want to feel? 3. Can these services reflect those values? 4. Compare the actual situation (or assumptions) to determine whether (1) the service is properly expressed? Whether the user feels these services. (2) Are there any unnecessary services or services that are missing or not expressed? (3) are functions directly presented to users? (UI)
※Functions are often abstract results, rather than services directly felt by users, and are not the final value of users. Therefore, do not consider functions as services or values. When analyzing user values, do not enter the abstract stage at will, which is easy to mislead the function. Remember, as long as the user value analysis is clear, everything else is a matter of course.
