Growth Team

	THIS PAGE IS A WORKING DRAFT
	The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly. If you have any questions or ideas, please add them as a new topic on the discussion page.

Who are we?

The growth team is a small group of cross-functional people who are never satisfied that Mozilla has done their best. We question norms, expose opportunities, and are data driven to improve experiences that resonate with our target audience that ultimately further Mozilla's mission.

Team members:

• Eric Petitt (Business Owner)
• Chris More (Program Owner)
• Winston Bowden (Product Marketing)
• Gareth Cull (Web Analytics)
• Jon Petto (Web Development)
• Sevaan Franks (UX)
• John Jensen (Metrics)
• Michael Verdi (Support)

What are our goals and key milestones?

We are currently focused on the Firefox desktop and Firefox Android products with our growth testing and optimization work. In the future, we may include other products, but for now we are going to be working with Firefox opportunities.

• 8/19/2014: Kick-off Growth Team with stakeholders
• 8/27/2014: Triaged opportunity backlog
• 8/28/2014: Start iterative testing process
• 10/15/2014: Attribute optimization to 1.25% growth in Firefox monthly hourly usage

What tools and data are available

• Google Analytics
  • Metrics and reporting about website user experiences.
  • Google Content Experiments for A/B testing
  • A/B testing of different web pages and downloads.
• Optimizely
  • Quick A/B and funnel testing of different web page content and layouts
• SurveyGizmo
  • Surveying users on key web pages.
• UserTesting.com
  • Real people testing different experiences with videos and data of their test.
• Firefox product data
  • Firefox Health Report
  • ADI pings
  • Funnelcake builds
  • Telemetry

What is our process?

We will be using the following steps for how we approach our optimization and growth experiments.

1. Define what is success and how it can be measured
2. Identify bottlenecks or constraints in our user experiences
3. Create a hypothesis based on an identified bottleneck or constraint
4. Prioritize backlog of tests
5. Perform test
6. Identify and communicate key learnings and define next steps
7. Repeat

How can I get involved?

Collaboration:

• Daily stand ups (coming soon)
• Weekly check-in meeting
• IRC: #growth on irc.mozilla.org

Dashboards:

(ask cmore for access if you don't have access)

• Opportunity Backlog
• Testing Results

Templates:

• Test plan template (coming soon)
• Test results template (coming soon)