CaddieOpen in CaddieDownload for Mac

Build a team where disciplines collide

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

Put theorists, experimenters and outsiders where they keep meeting, and manage them as a guide, not a rival. Mixed disciplines improve each other's work only if the space, the hiring and the boss all make meeting easy.

2 Key takeaways

  • Design the building so different disciplines must cross paths. Meetings happen when the layout forces them.
  • Combine skills and temperaments on purpose, and pay to fill a missing skill. A team without a key capability stalls, however good the rest is.
  • Bring in people from adjacent fields to reframe stubborn data. Outsiders ask questions that insiders no longer think to ask.
    • Dalton saw combining proportions that chemists had missed Thomas S. Kuhn.
  • Value and protect the colleague who asks good questions. Their effect on others can exceed their own output.
  • As a manager, guide your reports and never compete with them. A star who races his team for credit can destroy it.

Men are a kind of material, too.

Jon Gertner, Bell Labs

2.1 Build a space that forces collisions

People from different fields only improve each other's work if the building makes them meet.

  • Separate people's labs from their offices so they must walk between them Jon Gertner, Bell Labs.
    • Route that walking through long shared corridors on the way to common spaces.
    • Murray Hill connected all wings and used a 700-foot corridor.
  • Build with modular walls so teams can resize quickly Jon Gertner, Bell Labs.
    • Fit every module with full utilities, so changing a team's size does not mean rebuilding.
    • Murray Hill used six-foot modules with full utilities.

2.2 Combine people, and pay for the missing skill

Treat people as a material to be combined, and spend what it takes on the skill you lack.

  • Mix theorists with experimentalists, across skills and temperaments Jon Gertner, Bell Labs.
    • Put the theorist in the experimenter's lab, so the two work side by side.
    • Bardeen landed in Brattain's lab, which started the theorist and experimentalist partnership.
  • When the team lacks a key skill, find the few people who have it and pay what it takes Jon Gertner, Bell Labs.
    • Name the gap first, then count how many people could fill it.
    • Shockley and Fisk judged that only about three people in the country could fill the theory gap.

2.3 Bring in outsiders to reframe old data

Someone trained in a neighboring field can make stubborn data answer new questions.

  • Bring in people from adjacent fields when your data will not yield Thomas S. Kuhn.
    • Look for people whose training gives them different questions and concepts.
    • Dalton was a meteorologist studying gas absorption.
  • Watch neighboring specialties for tools and results Thomas S. Kuhn.
    • Absorbing what they find can also trigger change in your own field.
    • Dalton imported questions from physics and meteorology into chemistry.

2.4 Protect the people who ask good questions

Top patent holders shared one thread: meals with Nyquist
A patent lawyer's study found that eating with Nyquist was the only common factor among Bell Labs' most prolific inventors.

Some colleagues lift everyone around them by drawing people out, not by handing over answers.

  • Value the colleague who asks good questions over the one with the most raw output Jon Gertner, Bell Labs.
    • Seek these people out and protect them, because their effect can exceed their own output.
    • A patent lawyer's study found that eating with Nyquist was the only common thread among the top patent holders.

2.5 Manage as a guide, not a competitor

A manager who races his people for credit can lose the whole team.

  • Guide your reports and never compete with them Jon Gertner, Bell Labs.
    • A star who races subordinates may produce a better design but still destroy the team.
    • Bardeen left for Illinois, and Brattain asked to stop reporting to Shockley.
  • Promote on management fit, not brilliance alone Jon Gertner, Bell Labs.
    • Ask whether the person can draw out a team before asking how brilliant they are.
    • Later, Shockley's staff left after he asked them all to take polygraph tests.

2.6 Where the books differ

Outsiders reframe questions, specialists fill a known gap
OutsiderPaid specialist
Use whenOld data won't yieldYou can name the exact gap
BringsNew questions and conceptsA scarce key skill
ExampleDalton, a meteorologist, in chemistryBardeen, hired at a top salary
Watch forIdeas from neighboring fieldsA star competing with the team
Choose an outsider when old data won't answer, and a paid specialist when you can name the missing skill.

Outsiders and scarce specialists solve different problems, and a star's talent needs managing.

  • Use an outsider when old data will not answer, and a paid specialist when you know the exact gap.
  • Hire stars for the gap, but do not let them compete with the team.
    • Paying for rare talent worked for Bardeen's hire, yet a star manager's secret design cost the lab its people Jon Gertner, Bell Labs.

Sources

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