Photo by Austin on Unsplash

Newton did not begin with equations. He began with a more irritating problem: something in the world was clearly shaping motion, but the thing itself could not always be seen.

An object resisted acceleration, and from that resistance mass had to be inferred. A body remained at rest, or stayed in motion, and inertia revealed itself not as a visible substance but as a pattern in behavior. Planets curved toward one another across empty space, and gravity announced its presence through consequence long before it could be named with confidence. What mattered was not merely what moved, but why it moved as it did: what pulled on it, what slowed it, what kept it going, and what made some bodies harder to redirect than others.

The visible event is only the clue. The real task is to reason backward from motion to structure; from acceleration to force, from resistance to mass, from orbit to gravity, from persistence to inertia. Discovery begins when observation stops taking movement at face value.

Organizations invite the same mistake. We talk about decisions, personalities, priorities, and leadership as though intent were the primary engine of motion. But anyone who has spent enough time inside a real company knows that what is visible on the surface rarely explains what is actually happening underneath. Teams stall for reasons that have little to do with attitude. Initiatives gather momentum long after their purpose has thinned out. Some changes require enormous effort to produce almost no movement at all, while other small interventions redirect entire functions.

Businesses, like physical systems, are shaped by forces that are easiest to notice through their effects. They have mass in the form of legacy systems, habits, dependencies, and institutional memory. They have inertia in routines that persist because they are already in motion. They have resistance in fatigue, bureaucracy, mistrust, and misaligned incentives. They even have gravity: centers of power, process, and history around which everything else begins to bend.

Newton was not writing leadership theory, and companies are not clockwork. Their variables are messier, more political, and inconveniently human. The discipline still applies.

If we want to understand how organizations actually move, and what leadership really does inside them, we have to begin the same way: by learning to identify the forces at work beneath the motion we can see.

Force and Structure

Once you begin looking at organizations as systems of motion rather than theaters of intention, one pattern becomes difficult to ignore: many businesses are spending extraordinary amounts of force to produce outcomes that should not require that much effort to sustain.

The same priorities must be restated every quarter. The same coordination failures require the same escalations. Teams hit the same bottlenecks often enough that the workaround becomes part of the job. Progress occurs, but only through repeated exertion.

That kind of movement is real, and it can look impressive for a while. But when outcomes depend on fresh effort every cycle, the problem is usually not motivation. It is that too little energy has been stored in the structure of the work itself.

A team can move water by carrying buckets. Enough labor, enough oversight, and enough insistence will usually get water from one place to another. But if the need is constant, the more revealing question is not how to make people walk faster. It is why the organization is still organized around buckets at all.

Some leaders operate primarily through direct force. They supply urgency, apply pressure, resolve conflict, create accountability, and push stalled work back into motion. In certain conditions, that is exactly what is needed. Dead systems rarely recover through sentiment, and a team in crisis may need concentrated effort before it needs elegance.

But direct exertion is only one way of producing motion, and not usually the most durable one.

Another class of leader works by changing the conditions through which force travels. Instead of repeatedly supplying the same energy by hand, they redesign the terrain so that effort goes farther once applied. They reduce drag, remove collisions, and redirect load. They create channels through which work can move with less waste, less repetition, and less dependence on constant supervision.

This is the difference between direct force and mechanical advantage: between making people carry harder and building the aqueduct.

This is one of the clearest ways to understand the leadership value of architects, platform owners, stewards, principal engineers, and other senior technical operators whose influence is often underestimated in environments that still equate leadership with visibility, hierarchy, or headcount.

An architect, at their best, studies where motion is breaking down: where dependencies collide, where effort dissipates, where local optimization is creating systemic drag. Their value is not simply that they know more technology, but that they can reshape the environment so that the same outcome requires less repeated force. Water still has to move, but now it moves through structure rather than strain.

A steward serves a different structural function: preserving integrity over time. Good stewardship is not bureaucratic hesitation, but the discipline of noticing when apparent acceleration is really deferred damage; when speed is being purchased by transferring strain into the future. The steward protects the system from forms of motion that look productive while quietly increasing fragility.

A platform owner governs something equally consequential: the instrument through which future force will be applied by many other people. Every improvement to reliability, usability, clarity, or scale changes the landscape of the organization around it. When work becomes more predictable, fewer decisions sit between intent and execution. Friction is not merely endured; it is designed down.

This kind of leadership is easy to undervalue because, when it works, the organization often looks less dramatic. There are fewer emergencies, fewer heroic recoveries, fewer rituals of re-alignment, and ultimately, fewer people marching back and forth with buckets.

To organizations addicted to visible urgency, that can look like passivity. In reality, it is often a sign that force has finally been aligned with structure, and structure with purpose.

That distinction matters because organizations that rely only on direct exertion will spend themselves recreating motion again and again. Organizations that invest in mechanical advantage do something more durable: they store effort in standards, tools, pathways, and shared systems that continue working after the meeting ends.

The Problem of Visible Leadership

Once you start looking for leverage rather than spectacle, another pattern becomes hard to miss: organizations are much better at noticing force in motion than force conserved, redirected, or made unnecessary.

They easily recognize the leader driving a difficult initiative because the effort is visible. They can hear the executive announcing a new priority, watch the manager pushing a team through resistance, and rally around the emergency responder who steps into a failing situation with enough authority to restore order. These forms of leadership produce an obvious narrative. There is motion, conflict, intervention, and a protagonist standing near the center of it.

The person who made the crisis less likely in the first place often produces no comparable scene.

That does not make their contribution smaller, but prevention rarely creates spectacle, and stability does not photograph well. A well-designed platform does not generate the same emotional satisfaction as a late-night recovery call. A process that quietly prevents collisions across teams does not feel as dramatic as a leader “taking charge” once those collisions have already turned into failure.

Organizations tend to infer value from what they can easily narrate, and visible exertion is easier to narrate than structural advantage. Action, rescue, and escalation are legible. The slow accumulation of good constraints, shared standards, usable platforms, and durable architecture, however, often disappears into the background precisely because it is doing its job. When force is successfully stored in structure, later motion feels natural, and people forget to ask what made it so.

Every business says it values scale, resilience, consistency, and efficiency. But the people most capable of producing those outcomes are often left structurally undernamed. Architects get treated as senior technical specialists rather than leaders altering the organization’s capacity to move. Platform owners are reduced to tool custodians rather than recognized as governors of shared mechanical advantage. Stewards are dismissed as bottlenecks by people who can see the friction they introduce but not the fragility they prevent.

In each case, the misunderstanding is similar: the organization notices local drag more easily than systemic protection.

And so advancement models tilt toward visible command. Influence gets associated with headcount, budget, crisis response, or proximity to executive attention, while quieter forms of load-bearing leadership remain harder to classify. The people issuing force are easier to reward than the people redesigning the paths through which force must travel.

Over time, the cost of that misrecognition compounds. Critical knowledge concentrates in a few overburdened individuals instead of being translated into shared systems. Standards remain implicit rather than operationalized. The same arguments recur because the underlying decisions were never encoded into structure. Teams continue working around problems that should have been removed at the level of architecture, process, or platform design.

Leadership keeps demanding acceleration, while the organization beneath it keeps paying the tax of avoidable friction.

From the outside, this often looks like a speed problem. In reality, it is usually a leverage problem.

The business keeps rewarding the people who carry buckets fastest, while failing to invest in the people who might have built the channel.

Command and Constraint

Newton’s real usefulness here is not that he gives us a tidy model for managing people. Human systems are too interpretive, political, emotional, and self-aware to submit cleanly to physical law.

Instead, he reminds us that visible motion always has an explanation. To understand why something moves, stalls, resists, accelerates, or breaks, you have to look beneath the event itself and reason backward toward the forces shaping it. You have to ask what carries weight, what absorbs force, what preserves momentum, what creates drag, and what everything else has already begun to orbit.

Most organizations reward too little of that kind of seeing.

They still talk about leadership as though command were mainly a matter of clarity, confidence, decisiveness, or will. Certainly, those things have their place; but they are not, by themselves, a sufficient account of motion inside a real system. Intention does not cancel inertia. Pressure does not erase drag. Urgency does not remove mass. And authority, however exercised, does not free anyone from the structures already shaping the path of force.

Through this lens, leadership is not merely the ability to demand effort, perform certainty, or occupy the center. At its best, it is a disciplined understanding of how motion actually works inside a system, and how to intervene without wasting force or transferring damage somewhere less visible.

Sometimes, of course, the intervention must be direct. There are moments of crisis, ambiguity, and transition when motion has to be reestablished through concentrated effort. Some burdens will always have to be carried by hand.

Mature organizations do not confuse that necessity with an ideal. They recognize the people who make force travel farther, reduce the energy lost to friction, and store effort in structure so progress does not have to be recreated from scratch every quarter.

They recognize the people who build channels instead of merely demanding more buckets. The people who build levers instead of praising themselves for lifting harder. The people who understand that good structure is not the enemy of speed, but the only reason speed survives contact with scale.

The strongest leaders, in the end, are not always the ones applying the most force. More often, they are the ones who understand force well enough to stop wasting it.