# Why growth should be a continuous system, not a backlog you revisit

# Why growth should be a continuous system, not a backlog you revisit

## The short version

AI coding tools let a small team, or one person, ship in a weekend what used to take months. That moves the hard part of building a product. Shipping is no longer the bottleneck. Getting the right people to notice the product, and then to stay, is.

This essay argues that growth should therefore be a continuous system that learns from the product, its market and its customers. It should not be a backlog you revisit when the building stops. It is written for product managers and founding engineers who ship often and have no dedicated growth owner.

The framing follows the [Hockeysticky mission](https://hockeysticky.com/mission), which states: 'Growth should not be a backlog founders revisit when the building stops.'

## Building got easy, so attention got scarce

When many people can build a working product, the product alone stops being a signal. Two things follow:

- **Attention is scarce.** The hard part is getting the right people to notice you at all.
- **Stickiness is harder.** With alternatives one click away, customers can try a product, drift and leave before they see enough value.

This is the argument from the mission page. It is a position, not a measured result, and this post does not put numbers on it. See also **Building is easy now** *(existing post: insert link before publishing)*, which covers the shift in more depth.

## Why a backlog is the wrong shape for growth

A growth backlog is a list of ideas: write the post, try the channel, reach out to the creator. Lists like this tend to have the same weaknesses when product work competes with them:

- **They wait for a quiet moment.** Growth tasks get picked up when the roadmap allows, which is usually after a release has already gone unannounced.
- **They go stale.** The ranking of ideas reflects what was known when the list was written, not what the market or the product looks like now.
- **They have no memory.** Without a loop that records what worked, each task starts from zero.
- **They have no owner.** Small teams without a growth function often have nobody accountable for experiments.

These are the failure modes small product teams describe. The point is not that backlogs are bad. A list cannot do the work of a system that reads what changed, decides what to try, acts and remembers the result.

## The journey: Reach to Expand

Continuous growth also means looking past the first visit. The mission describes five stages of the customer journey:

| Stage | What it means |
|---|---|
| 01 Reach | Help the right people discover that the product exists. |
| 02 Onboard | Make setup clear, fast and easier to improve. |
| 03 Activate | Help the right customer reach the right value quickly. |
| 04 Retain | Turn first value into sustained, useful habits. |
| 05 Expand | Recognise when successful customers are ready for more. |

Awareness comes first, because nothing else matters if nobody arrives. Customers that stick come next. Each stage feeds the next, and what you learn at later stages (who activates, who retains, who expands) should shape who you try to reach.

Hockeysticky starts with Reach. Its [playbooks page](https://hockeysticky.com/playbooks) currently covers two goals, Awareness (getting found) and Trial (turning visitors into sign-ups). Onboard, Retain and Expand are listed there as coming, not available.

## The loop: read, propose, execute, learn

A continuous system replaces the list with a loop. Every release, market signal or result is a trigger for the next turn.

```mermaid
flowchart LR
  A[Read the release, product context and audience] --> B[Propose plays, channels and tools worth testing]
  B --> C[Execute within guardrails]
  C --> D[Learn from qualified visits and sign-ups]
  D --> A
```

1. **Read.** Start from what changed: the release, the product context and the audience. For a product manager or founding engineer, the release is already the best source of material.
2. **Propose.** Choose the plays, channels and tools worth testing, ranked by what to try first. Proposals are for a person to approve or dismiss.
3. **Execute.** Create, publish, reach out and launch. This is the step that most often stalls when growth competes with the roadmap, so the guardrails (what may be published, and what needs sign-off) matter.
4. **Learn.** Measure qualified visits and sign-ups by play, then feed the result into the next playbook. A loop with no learning step is just a faster backlog.

## What this looks like day to day

For a small team, a continuous system comes down to a few habits:

- **Treat each release as a growth moment.** Decide what the release is for, and who should hear about it, before it ships.
- **Review on a schedule.** A weekly routine that checks releases, traffic and market signals keeps the playbook current without a big planning session. See **the weekly growth review post** *(existing post: insert link before publishing)* for how to run one.
- **Define 'qualified' for your product.** Agree what a qualified visit means, set a baseline and measure against it, so that traffic alone is not mistaken for progress.
- **Set guardrails once.** Decide what can go out without review and what cannot, so approval is quick and not a bottleneck.
- **Write learnings down.** The next turn of the loop should start from the last one.

## Where Hockeysticky fits

Hockeysticky is positioned as an AI growth autopilot for early-stage products. It builds a tailored playbook for your product, updates it as you learn, and runs the tactics within your guardrails. The home page describes the same loop as four steps: Understand, Propose, Execute, Learn. The early playbooks focus on getting found, such as content you own, comparison pages, live conversations and customer outreach.

The playbooks page notes that its 'typical potential' ratings are a general editorial view for a solo founder or small team over about 90 days, not measured results. Treat the same caution as applying to this post: it describes an approach, not a proven outcome.

## Related reading

- **Building is easy now** *(existing post: insert link before publishing)*
- **Weekly growth review** *(existing post: insert link before publishing)*
- [Hockeysticky mission](https://hockeysticky.com/mission)
- [Growth playbooks](https://hockeysticky.com/playbooks)

## Try the loop

If you ship often and nobody runs growth, [join the Hockeysticky waitlist](https://hockeysticky.com/) for early access.