Acceleration Is Not A Strategy

The acceleration instinct#

The modern operating environment is now organised around an unstated assumption: that faster movement reliably produces better outcomes. Reply faster, decide faster, ship faster, scale faster, respond faster. The assumption sits inside the cadence of nearly every contemporary institution — the quarterly earnings call, the two-week sprint, the slide deck due in the morning, the inbound message awaiting a reply that should ideally have arrived already. It rarely needs to be argued for, because the apparatus carrying it never pauses long enough to be questioned.

The assumption is understandable. Speed creates visible advantage. Organisations that respond quickly capture opportunities others miss. Teams that execute rapidly build momentum that compounds. Leaders capable of deciding under pressure appear, and frequently are, more capable than peers who require additional time to arrive at the same conclusion.

But underneath the cadence sits a question the apparatus is structurally bad at asking: when does acceleration stop creating advantage and begin creating distortion? Because speed and effectiveness are not identical capacities, and confusing them is one of the more expensive errors modern organisations make without noticing they have made it.

The argument of this essay is narrower than it may sound. It is not that fast is bad. It is that a tempo, sustained across years, gradually reshapes the system carrying it — and the reshaping is rarely visible until the system can no longer absorb its own pace.

Acceleration consumes time. Pace creates time. The distinction initially appears small. Its consequences rarely are.

The asymmetry of visibility#

Part of the confusion is structural. Speed announces itself. Sustainability usually does not.

Speed is observable in the room — the rapid response, the compressed timeline, the launch shipped on Friday, the meeting that produced a decision in twenty minutes rather than ninety. Sustainability behaves on a different clock. It reveals itself across years rather than weeks, often only in the absence of something — the burnout that did not occur, the rework that was not needed, the senior departure that did not happen, the customer trust that did not erode, the quality incident that did not require a public statement.

The asymmetry produces a predictable institutional pattern. One organisation ships relentlessly, expands continuously, responds immediately, and reads as energetic. Another introduces intervals, builds recovery into its systems, protects periods of reflection, and reads as slow. The first is rewarded immediately, because energy is legible. The second is understood much later, often only when fatigue, attrition, or quality decay appear inside the first.

This is not because speed predicts stronger outcomes. It is because speed is more visible than rhythm. The apparatus is built to detect throughput, and throughput is what it rewards.

Rosa and the scarcity acceleration produces#

The most disciplined intellectual work on the acceleration problem belongs to the German sociologist Hartmut Rosa. His central claim, developed across two decades, is not the familiar observation that life has become faster. It is that acceleration has gradually changed the relationship between modern systems and time itself — and that the change has produced a result none of its architects intended.

Rosa's specific mechanism is worth stating precisely, because it is what gives the argument its weight. Technological acceleration was supposed to give us more time. It hasn't. The reason is that each gain in throughput creates a new baseline of expectation, and the new expectation creates new pressure, and the new pressure is absorbed by additional acceleration before the gain can be experienced as rest. The faster email made replies expected within hours rather than days. The faster reply made replies expected within minutes. The faster meeting made the calendar denser, not lighter. Each acceleration was real. None of them produced the time they were sold as producing. The time was consumed by the expanded baseline before it could be realised.

This is the mechanism that organisations now run on without naming it. More tools, more automation, more efficiency, more optimisation — and less space, less reflection, less recovery, less distance from the work. The productivity gains are real. They are also immediately re-spent on additional throughput, because the apparatus has no mechanism for converting throughput gains into time. The result is the peculiar modern experience that Rosa identified: despite saving more time than any generation in history, we possess less of it.

Acceleration eventually stops creating freedom. It begins consuming it. And inside organisations, what it consumes first is the slack — the unstructured time, the reflection, the recovery — that the system needed in order to remain capable of judgment under pressure.

Boeing and the 737 MAX#

The clearest institutional embodiment of this failure is Boeing's 737 MAX program.

For most of the twentieth century, Boeing was an engineering company that happened to manufacture aircraft. The cadence of the institution was set by engineering judgment — the willingness to extend a certification timeline by a year if the data demanded it, the assumption that the chief engineer's signature carried equal weight with the chief financial officer's, the cultural understanding that the cost of being wrong about an aircraft was categorically different from the cost of being late. That cadence was not a slogan. It was the operating tempo of the institution, and it was what the FAA's delegated-certification model implicitly relied upon.

After the 1997 merger with McDonnell Douglas, the tempo gradually changed. The headquarters moved from Seattle to Chicago, away from the engineering organisation it was meant to oversee. Financial metrics took on greater weight in executive compensation. Share buybacks consumed capital that had historically been reinvested in engineering capability. Certification timelines compressed. Engineering authority was decentralised to suppliers. Each individual decision was defensible. The cumulative effect was a different company operating at a different pace, certifying aircraft inside a tempo that the underlying engineering culture had not been designed to sustain.

The 737 MAX was the product that tempo eventually produced. The MCAS system that brought down Lion Air 610 in October 2018 and Ethiopian Airlines 302 in March 2019 — killing 346 people in total — was not the failure of a single engineer or a single decision. It was the failure of a system that had accelerated past the point at which it could still catch its own errors. The internal Boeing messages later released to Congress made the tempo visible: engineers describing the certification process as designed by clowns supervised by monkeys, knowing the documentation was inadequate, knowing the training was insufficient, and shipping anyway because the program tempo did not permit the interruption that catching the error would have required.

The subsequent Alaska Airlines door-plug incident in January 2024 reopened the same question. The grounding had cost Boeing more than $20 billion. The CEO had been replaced. The certification process had been reformed. And yet, six years after the second crash, a door plug separated from a 737 MAX 9 at altitude because four bolts had not been installed during reassembly at the Renton factory — a process failure of exactly the kind the original investigation was supposed to have eliminated.

The intelligence was real. The expertise was real. The processes were real. The company was no longer the company the processes had been designed for.

Reflection still has its failure mode#

None of this is an argument for slowness. The opposite failure is real and equally expensive.

Organisations can become excessively procedural. Leaders can hide behind endless reflection, treating each additional analysis as evidence of thoroughness when it has in fact become avoidance. Delay can become caution performing intelligence — the appearance of judgment, with none of the responsibility that judgment imposes. The leader who treats every decision as deserving another week of consideration produces, over time, the same kind of damage as the leader who treats every decision as deserving twenty minutes. Both have abdicated the cadence question; they have simply abdicated it in opposite directions.

The argument is narrower. Speed is necessary. It is not sufficient. The problem emerges when speed eliminates the rhythm the system requires in order to remain capable of catching its own errors — and the leader optimising for visible tempo is rarely the one who notices the rhythm has been lost.

Speed answers: how quickly can movement occur? Sustainability asks: at what cost can movement continue? The two questions are partners. The failure mode at either extreme is the elimination of the other.

The tempo review#

Complex environments increasingly require a discipline institutions rarely perform: tempo review. Not how quickly are we moving, but what pace can this system survive. Not how much more can be added, but what recovery have we protected. Not can acceleration continue, but what breaks if it does, and how would we know in time.

The difficulty is not intellectual. The difficulty is that slowing visible movement frequently feels irresponsible inside systems that have been rewarding urgency for a decade. The leader who introduces deliberate slack is making a bet against the operating logic of their own institution, and the bet only pays off in things that do not happen — the burnout that did not occur, the error that was caught before it shipped, the senior engineer who did not leave. The apparatus has no mechanism for measuring averted failure, and so the leader who produces it is rarely credited for it. Institutions do not reward what did not happen.

The leaders who hold this discipline tend to build it structurally — a standing practice of asking, on a calendared cadence, whether the tempo their organisation is operating at is one the underlying system can absorb without distortion. Not a performance review. A tempo review. The board cycle measures whether the plan is being executed. Almost no institution has a comparable cycle for asking whether the pace of execution is one the institution can survive at scale.

The quieter distinction#

The institutions of the next decade will continue rewarding speed. They should. Speed remains valuable. Responsiveness remains valuable. The capacity to move quickly through complex environments remains genuinely scarce.

But environments shaped by sustained complexity and compounding expectation increasingly reward a quieter capability: the ability to distinguish acceleration from sustainability, and the willingness to interrupt the first in order to protect the second. Some leaders will continue optimising for visible movement velocity. Others will design for the cadence the system can hold over decades. The difference initially appears small. Over a decade, it is the gap between Toyota in 2010 and Boeing in 2024.

Acceleration consumes time. Pace creates time.

And the fastest leaders are not always the most effective. They are often the ones who reached terminal velocity before they noticed the system underneath them was no longer designed for it.