Closed Bug 1617762 Opened 6 years ago Closed 6 years ago

Consultation to understand why users pay for add-ons

Categories

(User Research :: Consultation, task)

task
Not set
normal
Points:
2

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: caitmuenster, Assigned: jdavidson)

Details

Request Description
The add-ons team wants to explore how to create monetization value for Firefox extension developers as a revenue opportunity. In late 2019 and early 2020, they will interview extension developers and users who have paid for extensions using the NIHITO (“Nothing Important Happens In the Office”) method to learn about their experience with monetization and develop an understanding of their problems. The team will use this information to develop future products and features that can lead to monetization.

Deadline
We would like to have research completed by March 13, 2020.

Priority Level
2 - Medium

Priority Level Description
The monetization project is part of the 2020 add-ons roadmap. See https://docs.google.com/presentation/d/1xNP_I5QAGiMhGcAzE5lgbLTq7Fhm-qYyvpFjOYNlAHA/edit.

The project is broken down on the following timeline:
Q1: Research and develop personas
Q2: Create experiments to validate hypothesis
H2: Determine what features belong on the roadmap and build

Supporting Information
Research overview and protocol: https://docs.google.com/document/d/1eXtFt6w99IJzrJIc-9x4jfT_fJPgLQaj4ZIkKOdHqFg/edit#

Jennifer Davidson has been really helpful with add-ons related research and we have already approached her to consult for this project.

Assignee: nobody → jdavidson
Status: NEW → ASSIGNED

I've been consulting with Caitlin on this, and we have a usertesting.com study up in action. It's kind of like an exploratory pre-interview. I know usertesting.com isn't the perfect venue for this, but the team needed a quick turnaround without any UR resources, so this felt like a way to get some information to seed perhaps future efforts.

Points: --- → 2

The pilot went smoothly. Added 9 more participants today.

Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.