Skip to content
    Influence & decisionsChapter 35

    What Do You Care What Other People Think? (Short Summary)

    Richard Feynman on independent thought, engineering integrity, risk, and the connection between experiment and management decisions.

    Book summaryworking30 minevergreen · reviewed Aug 13, 2026
    Tech Lead
    Staff+
    Chapter outline

    What Do You Care What Other People Think?

    Authors: Richard P. Feynman, Ralph Leighton
    Publisher: W. W. Norton & Company
    Length: 1988

    Richard Feynman on independent thought, engineering integrity, risk, and the connection between experiment and management decisions.

    What Do You Care What Other People Think? — original coverOriginal
    What Do You Care What Other People Think? — translated coverTranslation

    Brief

    The essential idea

    Richard Feynman's book combines personal stories with his account of the Space Shuttle Challenger investigation. For engineering leaders, the important link is between individual intellectual honesty and organizational safety: technical reality must outrank status, reputation, schedules, and a convenient report.

    The Challenger case illustrates a recurring organizational failure. Engineers observe a risk, the signal loses force as it moves through reporting layers, uncertainty is reframed as acceptable safety, and management ends up controlling the presentation of risk rather than the risk itself.

    The practical response is a culture of independent thought, explicit assumptions, honest probability and impact estimates, falsifiable hypotheses, cheap experiments, early-warning signals, and documented stop criteria. Disagreement grounded in evidence must be treated as a safety mechanism rather than disloyalty.

    Decision lens

    Key takeaways

    Independent thinking is a professional engineering duty, not merely a personality trait.

    High-stakes systems cannot replace explicit risk estimates with optimistic narratives.

    Facts, interpretations, and conclusions should be separated in documents and reviews.

    Simple experiments can expose reality more effectively than long approval chains.

    ADR, postmortems, and operating standards preserve assumptions and organizational memory.

    Leaders must create a safe path for engineers to challenge management with evidence.

    Workplace experiment

    Apply it at work

    1. 1

      Revisit one contested technical decision and separate known facts from assumptions and interpretations.

    2. 2

      Ask the team to formulate the strongest counterargument to the preferred option.

    3. 3

      Design one inexpensive experiment for the riskiest hypothesis before taking an irreversible step.

    4. 4

      Update the decision record with early-warning indicators and explicit triggers for changing course.

    Choose one action, define the observable effect, and keep the first test small enough to reverse.

    Evidence

    Sources and further reading

    Additional sources

    Channel, aggregator, and commentary links confirm the work; they are not the primary source.

    Previous chapterHow Product Managers, Analysts, and Designers Create Value Through ThinkingNext chapterTechnology Strategy Patterns (Short Summary)