Firefox/Accounts/Progress Report/2017Q3

Sept 5, 2017

Q3 OKR Progress

Objective	Key Result	Confidence	Features	Notes
Jul 10	Jul 24	Aug 8	Aug 21	Sep 5	Sep 18	Score
1. To have improved the quality for the Firefox Account experience on desktop.	1.1 Close ALL (100%) issues in the Quantum/Photon milestone. (Crouton)	60%	65%	70%	75%	90%			Priorities for support of Quantum/Photon in 57: Crouton Flow Issues for 57 release.	As of Sept. 5th, there were only a handful of "crouton" bugs remaining. Confidence % reflects where we were at on Sept. 5th. By week of Sept 11th, they were all finished! Confidence will be updated to 100% at next team review on Sept. 18th. Crouton Flow Burndown Chart
	1.2 Close 50% of our Q3 quality backlog.		50%	75%	75%	90%			Quality Priorities for Q3: Quality related P1s that we’ve identified to fix in Q3.	Great progress has been made on the Quality P1s. Nearly at 50% closure, the goal for this OKR. In this sprint (as of Sept. 14th): A couple are in review: Issue 5197: Sign-in flow: Never send users to about:preferences after Sign-in and Issue 5262: Expand Connect Another Device to all sync Desktop sign-ins One is active: Issue 4863: Add descriptions to Choose What to Sync A couple were moved to the backlog: Issue 5009: Only show "email verified" on /connect_another_device if the user actually verfied their email. and Issue 5196: Sign-up/in flow: Don't ask to connect a mobile device when you started flow on mobile Quality P1s Burndown
	1.3 Increase by 15% the rate of users that become multi-device as a result of going through our first run flow.	50%	50%	50%	40%	0%			Supports the onboarding team, marketing retention team and Mozilla.org team to improve user retention (through converting first run users to multi-device users). Dashboards related to user retention Issue 5332: ABC test for CAD phase 3 (deep link)	Still not seeing any difference in outcomes between the different phases in our ABC test. Landed our iOS deeplink patch on Sept 7th so signinCodes consumption should have increased since that date. Form views on iOS should also have increased since that date thanks to deeplinks. Leif will compare form views per phase. The bottom charts of our dashboard are not measuring phase 2 and 3 the same way. They show very different results because phase 3 uses the flow_id. There may be a bug with the flow_id so Leif will copy the phase 2 chart for phase 3. Will see what difference that makes.
	1.4 Fix newsletter subscription when email is confirmed on a 2nd device.	95%	95%	95%	95%	90%			Fixes a problem with getting marketing newsletter opt-in data over to Salesforce.	Not sure if the fix is working. Maybe the situation it fixed was small numbers and just not noticeable. We should be able to go through the flow ourselves and have Ben verify.
2. To have improved the quality of the Firefox Account experience on mobile.	2.1 Measure and A/B test best push opt-in screen on iOS.	50%	40%	55%	55%	50%			FxA Sync prioritization backlog for iOS Proposed mock up	Next step is to design test to measure results.
	2.2 Complete 80% of Q3 mobile bugs.	N/A	60%	60%	60%	65%			Identification and fixing of the most impactful bugs on iOS Mobile Bugs for Q3 Currently working on: Issue 5279: Update Confirm view to handle when verification is using Push Issue 335: Display FxA avatar in settings [bz1382756] Issue 332: Use Firefox Account server's /.well-known/fxa-client-configuration to configure servers in Firefox for iOS [bz1237407]	Did the easy ones first. Medium level ones are left to do. Should have 9/13 done by next week. Mobile Quality Burndown Chart
3. To have completed all features that are still in flight from Q1 and Q2.	3.1 Have a device pairing flow ready to A/B test.	75%	75%	50%	25%	0%			Allow users to test out device pairing. This does not necessarily mean that QR codes are used. Feature doc and Issues coming soon.	Not confident that we’ll have QR codes ready to test Too many unknowns to have any confidence We can try a file input but that would be a crappy experience. Have never tried to import a photo into the encoder. What if there’s too much noise in the photo or the QR code? We can play with the one built into iOS but still might not have time to figure it out by the end of the quarter. Confidence level for use of a QR code is <25%; type a code maybe >50% Need to regroup now that we know more about technical limitations and figure out what we want to do. Need a smaller discussion about what the next steps are. Ryan will reach out to iOS team.
	3.2 Ship secondary email.	80%	80%	90%	90%	90%			We are allowing users to add a secondary email. Allows users to change primary email. Issues for changing primary email: Issue 278: Add ability for a FxA user to change their primary email Issue 341: Detect when account email has changed, and update local state to match Issue 1999: (node:48) DeprecationWarning: DeprecationWarning for mem.emailRecord: Use mem.accountRecord Issues 341: Detect when account email has changed, and update local state to match	Shipped Shaking out the downstream bugs in terms of getting the devices to update themsleves. That’s browser work that we don’t have a lot of control over. Grisha is working on Android piece. Still confident we an get it out the door.
	3.3 Land support for relier encryption keys.	70%	70%	75%	75%	75%			Relier encryption keys	Waiting to engage crypto consultants. Issue 245: Prototype key support api for Firefox Notes
	3.4 Integrate 100% of high priority Amplitude events.	75%	75%	75%	75%	75%			Implementation of Amplitude	Getting help from Amplitude to move forward Still discovering new things Should have environment with train-95 that we can send events to.