Growth hacking. Hypothesis testing. Feature prioritization framework
Ani Aghababyan
Product Manager at SFL
+ 8 years | web, mobile
Growth hacking
Definition
Growth hacking is all about using innovative techniques to dramatically increase your traffic, conversion rate and user base with minimal expenditure—and thus grow your company quickly
Growth team
Growth hacking
PRODUCT
GROWTH
MARKETING
Growth hacking
Before
Now
RUNNING A LOT OF EXPERIMENTS
Timing
Timing
Days left to run �experiments �215 days�=�43 weeks
Intensity
1 hypothesis per week
< 30% hypotheses being approved
= 13 growth hacks per year
= 2-5% growth
Intensity
5 hypothesis per week
= 65 growth hacks per year
= 130% growth
< 30% hypotheses being approved
Scientific approach. Hypothesis
A specific, testable prediction. �It describes, in concrete terms, what you expect will happen in a certain circumstance.
Growth hypothesis�Action [X] will increase metrics [N] with [Y] value because of [Z].
Where do the hypotheses come from
Case studies
Examples
Advises
Researches
Reports
Ideas
Hypotheses
Hypothesis generation
Action | On plan selection page change “Buy now” button color from red to green |
Expected result | Payment page conversion will increase by 10% |
Justification | Bottle neck, conversion rate increase on this layer will significantly affect our target metrics + I love color green |
ICE Score - Estimation of hypothesis
ICE Score
ICE Score
Impact�1 - 10
The potential gain from the feature, presented in terms of business/strategic objectives
�1 : No impact on revenue (or other target business metric)�2 – 5: Minimal impact on revenue (or other target business metric)�6 – 8: Definite impact on revenue (or other target business metric)�9 – 10: Significant impact on revenue (or other target business metric)
ICE Score
Confidence�1 - 10
The level to which the team feels the feature is understood/scoped and possible to do�
1 – 3: High risk (many unknowns and little supporting evidence about the potential feature) �4 – 7: Medium Risk (good information is available, but the blueprint for execution is still unclear)�8 – 10: Low/mitigated risk (plenty of customer feedback and data points backing the feature)
ICE Score
Ease�1 - 10��The degree of complexity involved in completing the feature (in simple terms – how long it will take to finish)��1 – 2: One month or more�3 -5 : One to two weeks�6 – 7: Less than a week�8 – 10: Less than one day
Score and Prioritization
Score�I + C + E = XX (Sum of impact, confidence and ease)
Team member | 1 | 2 | 3 | … |
Impact | 8 | 8 | 8 | … |
Confidence | 7 | 5 | 8 | … |
Ease | 2 | 7 | 8 | … |
Score | 17 | 20 | 24 | … |
Priority |
61 |
Other frameworks
Iconic Growth Hacking Examples
Thank you!
Ani Aghababyan
ani.aghababyan@sflpro.com