You can split the tasks on the desktop/system into four major roles.
The Four Major Roles User : Desktop as tools and occasional barriers to getting things done Admin : Providing support and maintaining the system Builder: Collects, selects, bundles, customizes and installs/deploys. Developer: Creates/Hacks software.
It is also possible to classify the approach people take in performing each of the four roles.
The Four Classes of approach. Casual : Intermittent, Beginning, or busy/lazy users. Everyday : General day to day users Power : Customize and Automate Guru : In depth knowledge and command line shortcuts
It is obvious that some people perform more than one role and can approach each role as a differing class of approach, based upon their knowledge and desire. It is also obvious that each has different requirements and that attempting to force any user interface which does not match that person's approach is going to irritate them and become a barrier to adoption for the user.
While it is possible to up skill, if it's not a direct requirement of their employment, most people consider it a hassle not worth the effort. Microsoft's approach has been to further dumb down the builder,admin and developer user interfaces, which irritates many everyday, power and guru users.
A truly successful Linux/Open Source/Free desktop environment would continue to provide multiple *synchronized* user interfaces for each of the four roles targeting each individual approach.
For the role of user, this could mean bolting on to applications Druid/Wizard walk though for casual users to proving scripting interfaces for power users and command line UIs for gurus. The desktop environment could start the application on everyday mode by default and let the end user switch interfaces.
Automation Over Time Demands Consistent Interfaces
Both power and gurus need long term consistent interfaces for customization and automation. Microsoft introduces entirely new API/scripting interfaces with almost each release of MS Office, a "feature" which drives many Microsoft Office power users nuts.
Learn about Linux
Download Linux
Get Linux help
Casual, Everyday, Power and Guru users
Posted by: David Mohring on January 05, 2004 05:42 PMUser Interface Target Matrix
You can split the tasks on the desktop/system into four major roles.
The Four Major Roles
User : Desktop as tools and occasional barriers to getting things done
Admin : Providing support and maintaining the system
Builder: Collects, selects, bundles, customizes and installs/deploys.
Developer: Creates/Hacks software.
It is also possible to classify the approach people take in performing each of the four roles.
The Four Classes of approach.
Casual : Intermittent, Beginning, or busy/lazy users.
Everyday : General day to day users
Power : Customize and Automate
Guru : In depth knowledge and command line shortcuts
It is obvious that some people perform more than one role and can approach each role as a differing class of approach, based upon their knowledge and desire. It is also obvious that each has different requirements and that attempting to force any user interface which does not match that person's approach is going to irritate them and become a barrier to adoption for the user.
While it is possible to up skill, if it's not a direct requirement of their employment, most people consider it a hassle not worth the effort. Microsoft's approach has been to further dumb down the builder,admin and developer user interfaces, which irritates many everyday, power and guru users.
A truly successful Linux/Open Source/Free desktop environment would continue to provide multiple *synchronized* user interfaces for each of the four roles targeting each individual approach.
For the role of user, this could mean bolting on to applications Druid/Wizard walk though for casual users to proving scripting interfaces for power users and command line UIs for gurus. The desktop environment could start the application on everyday mode by default and let the end user switch interfaces.
Automation Over Time Demands Consistent Interfaces
Both power and gurus need long term consistent interfaces for customization and automation. Microsoft introduces entirely new API/scripting interfaces with almost each release of MS Office, a "feature" which drives many Microsoft Office power users nuts.
#