Define a Classification System for Dashboard Sets

[BenLloydPearson]

This project needs a system of classification for dashboard sets to make it easy for people to identify the metric sets they need for their specific use case. The classification system should provide clear definitions for what problems or goals each dashboard set seeks to resolve and what individuals would potentially be interested in utilizing the set.

I propose a system that uses three mechanisms for classification:

• User Role - These dashboards would be targeted at specific types of users. E.g. a community manager would be interested in set A, a development manager would be interested in set B, etc. This classification system would be fairly broad and would seek to provide all metric sets each of these individuals might be interested in.
• User Problem - These dashboards would seek to help the user solve a specific problem. E.g. my project is declining in community participation, my project is taking longer to get committed into the master branch, etc.
• User Goal - These dashboards would seek to help users reach desired goals. E.g. I want to increase community participation, I want to find the best geographic location to host events, etc.

Realistically, these categories will likely have some overlap, meaning that individual dashboards will likely be used in multiple classifications. For example, Identifying the best geographic location for an event (user goal) would also be valuable in a more general dashboard for community managers (user role).