The Moth Effect

There is a particular kind of leader I have encountered more times than I can count.

They are capable. Often extraordinarily so. They are smart, fast, decisive, good in a room. They have a track record of results that is real and earned. They have risen to significant levels of responsibility on the back of genuine ability.

And they are slowly burning their organizations down.

Not through incompetence. Not through bad intentions. Through a pattern of behavior so rewarded, so culturally celebrated, so deeply embedded in how, most organizations define leadership, that almost no one around them can name it as a problem.

They are drawn to the flame.

Every crisis, every escalation, every urgent problem with visible stakes and a ticking clock: they are there. They show up, they engage, they take control, they resolve it. And then they move to the next one. The organization runs on urgency. The leader runs on urgency. And the building: the deliberate, patient, unglamorous work of constructing something durable, never quite happens.

I call this the Moth Effect.

The Shape of the Flame

The flame takes many forms.

Sometimes it is a literal crisis: a product failure, a customer defection, a regulatory issue, a public relations problem that demands immediate attention. These are real. They require real response. But the Moth Effect is not about how leaders handle the occasional genuine crisis. It is about what happens when crisis becomes the default mode of operation: when the urgent is so consistently prioritized over the important that the important never gets built.

Sometimes the flame is an opportunity. A new market, a high-profile partnership, a strategic initiative that generates excitement at the top. These are worth pursuing. But the Moth Effect leader pursues them the same way they handle crises: reactively, completely, at the expense of whatever was being built before: the new light appeared.

Sometimes the flame is simply the inbox. The calls to return, the messages demanding response, the constant low-level urgency of a senior leader's operating environment. This is the most insidious version, because it does not feel like distraction. It feels like work.

In each version, the pattern is the same: the light is bright, the pull is strong, and the leader moves toward it. The building waits.

Things do not calm down in organizations run by urgency. They calm down in organizations that have done the building: that urgency prevents.

Why the System Produces Moths

The Moth Effect is not a character flaw. It is a rational response to a distorted incentive system.

Crisis response is visible. When a senior leader steps into a burning situation and extinguishes it, everyone sees it. The resolution is concrete and immediate. The connection between the leader's action and the outcome is clear and legible. Recognition follows. Reputation is built.

Building is invisible. When a leader spends three months restructuring how decisions get made, or works patiently to improve communication between two functions that have been misaligned for years: no one is standing by to applaud. The improvement is structural and slow. The feedback loop is long. The connection between the leader's investment and the eventual outcome is diffuse and hard to attribute.

Organizations reward what they can see. And what they can see is the leader standing in the middle of the fire: directing traffic, solving problems in real time, moving fast. The leader who is quietly building the structures that would prevent the fire is harder to recognize, harder to promote, harder to celebrate in a town hall.

And urgency feels like competence. When everything is in motion, when there is always something to respond to, when the calendar is full and the decisions are flowing and the problems are being resolved: it feels like leadership. The slow, patient, unglamorous work of building something durable does not feel that way. There are stretches where nothing visible is happening. That discomfort is real. And it pulls leaders back toward the fire.

What the Moth Effect Consumes

The cost of the Moth Effect is not usually obvious until it is catastrophic. In the short term, the urgency-driven leader appears to be producing. Problems get solved. Crises get contained. The organization moves, even if the movement is reactive. Metrics that measure activity look fine.

What is being consumed in the meantime is structural.

The first thing consumed is people. The talent around a Moth Effect leader eventually learns that initiative is not what is valued: crisis response is. The person who identifies a problem early and resolves it quietly is less visible than the person who escalates dramatically and gets the leader's attention. Over time, the organization trains itself to produce the very urgency it is spending all its energy responding to.

The second thing consumed is trust. The Moth Effect leader is constantly in motion, constantly changing focus, constantly reprioritizing based on what is loudest. The people who work for them learn that commitments are contingent, direction is temporary, and the only reliable signal of what matters today is whatever the leader is currently pointed at.

The third thing consumed is time: specifically, the time that building requires and that urgency eliminates. Great organizational structures are not built in crisis mode. The clarity that comes from thinking carefully about how work flows, how authority should be distributed, how information should travel: this requires protected attention. The Moth Effect leader is never not in crisis mode. The protected time never materializes. And the building never gets done.

What have you built here that will still be standing when you leave?

The Self-Reinforcing Loop

Here is what makes the Moth Effect so difficult to break: it creates the conditions for its own continuation.

An organization led by urgency becomes an organization that produces urgency. Problems that could have been addressed at the systemic level: the process: that keeps failing, the communication breakdown that keeps producing the same escalation: are never resolved structurally because the leader is always occupied resolving the latest instance. The instance recurs. The leader responds again. The cycle continues.

I have worked with senior teams where the calendar was, effectively, a rotation of crises. There was always something urgent. There was always a reason why this was not the moment to do the structural work. And when I asked these teams: when, exactly, they planned to do the building, the answer was always some version of: once things calm down.

Things do not calm down in organizations run by urgency. They calm down in organizations that have done the building that urgency prevents.

The only way out of the loop is to interrupt it deliberately. To protect time for structural work even when urgency is present. To develop the people and systems that can handle the acute situations without consuming the leader's attention. To build, even when building is uncomfortable and invisible and: the flame is bright.

The Builder's Different Relationship with Urgency

The builder-leader is not indifferent to urgency. They respond to genuine crises when they arise. But they are working simultaneously to reduce the number of genuine crises by identifying and resolving the structural conditions: that produce them.

When a crisis surfaces, the builder-leader asks two questions: What needs to happen right now? And: What condition produced this, and how do we build the structural response to it? The first question resolves the crisis. The second question prevents the next one.

The builder is also working to develop the people around them to handle more of the acute situations themselves: not because the builder is abdicating responsibility, but because an organization in which senior leaders must personally engage every significant problem is an organization whose leaders have not built the people and systems required to scale.

And the builder has learned to sit with the discomfort of the slow work. To trust that the foundation being laid: the alignment being built, the authority being distributed, the adaptability being developed: will produce results that urgency never could. That trust is hard to maintain when the flame is bright and every instinct formed by years of being rewarded for crisis response is telling you to move toward it.

The builder moves away from the flame. Toward the foundation.

The Moth Effect and the Four A's

The Moth Effect is, at its core, an Attention problem. The leader's attention, the scarcest organizational resource, is being claimed by urgency rather than directed by intention. The Four A's of Organizational Readiness™ framework places Attention first for exactly this reason: an organization whose leader cannot protect and direct their own focus cannot build the other conditions the framework requires.

Alignment is built in protected time: in the patient conversations that build shared understanding of what matters and why. A Moth Effect leader has no protected time. Authority is developed by deliberately designing who decides: what and then trusting those decisions, but a Moth Effect leader reclaims authority every time a crisis arrives, teaching the organization that delegation is conditional. Adaptability requires learning from what is happening: but: the Moth Effect leader is always responding to what just happened, never studying it.

The Moth Effect does not just prevent building. It actively degrades every condition the organization needs to sustain itself.