CaddieOpen in CaddieDownload for Mac

Learn from missed chances and outside threats

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

Sort each failure by its cause, give failed work a second look, and check whether outsiders or your own breakthroughs threaten you. Bell Labs missed the integrated circuit, lost a waveguide bet and watched its own work undercut its monopoly.

2 Key takeaways

  • Name the type of failure before you decide what to fix. Missed opportunities, mistakes of perception and mistakes of judgment have different causes and different fixes.
    • Jon Gertner, Bell Labs: the lab missed the integrated circuit, bet on waveguides that glass fiber made obsolete, and launched a Picturephone nobody wanted.
  • Review failed work whenever a new problem appears. A weakness that sank a product in one setting can stop mattering in another.
    • Jon Gertner, Bell Labs: the silicon solar cell was too costly for rural phones, but in space nothing else could recharge batteries.
  • Do not let a leader's belief or your sunk cost close a direction. You can own every ingredient and still lose the invention.
    • Jon Gertner, Bell Labs: Jack Morton believed multi-component chips could never be reliable and pursued functional devices instead.
  • Never assume your network is a moat rivals cannot copy. Widely licensed technology lets others build what you built.
    • Jon Gertner, Bell Labs: MCI built a cheaper microwave long-distance network without durable gear or local subsidies.
  • Ask whether your own breakthroughs remove the conditions that protect you. Your best work can spread, get improved and return as competition.

Shannon's theorem was the mathematical basis for breaking up the Bell System.

Jon Gertner, Bell Labs

2.1 Sort each failure by its cause

Name the failure type before choosing the fix
Missed opportunityMistake of perceptionMistake of judgment
Diagnostic questionHad the parts, someone else assembled them?Better answer came from elsewhere?Product failed the need?
Bell Labs caseIntegrated circuit (Noyce, Kilby)Waveguides beaten by glass fiberPicturephone nobody wanted
What to examineParts you held and who combined themWho solved it and their core skillsFunction, cost and timing separately
Bell Labs made all three kinds of mistake: it missed the integrated circuit, backed waveguides over glass fiber and launched the Picturephone.

A failure only teaches you something once you know which of three kinds it was.

  • Ask first whether you had the ingredients and someone else assembled the breakthrough. That is a missed opportunity Jon Gertner, Bell Labs.
    • List the parts you already held and who put them together first.
    • A Bell Labs insider said: "We had all the elements to make an integrated circuit... But nobody had the foresight except Noyce and Kilby."
  • Ask whether a better solution from elsewhere eclipsed your bet. That is a mistake of perception Jon Gertner, Bell Labs.
    • Look at who produced the better answer and what skills they started from.
    • Such breakthroughs often come from groups with different core skills and different needs.
  • Ask whether the product failed the need. That is a mistake of judgment Jon Gertner, Bell Labs.
    • Check function, cost and timing separately, because each points to a different fix.
    • A product that failed on cost for one use may still be the only option for another.

2.2 Give failed work a second life

Shelved work can become essential once the right problem shows up.

  • Keep an inventory of shelved and failed components, and review it when a new idea appears. Jon Gertner, Bell Labs
    • Record each item with the reason it failed.
    • Check the list before you start building something new.
    • Joe Chaffee's 1937 feedback receiver was considered largely useless. It was revived for Echo and Telstar.
  • Look for a problem where the old weakness stops mattering. Jon Gertner, Bell Labs
    • Name the weakness that sank the product.
    • Search for a use where that weakness does not count against it.
    • Old work can become essential once the right problem shows up.

2.3 Test the beliefs that close off a direction

A confident "never" and money already spent can both blind you to the better path.

  • Treat a leader's "this can never work" as a hypothesis to test. Jon Gertner, Bell Labs
    • When a hard manufacturing problem blocks a better design, test whether it can be solved later.
    • Make dissent safe.
    • Kilby and Noyce bet that reliability could be fixed later. They built the integrated circuit on Bell Labs processes like diffusion and photolithography.
  • Check whether money already spent is shaping how you judge alternatives. Jon Gertner, Bell Labs
    • Ask people with no investment in your approach to judge the alternatives.
    • Bell Labs spent years and millions on hollow waveguides. Baker still championed them in a 1968 speech.

2.4 Watch for outsiders who can copy you

Outsiders won while Bell Labs defended its bet
The breakthrough came from glass specialists with no sunk investment, and the network turned out not to be a moat.

The threat often comes from groups with different skills, and your network will not stop them.

  • Watch outsiders with different expertise and no sunk investment. Jon Gertner, Bell Labs
    • Track fields whose core skills differ from yours but whose needs overlap.
    • Charles Kao argued for pure glass fiber in 1966. Corning announced very low loss fiber in September 1970.
  • Do not treat your existing network as a moat. Jon Gertner, Bell Labs
    • If your technology is widely licensed, others can build what you built.
    • The attitude to avoid: "You don't have to worry about this, because we have the network. No one else has the network."
  • Plan for low-cost entrants before regulators force the issue. Jon Gertner, Bell Labs
    • Expect them to target your most profitable segment without your obligations.
    • In 1971 the FCC ordered AT&T to connect MCI to its local switching centers.

2.5 Check whether your own breakthroughs undercut you

Bell Labs' own breakthroughs undercut its monopoly
List what protects your position, then check whether your latest work removes it.

Your best work can remove the conditions that protect your position.

  • Map how each innovation changes the economics of your market. Jon Gertner, Bell Labs
    • Assume your work can spread, get copied and improved, and return as competition.
    • Shannon's digital information let any company code and decode messages.
  • List what protects your position, then ask whether your latest work weakens it. Jon Gertner, Bell Labs
    • Plan for the result before the market delivers it.
    • Cheap, freely licensed transistors meant any company could do that coding and decoding. That undercut the case for the monopoly.

Sources

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