Support/Kitsune/Features/Forum-Data-Clustering: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 3: | Line 3: | ||
== Problem statement/description == | == Problem statement/description == | ||
Data on the forums is unstructured right now. There is no way to track the categories of issues on the forum, nor how we respond to these issues. This impacts the quality of our Responses, as well as making search faceting difficult. | |||
== Measurable outcome == | == Measurable outcome == | ||
An easy way to identify top issues trending in the forums. Active monitoring and alerts for breaking issues. | An easy way to identify top issues trending in the forums. Active monitoring and alerts for breaking issues. Being able to improve the quality of our responses to different "buckets" of issues. Ability to serve accurate results from the forums in our search implementation. | ||
This impacts our various groups in this way: | |||
* User Advocacy - Greater insights into types of questions coming into the forums. Ability to establish problem buckets rather than problem threads. More accurate reporting of scale of problems | |||
* Content Manager - Ability to identify which buckets drive the most traffic to the forums. Ability to create and modify KB to better address these issues. | |||
* Community Manager - Ability to identify which buckets our unsolved issues fall into. Ability to create further training around these buckets or recruit specialists for the problems. | |||
* User Advocacy - Ability to generate graphs based on trends for individual buckets. Greater insights into trends and bigger product issues | |||
== Possible Solutions: == | == Possible Solutions: == | ||
Latest revision as of 18:07, 23 August 2012
Title
Support forum data clustering
Problem statement/description
Data on the forums is unstructured right now. There is no way to track the categories of issues on the forum, nor how we respond to these issues. This impacts the quality of our Responses, as well as making search faceting difficult.
Measurable outcome
An easy way to identify top issues trending in the forums. Active monitoring and alerts for breaking issues. Being able to improve the quality of our responses to different "buckets" of issues. Ability to serve accurate results from the forums in our search implementation.
This impacts our various groups in this way:
- User Advocacy - Greater insights into types of questions coming into the forums. Ability to establish problem buckets rather than problem threads. More accurate reporting of scale of problems
- Content Manager - Ability to identify which buckets drive the most traffic to the forums. Ability to create and modify KB to better address these issues.
- Community Manager - Ability to identify which buckets our unsolved issues fall into. Ability to create further training around these buckets or recruit specialists for the problems.
- User Advocacy - Ability to generate graphs based on trends for individual buckets. Greater insights into trends and bigger product issues
Possible Solutions:
- Manual tagging of questions based on a predefined set of tags in the AAQ Flow
- Manual tagging of questions based on a predefined set of tags in the forums by contributors
- Clustering through Mechanical Turk
- Automated clustering based on machine learning