Growth Hacking
グロース・ハッキング
Growth Hack is a rapid growth experiment loop for deciding which growth hypothesis deserves the next experiment and which should be stopped.
What it means
Growth Hack is a disciplined experiment loop that searches for scalable growth levers across acquisition, activation, retention, referral, and monetization. In practice it is used to decide which growth hypothesis deserves the next experiment and which should be stopped by reading experiment velocity, activation lift, CAC movement, retention effect, channel quality, and learning rate.
When it helps
Growth Hack moves discussion from preference to evidence by putting experiment velocity, activation lift, CAC movement, retention effect, channel quality, and learning rate on the same decision table. Growth Hack makes the decision of which growth hypothesis deserves the next experiment and which should be stopped manageable with an owner, timing, and review trigger. Growth Hack reveals whether acquisition, retention, pricing, quality, or risk should dominate the next decision.
- Growth Hack moves discussion from preference to evidence by putting experiment velocity, activation lift, CAC movement, retention effect, channel quality, and learning rate on the same decision table.
- Growth Hack makes the decision of which growth hypothesis deserves the next experiment and which should be stopped manageable with an owner, timing, and review trigger.
- Growth Hack reveals whether acquisition, retention, pricing, quality, or risk should dominate the next decision.
How to use it
- Treat it as a rapid growth experiment loop, not a descriptive label.
- Use experiment velocity, activation lift, CAC movement, retention effect, channel quality, and learning rate to fix the evidence used in the decision.
- Translate which growth hypothesis deserves the next experiment and which should be stopped into an owned next decision.
- Compare nearby terms so the right tool is used in the right situation.
- After movement appears, review customer impact and risk in the same cadence.
Example
A team uses Growth Hack after noticing that discussion keeps producing activity without a clear management decision. For Growth Hack, the team defines the intended outcome, names one accountable owner, and lists the evidence that would change the decision. During the Growth Hack review, the team compares current evidence with the recorded boundary, adjusts the scope, and assigns follow-through work. The Growth Hack record now helps people see why the action was chosen, what risk was accepted, and when the decision should be revisited.
Compare with
Separate nearby terms so decisions do not blur together. Go-to-market strategy | Sets the market motion | Growth hacking tests narrow levers inside that motion CAC | Measures acquisition cost | Growth experiments must watch whether CAC quality improves Product usage activation | Measures early value | Growth hacks that hurt activation are usually false wins
| Metric | Difference | Why read together |
|---|---|---|
| Go-to-market strategy | Sets the market motion | Growth hacking tests narrow levers inside that motion |
| CAC | Measures acquisition cost | Growth experiments must watch whether CAC quality improves |
| Product usage activation | Measures early value | Growth hacks that hurt activation are usually false wins |
Common mistakes
- Growth Hack cannot be judged from one metric or slogan alone.
- Improving Growth Hack is not a good decision if the guardrail metrics deteriorate.
- Growth Hack is not settled once; it should be reviewed when the evidence changes.
Frequently asked questions
Is growth hacking random experimentation?
No. It needs a hypothesis, target metric, guardrail metric, owner, and decision rule.
What is the biggest risk?
Optimizing top-of-funnel volume while damaging retention or unit economics.
When should an experiment scale?
Scale only after the lift survives quality, retention, and cost checks.