# What is a growth playbook, and how is it different from a template library?

# What is a growth playbook, and how is it different from a template library?

## The short answer

A growth playbook is a plan for how one specific product will get found, win sign-ups and, later, keep customers. It is built around the product, its audience and the evidence available, it ranks what to try first, and it is revised as results and market signals come in.

A template library is a collection of reusable formats, such as a launch checklist, an email sequence or a content calendar. Templates can be useful, but they are written for nobody in particular. Choosing which ones fit, in what order, is left to you.

## What a growth playbook contains

A useful playbook answers a handful of practical questions for one product:

- **Goal.** What is this play meant to achieve? For early-stage products the first goals are usually awareness (getting found) and trial (turning visitors into sign-ups).
- **Plays.** Which tactics are worth testing, for example content you own, comparison pages, live conversations or customer outreach?
- **Order.** Which play comes first, and why?
- **Key metric.** How will you tell whether the play is working, for example qualified visits and sign-ups from search?
- **Fit.** Does the play suit your motion (B2B, B2C and so on), your budget and the tools you already use?
- **Review.** When will you revisit the plan, and what will change it?

The [Hockeysticky playbooks page](https://hockeysticky.com/playbooks) describes each of its playbooks in these terms: a key metric, a motion fit and the tools it needs.

## Growth playbook vs template library

| | Template library | Tailored growth playbook |
|---|---|---|
| Built for | Anyone | One product and its audience |
| Starting point | A format or tactic | Your product, audience and evidence |
| Prioritisation | You choose what to try first | Ranked by what to try first |
| Over time | Static until someone rewrites it | Updated as you learn |
| Main output | Formats to fill in | A sequence of plays with a metric for each |
| Your effort | Pick, adapt and apply each template | Review and approve the plan, then run it |

The difference is mostly about decisions. A template tells you how to do a tactic. A playbook tells you which tactics suit this product right now and what to look at to judge them.

## Why the ranking matters

Solo founders and small teams rarely lack ideas. The usual problem is that growth tactics are scattered and it is hard to say which one to try first. A long list of options can feel like progress while nothing ships.

A ranked playbook narrows the choice. The ranking should come from things you can point to, such as:

- What the product does and who it is for.
- Where the audience already looks for answers or discusses the problem.
- What you can realistically run with your time, tools and budget.
- What you have already learned from earlier attempts.

A ranking is a hypothesis, not a guarantee. Any order of plays can turn out wrong, which is why the next section matters.

## Why a playbook has to keep changing

A product, its market and its audience all move. A playbook written once and left in a document goes stale. A living playbook runs as a loop:

```mermaid
flowchart LR
  A[Understand product, audience and evidence] --> B[Rank plays by what to try first]
  B --> C[Run the top plays]
  C --> D[Measure the key metric for each play]
  D --> E[Update the playbook]
  E --> B
```

Each new release, market signal or result is a reason to revisit the ranking. This is the main practical difference from a static template: the output of one round becomes the input of the next.

## How to build a basic growth playbook yourself

1. **Write down the product and audience.** One or two sentences on who it is for and the problem it solves.
2. **Pick one goal.** For a product with few users, getting found is often the first goal. Sign-ups come next.
3. **List candidate plays.** Examples include blog and docs content, comparison pages, joining relevant conversations and personal outreach.
4. **Score each play.** Use simple criteria: fit with your audience, effort, cost and how soon you would see a first signal.
5. **Choose a small number to start.** Rank them and run the top one or two.
6. **Set one key metric per play.** Qualified visits and sign-ups are easier to act on than raw traffic.
7. **Schedule a review.** Revisit the ranking regularly and after each release.

No outcome is promised by following these steps. They only make the decisions explicit so you can test them.

## Where Hockeysticky fits

Hockeysticky is an AI growth autopilot for early-stage products. It builds a tailored growth playbook around your product, keeps it updated as you learn, and runs the tactics within your guardrails. Its playbooks page notes that any "typical potential" shown is a general editorial view for a solo founder or small team over about 90 days, not a measured result.

## Frequently asked questions

**Is a growth playbook the same as a growth strategy?**
They overlap. A strategy sets direction and goals. A playbook turns that direction into specific plays, an order to try them in and a metric for each.

**Can a template library be part of a playbook?**
Yes. A playbook can use templates as building blocks for individual plays. What makes it a playbook is the product-specific selection, ranking and review around them.

**Does a playbook guarantee growth?**
No. It is a structured way to decide what to test and to learn from the results.

**How often should a playbook be updated?**
Whenever something meaningful changes, such as a release, a market signal or a result from a play you ran. A regular review helps keep it current.

## Next step

See how Hockeysticky structures its playbooks, including the goal, key metric, motion fit and tools for each: [explore the growth playbooks](https://hockeysticky.com/playbooks).