Don’t show more options than necessary ... but ensure that if more options are needed, they are available.
Coe-Truman is an organization that has successfully catered to many of the most prominent associations in the science, technology, and medical space. We have unquestionably created some great, industry-leading features in our software. Nevertheless, there are, at times, conflicting opinions about how a certain feature should be implemented. This can lead to a tug-of-war of sorts if we are not careful … a proverbial case of catering to one set of demand, only to backtrack and try to appease another set of related (but different) demands, later. A successful way to manage this effect in a SaaS (Software as a Solution) system is to ensure that there is careful consideration for doing only what is essential and universally valuable in any given region of our software. This is not to say that extended, specialized features cannot also exist. This is to say that no single user should ever be confused by a particular feature-set they have arrived at in our software. Quite simply, if more options become necessary, they should be available if they are carefully planned. The location of their availability should be situated in a separate, focused region of the application that may be arrived at intuitively. Again, even when features exist in a specialized location in the application, there should be careful consideration for doing only what is essential and universally valuable in that region … even when the request seems complicated.
Coe-Truman is an organization that has successfully catered to many of the most prominent associations in the science, technology, and medical space. We have unquestionably created some great, industry-leading features in our software. Nevertheless, there are, at times, conflicting opinions about how a certain feature should be implemented. This can lead to a tug-of-war of sorts if we are not careful … a proverbial case of catering to one set of demand, only to backtrack and try to appease another set of related (but different) demands, later. A successful way to manage this effect in a SaaS (Software as a Solution) system is to ensure that there is careful consideration for doing only what is essential and universally valuable in any given region of our software. This is not to say that extended, specialized features cannot also exist. This is to say that no single user should ever be confused by a particular feature-set they have arrived at in our software. Quite simply, if more options become necessary, they should be available if they are carefully planned. The location of their availability should be situated in a separate, focused region of the application that may be arrived at intuitively. Again, even when features exist in a specialized location in the application, there should be careful consideration for doing only what is essential and universally valuable in that region … even when the request seems complicated.
No comments:
Post a Comment