- 1 Who are we?
- 2 What we do
- 3 What are our goals?
- 4 Our Tools
- 5 Our Process
- 6 Define what is success and how it can be measured
- 7 Develop insights, identify bottlenecks, or constraints in our user experiences
- 8 Create a hypothesis based on an identified bottleneck or constraint
- 9 Prioritize backlog of tests
- 10 Perform test
- 11 Identify and communicate key learnings and define next steps
- 12 Repeat
Who are we?
The growth team is a group of Mozillians who evaluate the current state of Firefox's acquisition and retention pipelines, develop growth hypotheses, and execute on scientific test plans to determine if possible opportunities lead to positive growth of Firefox. We have core members who lead the team and then supporting cross-functional members who bring insights and expertise on all touch-points of the Firefox experience. We believe that any test, regardless of the result, will lead to a continuous learning environment and a better product experience that will ultimately drive growth.
Core team members
- Chris More (Team lead & Growth Marketer - Desktop & Web Focus)
- Alex Davis (Firefox Accounts/Sync Product Manager)
- Justin Crawford (Growth Marketer)
- TBD (Growth Engineer)
What we do
- Define and evaluate effectiveness of Firefox growth models & funnels
- Develop hypotheses for growth opportunities
- Develop test plans & create prototypes
- Run scientific tests & analyze results
- 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.
- Google Analytics
- Metrics and reporting about website user experiences.
- A/B testing of different web pages and downloads.
- Firefox product data
- Firefox Health Report
- ADI pings
- Funnelcake builds
- Surveying users on key web pages.
- Real people testing different experiences with videos and data of their test.
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
Identify and communicate key learnings and define next steps
We do growth testing on various touchpoints across Mozilla's websites, products, and services.
- IRC: #growth on irc.mozilla.org
- Slack: #growth
- Submit your growth opportunity idea