Growth team meeting, which should generally be held once a week, provide a rigorous forum for managing the team’s testing activity, reviewing results, and determining which growing hacks to try next. The standing meeting practice, which is a well-established part of the agile software development method, can be easily adapted for growth hacking.
Involve the right people
Growth team meetings are decision-making meetings and diverse groups are better at making decisions because they bring different views to the table. Growth teams should bring together members who have a deep understanding of the strategy and business goals, those with the expertise to conduct data analysis, and those with the engineering chops to implement changes in the design, functionality, or marketing of the product and program experiments to test those changes. If your decision makers are too similar (in role, seniority, or perspective), your decision and growth will suffer.
Come ready to decide
During the week all members should submit ideas using the existing growing hack pipeline. In preparation for this meeting, the growth lead review a summary of the findings so far and suggested experiments. Members who were evaluating experiments prepare the results to share.
Growth team meeting minutes
METRICS REVIEW AND UPDATE FOCUS AREA (15 MINUTES)
Reviews the latest data for the North Star metric and the other key growth metrics, such as progress on short-term growth objectives, OKR, Churn rate, LTV and others. This helps get everyone up to date on whether things are going well or not, what is working in the business, and what could be better.
Additionally, the following set of information should be highlighted:
- Improvements in metrics resulting from experiments.
- Drop-offs in performance and a review of issues that are holding back growth.
- What part of the user experience or growth lever is the team focused on?
- Are there any short-term objectives that the team needs to work toward?
LAST WEEK’S TESTING ACTIVITY REVIEW (10 MINUTES)
A retrospective of a previous week results that include assessment of the number of launched and not launched experiments. Start a discussion that should explain why experiments were postponed.
KEY LESSONS LEARNED FROM ANALYSED EXPERIMENTS (15 MINUTES)
The growth lead and data analyst, together with the experiment owners discuss the preliminary results from each launched experiment. It’s time for the collaborative discussion about further ways of analysis, assessment of the experiment and its implications for further actions.
SELECT GROWTH EXPERIMENTS FOR CURRENT CYCLE (15 MINUTES)
Decide on the nominations for the next set of experiments to be launched. Each member gives a brief overview of the submitted ideas, which is followed by a discussion among the team about the merits of those experiments. The experiments are then assigned to team members who would be an owner of the experiment and responsible for getting the test launched. Members from different teams should be engaged (for example developers, marketing, design team members)
CHECK GROWTH OF IDEA PIPELINE (5 MINUTES)
Review the backlog of the submitted experiments waiting for consideration. If there are not many left, inspire the team to add more ideas in the coming weeks.
With a little planning, a basic understanding of group dynamics, and adopted scoring system for new experiments, your team can make this weekly growth meetings a key to successful growth hacking. Save more time on writing and focus on what’s important with real-time meeting transcription by Tactiq.io