Support/Goals/SUMO-KPI-dashboard: Difference between revisions
| Line 11: | Line 11: | ||
** by SUMOdev | ** by SUMOdev | ||
KPIs to be implemented | |||
1. Number of visitors for the site (Sprint 3) | |||
2. % of people who vote “yes, I was helped” on our exit survey (Sprint 4) | |||
3. Helpfulness of KB articles and Forum (“yes”/total votes for both) (Sprint 2) | |||
4.% of people searching who click on an item on the search results page (CTR) (Sprint 2) | |||
5.% of non-english speakers that hit a localized article (Sprint 4) | |||
6. % of questions that get an action within 72 hours (Sprint 2) | |||
7. % of threads that have answer marked as a solution (Sprint 1) | |||
8. Number of active contributors to the English KB (Sprint 3) | |||
9. Number of active contributors to the non-English KB (Sprint 3) | |||
10. Number of active AoA contributors (Sprint 3) | |||
11. Number of active forum contributors (Sprint 3) | |||
==How do we know it's done?== | ==How do we know it's done?== | ||
Revision as of 10:22, 24 January 2012
Purpose
Track SUMO KPI and display them in the most effective way
Project plan
- Define KPIs
- Gather requirements for KPIs
- with Cheng, Ibai
- Gather resources to implement KPIs
- with Ricky
- Implement KPIs
- by SUMOdev
KPIs to be implemented 1. Number of visitors for the site (Sprint 3) 2. % of people who vote “yes, I was helped” on our exit survey (Sprint 4) 3. Helpfulness of KB articles and Forum (“yes”/total votes for both) (Sprint 2) 4.% of people searching who click on an item on the search results page (CTR) (Sprint 2) 5.% of non-english speakers that hit a localized article (Sprint 4)
6. % of questions that get an action within 72 hours (Sprint 2) 7. % of threads that have answer marked as a solution (Sprint 1)
8. Number of active contributors to the English KB (Sprint 3) 9. Number of active contributors to the non-English KB (Sprint 3) 10. Number of active AoA contributors (Sprint 3) 11. Number of active forum contributors (Sprint 3)
How do we know it's done?
- We have a way to request a value for every single KPI
Schedule
Estimated time: 2 month
- Define KPIs: January 1 - January 14
- Gather requirements: January 1 - January 14
- Implementaton: January 14 - February 30
Blocked
NO
Notes
Next step: