---
title: What Is Growth Marketing — RGM Training
url: https://realgrowthmatters.com/training/growth-marketing-foundations/what-is-growth-marketing/
updated: 2026-06-10
source_html: https://realgrowthmatters.com/training/growth-marketing-foundations/what-is-growth-marketing/
---

[Home](../../../index.html) › [Training](../../index.html) › [Growth Marketing Foundations](../index.html) › What Is Growth Marketing

RGM° · Training

# What Is Growth Marketing

A discipline, not a job title. Origins, the four core ideas, growth vs traditional marketing, where growth fits in an org, and when it applies.

### What you will learn

1. [Why growth marketing is a discipline, not a job title](#why)
2. [Origins: Sean Ellis and the growth hacker era](#origins)
3. [The four core ideas of growth marketing](#core)
4. [Growth marketing vs traditional marketing vs product marketing](#vs)
5. [How growth fits in an org](#org)
6. [The growth mindset: hypothesis-experiment-learn](#mindset)
7. [When growth marketing applies and when it doesn't](#fit)
8. [Advanced playbook](#advanced)
9. [Common mistakes](#mistakes)
10. [Operating checklist](#checklist)

## Why growth is a discipline

Growth marketing emerged in the 2010s as software companies needed a discipline that bridged product, marketing, and analytics — with experimentation at the core. It's not just marketing-with-better-tools. It's a way of operating that treats every part of the customer journey as a system to be measured and improved.

The mistake some teams make: treat growth as a job title, hire one person, expect transformation. The reality: growth is an operating model that requires cross-functional commitment.

## Origins

- Sean Ellis coined "growth hacker" in 2010 describing the role he'd played at Dropbox, LogMeIn, and Eventbrite.
- The premise: founders had built products; they needed someone whose only goal was growth, with permission to experiment across product, marketing, and ops.
- Andrew Chen, Brian Balfour, and others extended the discipline through writing, frameworks, and Reforge programs.
- By the mid-2010s, growth teams existed at most consumer tech companies; by the late 2010s, B2B SaaS too.
- By 2024+, growth has matured: less "hacking," more rigorous experimentation, MMM, and customer-data discipline.

## The four core ideas

- **Full-funnel ownership.** Growth touches acquisition, activation, retention, referral, monetization — not just top-of-funnel.
- **Experimentation as default.** Hypotheses tested rigorously; data drives decisions; failure surfaces learning.
- **Cross-functional collaboration.** Marketing, product, design, engineering, data all contribute.
- **Unit economics discipline.** CAC, LTV, payback, retention curves — every growth tactic evaluated against these.

## Growth vs traditional marketing vs product marketing

| Discipline | Primary focus |
| --- | --- |
| Traditional marketing | Brand, demand gen, top-of-funnel acquisition |
| Growth marketing | Full-funnel; experimentation; unit economics |
| Product marketing | Product positioning, launches, customer enablement |
| Demand gen | B2B lead generation, pipeline contribution |
| Performance marketing | Paid channels at scale; ROAS optimization |
| Lifecycle marketing | Activation, retention, expansion via owned channels |

The lines blur in modern orgs. Growth often includes performance, lifecycle, and product marketing components.

## How growth fits in an org

- **Embedded in product (PLG companies).** Growth team works inside product org; tests are product features.
- **Marketing-led (most B2C).** Growth reports to CMO; coordinates with product.
- **Standalone GM with mixed reporting.** Head of Growth reports to CEO or COO; coordinates marketing + product.
- **Revenue-team integration (B2B trend).** Growth, sales, marketing under CRO or revenue ops leader.

## The growth mindset

1. **Hypothesis.** Specific predicted outcome with reasoning.
2. **Experiment.** Test designed with statistical rigor.
3. **Measure.** Outcome compared against prediction.
4. **Learn.** What did this tell us? What changes next?
5. **Repeat.** Cycle continues with new hypotheses informed by learning.

Mature growth teams run 5–20+ experiments per month. Most fail. The compound learning across experiments is the value.

## When growth applies and when it doesn't

### Growth works when

- Product-market fit exists (without it, growth amplifies churn).
- Sufficient traffic and conversion volume for statistical testing.
- Unit economics support scalable acquisition.
- Leadership commits to data-driven decisions, not opinion-driven.
- Cross-functional collaboration is feasible.

### Growth doesn't work when

- Product-market fit unclear; experiments scale a broken funnel.
- Volume too low for statistical inference; tests inconclusive.
- Unit economics broken; more growth = more loss.
- HiPPO culture; data doesn't change decisions.
- Functional silos prevent collaboration.

## Advanced playbook

- **Growth manifesto.** Documented operating principles; what we believe and how we work.
- **Quarterly growth strategy.** Specific priorities, channels, experiments aligned with business goals.
- **Cross-functional growth squad.** PM + designer + engineer + analyst + marketer working together on growth problems.
- **Experimentation cadence.** Weekly tests for fast-moving programs; monthly for slower-cycle.
- **Learning archive.** Searchable record of past experiments; institutional memory.
- **Growth metrics tree.** North Star + driver metrics + leading indicators all connected.
- **Build vs buy decisions.** When to build internal tools, when to use vendor.
- **Investment in instrumentation.** Without data, no growth. Data engineering matters.
- **Growth maturity model.** Quarterly assessment of where the team stands on key capabilities.
- **Annual retrospective.** What worked? What didn't? What should change?

## Common mistakes

- Hiring a growth hacker before product-market fit.
- Growth treated as job title, not operating model.
- Top-of-funnel optimization only; ignoring retention.
- Tactics without strategy; experiments without priority.
- No unit economics discipline; growth at any cost.
- Functional silos prevent cross-functional collaboration.
- Opinion-driven decisions despite data infrastructure.
- Learning archive missing; lessons forgotten.
- No instrumentation; data unavailable for tests.
- Growth team disconnected from product.
- Following someone else's playbook; not adapted to your context.
- No quarterly strategy; growth becomes random tactics.

## Operating checklist

- Growth manifesto documented
- Quarterly growth strategy
- Cross-functional growth squad structure
- Experimentation cadence (weekly to monthly)
- Learning archive maintained
- Growth metrics tree from North Star down
- Unit economics tracked alongside acquisition metrics
- Instrumentation investment ongoing
- Full-funnel ownership; not top-of-funnel only
- Annual retrospective and re-strategy
- Leadership commitment to data-driven decisions
- Growth maturity assessed annually

## Sources and further reading

- Sean Ellis — founder of GrowthHackers; original growth hacker
- Andrew Chen — growth essays and Andreessen Horowitz writing
- Brian Balfour, Reforge — growth model frameworks
- Hiten Shah — product and growth writing
- Casey Winters, Reforge — growth model and consumer growth
- Lenny Rachitsky — growth and product newsletter
- Eric Ries, "The Lean Startup"
- Alistair Croll and Benjamin Yoskovitz, "Lean Analytics"
- Reforge growth programs and library
- GrowthHackers community archives
- Andrew Chen, "The Cold Start Problem" (book)
- Elena Verna — PLG and growth strategy

---

Part of the [Growth Marketing Foundations](../index.html) series.