I think that the definition of intuitive in terms of training is a good one. Should it be in terms of _extra_ training?
To clarify, suppose that someone is designing something, e.g. some software, that it's known will be used only by professional musicians. The designer could create something with an interface that uses musical concepts e.g. a musical score. This would be great for musicians - they would just be using something with which they are already familiar.
However, non-musicians using the software would be left cold - they'd have to learn the musical concept and then how to use the software. So, what's intuitive to the musicians isn't to non-musicians. Should the designer create an interface that doesn't rely on musical knowledge so that non-musicians can use it, even if it makes it _less_ intuitive to the musicians?
I think that the definition of intuitive in terms of training is a good one. Should it be in terms of _extra_ training?
To clarify, suppose that someone is designing something, e.g. some software, that it's known will be used only by professional musicians. The designer could create something with an interface that uses musical concepts e.g. a musical score. This would be great for musicians - they would just be using something with which they are already familiar.
However, non-musicians using the software would be left cold - they'd have to learn the musical concept and then how to use the software. So, what's intuitive to the musicians isn't to non-musicians. Should the designer create an interface that doesn't rely on musical knowledge so that non-musicians can use it, even if it makes it _less_ intuitive to the musicians?
Posted by: Bob Salmon | Wednesday, 21 March 2007 at 12:59 PM