Hacking Growth
Sean Ellis & Morgan Brown · 2017
Editorial rating
- Evidence
- 7/10
- Actionability
- 8/10
- Originality
- 6/10
The thesis
Sustainable growth comes from cross-functional teams running rapid experiments across the entire customer journey - acquisition, activation, retention, and monetization - not from silver-bullet marketing tactics or viral gimmicks.
Who this is for
Growth marketers and product managers at startups past product-market fit, marketing leaders frustrated with traditional campaign-based approaches, and founders who've plateaued after initial traction and need systematic methods to reignite growth.
My favorite quote
If you're not running experiments, you're probably not growing.
Why it matters
Most companies treat growth as a function of effort - more ads, more content, more features. This reframes growth as a function of learning velocity. The company that learns fastest wins.
Do this
This week, run one small experiment on your highest-friction user touchpoint. Measure the result before scaling.
Start here
Before any growth experiments, validate you have product-market fit using the Sean Ellis Test: survey users asking "How would you feel if you could no longer use this product?" If fewer than 40% say "very disappointed," stop growth efforts and fix your product. Growth tactics on a leaky bucket just accelerate your burn rate.
Critical summary
Sean Ellis coined the term "growth hacking" and led early growth at Dropbox, LogMeIn, and Eventbrite. This book systematizes the approach that made those companies successful, moving beyond the hype around "hacks" toward a rigorous methodology.
The core framework is straightforward: build cross-functional growth teams, identify your "North Star" metric, map the customer journey (AARRR: Acquisition, Activation, Retention, Revenue, Referral), generate experiment ideas, prioritize using ICE scoring (Impact, Confidence, Ease), run rapid tests, and iterate. The book dedicates chapters to each stage of the funnel with specific tactics and case studies.
What it gets right
- Strong emphasis on product-market fit as a prerequisite - you can't growth-hack your way out of a bad product
- ICE prioritization framework is practical and widely adopted
- Clear structure for organizing growth teams and processes
- Good balance of strategic frameworks and tactical examples
What it misses
- "Growth hacking" terminology has become cringe-worthy, associated with spammy tactics
- Many examples are from 2010-2015 and feel dated (referral programs, email sequences)
- Assumes significant engineering resources for experimentation - less applicable to early-stage teams
- The line between "growth hacking" and "good product development" is blurry
Evidence is primarily case studies from successful companies, which carries survivorship bias. The authors acknowledge that most experiments fail, but the book highlights winners. Still, the systematic approach is sound even if specific tactics expire.
Key concepts
The Sean Ellis Test
"How disappointed would you be if you could no longer use this product?" 40%+ "very disappointed" indicates product-market fit.
North Star Metric
The single metric that best captures the core value your product delivers. All growth efforts should ultimately move this number.
ICE Scoring
Prioritization framework scoring ideas on Impact (1-10), Confidence (1-10), and Ease (1-10). Average the scores to rank experiments.
High-Tempo Testing
Run as many quality experiments as possible. Aim for 20-30 experiments per week at scale, minimum 2-3 for small teams.
Growth Loop
Self-reinforcing cycle where outputs from one user become inputs for acquiring the next (e.g., content creation, referrals, network effects).
Activation Metric
The behavior that correlates with long-term retention. Facebook's was "7 friends in 10 days." Find yours and optimize ruthlessly for it.
Core insights
-
Growth teams must be cross-functional
You need engineering, product, marketing, and data in the room. Growth lives at the intersection of product and marketing.
-
40% "very disappointed" is your green light
Don't invest in growth until you hit this threshold. Everything else is premature optimization.
-
Your activation metric is your most important discovery
Find the behavior that predicts retention and design your entire onboarding around achieving it.
-
Most experiments fail - that's the point
A 10% success rate is normal. The goal is learning velocity, not batting average.
-
Retention is the foundation
Acquisition fills a bucket; retention determines if it leaks. Fix retention before scaling acquisition.
Implementation steps
Today
- Send the Sean Ellis survey to your current users - calculate your "very disappointed" percentage
- Identify your current activation metric (or admit you don't have one)
This week
- Map your full customer journey across AARRR stages
- Generate 10 experiment ideas and ICE score them
This month
- Run 4-8 small experiments, documenting hypotheses and results
- Establish a weekly growth meeting rhythm with cross-functional stakeholders
Ongoing
- Target 2-3 experiments per week minimum
- Build an experiment backlog and maintain a "learnings library" for institutional memory
Suggested 30-day practice plan
An editorial application plan created by Monolithic Vault - an interpretation of the book's ideas, not part of the original book.
- Day 1
Run the Sean Ellis Test survey with current users
- Day 2
Map your customer journey and identify the highest-friction stage
- Day 3
Brainstorm 20 experiment ideas across all funnel stages
- Day 7
ICE score all ideas; select top 3 for week one experiments
- Day 14
Review week one results; launch next batch of experiments
- Day 21
Analyze patterns - which funnel stage is yielding the best learnings?
- Day 30
Establish ongoing growth meeting cadence and experiment velocity targets
Free PDF summary
Take this analysis with you: a designed two-page field-notes sheet with the thesis, my favorite quote, the key concepts and core insights, and the full 30-day checklist. Print it or keep it - free, no signup.
Go deeper
If this analysis earned your attention, the full book goes further than any summary can. The original is always the primary source.
