CloudServices/Sync/OKRs 2016Q3
< CloudServices | Sync
Jump to navigation
Jump to search
1. Build user trust by improving structural data integrity for bookmarks.
| Description | Rating | |
|---|---|---|
| 1.1 | Measure structural integrity defects in users' bookmark trees. | |
| 1.2 | Land fixes to the underlying defects related to the disabled, failing bookmark validation tests in TPS and enable these tests in TPS. | |
| 1.3 | Deploy sync server API for batch atomic writes to production and land client integrations on Desktop. (iOS and Android need coordination) | |
| 1.4** | Land improvements to the sync change tracker to ensure that users' bookmark changes are tracked before Sync has initialized or during a sync. | |
| 1.5* | Land repair code that uploads missing bookmarks. | |
| 1.6 | Land validators to measure the integrity of 3 other sync data types. Integrate the validators into TPS and report defect rates via telemetry. |
*Won't achieve ** At risk
2 Create value by helping users with task continuity between mobile and desktop.
| Description | Rating | |
|---|---|---|
| 2.1 | Add affordance to Desktop context menu to send tab to connected sync devices. | |
| 2.4 | Add measurement to the sync ping for send tab usage. | |
| 2.2 | Improve timeliness of sending tabs to devices using push events on Nightly Desktop, Android, and iOS. | |
| 2.3 | Land messaging to inform users of incoming tabs in Desktop (bug 1244597). |
3. Use data to help prioritize new features and fix defects in Sync
| Description | Rating | |
|---|---|---|
| 3.1** | Create a bookmark structural integrity dashboard on https://sql.telemetry.mozilla.org/. Dependent on 1.1 | |
| 3.2** | Create a integrity of 3 sync data types (1.6) dashboard on https://sql.telemetry.mozilla.org/ . Dependent on 1.6 | |
| 3.3** | Visualize send tab usage from 2.4 on https://sql.telemetry.mozilla.org/. | |
| 3.4** | Measure lost data occurrences due to single device password resets, visualize on https://sql.telemetry.mozilla.org/ |
- At risk but we believe we can get data in Presto or Redshift in order to make Re:Dash dashboards
4. Validate an experience that improves user trust by retaining sync data through a password reset
| Description | Rating | |
|---|---|---|
| 4.1 | Validate with users cross-platform alternatives that persists user data through a password reset. | |
| 4.2 | Instrument the current reset experience as a baseline for future improvements, | |
| 4.3 | Plan measurement of the new experience. |
5. Increase multi-device usage by improving in-context messaging
| Description | Rating | |
|---|---|---|
| 5.1 | Document options for creating in-context messages reinforcing value of sync features. | |
| 5.2 | Create mocks detailing the user experience through a chosen design. | |
| 5.3 | Test and create report of feature viability through testing on small user sample. |