Overview
The Statistics view compiles performance metrics for the organization and teams. Different statistics require specific permissions.
Opening and Filtering Statistics
- Open the Statistics view.
- Select the report you want to view.
- Filter the data using available filters, such as time period or team.
- Review the summary and drill down into more detailed information if needed.
Available Statistics
Depending on permissions and products, the following views may be available, among others:
1. Customer, device, and event counts (table)
2. Team comparison (bars) - You can compare your team's numbers to other teams or Gilli's own reference values. You can also click on the charts to delve deeper into the data.
3. Summary of triggers (graphics) - Shows response times and counts for triggers.
4. Reasons for acknowledging triggers (table) - Shows users' acknowledgments of triggers.
5. Teams' response to triggers (scatter plot) - Displays team rankings on a graph based on timely acknowledgment of triggers and actions taken according to leadership criteria.
6. Response to triggers over the past year (scatter plot) - Shows the above rankings on a graph covering the past year.
7. Triggers leading to actions (tree map) - Displays triggers that led to actions by selected teams during the selected time period.
8. Login times (table) - Shows how often a user has logged into the platform and the time of their most recent login.
9. Performance meter (graphics) - KPI dashboard for displaying target percentages, for example, for medication dispensers or remote visits.
10. Device errors (table) - Shows, for example, if a device is connected to an archived customer or if a customer for whom data entry is attempted cannot be found in Gilli.
11. Cost-effectiveness (table) - Cost impact caused by responses to triggers.
Best Practices for Utilizing Statistics
- Regularly review key metrics during team meetings.
- Agree on common practices for handling triggers and documenting actions.
- Compare results both to previous periods and to other comparable teams.
- Target training and support based on usage statistics.
- Collect user feedback on underused features and identify obstacles to usage.
- Focus on the overall picture and long-term trends rather than individual figures.