01 / The Canon
Ellis and Brown: The growth problem is often a handoff problem in disguise.
Read the opening BitTorrent case study from Chapter One of Sean Ellis and Morgan Brown's Hacking Growth, through "Silos Breached at Last". A single customer-research finding - active users did not know a paid version existed - becomes valuable only because it reaches the people who can turn it into an experiment.
/Users/sushil/Documents/Operation Alpine Thunder/Books/Hacking Growth.epubUse Read on phone for the Drive copy. On Mac, copy the command and paste it into Terminal; browsers do not open local files directly from this page.
Chapter Reader
Read first for the organizational reversal: the marketing plan was not useless, but it was too narrow for the discovered opportunity. Read again for the operating loop: customer signal, cross-functional interpretation, small product change, measurement, and the next test.
BitTorrent was organised in conventional functional lanes: marketing brought people in; product and engineering built features; data supported the groups. The mobile launch had a plan, but adoption remained slow. When Annabell Satterfield investigated customers who had not upgraded, the strongest opportunity turned out to be inside the existing audience, not at the top of the funnel.
That distinction is practical. A customer-research project should not be pre-decided as a messaging exercise merely because marketing commissioned it. If the evidence points to activation, retention, pricing, or product comprehension, the next owner may be somewhere else.
The revealing BitTorrent response was simple: many free users did not know the paid Pro version existed. The team did not need a grand campaign to act on it. They gave the upgrade a more visible place in the app and saw an immediate revenue increase. The value of the survey was not that it produced a clever answer; it gave the team a specific, reversible change to test.
Ellis and Brown then show the same pattern in the review prompt and battery-saving feature. Each move links a concrete behavior or pain point to a defined moment in the product, then lets engineering, product, marketing, and data make and judge the change together.
The book treats silos as a speed and learning problem. A function can be excellent at its own output while the customer signal still dies at the boundary. BitTorrent's growth group gained momentum when a marketer, engineers, and a data analyst could share evidence, propose tests, implement them, and decide what the result meant without waiting for a perfect departmental handoff.
The lesson is not to abolish expertise. It is to assemble a small team around a measurable customer constraint, give it a clear decision owner, and keep its experiments close enough to the evidence that the work can compound.
top of the funnel
many of the best growth opportunities appeared to lie farther down the funnel
The users had no idea there was a paid version
Silos Breached at Last
cross-functional collaboration
Close Reading Sequence
- What assumption about where growth lived did Satterfield's customer research overturn at BitTorrent?
- Why is "users did not know there was a paid version" a more useful finding than a general statement that conversion needs improvement?
- Trace one BitTorrent change from observed behavior to experiment to measured outcome. Which function supplied each part of the loop?
- Where does a customer signal currently lose force in your work: collection, interpretation, implementation, or measurement?
- What is the smallest reversible product, message, or workflow change your team could test after its next customer insight?
02 / The Principle
Give the signal a team, a test, and a clock.
Growth work gets vague when it is owned only as an ambition. It becomes learnable when one customer observation is translated into a hypothesis, a small change, a measure, and a named group that can move it from evidence to result without sending it through a queue of separate priorities.
A B2B product team hears in onboarding calls that new administrators invite no colleagues in their first week. Marketing plans an email sequence, while product is focused on reporting. Instead, a growth pod reviews the calls and event data together, tests a contextual invite prompt immediately after a useful report is shared, and measures invited-workspace activation against a holdout. The email may still matter, but the product moment gets tested rather than assumed away.
Choose one live customer signal: a support pattern, an exit-survey answer, a sales objection, or a behavior drop-off. Write a one-page experiment brief with five lines: the exact evidence, the user moment, the smallest reversible change, the success measure, and the person from product, marketing, engineering, or data needed to decide it this week.
03 / Field Notes
Three signals that growth is moving from a functional output to a shared learning loop.
Domino's pays diners to beta test its relaunched app and website
What happened: Domino's is offering qualifying digital-order customers $5 off a later order while promoting its relaunched website and app and inviting feedback on the ordering experience. Marketing Dive reports that the offer runs alongside TV, online video, social, and digital campaign support. Why it matters: The useful move is not the coupon alone. It turns a launch into an instrumented feedback moment around the behavior that matters: ordering. That is closer to Ellis and Brown's loop than treating the campaign and the product experience as separate jobs. Watch: Whether Domino's publishes changes or learning from the feedback, especially at the moments where the new ordering flow creates hesitation or abandonment.
Read sourceHome Depot consolidates technology teams around its customer-experience strategy
What happened: Home Depot moved its store, supply-chain, and Pro-product technology teams under its new EVP and CTO as part of a reorganisation tied to streamlined core offerings, interconnected shopping, and its professional customer base. Why it matters: This is the structural version of the chapter's argument. Customer experience improvements require the teams that own different moments of the journey to share a direction and decision path; otherwise each function can optimise its slice while the overall journey stays fragmented. Watch: Whether the new structure yields a visible increase in the pace or coherence of improvements for DIY and Pro customers, rather than a leadership change without a tighter operating loop.
Read sourceAirbnb pairs faster feature shipping with an opt-in AI search test
What happened: Airbnb said AI has reduced time from concept to launch by as much as 60% on key initiatives and is testing a toggle for a natural-language, visual AI search experience instead of forcing it on customers accustomed to filters. Why it matters: Speed is only a growth advantage if it improves the quality of the learning loop. The toggle preserves a comparison: Airbnb can observe whether a new discovery behavior earns use, rather than mistaking faster production for customer value. Watch: How Airbnb defines success for the AI-search test: discovery quality, booking completion, repeat use, or a combination that does not sacrifice familiar search behavior.
Read source04 / Collected Fragments
One fragment on reducing the cost of a handoff.
A product workflow that carries a task summary between sessions
The post describes a feature that sends a summary, rather than full history or files, to another Claude Code session. It is a small illustration of the chapter's operating problem: a handoff improves when the next owner receives the decision-relevant context without needing the whole backstory.
New in Claude Code: your sessions can now message each other. Instead of having to re-explain yourself in another session, you can now tell Claude to do it. It sends a summary (not your history or files), and the other session picks it up mid-task.
Open on X
05 / The Practice
Turn one customer signal into a shared experiment.
After reading, write a five-line experiment brief from one real customer observation. Make the proposed change small enough to ship or test this week, then name the cross-functional pair or trio who must see the same evidence before it can become a result.