Canmove, confirm
1,953
edits
Changes
Created page with "=2017 Objectives= == Q1 Key Results== {| class="wikitable" ! Marketing 2017 Objective ! Marketing 2017 Key Result / MDN 2017 Objective ! MDN Q1 Key Results |- |rowspan="4" st..."
=2017 Objectives=
== Q1 Key Results==
{| class="wikitable"
! Marketing 2017 Objective
! Marketing 2017 Key Result / MDN 2017 Objective
! MDN Q1 Key Results
|-
|rowspan="4" style="vertical-align:top;" | On a survey of developers in key markets (NoAm, India, Germany), 25% view Mozilla as highly influential, up from 18% in most recent study.
| style="vertical-align:top;" | 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.<br/>
b. Complete SEO Audit and SEO/SEM rollout prioritization. <br/>
c. Document the top 30 JS errors shown to developers (to be linked to from Firefox) <br/>
d. Document Advanced HTTP topics to offer complete coverage of an important web standard on MDN (to be linked to from Firefox)<br/>
e. Document the 101 web platform changes in Firefox 52 by the release of Firefox 52 and Firefox 53 by the release of beta <br/>
f. Activate 2 new localizers in one locale, prioritized by Dev Marketing<br/>
g. (removed from plan)
|-
| 80%<sup>[[#1]]</sup> 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<br/>
j. Publish 10 reference pages and tutorials about WebAssembly<br/>
k. Document new APIs for PWA for marketing push<br/>
l. Document DevTools features of Firefox 52 and 53<sup>[[#2]]</sup><br/>
m, n. (removed from plan)
|-
| 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 <br/>
q. Complete prototype for compat data as defined in budget plan
|-
|
|Increase the first quartile<sup>[[#3]]</sup> of 3-week contributor retention to 3% from 1.48% (2016-H2 baseline).
| r. Redefine and begin re-implementing contributor pathways.<br/>
s. Run and analyze 5 contributor engagement experiments to select proven tactics for increasing retention
|}
<ol>
<li id="1">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.</li>
<li id="2">We aim to document DevTools features immediately after the Aurora launch.</li>
<li id="3">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.</li>
</ol>
== Q1 Key Results==
{| class="wikitable"
! Marketing 2017 Objective
! Marketing 2017 Key Result / MDN 2017 Objective
! MDN Q1 Key Results
|-
|rowspan="4" style="vertical-align:top;" | On a survey of developers in key markets (NoAm, India, Germany), 25% view Mozilla as highly influential, up from 18% in most recent study.
| style="vertical-align:top;" | 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.<br/>
b. Complete SEO Audit and SEO/SEM rollout prioritization. <br/>
c. Document the top 30 JS errors shown to developers (to be linked to from Firefox) <br/>
d. Document Advanced HTTP topics to offer complete coverage of an important web standard on MDN (to be linked to from Firefox)<br/>
e. Document the 101 web platform changes in Firefox 52 by the release of Firefox 52 and Firefox 53 by the release of beta <br/>
f. Activate 2 new localizers in one locale, prioritized by Dev Marketing<br/>
g. (removed from plan)
|-
| 80%<sup>[[#1]]</sup> 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<br/>
j. Publish 10 reference pages and tutorials about WebAssembly<br/>
k. Document new APIs for PWA for marketing push<br/>
l. Document DevTools features of Firefox 52 and 53<sup>[[#2]]</sup><br/>
m, n. (removed from plan)
|-
| 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 <br/>
q. Complete prototype for compat data as defined in budget plan
|-
|
|Increase the first quartile<sup>[[#3]]</sup> of 3-week contributor retention to 3% from 1.48% (2016-H2 baseline).
| r. Redefine and begin re-implementing contributor pathways.<br/>
s. Run and analyze 5 contributor engagement experiments to select proven tactics for increasing retention
|}
<ol>
<li id="1">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.</li>
<li id="2">We aim to document DevTools features immediately after the Aurora launch.</li>
<li id="3">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.</li>
</ol>
