Chapter 29 of 29 · Discovering together in a small group
← The growth course
1. Finding Product-Market Fit
Test for real customer pull earlyPick a narrow niche to start inLaunch a simple first version fastLearn from users and customersRead early signs of product-market fit2. Onboarding and Activation
Structure onboarding as a storyAsk and use onboarding questionsGet users to the aha moment fastDecide how long onboarding should beBuild quiz funnels for paid traffic3. Paywalls and Pricing
When to choose a hard paywall over freemiumDesign a paywall that convertsPrice annual and monthly plansSet, raise and localize pricesRun free trials and free tastes4. Business Models and Revenue
Structure subscription tiersKeep a free tier that pays offCharge for usage and AI creditsPair hardware with a subscriptionAdd ads, affiliates and partners5. Retention and Engagement
Measure retention honestlyBuild habit loops that bring users backUse notifications and lifecycle messagesReduce churn and handle cancellationsBuild social loops and community6. Brand and Positioning
Position against bigger incumbentsName and describe your productEarn trust in high-stakes categoriesBorrow credibility from celebrities and experts7. Organic Content and Creators
Find, vet and recruit creatorsPay creators fairly and safelyBrief and manage creatorsFind and copy viral formatsScale one format across many accountsRank in AI search and SEO8. Paid, App Store and Viral Growth
Make ads that convertTurn organic winners into paid adsStructure and scale Meta campaignsTell if paid acquisition is profitableWin in the App StoreBuild viral and referral loops9. Experimentation and Analytics
Run trustworthy experimentsJudge test results correctlyRun more experiments fasterWhat metrics to track and how to define them10. Building AI Products
Build for the models of tomorrowDesign AI interfaces beyond chatDesign AI agents people can trustMeasure AI quality with evalsControl AI costs and pricingBuild products with AI coding tools11. Teams, Hiring and Funding
Hire people who thrive on ambiguityOrganize small product teamsRun exploratory bets and kill themWork as a team with AI agentsWhen to raise money or sell your company12. Founder Principles
Pick a mission worth building a company aroundWhy to trust your own judgment over the consensusTurn failure and setbacks into the next stepLearn from rivals and copy what works13. Choosing Where to Compete
Make low cost your competitive advantageCreate a market instead of fighting for shareWhy scarcity and brand can beat volumeBuild an advantage that feeds itselfAttack a bigger rival where it cannot followWhen to stay focused on the core business14. Building and Leading the Company
Hire great people and give them roomAlign pay and ownership with the missionKeep your culture and standards as you growBuild candor and fast decision-makingWhy leaders must stay close to the work and customersChoose and prepare a successor15. Capital and Deals
Fund growth without losing controlAcquire companies and keep what makes them workWhat to do with cash: reinvest, buy back or holdWhy to keep a cash cushion and avoid heavy debtStructure ownership to protect your missionNegotiate deals that keep your leverage16. Finding Ideas and Thinking
How to find ideas worth writing aboutWhy writing is how you find out what you thinkHow to research so the writing carries feelingHow to read like a writer17. Structure and Argument
How to open so readers keep goingHow to find the shape before you draftHow to keep readers curious with questions and cluesHow to argue without preachingHow to end so the last page lingers18. Clear Sentences and Voice
How to write plainly for a reader who knows nothingHow to choose specific details over generic onesHow to sound like yourself on the pageHow to shape rhythm and phrases people remember19. Characters and Storytelling
How to build characters readers care aboutWhat makes a scene move: want, obstacle and changeHow to write dialogue that sounds real but stays shortHow to make readers feel without telling themHow to turn information into a story20. Revising, Habits and Readers
How to cut and rewrite your own draftHow to get feedback you can useHow to build a writing routine that lastsHow to get unstuck when a draft stallsHow to use AI without losing your voiceHow to write for one specific reader21. Why people play games
How to design around the feeling you wantHow to find a game idea with a hookHow to decide who your game is forWhy rewards and motivation need careful designHow to use mystery and curiosity to pull players on22. Core mechanics and loops
How to build a game around one core verbHow to give each mechanic several jobsHow to add depth with holds, timing and chainsHow to use feedback loops to keep games balancedHow to use randomness without frustrating playersHow to make synergies feel powerful and earned23. Challenge, difficulty and feel
How to make hard games feel fairHow to tune difficulty with many leversHow to offer assists without breaking your intentHow to make death and retries painlessHow to make movement and controls feel goodHow to add camera and juice that sell impact24. Teaching players and designing levels
How to teach mechanics without a tutorialHow to introduce mechanics one at a timeHow to guide players without markersHow to build levels around one mechanicHow to design puzzles with a catch and a revelationHow to design dungeons from locks and keys25. Progression, systems and story
How to gate exploration without trapping playersHow to design unlocks and skill treesHow to let systems create emergent playHow to design enemy AI players can readHow to tell stories through mechanicsHow to make player choices and consequences matter26. Prototyping, testing and accessibility
How to prototype before you commitHow to scope and cut a game to finish itHow to run playtests that reveal real problemsHow to turn player feedback into the right fixHow to build accessibility in from the start27. How a field works and shifts
Make steady progress inside a working frameworkSpot a surprising result worth chasingWhen to abandon a model that mostly worksWhat your tests and metrics quietly assumeWin agreement for a new approach28. Organising a place for discovery
Build a team where disciplines collideFund open-ended research and keep it usefulMove a promising result into real useLearn from missed chances and outside threats29. Discovering together in a small group
Share work, credit and priority in a groupFind the cause when results behave erraticallyGet a new result noticed and adopted1 The bottom line
Find the cause of unpredictable results by logging every trial by number, testing each input alone, and splitting any part that does two opposed jobs. Mixed inputs and overloaded parts hide the cause, so results look random.
2 Key takeaways
- Give every trial a number and write it down. Results only compound when you can look back at them.
- Josiah Wedgwood began recording trials in 1759 and kept going for thirty-five years, to nearly five thousand.
- Test each input source on its own. Mixing sources hides which one is causing the swings.
- One batch of Wedgwood's moor-stone fired white and fine, the next cinnamon, and one melted to glass.
- Fix the input before you judge the remedy. A variable input makes a good remedy look unreliable.
- William Withering switched from the variable foxglove root to dried powdered leaves.
- Split a part that has two opposed jobs. One component cannot be best at both.
- James Watt moved condensing out of the Newcomen cylinder into a separate vessel.
This good woman knew the medicine of her country but not the dose of it.
William Withering, in Jenny Uglow's The Lunar Men
2.1 Keep a numbered record of every trial
Jasper took eighteen years of numbered trials
A numbered log turns scattered attempts into evidence you can build on.
- Start the log when the work feels stale, not when it feels promising. Wedgwood began in 1759, when the trade seemed stale and demand was falling.
- Number each trial and record it every time.
- The habit let him grind through jasper, which kept cracking or blistering for years. He mastered it only in late 1777, after five thousand experiments.
- Expect to repeat the same trial many times, and keep logging. Wedgwood treated persistence as a duty of the work.
- Use the log to see which changes you have already tried.
- His own words: "We must have our Hobby Horse, & mount him, & mount him again if he throws us ten times a day."
2.2 Test each input on its own
Fire each source alone to expose the odd one
When batches differ, run every source separately so the odd one shows itself.
- Do not blend your sources while you are hunting for the cause. Wedgwood only understood his moor-stone after firing every lump by itself instead of mixing them.
- List every source that feeds a batch.
- Run each source alone, under the same conditions.
- Write each result in the log under its own trial number, so you can match outcomes to sources.
- He experimented with moor-stone for about five years.
2.3 Standardize the input before testing a remedy
A remedy cannot be judged until the thing you give it is the same every time.
- Swap a variable input for a fixed form, then test. Withering traced a folk dropsy cure to foxglove and replaced the variable root with dried powdered leaves.
- Record every case, including side-effects.
- Publish the cautions alongside the benefits.
- His Account of the Foxglove listed side-effects up to a pulse as low as 35, convulsions and death.
2.4 Measure the waste, then split the overloaded part
Give each opposed job its own component
Measure where the loss is, take odd results to someone with a theory, then separate the jobs.
- Measure the waste directly, and bring the odd result to a colleague. Watt found the problem with a kettle test, then took the strange result to Joseph Black.
- Black's theory of latent heat explained what Watt had measured.
- In the kettle test, the water level rose by a sixth.
- Look for a part that has to do two opposed jobs, and give each job its own component. The Newcomen cylinder had to stay hot for efficiency but be cooled to make a vacuum.
- Watt moved condensing into a separate vessel so the cylinder could stay hot Uglow.
- A model built within days predicted lifting water to 44 feet with the steam Newcomen engines used for 32 Uglow.
- Watt later said: "I had not walked further than the Golf-house when the whole thing was arranged in my mind." Uglow
← Previous lessonShare work, credit and priority in a groupNext lesson →Get a new result noticed and adopted
Sources
Part of Discovering together in a small group in the growth library.