Test Pilot/2016Q3: Difference between revisions
Jump to navigation
Jump to search
m (→2016 Q3 Goals) |
(→2016 Q3 Goals: modified goal) |
||
Line 16: | Line 16: | ||
* '''Objective:''' Make it easy for existing Test Pilot users to learn about new experiments and start using them. | * '''Objective:''' Make it easy for existing Test Pilot users to learn about new experiments and start using them. | ||
* '''Key Results:''' | * '''Key Results:''' | ||
** '''TODO: | ** '''TODO: Get new experiment within 24 hours of launch at a rate 10% higher than our baseline engagement ratio. | ||
** Implement a notification system in Test Pilot | ** Implement a notification system in Test Pilot | ||
*** ''(task) push notifications used by 80% of users'' | *** ''(task) push notifications used by 80% of users'' | ||
Line 22: | Line 22: | ||
** 5% of active Test Pilot users share an experiment socially | ** 5% of active Test Pilot users share an experiment socially | ||
* '''Objective:''' Demonstrate that the Test Pilot experiment | * '''Objective:''' Demonstrate that the Test Pilot experiment life cycle is valuable and sustainable. | ||
* '''Key Results:''' | * '''Key Results:''' | ||
** Ensure at least one experiment graduates | ** Ensure at least one experiment graduates |
Revision as of 15:58, 6 July 2016
2016 Q3 Goals
- Objective: Grow the Test Pilot user base.
- Key Results:
- TODO: r?jgruen on percentage here Grow total Test Pilot user base by 66%
- Add localization support to Test Pilot and get 80% of users using Test Pilot in their first choice language.
- (task) Site & Add-on is available in FIGS languages
- (task) Send one marketing email in FIGS languages
- All new Test Pilot experiments support localization when appropriate.
- (task) Document our supported solutions
- (task) Site support for identifying experiments based on contextutal information (eg. language, region, platform, etc.)
- Get 6% of our legacy users into the new Test Pilot program.
- (task) Review & Implement the legacy migration program
- Remove Firefox Accounts integration
- Objective: Make it easy for existing Test Pilot users to learn about new experiments and start using them.
- Key Results:
- TODO: Get new experiment within 24 hours of launch at a rate 10% higher than our baseline engagement ratio.
- Implement a notification system in Test Pilot
- (task) push notifications used by 80% of users
- (task) (stretch) integrate opt-in email
- 5% of active Test Pilot users share an experiment socially
- Objective: Demonstrate that the Test Pilot experiment life cycle is valuable and sustainable.
- Key Results:
- Ensure at least one experiment graduates
- Ensure at least one new experiment is publicly available
- Publish conclusions
- Build an offboarding process
Non-Goals
The below were discussed as part of our goal setting but were not selected. They are included here for posterity and/or future planning.
- Objective: Expose standardized experiment performance data in an easily consumable format
- Key Results:
- Build a standardized “report card” with high level statistics
- Send an automated weekly summary email to executives