Static vs. dynamic management system

When introducing Q.wiki, it is important to be clear about the type of documentation you want to produce. In practice, static management systems have proven to be of little use in everyday work. They serve merely as a verification management system:

In everyday work, knowledge transfer often involves imparting process knowledge, e.g., with the help of BPM. Extensive flowcharts that are too complex for individual employees.

On the one hand, they are difficult to understand, and on the other hand, they are of no use in everyday work because this form of presentation makes it difficult to convey knowledge.

These processes are not an adequate means of knowledge transfer:

• Because the processes provide very little information for new employees
• The processes are difficult to convey without background knowledge
• A high level of training is necessary because the process mapping does not explain anything, does not stand alone, and therefore does not add value
• No transparent information can be gleaned
• These process mappings are difficult to change – they are not dynamic

Bring your management system to life

• Bundle all of your employees' knowledge and increase transparency, especially at interfaces
• Active knowledge exchange and new experiences can be contributed immediately and independently by every employee
• Processes are optimized by the employees themselves because best practices are always documented
• Contribute content that is useful for everyday work
• Step-by-step recipes with all the information and details needed to complete a work order