SuperAPI AI Directory

growth-hacking-skill

Marketing & growth

View repository

Updated 10-15 23:24

About this skill

Growth Hacking · Thinking Tool

"A growth hacker is a person whose true north is growth." — Sean Ellis

Activation Conditions and Trigger Words

  • Direct invocation: "Use growth hacking to analyze...", "Growth diagnosis...", "Run a growth experiment"
  • Semantic triggers: the user mentions declining retention, high customer acquisition cost, stagnant growth, or low conversion rate
  • Combined invocation: "First use growth hacking to find growth levers, then use Lean Startup to validate"

Method Framework Overview

The core of growth hacking is treating growth as a process that can be systematically experimented on; it anchors direction through a North Star metric, optimizes every layer of the full funnel, and finds the aha moment to drive a sustainable growth engine.

Core principles (3-7, each must be accompanied by ≥2 pieces of cross-domain evidence)

Principle 1: Growth is a process that can be systematically experimented on

One-sentence definition: Growth is not driven by one big move, but continuously driven by countless small experiments.

Cross-domain evidence:

  1. Cloud storage: Dropbox discovered the optimal parameters of its invitation mechanism through multiple rounds of A/B testing (Source: Dropbox Growth Study, 2010)
  2. E-commerce: Amazon continuously iterates its recommendation algorithm, and every change is supported by experimental data (Source: Collection of Bezos shareholder letters, 1997-2010)

How to apply: Establish a "hypothesis → experiment → measurement → decision" loop, completing at least 10 growth experiments per month.

Limitations: Experiments require a sufficient sample size. For small products (DAU<1000), experimental data is noisy and statistical significance is insufficient.

Principle 2: The North Star metric anchors direction

One-sentence definition: A single metric that reflects core user value, to which all growth experiments are aligned.

Cross-domain evidence:

  1. Video streaming: Netflix replaced subscriber count with viewing time as its North Star (Source: Netflix TechBlog, 2015)
  2. Messaging: WhatsApp used average daily messages sent rather than DAU as its North Star (Source: WhatsApp Blog, 2014)

How to apply: For every experiment, ask "If I win, will the North Star move?" Experiments that will not move it are deprioritized.

Limitations: Choosing the wrong North Star can lead to harmful optimization (e.g., using page views as the North Star leads to clickbait).

Principle 3: Each layer of the full funnel is optimized independently

One-sentence definition: Acquisition, activation, retention, monetization, and referral are not the same problem.

Cross-domain evidence:

  1. Social: Facebook discovered that the growth bottleneck was not acquisition but activation—the "10 friends in 7 days" rule (Source: Palihapitiya, Growth at Facebook, 2013)
  2. Image community: Pinterest's bottleneck was not acquisition but that new users had no Pins to interact with (Source: Pinterest Engineering Blog, 2013)

How to apply: Use the AARRR model to diagnose layer by layer, find the break point, and then focus optimization. Do not experiment on all five layers at the same time.

Limitations: Funnel layers influence one another; optimizing one layer in isolation may cause another layer to collapse.

Principle 4: The aha moment is the fuel of the growth engine

One-sentence definition: The moment a user first feels "this thing is really useful" determines whether they stay.

Cross-domain evidence:

  1. Cloud storage: Dropbox's Aha was the first successful file sync (Source: Houston, Dropbox Growth Story, 2011)
  2. Enterprise collaboration: Slack found that after a team sends 2,000 messages, it becomes an everyday necessity (Source: Butterfield, Slack internal data, 2014)

How to apply: After identifying the Aha Moment, reverse-engineer the new user onboarding so users reach that moment as quickly as possible.

Limitations: Not every product has a clear Aha Moment. The value of tool-type products is cumulative.

Principle 5: Data-driven hypotheses, not data-driven decisions

One-sentence definition: Use data to generate hypotheses and experiments to validate them, rather than letting data make decisions for you.

Cross-domain evidence:

  1. Search: Google's 20% time projects were not derived from data analysis, but progress was tracked with data (Source: Google Founders' Letter, 2004)
  2. Video platform: YouTube's switch from star ratings to like/dislike was based on a behavioral hypothesis, not a direct data requirement (Source: YouTube Creator Blog, 2010)

How to apply: Look at the data to find "what's off," propose a "why" hypothesis, and design experiments to validate it.

Limitations: Over-reliance on historical data will miss disruptive opportunities (e.g., pre-launch research for the iPhone did not support a touchscreen phone).

Operating Protocol (Agentic Protocol)

Step 1: Problem classification

Applicable signals:

  • The product has PMF but growth has stalled or slowed
  • User scale is considerable but retention/monetization has problems
  • Need to systematically find growth levers

Not applicable signals:

  • The product does not yet have PMF (Lean Startup applies)
  • B2B large-account sales model (growth hacking excels at self-serve growth)
  • Long-term decisions related to brand and reputation

Step 2: Growth hacking-style analysis

Research dimensions(each dimension must trace back to a core principle):

  1. North Star metric diagnosis: What is the team's North Star metric? Does it directly reflect user value?

    • Source principle: Principle 2
    • How to do it: Test by asking "Would users be willing to pay for this metric?"
  2. Funnel breakpoint localization: Which layer in AARRR has the lowest conversion rate? Where is the largest absolute improvement opportunity?

    • Source principle: Principle 3
    • How to do it: List the conversion rate for each funnel layer, and measure improvement opportunity by percentage × base
  3. Aha moment identification: At what moment do users first feel "this is really useful"?

    • Source principle: Principle 4
    • How to do it: Do retrospective analysis on active users—what did they do that made them become active?
  4. Growth experiment design: Design specific, measurable experiments based on the diagnosis

    • Source principle: Principle 1 + Principle 5
    • How to do it: Format: "If [do X], then [metric Y] will [change Z], because [reason]. Validate with [metric W]."

Step 3: Growth hacking-style output

  • North Star metric recommendation (including rationale for improvement)
  • Funnel diagnostic report (data for each layer + localization of the broken layer)
  • Aha Moment Hypothesis + Validation Plan
  • 3 Priority Experiment Designs

Applicability/Non-applicability Assessment

Problem Type Applicability Description
B2C User Growth Stagnation High Classic Scenario
Low New User Activation Rate High Growth hacking excels at optimizing the new user journey
Declining Retention Rate Medium Requires product improvements, not purely growth tactics
Low Brand Awareness Low Growth hacking is better suited for conversion optimization than brand building
Unvalidated PMF Low First validate with Lean Startup, then discuss growth

Classic Case Library

Success Cases

  1. Dropbox Invitation Mechanism(Cloud Storage/2009-2010)

    • Problem: High customer acquisition cost (CAC ~$300)
    • Method Application: Two-sided reward invitation mechanism, A/B testing button copy and reward amounts
    • Result: Signups grew 3900%, CAC approached zero
    • Source: Dropbox Growth Study; Houston, Startup Lessons Learned (2011)
  2. Airbnb Cross-platform Growth(Travel/2011)

    • Problem: Demand-side growth bottleneck
    • Method Application: Leveraged Craigslist's existing user base for one-click cross-posting
    • Result: Significantly expanded supply-side exposure
    • Source: Airbnb Growth Story; Chen, "Growth Hacker is the New VP Marketing"
  3. Hotmail Signature Growth(Email/1996)

    • Problem: Needed free customer acquisition
    • Method Application: Added "Get your free email at Hotmail" at the bottom of every outgoing email
    • Result: From 0 to 12 million users in 18 months
    • Source: Draper Fisher Jurvetson, Viral Marketing (2000)

Failure Cases

  1. Quibi's Growth Misstep Without an Aha Moment(Streaming/2020)
    • Problem: Short-form drama streaming had no PMF
    • Misuse Method: Invested huge marketing budgets in customer acquisition, but the product had no memorable Aha Moment for users
    • Lesson: The prerequisite for growth hacking is that the product has an Aha Moment. Doing growth without PMF accelerates failure
    • Source: Wall Street Journal, Quibi Shutdown Analysis (2020)

Misuse Detector (≥3 Misuse Patterns)

Misuse Signal Detection Logic Warning Message Recommended Action
Method and Problem Mismatch Large-scale growth investment when the product has no PMF "Doing growth for a product without PMF accelerates failure. First validate PMF with Lean Startup." Recommend Lean Startup
Skipping Key Steps Directly asking "how to do viral growth" without first diagnosing the funnel "First diagnose the funnel breakpoint before designing experiments. Doing viral growth directly may lead to a broken funnel." Guide back to funnel diagnosis
Complexity Exceeds Limits Simultaneously optimizing acquisition + activation + retention + monetization + referral "Optimizing the entire funnel at once makes effective attribution impossible. Focus on only one experiment in one layer at a time." Guide focus to a single layer

Honest boundaries (≥3 specific limitations)

  1. Sample size requirements: A/B testing requires a sufficient sample. Products with fewer than 1,000 daily active users lack statistical significance
  2. Not applicable to large B2B clients: Enterprise sales involves multiple decision-makers and long cycles, so a self-serve growth model is not applicable
  3. May breed spammy growth: Overfocusing on metrics may lead to clickbait, incentivized sharing, and other tactics that harm the long-term brand
  4. Data lag: Growth experiments reveal past behavioral patterns and cannot predict fundamental market changes

Research sources (primary sources must account for >50%)

# Source Type Primary/Secondary Weight
1 Ellis, Hacking Growth (2017) Book Primary High
2 Chen, The Cold Start Problem (2021) Book Primary High
3 Dropbox Growth Study (2010) Case study Primary High
4 Palihapitiya, Growth at Facebook talk (2013) Talk Primary Medium
5 Balfour, Growth Loops vs Funnels (2018) Article Primary Medium
6 Netflix TechBlog (2015) Technical blog Primary Medium
7 WSJ: Quibi Shutdown (2020) Report Secondary Medium

This Skill was generated by Forge Skill — Forging Thinking Tools Generated