Q3 Objectives and Key Results

Edwin Wong edwong at mozilla.com
Fri Jun 17 10:33:37 UTC 2016


Hi,

The team met and have our first draft of Q3 OKRs.  Next steps are to refine
and prioritize KRs, then break down work into bugs.

https://docs.google.com/document/d/1N1owRy3zVh2J3nqInrUU6MszdIEnBCB4BLWK7fmZwDY/edit

---------------
Objective #1 - Build Trust - Improve data integrity

   -

   KR#1 - Fixing and measuring parent/child/tree missing issue (this is a
   bounded fix rather than all data integrity issues). All Fx5x less 5% of
   data corruption with this type of error.
   -

   KR#2 - Implement validator for other data choices and report via
   telemetry or TPS
   -

   KR#3 - TPS run on clean profile results in zero fails with hacks removed

Objective #2 - Build Understanding/Value - Send tabs to device for Android
and Desktop (use case: tabs on airplane)

   -

   KR#1 - land sync support send tab to device
   -

   KR#2 - land push support send tab to device
   -

   KR#3 - land push support in Android (iOS doesn’t support inbound push
   events)
   -

   KR#4 - telemetry on discovery and engagement (consider server side
   metrics)
   -

      Measure engagement in user repeat usage of feature across sessions.
      -

      If user sends same tab over and over is an error case
      -

      count sends and receipts should be equal as an error metric

Objective #3 -  Build Trust -  Improve Timeliness/Reduce Latency

   -

   KR#1 - land push support in Android
   -

   KR#2 - land push support in Desktop (related 4.2)
   -

   KR#3 - measure - how do we know this is working or gives users value.
   -

      Qualitative measure - diary study or heartbeat survey when 2nd device
      receives.
      -

      Quant - when 2nd device is offline

Objective #4 - Build Trust - Persist data through password reset

   -

   KR#1 - document a plan to solve this via UX, (e.g. optional basic or
   strong)
   -

   KR#2 - produce mocks for UX changes to enable
   -

   KR#3 - validate UX via small user testing sample

Objective #5 - Build Understanding/Value of Sync

   -

   KR#1 - smart UI tour: document a plan
   -

   KR#2 - smart UI tour: produce mocks for UX changes to enable this
   -

   KR#3 - smart UI tour: validate UX via small user testing sample

Dependencies

   -

   FxA device registration on Android (WIP) and iOS (eoger POC)
   -

   Push on Android and iOS
   - Context Graph may have requests but for now nothing actionable.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/sync-dev/attachments/20160617/eeeaf48e/attachment.html>


More information about the Sync-dev mailing list