Growth Team: Difference between revisions
Line 47: | Line 47: | ||
|} | |} | ||
== | == Our Tools == | ||
*Google Analytics | *Google Analytics |
Revision as of 03:08, 18 February 2015
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)
- Gareth Cull (Web Analytics)
- Michael Verdi (Firefox UX)
Supporting team members
- Winston Bowden (Firefox Product Marketing)
- Eric Petitt (Firefox Product Marketing)
- Jon Petto (Web Development)
- Javaun Moradi (Firefox Product Management)
- Sevaan Franks (Firefox UX)
- John Jensen (Metrics)
- Matt Grimes (User Advocacy)
- Chris Karlof (Firefox Accounts)
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 | Creating front-end templates | Gareth Cull |
P1 | Firefox First Run Improvements | Finalizing UX and content | Chris More |
P1 | Yahoo Firefox Promotions and Experiments | Setting up testing infrastructure | Chris More & Eric Petitt |
P2 | Firefox Stub Installer Content Improvements | Researching | Michael Verdi |
P2 | Upgrade www.mozilla.org to Universal Analytics & Tag Manager | Planning | Gareth Cull |
P2 | Defining the Firefox Growth Model | Researching | Chris More |
Our Tools
- 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.
- Define what is success and how it can be measured
- 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
How can I get involved?
Collaboration:
- Daily stand ups @ 9:15am PST via Chris More's vidyo room, etherpad, and IRC
- Bi-Weekly backlog triage meetings on Mondays @ 9am PST.
- IRC: #growth on irc.mozilla.org
- Bugzilla: Bugs tagged with fxgrowth in the whiteboard field.
- Public Action Item Board
Dashboards: (ask cmore for access if you don't have access)
Templates: