Engagement/MDN Durable Team/Accountability/2017
From MozillaWiki
Contents
2017 Objectives
Q4 Key Results
| Developer Outreach 2017 Objective | MDN Q3 Key Results |
|---|---|
| Increase number of MDN sessions 40% y/y | Serve 43 million sessions on MDN (an increase of 12m sessions y/y) |
Evaluate the impact of SEO recommendations on CTR
| |
Complete static examples (excl. APIs)
| |
Launch rollout of final interactive code editor
| |
Content updates and Firefox 57/58 release support
| |
| Summary compat data tables in articles | |
| Upgrade MDN to latest Django to retain support | |
| 80% of MDN visitors to understand that MDN is powered by Mozilla (Baseline: 52%) | Complete redesign for all article pages, and all landing pages
|
| At least 1 editor offers access to MDN compat data | Complete migration of 100% of compat data
|
| Sign up one editor vendor for inclusion of compat data or decide on how to get compat data into 1 tool | |
| Launch experiments with 2 new types of community/contribution programs that help Mozilla promote web standards usage to developers | |
Deliver strategy and plan to establish and build a thriving core MDN Community that goes beyond casual editorial improvement of our documentation.
|
Q3 Key Results
| Developer Outreach 2017 Objective | MDN Q3 Key Results |
|---|---|
| Increase number of MDN sessions 40% y/y | Serve 39 million sessions on MDN (an increase of 11.2m sessions y/y) |
Evaluate the impact of SEO recommendations on CTR
| |
Complete static examples (excl. APIs)
| |
| Launch A/B test of final live sample code editor | |
Content updates for Firefox 56/57 release support
| |
100% of production traffic on AWS to provide stable technical foundation for MDN
| |
| 80% of MDN visitors to understand that MDN is powered by Mozilla (Baseline: 52%) | Complete redesign for home page, all article pages, and all landing pages
|
| Run brand perception survey on MDN | |
| At least 1 editor offers integrated access to MDN compat data by end of 2017 | Complete migration of 100% of compat data
|
| Sign up one editor vendor for inclusion of compat data by end of 2017 | |
| Launch experiments with 2 new types of community/contribution programs that help Mozilla promote web standards usage to developers | |
Deliver strategy and plan to establish and build a thriving core MDN Community that goes beyond casual editorial improvement of our documentation.
|
Q2 Key Results
| Marketing 2017 Objective | Marketing 2017 Key Result / MDN 2017 Objective | MDN Q2 Key Results (with links to project documents) |
|---|---|---|
| On a survey of developers in key markets (NoAm, India, Germany), 25% view Mozilla as highly influential, up from 18% in most recent study. | MDN is rated as the second most valuable resource for developers on a survey that asks Developers to rate MDN, Stack Overflow and w3schools among others. / Increase number of successful sessions 40% year/year. |
|
| 80%#1 of MDN visitors understand that MDN is powered by Mozilla (baseline: 52%) | * Initiate the separation between open web and Mozilla-specific documentation by moving at least one out of 24 product-specific projects out of MDN | |
| The number of developers who self-report as testing and debugging for Firefox is 70%. | At least 1 editor offers integrated access to MDN compat data by end of 2017 | |
| Increase the first quartile#2 of 3-week contributor retention to 3% from 1.48% (2016-H2 baseline). |
- 80% target is our understanding of what will lead to desired impact. Actual target will be decided once 2017 brand strategy (another Key Result in Q1) is defined.
- That is, 75% of cohorts have 3-week retention rates above this value. The 3-week mark was chosen to be about a month, while fitting with our sprint cadence.
Q1 Key Results
| Marketing 2017 Objective | Marketing 2017 Key Result / MDN 2017 Objective | MDN Q1 Key Results |
|---|---|---|
| On a survey of developers in key markets (NoAm, India, Germany), 25% view Mozilla as highly influential, up from 18% in most recent study. | MDN is rated as the second most valuable resource for developers on a survey that asks Developers to rate MDN, Stack Overflow and w3schools among others. / Increase number of successful sessions 40% year/year. | a. Complete qualitative user test for action oriented developers and rewrite first selection of articles in preparation of quantitative test in Q2. b. Complete SEO Audit and SEO/SEM rollout prioritization. |
| 80%#1 of MDN visitors understand that MDN is powered by Mozilla (baseline: 52%) | h. Define 2017 brand strategy for MDN as a Mozilla property that balances core brand attributes (browser agnostic vs powered by Mozilla) | |
| Support emerging technologies and upcoming Firefox releases | i. Publish 10 reference pages and tutorials about CSS grids j. Publish 10 reference pages and tutorials about WebAssembly | |
| Move MDN to a sustainable tech stack to ensure uptime doesn't go below 99.9% | o. Reduce monthly hours of site downtime due to planned db maintenance to zero | |
| The number of developers who self-report as testing and debugging for Firefox is 70%. | At least 1 editor offers integrated access to MDN compat data by end of 2017 | p.Validate demand for compat data plan with editor developers q. Complete prototype for compat data as defined in budget plan |
| Increase the first quartile#3 of 3-week contributor retention to 3% from 1.48% (2016-H2 baseline). | r. Redefine and begin re-implementing contributor pathways. s. Run and analyze 5 contributor engagement experiments to select proven tactics for increasing retention |
- 80% target is our understanding of what will lead to desired impact. Actual target will be decided once 2017 brand strategy (another Key Result in Q1) is defined.
- We aim to document DevTools features immediately after the Aurora launch.
- That is, 75% of cohorts have 3-week retention rates above this value. The 3-week mark was chosen to be about a month, while fitting with our sprint cadence.
