As Semantic Web technologies are geared towards representing metadata, they are also ideal for supporting the user for instance with personalized interfaces that adapt to contextual information, interests or job profiles.
As a user-centred system, it is vital that KiWi considers all of the following five aspects:

1. Role:
   KiWi reflects the role of the user, i.e. the position within a team (company, organisation, …), and the tasks for which the user accepts responsibility as well as the knowledge that she has, as this, too, is decisive for the roles she is able to accept.
2. Domain:
   KiWi is reflective of different domains, i.e. different fields of knowledge and of the concepts and relationships of the concepts that are relevant to a given domain. KiWi does, however, not limit itself to categories and concepts, but is also designed in a way that it is able to adapt to the styles of knowledge presentation and communication within a given domain. Lab reports, for instance, are a highly structured type of documentation used in chemistry and mechatronics; executive summaries rely on prose and rhetoric rather than on obvious structure and are typically used in business.
3. Context:
   Context is king in any form of successful communication. KiWi is therefore able to reflect at least central aspects of the context that shapes a particular task or presentation: What is it about? What does one want to create it or use it for? Who is going to use the results of this task or make use of this document?
4. Experience:
   A usable interface considers the experience of a user. The KiWi interface is designed in such a way that it does not ward off users by confronting them with arbitrary, system-immanent requirements that the user is not familiar with. While KiWi does not ask too much of the inexperienced user, it must also not ask to little of the experienced user: Not all users will be able, for instance, to enter metadata reliably – but the skills of those who are must be harnessed in a way to benefit the entire system.
5. Preference:
   User preference and the motivation and readiness to use a system are closely related. The usability of a system increases if users are given the opportunity to select their preferred presentation (and thus: interaction) style. This includes control over background colours and layout, but is ever more vital when it comes to choosing between, for instance, Gantt-diagrams or Navision reports as a preferred style of information.

Knowledge Management + Wiki Philosophy + Semantic Web = KiWi