Why do people complain more about application interface, navigation and interaction about application where they have to provide information?
It's simple requirement understanding, demand vs seek vs provide.
Seek: when end users are seeking information from any application they are more tolerant about the interface and interaction and therefore less demanding on other aspect. They see value in the information provided and are generally tolerant about UI and characteristic.
Provide: end users are more demanding about UI, navigation and other aspect as they have to provide information in the system, this process tends to have less attention span and make the user impatient about the whole activity and this tend to make the user demand more to be done in less time. User would be willing to wait and can tolerate inaccuracies with UI and Navigations issues for "seek" type while there expectations are complete opposite for "provide". Once the requirement are classified into seek and provide the application design can accommodate the balance and can utilize this classification.
The next one is "Demand", this is the case were the user is looking for information but this is more of a demand on the software to provide the information, this classification need a performance oriented and better navigational characteristic, user would not wait for the information, as the "demand" indicated this information should be available as fast as possible with a simple UI.
Examples are system reports: most of the run time reports are "demand", while most of the dashboard reports are "seek" while almost all of the entry screen are "provide". This simple classification helps in design the software and user experience better.
Seek: when end users are seeking information from any application they are more tolerant about the interface and interaction and therefore less demanding on other aspect. They see value in the information provided and are generally tolerant about UI and characteristic.
Provide: end users are more demanding about UI, navigation and other aspect as they have to provide information in the system, this process tends to have less attention span and make the user impatient about the whole activity and this tend to make the user demand more to be done in less time. User would be willing to wait and can tolerate inaccuracies with UI and Navigations issues for "seek" type while there expectations are complete opposite for "provide". Once the requirement are classified into seek and provide the application design can accommodate the balance and can utilize this classification.
The next one is "Demand", this is the case were the user is looking for information but this is more of a demand on the software to provide the information, this classification need a performance oriented and better navigational characteristic, user would not wait for the information, as the "demand" indicated this information should be available as fast as possible with a simple UI.
Examples are system reports: most of the run time reports are "demand", while most of the dashboard reports are "seek" while almost all of the entry screen are "provide". This simple classification helps in design the software and user experience better.
