Statistics in Q.wiki

Discover the vibrancy of your management system

The effectiveness and vibrancy of your Q.wiki system determine its added value for your company.

Questions such as “How well is Q.wiki being used?” or “How vibrant is our Q.wiki?” are key if you want to administer and optimize the system. 

In this article, you will learn how to overcome these challenges and which tools can help you do so.

Challenges at a glance:

• Usage transparency: How do you measure active use?
• Content optimization: How do you identify and remove outdated content?
• Process approvals: How often do approval processes take place?
• System changes: How many changes occur over time?

The usage report can be found (with key user rights) in the tool menu and shows statistics from Q.wiki (from the release in June 2022).

Basic statistical data is collected and used to evaluate the liveliness of the system:

1. Read and write access

The usefulness of your management system grows with its use. Recurring use by many employees is therefore an indicator of effective and value-adding management systems for us. The read accesses reflect the “total consumption” of the management system. The read accesses document the current relevance of the documentation – and thus the current relevance of the management system in the company. Read accesses document how often pages are opened, while write accesses record the number of storage operations. It is important to note that write accesses are counted independently of the quality of the changes. Constantly updating the documentation is particularly important for the future – this way, the content is always up to date and therefore relevant. 

Tip: In our experience, a ratio of 1:8 to 1:12 of write and read accesses is a healthy value. In other words, if about one in ten accesses is a write access, this ratio will keep your management system sustainably effective.

2. Interactivity

Interactivity indicates the number of users with write access per month. This allows you to determine how decentralized the system is: the higher the interactivity, the more employees work in the management system and make changes to the documentation. The interactivity also gives you concrete numbers on how many of your colleagues are actively introducing changes. If you have a lot of write accesses but a low interactivity, this is a sign that only few users are writing for many. 

If many employees are active in the system, you have taken the step “away from dependence on individuals” towards a participatory system! This is a good indicator of the acceptance of your company processes.

3. Top 10 editors

• This key figure helps to identify the most active users and to analyze the dynamics within departments.
• Analyzing this key figure monthly can reveal seasonal trends or project-related fluctuations in usage.
• It is important not to evaluate this data in isolation, as it does not provide any direct information about the quality of the contributions.

4. Released pages: 

The released changes show the sum of the final releases within the selected period. This makes them an indicator of a functioning release workflow. Many change proposals with few releases could mean that they are going in circles. The number of releases depends on the number of changes and thus the write accesses – if these numbers are in a similar ratio over a longer period of time, this indicates a fast release workflow and thus ensures documentation in almost real time. This implies that the documented content is highly up to date, which is great!

Page statistics (via the three-dot menu): 

• Frequently accessed pages can indicate well-prepared or frequently needed information.
• Pages that are hardly ever accessed could potentially be revised or archived to make the system more efficient.
• Get tips on designing process descriptions and work instruction

Q.wiki enterprise systems

By storing a Google Analytics identifier in Q.wiki, the features of Google Analytics can be used in Q.wiki. This makes it possible to evaluate, for example, how the system is used.

Support will help you set up the identifier once it has been created by the customer.

The old statistics are finalized and stored in Q.wiki. These can be accessed for the individual webs via the URL [web]/WebStatistics, e.g. www.meinqwiki.de/Processes/WebStatistics.