When Everyone Learns to Bring the Problem Upstairs

Every executive rescue solves a problem. Repeated rescue can also teach an organization where responsibility really lives.

Organizations learn leadership through repetition.

They notice which decisions managers are permitted to make, which mistakes executives tolerate, which problems receive immediate intervention, and what happens when uncertainty reaches the top.

Over time, these experiences create an operating logic more powerful than an organizational chart.

If difficult problems repeatedly travel upward and senior leadership repeatedly resolves them, the institution learns something consequential:

Complexity belongs upstairs.

The lesson is rarely intentional.

A capable executive sees a problem moving slowly and accelerates it. A founder notices a customer relationship deteriorating and intervenes. A CEO sees two departments struggling to reach agreement and makes the decision herself.

The immediate result may be excellent.

The problem is what happens next.

People remember where resolution occurred.

Rescue Creates Precedent

Every executive intervention has two outcomes.

There is the visible outcome: the immediate problem is resolved.

Then there is the institutional outcome: the organization receives information about how it should behave when a similar problem appears again.

That second outcome deserves more executive attention.

If managers discover that unresolved complexity eventually attracts senior intervention, waiting becomes rational.

If bringing a problem upward produces a better answer with less personal exposure, escalation becomes rational.

If the executive routinely reconstructs incomplete analysis, developing complete analysis becomes less necessary.

Eventually, an organization can become highly efficient at transferring uncertainty upward.

This can happen while everyone remains busy, competent, and well intentioned.

The executive experiences an increasing volume of decisions.

Managers experience an increasing need for executive confirmation.

The organization interprets this as collaboration.

It may actually be dependency becoming procedural.

The Escalation Test

Healthy escalation is essential.

Certain decisions belong at higher levels because they carry greater financial, legal, reputational, strategic, or institutional consequence.

The problem begins when difficulty becomes confused with consequence.

A difficult decision does not automatically belong to the CEO.

An uncomfortable conversation does not automatically belong to the senior executive.

An ambiguous situation does not automatically require another level of authority.

Executives should therefore examine not simply how many matters are escalated, but why the organization believes escalation is necessary.

Is additional authority required?

Is additional information required?

Does the decision exceed an established threshold?

Or has the organization simply learned that someone upstairs will make the uncertainty disappear?

Those are very different conditions.

Problems Should Arrive Differently

One of the simplest ways to interrupt unnecessary escalation is to change what qualifies as an executive problem.

A problem arriving upstairs should rarely arrive alone.

It should arrive with context.

It should identify what has already been attempted.

It should explain the material risk.

It should present viable options.

It should identify the decision owner.

And whenever appropriate, it should include a recommendation.

This changes the developmental value of escalation.

The executive is no longer functioning as the organization’s answer machine. Senior leadership becomes a place where judgment is refined, authority is exercised at the appropriate level, and consequential exceptions receive proper attention.

There is another benefit.

Requiring thought before escalation reveals where the real capability gaps exist.

Some managers need more authority.

Some need better information.

Some need clearer thresholds.

Some need experience.

And occasionally, someone occupying a decision-making role does not yet possess the judgment the role requires.

Constant executive rescue can conceal all five.

Allow Responsibility to Remain Where It Belongs

There is a particular discomfort experienced by highly capable leaders when they can see the answer before everyone else.

Waiting can feel inefficient.

Watching someone work through a problem you could resolve in minutes can feel unnecessary.

Allowing a competent subordinate to make a different but acceptable decision can feel like accepting a lower standard.

Yet leadership development requires space in which judgment can actually be exercised.

People cannot develop decision capacity while someone else continually absorbs the consequential decisions.

There will be moments when intervention is necessary.

But intervention should be deliberate enough that the organization does not mistake an exception for its operating model.

Because organizations eventually become proficient at whatever leadership repeatedly permits.

If leaders repeatedly rescue, people learn escalation.

If leaders repeatedly return appropriate decisions to their owners, people learn responsibility.

If leaders require recommendations rather than problems, people learn judgment.

If leaders establish clear decision rights, people learn authority.

And if leaders allow capable people to carry meaningful consequences, the institution begins accumulating something far more valuable than obedience:

decision capacity.

Every rescue teaches the organization something. Be certain you are teaching the lesson you intend.

Solve the problem when necessary. Preserve the ownership of the problem whenever possible.

— Dionne Marie