Encyclopedia directory
Search the complete atlas or narrow it by entry type, topic, and evidence state.
Filtered view
Program Management
William Knudsen's industrial persuasion helped begin U.S. rearmament, but victory required a changing coalition of public authority, private production, labor, science, logistics, and operational evidence—capable of extraordinary learning, output, and coercion.
How can a society convert strategy into production, logistics, research, training, and operations under existential time pressure?
Boeing's 737 MAX failures show how commercial commitments, derivative design, fragmented hazard analysis, delegated certification, and training choices can keep dispersed safety evidence from governing a whole aircraft. Two crashes killed 346 people. A redesign returned the MAX to service, but a 2024 door-plug separation and continuing regulatory intervention showed that manufacturing quality, safety culture, and accountability remained governance problems.
How can a large engineering institution keep dispersed safety evidence authoritative while coordinating complex products under commercial and schedule pressure?
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?
Apollo coordinated NASA centers, contractors, interfaces, tests, and configuration decisions into a temporary enterprise capable of landing people on the Moon under a fixed deadline. Apollo 1 also shows how prestige and schedule can narrow safety evidence despite formal systems.
How can a temporary enterprise integrate thousands of components, contractors, interfaces, risks, and decisions toward a fixed mission?
NASA historians Courtney Brooks, James Grimwood, and Loyd Swenson reconstruct how the Apollo command, service, and lunar modules moved from competing concepts through contracts, redesign, testing, failure, and flight. The official history makes systems integration tangible by following the interfaces among public program offices, contractors, engineers, budgets, schedules, and crews.