Content services: Difference between revisions

(→‎Product Guidelines: user choice controls)
 
(13 intermediate revisions by 3 users not shown)
Line 3: Line 3:
The Content Services Team was formed in late 2013 to explore opportunities that will provide additional value to our users, strongly align with our mission, and over time, generate new sources of diversified revenue.
The Content Services Team was formed in late 2013 to explore opportunities that will provide additional value to our users, strongly align with our mission, and over time, generate new sources of diversified revenue.


We are particularly fascinated by the content ecosystem online – which is one of the primary currencies of the web.   How does content get distributed? How does content get monetized? How can we create better content experiences for our users?  All questions we continue to ask ourselves.
The team works to make the web economically and socially sustainableWe want to sustain it economically, to ensure that the Web remains a place of economic opportunity for content creators. And we wish to make is socially sustainable, meaning that we wish to address the "maladies" that the advertising-supported content ecosystem has engendered on the Web, including:
* poor user experience
* widespread use of proprietary technology on the Web
* ad fraud
* lack of user control over data resulting in a loss of privacy


A group of Mozillians from the Steering Committee and Firefox team evaluated more than two dozen revenue related proposals in late 2013. Each idea we considered was closely evaluated on whether it resulted in incremental value to our users, aligned with our mission and values, and had the potential to significantly impact our sustainability over time.
Our current mission is to provide in-browser promoted content experiences for advertisers who want better, higher-quality relationships with their audience and who choose Mozilla Content Services in order to have a future-facing, ethical partner with scale.


Below are the initial projects we decided to test..
== Product Guidelines ==


To achieve our mission, we build products that rely on users trusting Mozilla including code that is in Firefox and add-ons as well as our services. We want to earn trust by being transparent with our policies, processes, and open source code. While not a strict requirement for releasing a new product, we will try to build trust into code so that users do not have to rely on Mozilla services operating according to policy. If our services need to collect data, we intend to only use the minimal amount of data necessary to answer specific questions, and we will document the behaviors and communicate to users/community that this is happening. We will also build controls into the products to provide better user choice as well as an easy mechanism to turn things off.


== Product Roadmaps==
== Product Roadmaps==


===Directory Tiles===
===[https://wiki.mozilla.org/Tiles Directory Tiles]===
:Every time a user opens up a new tab in Firefox, the browser displays Tiles. Frequent Firefox users see screenshots of the websites they visit most often in their Tiles. We look to leverage the Tiles on our New Tab pages and make them a source of revenue for Mozilla. There are a few opportunities that we will test in market (first in pre-release channels) within 2014 and the first of which is to provide sponsored content on First-Run-Tiles known as Directory Tiles. This should begin testing in Q2/3 and we will then work on additional Tile enhancements outside of First-Run.
:Every time a user opens up a new tab in Firefox, the browser displays Tiles. Frequent Firefox users see screenshots of the websites they visit most often in their Tiles. We look to leverage the Tiles on our New Tab pages and make them a source of revenue for Mozilla. There are a few opportunities that we began tests in market (first in pre-release channels) in 2014 and the first of which is to provide sponsored content on First-Run-Tiles known as Directory Tiles. This began testing in 2014 Q2/3. The successes here led to work on additional Tile enhancements outside of First-Run.


===Voices===
===[https://wiki.mozilla.org/Tiles Suggested Tiles]===
:We look to roll out a PBS/NPR style web-based content series about our Mozilla curated view of the world. This content series will go live weekly and be promoted across the Mozilla footprint. We will work with selected underwriters to sponsor this content to generate meaningful revenue.
:For existing users with browsing history, we want to provide users valuable content of new places to visit. We provide Firefox with additional data that it uses to decide if a suggestion should be made on the New Tab page. For example, if a user tends to visit web development sites, we can make a suggestion to visit "Mozilla Developer Network."


===UP/Intent Engine===
===[https://intranet.mozilla.org/UP UP/Intent Engine]===
:UP is our Intent Engine for across Mozilla that helps us deliver personalization platforms for all of our products and services. Our 2014 strategy is to keep building our UP platform to make it available to the desktop, OS, services, and other products and have the bridges built this year that each product team has the ability to read/write to it. We will do limited tests in Q2/3/4 of this year to test different Intent Engine modules (such as tasks, discovery, personalization, ads).  Within UP, we have a particular focus around Intentcasting and VRM.
:[https://intranet.mozilla.org/UP UP] is our Intent Engine for across Mozilla that helps us deliver personalization platforms for all of our products and services. Our 2014 strategy is to keep building our UP platform to make it available to the desktop, OS, services, and other products and have the bridges built this year that each product team has the ability to read/write to it. We will do limited tests in Q2/3/4 of this year to test different Intent Engine modules (such as tasks, discovery, personalization, ads).  Within UP, we have a particular focus around Intentcasting and VRM.
 
==Content Services Roadmap==
 
<b>Q1 2014:</b> Grow Team - We’ll start by hiring a small team of paid staff who can dedicate the majority of their time thinking about how to develop and execute these initiatives. We’ll also look to grow support within the Mozillian community by exploring opportunities for participation and through regular dialog.
 
<b>Q2 2014:</b> Directory Tiles Initial Testing & Grow Team<br>
June 16-20 will be a Work Week in New York City for Content Services.  We'll be spending time thinking about the product roadmap and working with the community and partners to achieve our goals.
 
<b>Q3 2014:</b> Voices Soft Initial Testing, Grow Team, Tiles (to Beta, redefine UI/UX), and UP's Personal Interest Dashboard
 
<b>Q4 2014:</b> UP Content Recommendation Testing, Voices Testing, and scale Tiles


== Content Services Resources==
== Content Services Resources==
Line 38: Line 32:
Check out our [https://blog.mozilla.org/advancingcontent/ Official Content Services Blog.]
Check out our [https://blog.mozilla.org/advancingcontent/ Official Content Services Blog.]


Watch the Directory Tiles Town Hall on [https://air.mozilla.org/town-hall-directory-tiles/ AirMozilla.]
Join our Interest mailing list [https://mail.mozilla.org/listinfo/contentservices-distro ContentServices Distro]
 
== Get Involved/Share Ideas & Feedback==
 
If you’re interested in what we are doing,  we’d love for you to subscribe to our group and contribute to the discussions. We are also actively hiring, so if you’re interested in joining our team, check out Mozilla’s careers page for opportunities. We have lots to talk about in the coming weeks and months!


In the meantime, if you have anything to add, feel free to reach out to [mailto:contentservices@mozilla.com?Subject=Your%20Subject%20Here the Content Services Team]
Reach out on email to [mailto:contentservices@mozilla.com?Subject=Your%20Subject%20Here the Content Services Team]


=June 2014 Work Week=
Find us on IRC #mozcontent
From June 16-20, 40+ Mozillians came to the Manhattan, NY based Content Services office to discuss Content Services. The schedule was packed with presentations from each Product Manager (Tiles, UP, Subscribe2Web, Voices, DirectPay & Notifications), community, outside speakers (The Media Kitchen, Wired), and many others.

Latest revision as of 09:09, 29 April 2015

Content Services Overview

The Content Services Team was formed in late 2013 to explore opportunities that will provide additional value to our users, strongly align with our mission, and over time, generate new sources of diversified revenue.

The team works to make the web economically and socially sustainable. We want to sustain it economically, to ensure that the Web remains a place of economic opportunity for content creators. And we wish to make is socially sustainable, meaning that we wish to address the "maladies" that the advertising-supported content ecosystem has engendered on the Web, including:

  • poor user experience
  • widespread use of proprietary technology on the Web
  • ad fraud
  • lack of user control over data resulting in a loss of privacy

Our current mission is to provide in-browser promoted content experiences for advertisers who want better, higher-quality relationships with their audience and who choose Mozilla Content Services in order to have a future-facing, ethical partner with scale.

Product Guidelines

To achieve our mission, we build products that rely on users trusting Mozilla including code that is in Firefox and add-ons as well as our services. We want to earn trust by being transparent with our policies, processes, and open source code. While not a strict requirement for releasing a new product, we will try to build trust into code so that users do not have to rely on Mozilla services operating according to policy. If our services need to collect data, we intend to only use the minimal amount of data necessary to answer specific questions, and we will document the behaviors and communicate to users/community that this is happening. We will also build controls into the products to provide better user choice as well as an easy mechanism to turn things off.

Product Roadmaps

Directory Tiles

Every time a user opens up a new tab in Firefox, the browser displays Tiles. Frequent Firefox users see screenshots of the websites they visit most often in their Tiles. We look to leverage the Tiles on our New Tab pages and make them a source of revenue for Mozilla. There are a few opportunities that we began tests in market (first in pre-release channels) in 2014 and the first of which is to provide sponsored content on First-Run-Tiles known as Directory Tiles. This began testing in 2014 Q2/3. The successes here led to work on additional Tile enhancements outside of First-Run.

Suggested Tiles

For existing users with browsing history, we want to provide users valuable content of new places to visit. We provide Firefox with additional data that it uses to decide if a suggestion should be made on the New Tab page. For example, if a user tends to visit web development sites, we can make a suggestion to visit "Mozilla Developer Network."

UP/Intent Engine

UP is our Intent Engine for across Mozilla that helps us deliver personalization platforms for all of our products and services. Our 2014 strategy is to keep building our UP platform to make it available to the desktop, OS, services, and other products and have the bridges built this year that each product team has the ability to read/write to it. We will do limited tests in Q2/3/4 of this year to test different Intent Engine modules (such as tasks, discovery, personalization, ads). Within UP, we have a particular focus around Intentcasting and VRM.

Content Services Resources

Doc Searls' Intention Economy Book.

Check out our Official Content Services Blog.

Join our Interest mailing list ContentServices Distro

Reach out on email to the Content Services Team

Find us on IRC #mozcontent