Wednesday Reality: When Small Forces Break Large Systems

The Frequency Hidden Inside the Structure

A bridge can survive an enormous load and still become dangerously unstable under forces that appear almost trivial. The apparent contradiction disappears once engineering stops treating structures as static objects. Every elastic structure can store and release energy. Deflect a beam and it attempts to return to its original position. A building sways under wind and moves back. A suspended bridge deck twists and recovers. Because mass and elasticity interact, these movements have preferred patterns and frequencies that engineers call natural modes. A structure does not respond equally to every disturbance, and some frequencies excite it far more effectively than others.

Most disturbances cause little trouble. Energy enters the structure, some becomes motion, and damping gradually dissipates it through friction, material deformation and interactions between components. Repeated excitation near a natural frequency changes the equation because the structure may not have finished one oscillation before another force arrives. Instead of allowing the previous movement to dissipate, the new input reinforces it, and subsequent inputs can do the same. The individual force may remain small while the amplitude progressively grows.

This is the uncomfortable property of resonance: failure does not necessarily require increasing force. Sometimes the force remains almost unchanged while the system's response becomes progressively larger. Engineers therefore cannot ask only how much load a structure can withstand. They must also understand how often that load arrives, how the structure responds dynamically and whether enough energy can dissipate between successive disturbances.

Tacoma, and the Danger of the Convenient Explanation

The collapse of the Tacoma Narrows Bridge in 1940 often appears in simplified explanations of resonance. Wind supposedly excited the bridge at its natural frequency until the structure tore itself apart. The reality proved more interesting. The bridge suffered from aeroelastic instability, particularly torsional flutter. The interaction between wind and the moving bridge changed the aerodynamic forces acting upon it. Motion influenced force, force produced more motion, failure does not necessarily require increasing forceand the system stopped behaving like a passive structure receiving an external disturbance.

That distinction matters because a system can enter a regime where the original forcing no longer explains the magnitude of what follows. Feedback takes over, and once that happens, asking whether the initial disturbance looked large enough to cause the final outcome becomes almost meaningless. Engineering therefore cares deeply about damping. A system needs somewhere for injected energy to go. Without sufficient dissipation, energy accumulates in motion and the behaviour of the system increasingly depends upon its own previous behaviour.

Organisations possess their own mechanisms for absorbing disturbance, although nobody can calculate their natural frequencies with an equation. Teams need time to understand a new direction, architectures need time to stabilise, responsibilities need time to become understood, relationships need repeated interactions before trust develops, and new processes need enough repetitions before anyone can distinguish a structural flaw from simple unfamiliarity. These activities may look like pauses between productive events, but they form part of the dynamics that allow the system to settle.

The Organisation That Never Stops Moving

Companies usually evaluate change by magnitude. A major reorganisation feels dangerous, as does replacing a core platform or changing an operating model. A small adjustment to priorities does not appear equally threatening. Neither does moving ownership of one service, adding another approval, changing a metric, introducing another tool or modifying the quarterly objectives. Each intervention looks harmless when examined independently, yet frequency can transform their combined effect.

Imagine an organisation receiving a modest strategic adjustment every six weeks. Teams redirect work, managers renegotiate dependencies, product plans change, architecture bends towards the new objective and reporting follows. Before those changes settle, another adjustment arrives. Nothing individually looks unreasonable, yet the organisation never returns to equilibrium because yesterday's adaptation remains in motion when tomorrow's disturbance enters the system.

Eventually the organisation develops oscillations strangely disconnected from the size of the decisions producing them. Projects accelerate and stop, ownership moves backwards and forwards, architectural migrations begin enthusiastically and remain half-completed, teams repeatedly reorganise around the latest constraint, and priorities receive intense attention before quietly disappearing. From above this can look like an execution problem. From inside the system, the frequency of intervention has exceeded its capacity to dissipate change.

When Flow Starts Oscillating

The first visible symptoms often appear in processes rather than people. Organisations rarely change every part of a value stream at the same speed. One component accelerates while another retains its previous capacity: development produces faster than review can absorb, sales closes customers faster than onboarding can integrate them, product generates initiatives faster than engineering can complete them, or engineering deploys faster than operational practices can mature. Work accumulates at the boundaries even though each component may appear locally productive.

The intuitive response is often to increase pressure on the constrained component through additional targets, greater visibility, more frequent status checks or another process. Yet a system repeatedly pushed between starvation and overload loses flow even when its average theoretical capacity appears sufficient. People switch contexts, work ages in queues, priorities change while tasks remain unfinished, and rework increases because assumptions made when the work started no longer hold when it finally reaches the next stage. The organisation appears busy everywhere while throughput becomes strangely disappointing, not necessarily because any individual component lacks capacity but because those components have stopped moving coherently.

People Learn the Frequency

Mechanical structures do not anticipate the next disturbance, but people do, and this changes organisational resonance profoundly because repeated intervention creates learning. If priorities historically remain stable for two years, investing deeply in a difficult architectural improvement makes sense. Building expertise around a strategic capability and challenging an expedient decision also make sense because their consequences will probably remain long enough to matter.

If priorities historically survive six weeks, the rational response changes. Engineers favour reversible decisions, managers hedge commitments, teams postpone investments whose return requires stability, and difficult migrations remain permanently halfway finished because completing them requires confidence that the destination will still matter. From outside, this behaviour can resemble a lack of ownership. From inside, the system has simply taught people the expected lifetime of organisational decisions.

As the forcing frequency rises, commitment acquires an economic cost and waiting acquires option value. People begin protecting themselves against organisational volatility much as engineers design systems to tolerate unstable environments. The organisation may then demand greater commitment precisely because its own behaviour has made deep commitment increasingly irrational.

The Quiet Withdrawal of Energy

Eventually some people stop trying to predict the next oscillation. They do not necessarily resign, disengage visibly or become poor performers. They continue attending meetings, delivering work and answering messages, while something less visible disappears: discretionary energy. They stop repairing things nobody explicitly asked them to repair, challenging decisions whose consequences they can already foresee, investing deeply in organisational improvements likely to disappear with the next initiative, or mentoring beyond what their formal responsibilities require.

This differs from simple laziness because experienced people often absorb enormous amounts of organisational disturbance. They translate ambiguous strategy into workable decisions, remember why previous approaches failed, resolve contradictions informally before those contradictions become escalations, and provide continuity while formal structures change around them. When those people withdraw discretionary effort, the organisation loses part of its capacity to dissipate disturbance. The next change therefore produces a larger oscillation, which management may interpret as evidence that stronger intervention has become necessary.

The resulting pattern can resemble silent resignation without anybody actually leaving. The employment relationship continues and measurable output may remain respectable, but the organisation gradually loses the invisible contributions through which experienced people once stabilised it. What disappears does not appear neatly in utilisation reports because the organisation usually never measured the energy those people absorbed in the first place.

The Silent Warriors

Others react differently because they refuse to withdraw. These are often the people who remember everything: the transformation from three years ago, the reason the current architecture exists, the tool that was supposed to solve the same problem last time, the abandoned migration, the temporary process that became permanent and the strategic priority quietly replaced before anyone acknowledged its failure.

At first, these people provide extraordinarily valuable resistance. Engineering systems need resistance because a structure without damping does not become agile. It becomes unstable. Organisations similarly need people willing to question enthusiasm, preserve institutional memory and prevent every fashionable idea from becoming an irreversible decision. The person asking an awkward question may therefore function less like an obstacle than a damper absorbing energy that would otherwise propagate through the system.

Repeated forcing, however, can transform useful resistance into something darker. Scepticism becomes anticipatory, every initiative resembles the previous failed initiative before evidence exists, new leaders inherit credibility debts from predecessors they never met, and new colleagues discover that ideas must survive an informal historical tribunal before anyone will invest in them. Sarcasm becomes an immune response, while informal networks form around shared scepticism among people who may sincerely believe they are protecting the organisation because, for years, that is exactly what they did.

Eventually the organisation labels some of them toxic, and sometimes the description has become accurate. What the label rarely explains is how valuable institutional resistance became corrosive in the first place. Treating the individual as the origin of the problem may remove an unpleasant symptom while leaving untouched the forcing conditions that produced it.

When Different Frequencies Collide

An organisation rarely receives only one forcing function. Finance works to quarterly rhythms, product discovery may operate continuously, engineering investments can require years, sales follows customer and market cycles, hiring responds on another timescale, while executive strategy moves according to board expectations, competitive events and capital constraints. Each rhythm can make sense independently while interacting badly with the others.

Product may ask teams to experiment rapidly while finance demands predictable quarterly commitments. Platform engineering may seek standardisation while business units demand local autonomy. Architecture may require continuity while portfolio management repeatedly reallocates capacity. Teams can simultaneously receive instructions to optimise reliability, delivery speed, innovation and cost. None of these objectives must be foolish for their combination to create instability.

The problem can lie in their phase relationship. Forces can reinforce one another or partially cancel, allowing considerable organisational energy to produce remarkably little net movement. The resulting frustration usually triggers demands for greater alignment, which frequently means another coordination mechanism, reporting layer, operating model or recurring governance process entering a system already struggling to dissipate previous interventions.

When the System Starts Forcing Itself

This is where organisational resonance becomes more interesting than the simple claim that companies change too often. Management observes queues and introduces process changes. People respond cautiously because previous process changes disappeared quickly. Management interprets caution as insufficient ownership and strengthens accountability. Experienced people become more sceptical, their scepticism gets interpreted as cultural resistance, and a transformation programme appears to repair the culture.

Each response remains understandable when examined locally, yet together they form a feedback mechanism. The organisation no longer needs a particularly incompetent leader, a malicious manager or a disastrous strategy. Rational actors can sustain the oscillation because each reacts sensibly to behaviour produced by the previous reaction. The system begins generating part of the disturbance that keeps it unstable.

Tacoma Narrows reached the frightening point where motion itself altered the forces acting upon the bridge. Organisations can cross a similar conceptual boundary when intervention creates behaviour and that behaviour subsequently justifies further intervention. The resulting intervention strengthens the behaviour that justified it, until cause and response become difficult to separate.

At that point, asking whether the latest organisational change was objectively large enough to create the observed disruption misses the system entirely. A structure capable of surviving an enormous isolated load can become unstable under much smaller repeated forces when they arrive at the wrong rhythm and the system cannot dissipate their energy.

Perhaps some organisations described as resistant to change suffer from something more complicated. The forces acting upon them may indeed look individually modest, and the people applying those forces may make entirely reasonable decisions when each decision is examined alone. The question engineering leaves behind is less comfortable: perhaps nobody has measured the force incorrectly, while almost nobody has thought to measure the frequency.