Firefox/Input/Gradient Sentiment: Difference between revisions
No edit summary |
|||
| Line 24: | Line 24: | ||
== Requirements == | == Requirements == | ||
=== v1 ( | === v1 (2014q4) === | ||
Requirements: | Requirements: | ||
| Line 30: | Line 30: | ||
# Add an additional gradient field to the db | # Add an additional gradient field to the db | ||
# Change the generic form to use a 1-5 gradient rating instead of the single happy/sad rating | # Change the generic form to use a 1-5 gradient rating instead of the single happy/sad rating | ||
# Add code to infer the happy/sad from a gradient | # Add code to infer the happy/sad from a gradient | ||
# Add gradient to the ES index | # Add gradient to the ES index | ||
# Add gradient to the analyzer's dashboard | # Add gradient to the analyzer's dashboard | ||
Revision as of 16:12, 14 October 2014
Gradient Sentiment
(This is rough sketch. I need a template for doing this better.)
Summary
Currently, a feedback response on Input captures a "happy or sad" sentiment, a description, (optional) a related url and (optional) an email address. Thus a feedback response has an indicator of whether the user is happy or sad and what it is they are happy or sad about. The problem with this is that we have no indicator of how happy or sad the user is regarding the thing they're happy or sad about. Are they sort of happy or sad? Are they furious? Is this an issue that is going to cause them to find a new browser? We can't tell.
This project covers experimenting with using a 1-5 gradient instead of the boolean happy/sad sentiment.
Status
- Project owner: Will Kahn-Greene
- Status: in-progress
History
- March 18th, 2014: Initial tracker bug was created and discussions started.
- May 7th, 2014: Had an Input stakeholders meeting and discussed switching to a 1-5 gradient there.
- September 17th, 2014: Talked with User Advocacy about gradients and changing the phases around.
FIXME: This is missing some history. We had a bunch of meetings with UX and other people to talk about what kind of rating scale to use, how to show it, cultural issues with rating scales, etc.
Requirements
v1 (2014q4)
Requirements:
- Add an additional gradient field to the db
- Change the generic form to use a 1-5 gradient rating instead of the single happy/sad rating
- Add code to infer the happy/sad from a gradient
- Add gradient to the ES index
- Add gradient to the analyzer's dashboard
- Add code to A/B test happy/sad vs. gradient
- Analyze the A/B test results
Anti-requirements:
- don't need to implement this in the Input API right now--we'll do that in the next version
- don't need to implement this in the Firefox OS form (which uses the Input API)--we'll do that in the next version
- don't need to change the public frontpage dashboard to show gradients
- don't need to change the public Input API
Bugs:
Tracker: https://bugzilla.mozilla.org/show_bug.cgi?id=985140
| ID | Summary | Priority | Status |
|---|---|---|---|
| 987209 | add django-waffle for a/b testing infrastructure | P2 | RESOLVED |
| 1020303 | add gradient column to Response model | P2 | RESOLVED |
| 1020307 | create mockups for generic feedback with gradient sentiment | P1 | RESOLVED |
| 1020313 | update Firefox OS feedback form to use gradients | P2 | RESOLVED |
| 1020331 | add gradient to input API | P2 | RESOLVED |
| 1128702 | add gradient faces to generic feedback form | -- | RESOLVED |
6 Total; 0 Open (0%); 6 Resolved (100%); 0 Verified (0%);
v2 (Future)
- implement this in the Input API
- implement this in the Firefox OS form (unless that's fallen out of use at this time)
- change the public frontpage dashboard to show gradients?
- change the public Input API?