Reading path · 4 pieces · About 41 min
Are you building a growth loop—or just replacing users who leave?
Map the loop, test the channel fit and examine retention. Then move from diagnosis to the work a growth team can own. Read the final case examples in a second session if you want a shorter first pass.
Who this is for: Founders and product teams with acquisition activity but an uncertain growth mechanism.
Take away: A growth-loop sketch, a retention check and an owned experiment aimed at a specific friction.
Start reading ↓Estimates use 250 words per minute, rounded up for each piece. Allow extra time for the reflection at the end. Open a piece for its selection note and available summary, then continue to the original.
01 / Map the mechanism
Reforge connects product, distribution and monetisation in a system of reinforcing loops. Use the examples to identify what your product produces that can feed another cycle of growth.
Pause here: What exactly passes from one cycle into the next?
02 / Fit the distribution channel
Brian Balfour connects a product’s attributes with the channel that can distribute it. Use the historical examples to test a dependency, not as a current playbook for platform rules.
Pause here: What must be true of your product for this channel to work?
03 / Test whether people stay
Andrew Chen examines retention curves, category differences and the limits of notification-driven fixes. Challenge your growth story with the behaviour of real cohorts, not acquisition totals alone.
Pause here: Are new arrivals finding repeat value, or merely replacing people who leave?
04 / Turn the diagnosis into work
Casey Winters connects growth work to the friction between people and a product’s existing value. His Pinterest and Grubhub examples show how quantitative signals and observation can redirect a team’s effort; copy the diagnostic habit, not the historical tactics.
Pause here: Is the next task creating missing value, or helping people reach value that already exists?
Reforge describes the loop, Balfour adds the distribution constraint, and Chen tests the story against retention. These are distinct failure points: a loop can fail to reach people, and a successful channel can bring people who do not stay. The examples describe their publication context; platform tactics and benchmark figures should not be treated as current guarantees. Winters adds the execution boundary: distinguish creating core value from removing friction that prevents people experiencing it. A growth-team label cannot repair a product nobody wants. Once the value is there, a measured intervention can test where access to it is breaking down.
Digna Legi synthesis of the linked readings, not a claim that the authors endorse this combined approach.
Put five minutes aside
Use paper or your own notes app. These prompts are Digna Legi’s exercise, drawn from the readings.
Before you leave: Which part of the growth story is currently evidence, and which part is still an assumption?
Allow Google Analytics to measure visits and reading-link clicks using cookies. Optional; the site works without it. Privacy details