Version 1 (modified by sauermann, 10 years ago) (diff)


Group Management

a DesignRationale.

In SMEs, we have found that people play certain roles regarding their work. These can be IT administrator, product manager, developer, instructor, or managing director. In another dimension, employees are a member of a group. For example, being in the sales department or technical department or product development.

Alltogether, in small enterprises, the roles overlap and there are typically only very few groups. For example, the founder of a company is typcially in many roles at the beginning and later leaves roles. In a company with 15 employees, there may be only 1-3 distinguishable groups. When employees are on holiday, colleagues switch into a different role and group to compensate. Communication happens now inside the group, between people of the same role, and also across group boundaries.

The question is now - how can OrganiK support communication needs that take advantage of group and role structures? Our current approach is: it should not and it can't. Communication can be modeled topic-based. The important fact is that people who need information about a certain topic need to be informed about it. The topic can be their role, their group, or a certain customer or work practice. Tags (represented in the SemanticApi) are enough to model these topics. A purely tag-based modeling of information can be used to simulate groups and roles by tagging information elements with the group or role tag.