Systems & Organizations
Stop Scaling Teams Like Heat Engines
Most leaders believe adding people speeds output, yet the Apollo 13 crew proved extra “heat” can jam the system.
2026-08-041 min read
Heat engines achieve more power only when they can move energy across a temperature gradient without bottlenecked flow. The same mathematics describes how information moves through an organization: each person is a conduit, and the gradient is the urgency of a decision. When a team grows faster than its communication channels, the “thermal resistance” of meetings, emails, and approvals rises sharply, throttling the whole system. The result is not a linear slowdown but an exponential drag that can stall even the most capable groups.
During the 1970 Apollo 13 crisis, flight directors faced a cascade of alarms, oxygen leaks, and power failures. Rather than flooding Mission Control with more engineers, they erected a single “white‑board” where every subsystem lead posted a concise status and a single “go/no‑go” decision point. This intentional bottleneck reduced thermal resistance, letting the crew’s limited power be allocated where it mattered most and ultimately saved lives.
Modern tech firms often ignore this law, hiring aggressively and layering meetings. The added “heat” of new hires and extra syncs raises friction, so the organization’s throughput collapses under its own weight. The paradox is that more capacity can produce less output unless the information pathway is deliberately narrowed.
The cure is to treat coordination as a heat‑exchange system: keep the gradient steep by limiting handoffs and centralizing decision points, rather than assuming raw headcount will automatically boost velocity.
Key insights
Coordination resistance grows faster than headcount; each new person adds more than one unit of friction.
Centralizing decision authority creates a low‑resistance path that lets scarce attention flow where it’s needed most.
Why it matters
Ignoring coordination drag turns hiring sprees into hidden budget overruns that cripple delivery schedules.
Unchecked information friction erodes employee morale, as workers spend growing fractions of time waiting for answers instead of creating value.
Use this tomorrow
1Open the last sprint’s retrospective notes, count how many distinct “decision‑owner” tags appear per story, and aim to reduce that count by at least one for the next sprint.
2In your team chat, identify the most frequent thread that contains a “who‑owns‑this?” question and assign a permanent owner; verify that the same question no longer resurfaces for two weeks.
Go deeper
The “thermal resistance” analogy originates from the study of heat transfer in engineering, where adding material can insulate rather than conduct. In organizations, each additional reporting line, meeting, or email thread acts like an insulating layer, reducing the net flow of actionable information. Researchers such as Carliss Baldwin have highlighted similar effects in “modular” product design, where overly tight coupling slows evolution.
The principle also appears in biology: ant colonies allocate a few specialized scouts to gather information, avoiding the chaos of every ant searching independently. Over‑distributed sensing leads to “information overload” that stalls collective foraging, mirroring how bloated teams stall execution.