Firefox/Desktop Onboarding/OKRs/Q4

2017Q4 OKR Progress

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
	1.2 Collect baselines for retention, heartbeat, and tour engagement performance							jdavidson to follow up with tyler downer and greg lind for heartbeat study. 100% that it 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
	1.4 Analyze onboarding shield study retention data, identify release vehicle to ship any recommended changes based on most successful variant							dashboards are up and we are collecting telemetry data.
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 hhaving further conversations to see if that is useful in the future.
	2.2 Add-on migration study
3. Identify areas to iterate on for the new user and update user Onboarding experience for Germany moved to Q1	3.1 Publish usability enhancement recommendations for Germany participants
4. Identify differences and similarities between Chrome Onboarding and Quantum Onboarding	4.1 Do a heuristic analysis/competitive analysis and a usertesting.com remote, unmoderated study	65%						Work is scheduled. study has not started.
	4.2 Publish recommendations for how Firefox could differentiate relative to Chrome	65%						Work is scheduled. study has not started.
5. Improve retention for Chrome migrators	5.1 Reduce average jank in data migration process by 50% (need to collect baseline) for Chrome migrators
	5.2 UX requirements concepts for data migration to test iterate on in Q1	75%						Sketch concepts of mverdi's ideas around this.
	5.3 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 withh stub installer team who plans on shipping functionality in Q1.
	5.4 Have profiles and STR to test automigration changes against (and graph)
	5.5 Determine best course for parallelism/sequential import in automigration						Bug 1338800
	5.6 To consider if History inserts can be done in batch (as was done with bookmarks)