CaddieOpen in CaddieDownload for Mac

How to build candor and fast decision-making

Shared by Caddie Library · Updated
Chapters show their main points
Chapter 14 of 15 · Building and Leading the Company
← The growth course
1. Finding Product-Market Fit
How to test for real customer pull earlyHow to pick a narrow niche to start inHow to launch a simple first version fastHow to learn from users and customersHow to read early signs of product-market fit
2. Onboarding and Activation
How to structure onboarding as a storyHow to ask and use onboarding questionsHow to get users to the aha moment fastHow to decide how long onboarding should beHow to build quiz funnels for paid traffic
3. Paywalls and Pricing
When to choose a hard paywall over freemiumHow to design a paywall that convertsHow to price annual and monthly plansHow to set, raise and localize pricesHow to run free trials and free tastes
4. Business Models and Revenue
How to structure subscription tiersHow to keep a free tier that pays offHow to charge for usage and AI creditsHow to pair hardware with a subscriptionHow to add ads, affiliates and partners
5. Retention and Engagement
How to measure retention honestlyHow to build habit loops that bring users backHow to use notifications and lifecycle messagesHow to reduce churn and handle cancellationsHow to build social loops and community
6. Brand and Positioning
How to position against bigger incumbentsHow to name and describe your productHow to earn trust in high-stakes categoriesHow to borrow credibility from celebrities and experts
7. Organic Content and Creators
How to find, vet and recruit creatorsHow to pay creators fairly and safelyHow to brief and manage creatorsHow to find and copy viral formatsHow to scale one format across many accountsHow to rank in AI search and SEO
8. Paid, App Store and Viral Growth
How to make ads that convertHow to turn organic winners into paid adsHow to structure and scale Meta campaignsHow to tell if paid acquisition is profitableHow to win in the App StoreHow to build viral and referral loops
9. Experimentation and Analytics
How to run trustworthy experimentsHow to judge test results correctlyHow to run more experiments fasterWhat metrics to track and how to define them
10. Building AI Products
How to build for the models of tomorrowHow to design AI interfaces beyond chatHow to design AI agents people can trustHow to measure AI quality with evalsHow to control AI costs and pricingHow to build products with AI coding tools
11. Teams, Hiring and Funding
How to hire people who thrive on ambiguityHow to organize small product teamsHow to run exploratory bets and kill themHow to work as a team with AI agentsWhen to raise money or sell your company
12. Founder Principles
How to pick a mission worth building a company aroundWhy to trust your own judgment over the consensusHow to turn failure and setbacks into the next stepHow to learn from rivals and copy what works
13. Choosing Where to Compete
How to make low cost your competitive advantageHow to create a market instead of fighting for shareWhy scarcity and brand can beat volumeHow to build an advantage that feeds itselfHow to attack a bigger rival where it cannot followWhen to stay focused on the core business
14. Building and Leading the Company
How to hire great people and give them roomHow to align pay and ownership with the missionHow to keep your culture and standards as you growHow to build candor and fast decision-makingWhy leaders must stay close to the work and customersHow to choose and prepare a successor
15. Capital and Deals
How to fund growth without losing controlHow to acquire companies and keep what makes them workWhat to do with cash: reinvest, buy back or holdWhy to keep a cash cushion and avoid heavy debtHow to structure ownership to protect your missionHow to negotiate deals that keep your leverage

1 The bottom line

Build candor by making it safe and routine to tell the boss the truth, and decide fast by treating most choices as reversible. Companies that hid bad news or waited for certainty lost years, while those that corrected quickly moved ahead.

2 Key takeaways

  • Reward the people who push back, and never punish bad news. Leaders hear the truth only when telling it is safe.
    • At NeXT, co-founder Daniel Lewin wrote that the product was over a year late and twice as expensive, and Jobs stripped him of his marketing role Steve Jobs, NeXT30:07.
    • Gates would not pull rank to end an argument and wanted people to win him over Bill Gates, Microsoft56:51.
  • Put honest feedback into routines instead of hoping people volunteer it. Powerful people rarely hear criticism unless a mechanism delivers it.
    • Pixar's Brain Trust gives a director candid notes from five to thirty people, with no power to order changes Ed Catmull, Pixar41:58.
    • Morita's weekly company newspaper let employees apply confidentially for other jobs, which exposed bad managers Akio Morita, Sony59:00.
  • Treat most decisions as reversible and make them at about 70% of the information. Being wrong costs less than being slow, if you correct quickly.
  • Replace long-range plans with scenarios and readiness. Outside events cannot be predicted, and a fixed plan slows the response.
  • Flatten the structure and set short clocks so information and decisions move together. Extra layers and loose deadlines quietly eat time.
    • Hock gave an engineer nine months to build Visa's whole authorization system, because computer people consume any time you give them Dee Hock, Visa1:56:30.
    • Jensen Huang designed a company he could manage directly, with about 60 direct reports Jensen Huang, Nvidia9:45.

We are not optimizing for not embarrassing somebody. We're optimizing for the company learning from our mistakes.

Jensen Huang, Nvidia

2.1 Make the truth safe to say

Candor starts with how the leader reacts to bad news and to disagreement.

  • Do not punish the person who brings bad news. See what it cost Steve Jobs at NeXT30:07.
    • Executives who griped about Jobs went silent the moment he walked in, and engineers kept promising "one more month" Steve Jobs, NeXT30:07.
    • Jobs fired manufacturing VP Linda Wilin for preparing for both possible circuit boards Steve Jobs, NeXT17:50.
    • Sales were hidden behind channel stuffing, and when distributors could not sell the machines NeXT was owed over $10 million Steve Jobs, NeXT30:07.
    • The honest answer was a year of seven day weeks. The chip finally delivered did not work and cost another full year Steve Jobs, NeXT17:50.
  • Hire and keep people who argue back.
    • Jobs wanted talented people whose ideas survived only if they could convince the smart people around them Steve Jobs, NeXT6:36.
    • Gates drilled into every position and would not pull rank to end an argument Bill Gates, Microsoft56:51.
    • Jobs told Ed Catmull he had fired two Apple board members because they never disagreed with him Steve Jobs, NeXT6:36.
    • At MITS, Ed Roberts ran a culture of fear where no one told him the truth, and Gates was the exception who got in his face Bill Gates, Microsoft56:51.
    • Noyce expected anyone in a meeting to challenge him Bob Noyce, Intel41:01.
  • Ask for criticism directly, even from admirers.
    • When the author started praising Zara, Ortega interrupted and asked her to explain what she did not like Amancio Ortega, Inditex39:30.
    • Morita invited Norio Ohga, a student who had severely criticized Sony's first tape recorder, to be a paid critic Akio Morita, Sony55:50.
    • Ortega knew that as one of the world's wealthiest people, most would say only nice things Amancio Ortega, Inditex39:30.
    • Ohga later became Sony's president, and likened the critic's role to a mirror for a ballet dancer Akio Morita, Sony55:50.

2.2 Build routines that deliver honest feedback

Do not wait for people to speak up. Build a mechanism that makes them.

  • Separate blunt critique from decision authority.
    • Pixar's Brain Trust has no authority, so the director does not have to follow any suggestion, and the fix comes from the filmmaker Ed Catmull, Pixar41:58.
    • Tell the team that early work is supposed to be bad, so people attack the idea and not the person Ed Catmull, Pixar40:30.
    • Catmull says all the films now seen as brilliant were once terrible, and the job is to make them suck less Ed Catmull, Pixar40:30.
  • Give employees a confidential way to signal a bad manager.
    • Morita started a weekly company newspaper listing openings elsewhere in the firm, and employees could apply confidentially Akio Morita, Sony59:00.
    • A manager that many people tried to leave stood out as inadequate. It started when a young employee said a "stupid" section chief had come to represent Sony to him Akio Morita, Sony59:00.
  • Give the board an off the record place to question you.
    • Chang emailed the agenda two weeks ahead and hosted independent directors to dinner the night before each meeting, off the record Morris Chang, TSMC48:12.
    • Directors raised the capex plan even before that dinner Morris Chang, TSMC48:12.
  • Tell people honestly how they are doing.
    • Noyce loved Andy Grove's five-level rating system, from Superior to does not meet requirements Bob Noyce, Intel45:01.
    • He believed the hotshots arriving in the late 1960s and early 1970s had never had honest grades, because colleges inflated marks to keep students out of Vietnam Bob Noyce, Intel45:01.

2.3 Test ideas hard and share the lessons widely

Challenge the content, not the person, and let the whole company learn from each failure.

  • Criticize in the open so one mistake teaches everyone.
  • Be the first to say your own strategy has failed.
    • Nvidia had recruited over 100 engineers on a vision of setting industry standards. Jensen told his co-founders the vision was dead and the company had to out-engineer rivals inside Microsoft's standard Jensen Huang, Nvidia41:22.
    • Admitting the failure let the company act in time, and led directly to the Riva 128 and the company's survival Jensen Huang, Nvidia41:22.
  • Make every claim face a test, in writing.
    • After a bad presentation in 2004, Bezos banned PowerPoint and required short narratives, because a memo's structure exposes what matters more than what Jeff Bezos, Amazon17:20.
    • Bezos assumes each sentence is wrong until he can prove otherwise, and he challenges the content, not the writer's motive Jeff Bezos, Amazon20:10.
    • Meetings open with about 20 minutes of silent reading Jeff Bezos, Amazon17:20.
  • Give every requirement a named owner who can defend it.

2.4 Flatten the structure so information and decisions move together

Fewer layers and shared codebases mean truth travels fast and people can act without permission.

  • Design an organization you can manage directly.
  • Tell everyone at the same moment, and organize around the mission.
    • In a robotics meeting, new grads, three vice presidents and two executive staff heard a decision at exactly the same time Jensen Huang, Nvidia29:09.
    • Teams are wired around a specific mission, with the best skills pulled from across the company Jensen Huang, Nvidia30:08.
    • The cost is high pressure on leaders, since no one has privileged information to lean on Jensen Huang, Nvidia30:08.
  • Remove the structures that make people wait.
    • Noyce put executives in one big room and sent cross-department problems to councils of the people on the line Bob Noyce, Intel41:01.
    • Facebook hired engineers into the company, not onto a team, and kept one codebase, so people could be reassigned quickly against Google+ Mark Zuckerberg, Meta3:32:50.
    • Bezos and Jassy mandated that all Amazon teams talk only through service interfaces, with no back doors and no shared data stores Jeff Bezos, Amazon Web Services46:35.
    • By 2002 Amazon's single 1995 codebase meant any new code risked breaking everything, and the company ground to a halt Jeff Bezos, Amazon Web Services46:35.
  • Meet on a fixed rhythm to spread what works.

2.5 Decide on partial information and make mistakes cheap

Speed comes from sorting decisions by reversibility and then accepting some errors.

  • Give two-way doors light process and decide at about 70% of the information.
    • Bezos said day two companies make good decisions slowly, and slow decisions drive builders away Jeff Bezos, Amazon1:07:50.
    • Reversible decisions should not get the heavy process of one-way doors Jeff Bezos, Amazon1:07:50.
    • The safeguard is being good at quickly spotting and correcting bad decisions. Being wrong then costs less than being slow, which is expensive for sure Jeff Bezos, Amazon12:45.
  • Disagree and commit instead of running a long persuasion cycle.
  • Choose a hill fast, and if it is wrong, turn and attack the other.
  • Treat mistakes as the price of being active.
    • Kamprad said fear of mistakes is the root of bureaucracy, and that mediocre people spend their time proving they were not wrong Ingvar Kamprad, IKEA18:57.
    • He admitted losing hundreds of millions of dollars on projects such as a TV factory stake, a Russian sawmill, and ventures in Romania and Thailand Ingvar Kamprad, IKEA18:57.

2.6 Plan by readiness and set hard clocks

Skip the forecast, rehearse the options, and give work a deadline that does not let it expand.

  • Steer day by day instead of writing a long plan.
  • Rehearse what-ifs, then move within hours when the chance arrives.
  • Set deadlines shorter than feels comfortable.
    • Kelleher told a new marketing vice president that a nine month commercial plan meant next Wednesday, because a smaller airline had to be faster Herb Kelleher, Southwest Airlines38:07.
    • Hock gave Aram Tulan nine months to build Visa's whole authorization system after IBM and integrators bid too high and too slow Dee Hock, Visa1:56:30.
    • Jensen Huang times each task as if there were no delays, queues or downtime, and judges teams against that speed of light Jensen Huang, Nvidia20:45.
    • The Visa system worked in nine months. Visa then built clearing and settlement, cutting average settlement from about a week to overnight and saving banks about $15 million in year one Dee Hock, Visa1:56:30.
    • Arnault phoned an employee two hours after a file reached the desk to ask how much had sold Bernard Arnault, LVMH13:53.

2.7 Where they differ

The goals match, but founders disagree on how hard to push and how public to be.

  • Combat or patience.
    • Jobs built a combative culture where veterans were told to dial it back at later jobs Steve Jobs, NeXT6:36.
    • Catmull never had a yelling argument with Jobs. He presented the facts and waited until Jobs said "you're right" Steve Jobs, NeXT46:00.
  • Public or confidential criticism.
    • Jensen Huang criticizes in front of the whole company so everyone learns Jensen Huang, Nvidia16:40.
    • Morita and Chang built private channels, a confidential transfer list and an off the record dinner Akio Morita, Sony59:00, Morris Chang, TSMC48:12.
    • Private routines suit upward feedback to a powerful leader. Public critique suits lessons that the whole company needs.
  • Pressure works only with honest reporting.
    • Arnault pushed staff relentlessly and built the leading French private house developer in 5 years Bernard Arnault, LVMH13:53.
    • At NeXT, pressure with no safe way to say "it will be late" produced "one more month" and hidden sales Steve Jobs, NeXT30:07.
  • Preparing for both outcomes.

Sources

Part of Building and Leading the Company in the growth library.