8. One size does not fit all

Scenario: Groupware are applications based on an underlying database that attempts to support all the user tasks: mail, calendar, bulletin board, chat, conference, archives etc. The pieces appear to work together well, but at the expense of being optimized to the tasks. They really all act like the underlying database, and not like a task-based product. E-mail inherits the architectural limitations of the database and cannot be optimized to the task without great expense. The user is frustrated by a high learning curve because the metaphor to the real world is broken.

Example(s): Creating micro applets (Java) that work together via a hub program and APIs. Each applet has its own architecture to support its tasks best.

Back to Benefit - Individual and Group Acceptance