797
edits
Engagement/Feature Based Communications/: Difference between revisions
Engagement/Feature Based Communications/ (view source)
Revision as of 11:26, 11 November 2011
, 11 November 2011no edit summary
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
Historically, Firefox communications and engagement with users, developers and press has revolved around release numbers and product updates. Examples of that engagement and communication strategy include campaigns and press cycles with Download Day for Firefox 3.0 and Firefox 4.0. | Historically, Firefox communications and engagement with users, developers and press has revolved around release numbers and product updates. Examples of that engagement and communication strategy include campaigns and press cycles with Download Day for Firefox 3.0 and Firefox 4.0. | ||
The move to a new development cycle has made it clear that although it is important to the Firefox userbase to get features at a faster pace, the update process itself is painful. Firefox engineering has consequently been working to implement parts of the “silent update” process for Firefox with Firefox 10 & 11. Firefox 11 or 12 could then consequently be the first “fully silent” experience for the Firefox userbase. This move is great for our users but is a departure from the typical strategies that Engagement teams and contributors have used to communicate with users, developers and press. <br> | The move to a new development cycle has made it clear that although it is important to the Firefox userbase to get features at a faster pace, the update process itself is painful. Firefox engineering has consequently been working to implement parts of the “silent update” process for Firefox with Firefox 10 & 11. Firefox 11 or 12 could then consequently be the first “fully silent” experience for the Firefox userbase. This move is great for our users but is a departure from the typical strategies that Engagement teams and contributors have used to communicate with users, developers and press. <br> | ||
== Silent Update: Implementation Timeline (Subject to Change)<br> == | == Silent Update: Implementation Timeline (Subject to Change)<br> == | ||
| Line 44: | Line 44: | ||
== Feature Based Engagement: What's Awesome<br> == | == Feature Based Engagement: What's Awesome<br> == | ||
=== User Communication<br> === | === User Communication<br> === | ||
*Better, more secure experience with Firefox for our users across the board. | *Better, more secure experience with Firefox for our users across the board. | ||
*Focused and themed communications that can be easily managed and integrated across all communications channels. <br> | *Focused and themed communications that can be easily managed and integrated across all communications channels. <br> | ||
**Highlight specific features that build on the product positioning,vision, themes and Mozilla values instead of having to list everything in a release (can make story feel disjointed). <br> | **Highlight specific features that build on the product positioning,vision, themes and Mozilla values instead of having to list everything in a release (can make story feel disjointed). <br> | ||
*Advance notice of features with the new development cycle make is significantly easier to coordinate with all contributors around major features, feature based campaigns, product demos and developer programs.<br> | *Advance notice of features with the new development cycle make is significantly easier to coordinate with all contributors around major features, feature based campaigns, product demos and developer programs.<br> | ||
=== Developer Communication<br> === | === Developer Communication<br> === | ||
*Opportunity to create strategic programs for developers | *Opportunity to create strategic programs for developers | ||
*a community-driven caniuse.com project where we can document technologies independently of version, and point to tables indicating which releases support them. | *a community-driven caniuse.com project where we can document technologies independently of version, and point to tables indicating which releases support them. | ||
*MDN documentation can be updated to serve developer community. | *MDN documentation can be updated to serve developer community. | ||
*Focused Product Demos Program <br> | *Focused Product Demos Program <br> | ||
=== Press Communications === | === Press Communications === | ||
*Create a strategic blog program for feature releases in parallel with developer communications. | *Create a strategic blog program for feature releases in parallel with developer communications. | ||
| Line 65: | Line 65: | ||
== Feature Based Engagement: Concerns<br> == | == Feature Based Engagement: Concerns<br> == | ||
''These are areas we need to be aware of, and in most cases, will be addressed with blockers. '' | ''These are areas we need to be aware of, and in most cases, will be addressed with blockers. '' | ||
=== User Communication<br> === | === User Communication<br> === | ||
| Line 98: | Line 98: | ||
*Clear Product Positioning to inform themes and help discern which features to promote and communicate.[PMMs] | *Clear Product Positioning to inform themes and help discern which features to promote and communicate.[PMMs] | ||
*Clear Value Propositions for all Features that are shared to all with advanced time to create campaigns. [PMMs] | *Clear Value Propositions for all Features that are shared to all with advanced time to create campaigns. [PMMs] | ||
*Clear Brand Strategy to help inform campaigns. [JSlater, KBaird?]<br> | *Clear Brand Strategy to help inform campaigns. [JSlater, KBaird?]<br> | ||
*Plan for rallying contributors around themes, campaigns instead of releases [Mary, LMesa, JFinette?] | *Plan for rallying contributors around themes, campaigns instead of releases [Mary, LMesa, JFinette?] | ||
| Line 109: | Line 109: | ||
*Communications plan for press, contributors and developers[Erica, LMesa, Stormy?] | *Communications plan for press, contributors and developers[Erica, LMesa, Stormy?] | ||
*New plan for PM, PMM feature/information outreach for contributors and paid staff to have a better understanding of upcoming features in order to better plan campaigns. [PMs & LMesa]<br> | *New plan for PM, PMM feature/information outreach for contributors and paid staff to have a better understanding of upcoming features in order to better plan campaigns. [PMs & LMesa]<br> | ||
*Blogging policy for development channels, releases and developer blogs [Stormy?, Erica J, LMesa]<br> <br> | *Blogging policy for development channels, releases and developer blogs [Stormy?, Erica J, LMesa]<br> | ||
== MozCamp Berlin Feedback<br> == | |||
Please add any thoughts you may have here: https://etherpad.mozilla.org/7GW4PMwumm<br> | |||
<br> | |||