|
|
| Line 12: |
Line 12: |
| ===Core team members=== | | ===Core team members=== |
|
| |
|
| * [https://mozillians.org/en-US/u/cmore/ Chris More] (Team lead & Growth Marketer - Desktop & Web Focus) | | * [https://mozillians.org/en-US/u/cmore/ Chris More] (Firefox Product lead, Growth & User Onboarding) |
| * [https://mozillians.org/en-US/u/adavis/ Alex Davis] (Firefox Accounts/Sync Product Manager) | | * [https://mozillians.org/en-US/u/adavis/ Alex Davis] (Firefox Accounts/Sync Sr. Product Manager) |
| * [https://mozillians.org/en-US/u/hoosteeno/ Justin Crawford] (Growth Marketer) | | * Product Manager, Screenshots & Send (coming soon) |
| * TBD (Growth Engineer)
| |
|
| |
|
| == What we do == | | == What we do == |
| Line 24: |
Line 23: |
| * Run scientific tests & analyze results | | * Run scientific tests & analyze results |
| * Apply learnings to all touch-points in the Firefox experience | | * Apply learnings to all touch-points in the Firefox experience |
|
| |
| == 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.
| |
| * At least 1 test running every week to promote continuous learning.
| |
|
| |
| == Our Tools ==
| |
|
| |
| *Google Analytics
| |
| **Metrics and reporting about website user experiences.
| |
| *Optimizely
| |
| **A/B testing of different web pages and downloads.
| |
| *Firefox product data
| |
| ** Firefox Health Report
| |
| ** ADI pings
| |
| ** Funnelcake builds
| |
| ** Telemetry
| |
| *SurveyGizmo
| |
| **Surveying users on key web pages.
| |
| *UserTesting.com
| |
| **Real people testing different experiences with videos and data of their test.
| |
|
| |
| == Our Process ==
| |
|
| |
| After we define a growth model for Firefox, we will use the following process for optimization and growth experiments.
| |
|
| |
| # Define what is success and how it can be measured
| |
| # Develop insights, identify bottlenecks, or constraints in our user experiences
| |
| # Create a hypothesis based on an identified bottleneck or constraint
| |
| # Prioritize backlog of tests
| |
| # Perform test
| |
| # Identify and communicate key learnings and define next steps
| |
| # Repeat
| |
|
| |
| We do growth testing on various [[Growth_Team/Touchpoints|touchpoints across Mozilla's websites, products, and services]].
| |
|
| |
| == Get Involved ==
| |
|
| |
| Collaboration:
| |
|
| |
| * IRC: #growth on irc.mozilla.org
| |
| * Slack: #growth
| |
| * [https://docs.google.com/forms/d/1r-sGtOPEKfDe-FzPYMFDL4lyu_KnOdbGU6LA0ggTA98/viewform?usp=send_form Submit your growth opportunity idea]
| |