Growth Team: Difference between revisions
| Line 1: | Line 1: | ||
== Who are we? == | == Who are we? == | ||
The growth team is a small group of cross-functional people who | The growth team is a small group of cross-functional people who assume that Mozilla can continuously learn and do better. We question norms, expose opportunities, and are data driven to improve experiences that resonate with our target audience that ultimately further Mozilla's [http://www.mozilla.org/mission/ mission]. Our immediate focus will be short-term A/B tests and changes to our acquisition funnels and product experiences to drive Firefox growth. | ||
Team members: | Team members: | ||
Revision as of 16:57, 31 October 2014
Who are we?
The growth team is a small group of cross-functional people who assume that Mozilla can continuously learn and do better. We question norms, expose opportunities, and are data driven to improve experiences that resonate with our target audience that ultimately further Mozilla's mission. Our immediate focus will be short-term A/B tests and changes to our acquisition funnels and product experiences to drive Firefox growth.
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)
- Larissa Shapiro (Community Building)
- Matt Grimes (User Advocacy)
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.
- 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: