CaddieOpen in CaddieDownload for Mac

Make steady progress inside a working framework

Shared by Caddie Library · Updated
Chapters show their main points
Chapter 27 of 29 · How a field works and shifts
← 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

Commit your team to a good-enough shared model, and work only on problems that model guarantees can be solved. A shared framework turns scattered effort into steady progress, because everyone knows which facts matter and what counts as an answer.

2 Key takeaways

  • Commit to a good-enough shared model. It only has to beat its rivals, and it stops each person from rebuilding the field alone.
    • Franklin's theory covered nearly all electrical effects and became the common paradigm. Thomas S. Kuhn
  • Work on puzzles, not on every important problem. A puzzle has an assured solution and rules for acceptable answers, and importance gives neither.
    • Curing cancer and securing lasting peace are urgent, yet they may have no solution. Thomas S. Kuhn
  • Keep the rules when a problem is hard. Changing the rules sets a new problem and leaves the old one unsolved.
    • Scientists kept the rules until, in 1750, one of them found how to apply them successfully. Thomas S. Kuhn
  • Teach newcomers with worked problems, not principles. A general law is nearly useless until problems show how to apply it.
    • Galileo's incline, Huyghens' physical pendulum and Daniel Bernoulli's efflux problem all use one vis viva law. Thomas S. Kuhn
  • Push the model past its proven range. A model kept to known facts is safe, but it can never lead to discovery.
    • Phlogiston theory, limited to the facts it already explained, could never have been challenged. Thomas S. Kuhn

Truth emerges more readily from error than from confusion.

Thomas S. Kuhn, The Structure of Scientific Revolutions

2.1 Commit to a good-enough shared model

A shared model that beats its rivals is enough to start, and it does not need to explain everything.

  • Pick the best available model and make it the team's common one. Thomas S. Kuhn
    • Without a shared model every fact seems equally relevant, and each person rebuilds the field from scratch.
    • The model only needs to beat its competitors, not explain everything.
    • Early eighteenth-century electricity had nearly as many views as major experimenters.
  • Treat what the model cannot explain as problems to solve. Thomas S. Kuhn
    • Keep a visible list of the model's leftovers and assign them as work.
    • Franklin's theory still could not explain every case of repulsion.

2.2 Pick problems the model guarantees can be solved

A puzzle guarantees a solution; importance guarantees nothing
AttributePuzzleImportant problem
Assured solutionYes, the framework guarantees oneNot guaranteed, may have none
Rules for acceptable answersClearOften missing
ExampleFranklin's unexplained repulsion casesCuring cancer, lasting peace
How to planAssign as normal workStaff and schedule separately
Test each problem on these two rows before you assign it, and send the open-ended ones to a separate plan.

Put your effort on problems with assured solutions, and plan open-ended ones separately.

  • Test every problem for a guaranteed solution and rules for acceptable answers before you assign it. Thomas S. Kuhn
    • A puzzle is defined by those two things, not by how important it is.
    • Fast progress comes from working only on problems the framework guarantees can be solved.
    • "Though intrinsic value is no criterion for a puzzle, the assured existence of a solution is."
  • Staff and schedule open-ended problems differently, and audit what your framework leaves out. Thomas S. Kuhn
    • Go through your list of important problems and mark the ones your framework silently excludes.
    • Such problems may have no solution, which is why they need a different plan.

2.3 Hold the rules when the work gets hard

Keep the destination fixed and find a new route
Proposals through the eighteenth century to swap the inverse square law for the moon's motion would have moved the goal without reaching it.

A hard problem is a reason to look for a new route, not to rewrite your core assumptions.

  • Keep the rules and push for a new route to the expected result. Thomas S. Kuhn
    • That push is what makes hard work productive.
    • The expected result stays fixed. Only the route to it changes.
  • Treat any proposal to change a core assumption as a new problem, not an answer. Thomas S. Kuhn
    • Ask whether the change solves the old problem or only sets a new one.
    • Through the eighteenth century some proposed swapping the inverse square law to explain the moon's motion.

2.4 Train newcomers on worked problems

People learn the model by solving concrete problems, not by reading its principles.

  • Build your training from solved examples that newcomers work through themselves. Thomas S. Kuhn
    • Working knowledge lives in concrete solved examples.
    • Choose examples that look different on the surface but rest on the same law, so people learn to see a new situation as like an old one.
    • Students often understand a chapter and still fail its problems until they spot the resemblance to one already solved.
  • Never hand over the general law alone. Thomas S. Kuhn
    • A law is nearly useless until problems show how to apply it.
    • The verbal vis viva law alone gave little guidance without the problems.

2.5 Stretch the model and spread the risk

Push the model past what it has proven, and let people weigh shared values differently so a few bet on anomalies.

  • Apply the model to cases beyond what it has already explained. Thomas S. Kuhn
    • Restricting a model to what is already observed makes it safe and stops all discovery.
    • Pushing it further creates puzzles, surprises and the anomalies that point to deeper change.
    • "Is it really any wonder that the price of significant scientific advance is a commitment that runs the risk of being wrong?"
  • Let members weigh shared values differently. Thomas S. Kuhn
    • Values like consistency and simplicity are widely shared but weighed differently by individuals.
    • Let a few people bet on anomalies and new ideas while most keep doing productive normal work.
    • Einstein saw an inconsistency in the old quantum theory as intolerable, while Bohr and others saw it as a difficulty normal work would resolve.

2.6 Where the books differ

Most keep the rules while a few chase anomalies
Because people already weigh shared values differently, the split spreads the risk that comes with stretching a model past what it has proven.

Every tip in this lesson comes from Kuhn, so the tension sits inside one account: keep the rules, yet bet against them.

  • Split the team: most keep the rules, a few chase anomalies. Thomas S. Kuhn
    • Tell the majority to hold the core assumptions and look for new routes to expected results.
    • Let a small group treat anomalies as serious, since people weigh shared values differently anyway.
    • Betting on a model beyond its proven range may prove you wrong. That risk is the cost of progress.

Sources

Part of How a field works and shifts in the growth library.