| Objective
|
Key Result
|
Confidence
|
Features
|
Notes
|
| Nov 1
|
Nov 15
|
Nov 29
|
Dec 13
|
Score
|
| 1. Execute on Photon Onboarding
|
1.1 Ship v57 release with no blocking bugs and no dot releases due to Onboarding
|
--
|
100%
|
100%
|
|
|
|
|
| 1.2 Collect baselines for retention, heartbeat, and tour engagement performance
|
--
|
50%
|
|
|
|
|
10/31
- jdavidson to follow up with tyler downer and greg lind for heartbeat study. 100% that it will get done.
11/15
- heartbeat study is designed and created, will go out the 11/17. will present findings on dec 6. 100% that it will get done.
- cindy to sync up saptarshi to work on getting baseline for retention.
11/29
- jdavidson needs to sync up with tyler. would like to have more NEW users to take the heartbeat study. 90% were upgrade users. 90% confident that the hheartbeat study baseline will get done.
|
1.3 Land mechanism to run A/B tests on content (inclusive of changing content and varying content per country)
- Potential: A/B test to compare illustrations v. screenshots
|
--
|
100%
|
|
|
|
|
11/15
- We have landed the capability to pref modules on and off. We will use this capability to pref on or off the notifications and do a notification experiment to see if we will keep notifications in the onboarding tour.
|
| 1.4 Analyze onboarding shield study retention data, identify release vehicle to ship any recommended changes based on most successful variant
|
|
|
|
|
|
- Onboarding SHIELD study for Onboarding 56 that looks at timing and placement of tour
|
- dashboards are up and we are collecting telemetry data.
11/29
- Su is going over data this week and will have update.
|
| 2. Increase retention for returning lapsed users
|
2.1 Create a baseline metric for lapsed returning user retention
|
|
|
|
|
|
|
- jenny has lapsed user data from email campaigns (engaged user email campaign). Worth having further conversations to see if that is useful in the future.
- need to define what exactly a lapsed user is. Will do that will verdi and cindy.
|
| 2.2 Add-on migration study
|
0%
|
0%
|
0%
|
0%
|
0
|
|
- Study will not happen in Q1
|
| 3. Identify differences and similarities between Chrome Onboarding and Quantum Onboarding
|
3.1 Do a heuristic analysis/competitive analysis and a usertesting.com remote, unmoderated study
|
65%
|
0%
|
0%
|
0%
|
0
|
|
- Work is scheduled. study has not started.
- Will not be in Q4 due to holiday break
|
| 3.2 Publish recommendations for how Firefox could differentiate relative to Chrome
|
65%
|
0%
|
0%
|
0%
|
0
|
|
- Work is scheduled. study has not started.
- Will not be in Q4 due to holiday break
|
| 4. Improve retention for Chrome migrators
|
4.1 UX concepts for data migration to iterate on in Q1
|
75%
|
75%
|
75%
|
|
|
|
10/31
- Sketch concepts of mverdi's ideas around this.
11/15
- Verdi will talk with rfeely on friday to talk through ideas and have actionable next steps.
11/29
|
4.2 Improve retention for Chrome ad-block users who install Firefox
|
--
|
--
|
--
|
--
|
--
|
|
- Team is changing approach for this. We are no longer have TPE team work on this and to ship this ASAP. Rather we are working with stub installer team who plans on shipping functionality in Q1.
|
| 4.3 Have profiles and STR to test automigration changes against (and graph)
|
--
|
100%
|
100%
|
|
|
|
- Ddurst's team is already testing the profiles.
|
| 4.4 Determine best course for parallelism/sequential import in automigration
|
--
|
50%
|
100%
|
|
|
|
- some debate as to whether there is a benefit to doing this.
11/29
|
| 4.5 Consider if History inserts can be done in batch (as was done with bookmarks)
|
--
|
75%
|
100%
|
|
|
|
- patch has been posted and there have already been comments for revision.
11/29
|
