Develop a Growth Hacking Playbook

Growth Hacking Grew Up, and It Is Called Growth Engineering Now

The term "growth hacking" carries baggage. It evokes images of viral tricks, referral loops, and the promise of exponential growth through clever shortcuts. Some of those tactics worked spectacularly in the early 2010s. Most of them do not work anymore. But the discipline underneath the hype has matured into something genuinely valuable.

The Problem

Growth hacking in its original form was about finding one weird trick that unlocked massive user acquisition. Hotmail's email signature. Dropbox's referral program. Airbnb's Craigslist integration. These stories are inspirational and deeply misleading, because they suggest growth is about finding a single lever.

Modern product growth is a system, not a hack. It involves understanding acquisition channels, activation flows, retention curves, and monetization mechanics as an integrated machine. Each component affects the others. Optimizing acquisition without fixing retention is pouring water into a leaky bucket.

According to a 2023 Reforge analysis, companies with dedicated growth teams achieve 2.5 times higher revenue growth than those without, but the growth teams that succeed focus 70% of their effort on retention and activation, not acquisition. The industry has learned, painfully, that acquiring users you cannot keep is worse than not acquiring them at all.

How This Prompt Works

This prompt generates a structured growth playbook that treats growth as a system rather than a collection of tactics. It starts by mapping your current growth model across the pirate metrics framework (AARRR: Acquisition, Activation, Retention, Revenue, Referral) and identifies the highest-leverage bottleneck.

The output includes:

• Growth model audit mapping current performance across each stage
• Bottleneck identification with data requirements for validation
• Experiment backlog of ten to fifteen testable hypotheses, prioritized by expected impact and implementation cost
• Measurement framework specifying what to track and what constitutes a meaningful result

A 2022 Lenny Rachitsky survey of 100 growth leaders found that high-performing teams run an average of fifteen experiments per month, but their success rate is only 12%. Volume and learning velocity matter more than any individual experiment.

When to Use It

• When growth has stalled and you need to diagnose where in the funnel the problem lives
• When building a growth team and need to establish a systematic approach from day one
• Before a fundraise to demonstrate a disciplined growth strategy, not just tactics
• Quarterly to refresh your experiment backlog and reprioritize based on learnings

Common Pitfalls

• Optimizing vanity metrics. Signups are not growth. Active users are growth. Revenue is growth. Make sure your experiments target metrics that matter.
• Running too few experiments. One experiment per sprint is not a growth practice. It is a hobby. Build the infrastructure to run experiments in parallel.
• Ignoring statistical significance. Declaring a winner after three days with 200 users is not data-driven. It is impatient. According to a 2023 Optimizely report, 61% of A/B tests that are stopped early would have produced different results if run to significance.
• Copying competitors' tactics. What works for a product with network effects will not work for a product with a sales-led motion. Growth strategies are context-dependent.

Sources

• Ellis, S. & Brown, M. (2017). *Hacking Growth*. Currency. https://www.hackinggrowth.com/
• Reforge. (2023). Growth Series. https://www.reforge.com/growth-series
• Rachitsky, L. (2022). Growth at Top Companies Survey. https://www.lennysnewsletter.com/