Growth Team: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 38: Line 38:
| P1 || Yahoo Firefox Promotions and Experiments || Not started || Chris More & Eric Petitt
| P1 || Yahoo Firefox Promotions and Experiments || Not started || Chris More & Eric Petitt
|-
|-
| P2 || Firefox Stub Installer Content Improvements || Documenting || Michael Verdi
| P2 || [https://bugzilla.mozilla.org/show_bug.cgi?id=1103164 Firefox Stub Installer Content Improvements] || Documenting || Michael Verdi
|}
|}



Revision as of 20:43, 7 January 2015

Who are we?

The growth team is a group of cross-functional Mozillians who believe that experiments and testing will lead to a continuous learning environment. We question norms, expose opportunities, and are data driven to improve the Firefox experience.

Core team members:

Supporting team members:

What are our goals?

Overall, we strive to:

  • Learn something from each experiment we perform.
  • Through learning, grow the usage of the Firefox product.
  • With the additional usage, spread the Mozilla mission further.

Priorities for Q1 2015:

Priority Project Status Owner
P1 Firefox Growth Dashboards 1.0 Requirements Gathering Gareth Cull
P1 Firefox First Run Improvements Requirements Gathering Chris More
P1 Yahoo Firefox Promotions and Experiments Not started Chris More & Eric Petitt
P2 Firefox Stub Installer Content Improvements Documenting Michael Verdi

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:

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

Templates: