IdeaClaim Cited
The Challenger record shows that a warning can be spoken, documented, and debated without retaining enough authority to change a decision. The official investigation, participant testimony, and later scholarship support different parts of that account; they do not make culture, informal organization, trust, voice, and psychological safety interchangeable causes or remedies.
What happens to a warning as it moves through status, routine, evidence, and production pressure?
InstitutionClaim Cited
Under Thomas J. Watson Sr. and Jr., IBM joined a disciplined sales-and-service culture to long-horizon investment in computing, then bet the company on System/360 as a common platform. The transition illustrates how institutional identity can coordinate enterprise change while hierarchy, labor, and market power constrain whose knowledge counts.
How can a technology company build a durable identity, professional customer interface, and coordinated bets across rapidly changing products?
InstitutionClaim Cited
A founder-centered renewal and mission movement that survived its founder's execution by becoming a distributed network of local assemblies, household communities, itinerant messengers, shared practices, and contested testimony.
How did a small founder-centered movement preserve purpose, coordinate dispersed communities, resolve disputes, and survive the founder's death without a settled canon, bureaucracy, or state power?
Thinker PractitionerClaim Cited
Amy C. Edmondson developed psychological safety as a team-level construct after an early hospital study exposed the ambiguity of detected error counts. Her research connects perceived interpersonal risk with learning behavior, while her books extend that inquiry to fluid collaboration and intelligent failure. Independent syntheses support important associations but also limit causal, universal, and impact claims.
Thinker PractitionerClaim Cited
Ben Horowitz turned the near-death experiences of Loudcloud and Opsware into an executive philosophy for decisions that remain painful after every easy answer has disappeared. His writing emphasizes truthful diagnosis, situational leadership, organizational design through action, and responsibility for layoffs and personnel decisions—while retaining the founder-and-investor viewpoint and its concentrated authority.
Thinker PractitionerClaim Cited
Chester Barnard drew organizational theory from four decades inside the Bell System and public institutions. He described formal organizations as fragile cooperative systems sustained by communication, willingness, and purpose; located authority partly in the recipient's acceptance rather than the superior's command; and made executive moral judgment central to keeping cooperation viable.
Thinker PractitionerClaim Cited
Chris Argyris studied the defenses that let intelligent people avoid learning while appearing rational and in control. Moving from conflicts between mature adults and formal hierarchy to theories-in-use, defensive routines, and double-loop learning, he made the reasoning behind action—not only outcomes—available for inquiry and change.
Thinker PractitionerClaim Cited
Karl E. Weick treated organization as ongoing organizing and developed influential accounts of enactment, sensemaking, and loose coupling, later co-developing a managerial synthesis of high-reliability organizing. His work is largely conceptual and case-interpretive; independent reviews document broad uptake while finding limited empirical testing of early claims and important gaps around power, institutions, embodiment, material causality, worker burden, and intervention effects.
Thinker PractitionerClaim Cited
L. David Marquet developed intent-based leadership while commanding the nuclear-powered submarine USS Santa Fe. His leader-leader model relocates control toward the people holding operational knowledge while requiring competence and shared clarity; its military setting also makes the boundaries between delegated judgment, lawful command, and genuine autonomy impossible to ignore.
WorkClaim Cited
Forsgren, Humble, and Kim built Accelerate from four years of voluntary, self-reported DevOps surveys, using statistical models to connect software-delivery measures with technical practice, culture, and organizational outcomes. The findings challenged a supposed tradeoff between speed and stability, but the study design establishes associations rather than a universal causal recipe, and its famous metrics have continued to change.