A growth process is the holy grail of every growth hacker’s work effectiveness and efficiency. In January 2017 I am working on 12 projects with 10 different teams. I cannot imagine handling this workload without leaning on a proven growth framework and following the growth process almost religiously. A growth team needs to be both, creative and exploratory, as well as highly efficient and organized.
“It is not so much about a specific tactic when you are doing this growth hacking, it is about this continuous process of experimentation and ideas and really building a culture around experimentation and ideas.”
The Growth Process
There are many interpretations of a growth process, most likely dating back to what Sean Ellis presented in 2013-2014 😏. However, since I learned the most about the growth process at Growth Tribe, let me present their growth process bellow.
How to execute the growth process?
The backbone of implementing growth process is growth sprint. We are all borrowing the ideas from lean methodologies & agile frameworks here, growth teams decide to have weekly or biweekly sprints. The continuity of these sprints is of incredible value.
Here are 3 resources/techniques that I find incredibly helpful:
- Weekly growth sprints (here is how you run these meetings) & daily sprints
- Trello board for running growth ops (based on this framework)
- Supporting documentations such as Growth Deck (Framework by Sujan Patel)
- Hypothesis spreadsheets to fee the idea backlog (Hypothesis 1-Experiment-Learnings/Insights-Hypothesis 1.1)
Other useful and interesting tools/ideas:
- Brian Balfour’s resources rock: Check out The Scientific Method: How to Design & Track Viral Growth Experiments and how to focus on insights
- Sean Ellis recommends prioritizing the idea backlog based on ICE score & focus area
- BRASS/PIES framework by Growth Tribe: Great for idea prioritization & specifying experiments
- For weekly growth meetings Sean Ellis recommends the following structure:
- 15 minutes: Growth metrics, issues and opportunities
- 10 minutes: Review the result of the previous week’s tests
- 15 minutes: Share key lessons learned from those tests
- 15 minutes: Identify new tests for this week
- 5 minutes: Review backlog of idea
Tweak everything to fit your needs
Each growth project and each growth team are unique. With some teams, we use dev SCRUM to manage our growth process. With others, we have extensive experiment design sheets, which are frequently presented to the management and others prefer to have laissez-faire structure. I also work in one team, where we have an expensive growth hacking reading list on our Growth Framework (ops) Trello board, which elps us feed the ideas backlog section 😂. I guess the only underlying element that needs to be well awarded of as well as well documented are the learnings/insights of the growth process. Especially in the early stages, in which the one metric that matters will most likely be the number of learnings, it is of vital importance to build future experiments on based on previous experiments’ learnings. I’ve already written about the early stage startup growth hacking experiment design.
Excellent. Get in touch.