Hacking Growth Book Summary

To identify your product's core value and "aha moment" that turns users into devoted fans, analyze user behavior data to find:

• The tipping point number of actions that engaged users take vs casual ones (e.g. Following 30 people on Twitter, adding 7 friends in 10 days on Facebook)
• The common actions that retained users take but lost users don't
• The key product features or parts of the user experience that most engage your fans

Then focus your user experience on driving more users to that aha moment as quickly as possible. For example, when Facebook identified adding 7 friends in 10 days as a key tipping point, they redesigned their new user experience to focus people on adding friends upfront.

Section: 1, Chapter: 2

To enable high velocity testing, create a growth idea pipeline that captures experiment ideas and follows these principles:

1. Empower everyone on the growth team to submit ideas in a standard format: Idea name, description, hypothesis, and metrics to track.
2. Use the ICE prioritization score (Impact, Confidence, Ease) to objectively rank and prioritize ideas. Rate each idea on a 1-10 scale for each.
3. Each week, review top ideas and decide which to resource. Assign an owner to each chosen experiment.
4. Run multiple experiments per week. More experiments = faster learning. But ensure each is well-constructed to give clear results.
5. Track all experiments and share learnings broadly. Build a knowledge base of past tests anyone can access. Be sure to also track failed experiments!

Section: 1, Chapter: 3

Chapter 4 lays out the four key steps in the growth hacking process:

1. Analyze: Review macro metrics, dive deep into user behavior data, and gather insights from customers via surveys/interviews to generate experiment ideas.
2. Ideate: Encourage the team to brainstorm bold experiment ideas aimed at improving a North Star metric. Create an idea pipeline and rank using the ICE method.
3. Prioritize: Each week, review top experiment ideas and prioritize based on impact, effort and company goals. Assign an owner to each.
4. Test: Launch experiments quickly, ensuring each is constructed to give clear, statistically significant results. Track results obsessively.

Section: 1, Chapter: 4

To keep experiments organized and surface key insights, document each test with the following details:

• Name: A concise label to refer to the test
• Description: What change is being made and who will see it (e.g. a 50/50 split test of two landing page headlines for new visitors)
• Hypothesis: The expected result and why (e.g. Changing the headline to emphasize key benefit X will increase signups by 10%)
• Metrics: The key metrics to track (signups, click-through rate, retention rate, etc.). Include a primary metric that determines success.
• Launch details: When it started/ended, sample size, anything that might affect results
• Results: The actual metric changes seen in the test. Note statistical significance.
• Conclusions: Insights gleaned and ideas for follow-up experiments to further optimize

Section: 1, Chapter: 4