CaddieOpen in CaddieDownload for Mac

Fund open-ended research and keep it useful

Shared by Caddie Library · Updated
Chapters show their main points
Chapter 28 of 29 · Organising a place for discovery
← 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 fit
2. 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 traffic
3. 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 tastes
4. 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 partners
5. Retention and Engagement
Measure retention honestlyBuild habit loops that bring users backUse notifications and lifecycle messagesReduce churn and handle cancellationsBuild social loops and community
6. Brand and Positioning
Position against bigger incumbentsName and describe your productEarn trust in high-stakes categoriesBorrow credibility from celebrities and experts
7. 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 SEO
8. 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 loops
9. Experimentation and Analytics
Run trustworthy experimentsJudge test results correctlyRun more experiments fasterWhat metrics to track and how to define them
10. 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 tools
11. 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 company
12. 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 works
13. 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 business
14. 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 successor
15. 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 leverage
16. 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 writer
17. 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 lingers
18. 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 remember
19. 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 story
20. 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 reader
21. 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 on
22. 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 earned
23. 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 impact
24. 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 keys
25. 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 matter
26. 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 start
27. 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 approach
28. 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 threats
29. 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 adopted

1 The bottom line

Give people protected time for self-chosen work, fund foundational bets apart from incremental work, and anchor the whole group to a need someone depends on. Without a real need behind it, even a great lab declines slowly and unnoticed.

2 Key takeaways

  • Make slack time for self-chosen work an explicit norm. Side work keeps promising plans alive until the timing is right.
    • Joel Engel, Bell Labs believed advancement required spending 20 or 30 percent of your time beyond your assignment, and he used it to plan cellular.
  • Back staff side projects that leaders are tempted to discourage. Leaders misjudge ideas that do not fit the current business.
    • Boulton and Watt discouraged Murdoch's gas lighting, and within years London streets and many mills were gas lit.
  • Fund steady work and risky bets separately. Incentives and competition mostly produce incremental gains.
    • Josiah Wedgwood ran useful ware and ornamental ware as separate partnerships with their own workshops, ovens, sales and accounts.
    • Mervin Kelly, Bell Labs spent decades improving the vacuum tube, then backed the transistor that made that work irrelevant.
  • Tie the group to a concrete need someone depends on. Buildings, equipment and people do not sustain research on their own.
    • Bell Labs was about a third of its former size by 2005, and Holmdel closed in 2006.
  • When a leader blocks your idea, wait and return with a budget and a competitive argument. Escalating at once can backfire.

The mission was absolutely essential to the research done at the old Laboratories, and that mission is gone and has not been replaced.

Jon Gertner, Bell Labs

2.1 Give people room for self-chosen work

Slack time keeps good ideas alive until the moment fits, and leaders have to make it normal and protect it.

  • Say out loud that people may spend part of their time beyond their assignment.
    • Make the norm explicit so people actually use it, as Bell Labs culture did informally.
    • Name a share of time. Google lets workers spend up to 20 percent on projects of their choosing Jon Gertner.
    • Joel Engel used his 20 or 30 percent to plan cellular before its time came.
  • Back staff side projects you are tempted to discourage.
    • Treat your own urge to discourage as a warning sign, and look at a demonstration before you say no.
    • Boulton and Watt discouraged Murdoch's gas lighting and talked him out of a patent. They backed it only after Gregory Watt saw a demonstration in Paris.
    • For the Peace of Amiens, 1802 to 1803, all of Soho blazed with gaslight Jenny Uglow.

2.2 Separate steady work from foundational bets

Give steady and risky lines their own books
Useful wareOrnamental ware
PartnershipSeparateSeparate
Workshops & ovensIts ownIts own
SalesIts ownIts own
AccountsOwn booksOwn books
DemandSteadyRiskier artistic trade
By 1769 Wedgwood ran two specialized factories with 150 employees, thirty of them on vases.

Keep the core line and the risky lines apart, so neither starves or hides the other.

  • Run the steady core apart from experimental lines, with their own books.
    • Give each line its own workshop, sales and accounts, as Wedgwood did with separate partnerships.
    • Refuse to merge them. He did this to balance steady demand against riskier artistic trade.
    • By 1769 Wedgwood had two specialized factories and 150 employees, thirty of them on vases.
  • Fund foundational bets with patient money, technically competent leaders and freedom to stop failed lines.
    • Do not expect incentives to deliver platforms. In the words of Jon Gertner, "Incentives are fine, but they produce incremental improvements in what's there."
    • Let people end a failed line without career damage.
    • Kelly spent decades improving the vacuum tube, then backed the transistor that made that work irrelevant.

2.3 Tie the group to a need someone depends on

Bell Labs lost its mission long before it closed
Prizes and papers continued, so the lost purpose stayed hidden for two decades.

Freedom lasts only while someone urgently needs what the group produces.

  • Name who depends on your output, and keep that link alive.
    • Do not assume buildings, equipment and people will sustain research alone. Great labs rise because someone urgently needs what they produce.
  • If the mission goes, replace it early, because decline is slow and hard to spot.
    • Watch for lost purpose even while prizes and papers continue.
    • After the 1984 breakup Bell Labs still won Nobel Prizes, yet it was split repeatedly.
    • By 2005 it was about a third of its former size, and Holmdel closed in 2006 Gertner.

2.4 Handle a leader's "no"

A leader's no is often only a delay
Waiting and coming back with a clear cost and a competitor beat escalating right away.

A blocked idea is often only delayed, if you pick the moment and the argument.

  • Hold your rebuttal, then return later with a clear budget.
    • Argue that someone else will act if you do not.
    • Do not escalate immediately, because it can backfire.
    • Kelly called the satellite a nonstarter in summer 1958, and a rebuttal was never sent.
    • After he retired, a January 6, 1959 proposal asking $1 million was approved as Project Echo Gertner. His summary: "Even great men can be wrong."

2.5 Where the books differ

The right move depends on whether you are the leader or the proposer, and on how much protection you already have.

  • Leaders should back the project at once, while proposers should often wait.
    • At Soho, the leaders themselves discouraged Murdoch, and backing came late Uglow.
    • At Bell Labs, the proposer waited out the leader and came back with a cost and a competitor Gertner.
  • Protection for foundational work may need to be built by design.
    • Monopoly security likely let Bell Labs escape the innovator's dilemma for a time.
    • Without a monopoly, separate accounts and workshops, as at Wedgwood, are one way to shield risky lines from steady demand.

Sources

Part of Organising a place for discovery in the growth library.