Metrics regarding average time to accepted solutions
Below are three metrics that help monitor how responsive the community is in terms of posting solutions, and the description of each metric as given by Lithium:
Metric A - Topics Posted to Solution Accepted Time (Avg): The number of minutes, on average, between when a reply is posted and is accepted as a solution. This metric gives you an indication of how quickly moderators and question authors respond to and accept replies as solutions.
Metric B - Topic Posted to Solution Posted Time (Avg): The number of minutes, on average, between when a question and solution are posted. This metric is updated each time a solution is accepted. It gives an indication of how rapidly community members are accepting solutions.
Metric C - Solution Posted to Solution Accepted Time (Avg): The number of minutes, on average, between when a reply is posted and is accepted as a solution. This metric gives you an indication of how quickly moderators and question authors respond to and accept replies as solutions.
For the sake of this post, I'll call these three metrics A, B, and C as denoted above.
- It is my understanding that Metric A is categorically higher than Metric B. In other words Metric A > Metric B for all posts, thus the average value should follow the same logic. However, I've found a few days where this isn't true. Any thoughts on this?
- Let's put aside the fact that the description given by Lithium for Metric A and Metric C are the same for a minute and assume that Metric C is suppose to measure how long it takes for a reply (not the post) to be marked as solution. It'd make sense for Metric C = Metric A - Metric B, but again this logic doesn't seem to work as my first question prohibits this logic. But even when Metric A > Metric B, this logic doesn't seem to follow.
I'm trying to make sense of these metrics, and making sure that I'm not making any errors on my end. Please share your thoughts and experiences!
p.s. all these metric values are called via Community API.
