top of page
Search

Nonprofit Leadership - Carrying the Weight of the World



Leadership can often feel like constant interruption and fires. You start the day with priorities, end the day solving problems you didn’t plan for, and somewhere in between, the actual work of leadership - vision, direction, strategy, development - gets pushed aside by urgency.


The common narrative is:

“We’re just in a busy season.” “Once things calm down, we’ll fix our systems.” “We’ll address structure when we have more capacity.”

But the truth is simpler and harder to accept: There will never be a time when the fires stop.


Not because leadership is broken, but because organizations are living systems, not stable machines. The work doesn’t pause, problems don’t queue politely, emergencies don’t schedule themselves around strategy sessions, and urgency doesn’t wait for readiness. So leadership becomes reactive.


“How do we improve our systems?” can feel overwhelming and unrealistic at times. Instead, reflect on recent "fires" you had to put out and analyze for patterns and themes.



Step 1: List the Fires (Reality Inventory)

Ask yourself or your team:

“In the last 30 days, what pulled me away from my core responsibilities?”


Example from a real organization:

  • Member code of conduct violations

  • Serious financial shortcomings (unable to pay rent, emergency loans)

  • Compliance emergency to regain good standing

  • Multiple leadership vacancies


Step 2: Map Where They Should Have Lived

Instead of thinking about who ended up handling each fire, consider where the responsibility should structurally live - even if it doesn't exist yet.


Structural Mapping

Fire

Where it should have lived

Member grievances

Operations / Member Relations

Financial collapse

Finance / Strategic Planning

Compliance failure

Governance / Compliance Systems

Leadership vacancies

Talent Systems / Succession Planning


This shifts the frame from reaction → architecture.


Step 3: Identify the Ownership Gap

This is where it becomes diagnostic instead of descriptive. Where are the potential gaps within leadership that caused the fires to burn?


Example from a real organization:

  • Board directors all doing everything

  • No clear role boundaries

  • No domain ownership

  • No system-level accountability

  • No functional separation


Step 4: Expose the Root Conditions (Not the Events)

Shifting language is the most important part of this process. Go from incidents to infrastructure.


Not: "We had a compliance issue.”

But: “We don’t have a compliance system.”


Not: “We had financial problems.”

But: “We don’t have financial governance and planning structures.”


Not: “We’re losing leaders.”

But: “We don’t have retention, onboarding, or succession systems.”


When you reframe in this way, it becomes easier to see the fires are symptoms of missing design.


Why Firefighting Feels Necessary

There’s another layer that that is important to acknowledge: Many leaders are here because they’re good in a crisis. They’re responsive. They’re reliable. They step in when things fall apart.


And when systems work too well, leadership can feel… invisible. Most organizations operate in a constant state of urgency bias - where immediate problems crowd out important but non-urgent work. Researcher and systems thinker Donella Meadows explains that systems tend to trap people into reacting to symptoms rather than addressing root causes, because the system rewards short-term fixes over long-term leverage points


Fires can feel random, but they’re usually predictable when you look at structure instead of events. Leadership burnout doesn’t come from workload alone, it also comes from structural absorption: where leadership becomes the system for everything that lacks one.


Because fires are not repetitive in clean patterns, it may seem like the events are bad luck or a one-time thing. You may even say, “We can’t build systems for everything.”

But it's important to remember systems aren’t about preventing every problem.


They’re about:

  • Containment

  • Ownership

  • Boundaries

  • Role clarity

  • Domain responsibility

  • Predictable response paths


Without that, everything defaults upward.


Final thoughts to leaders - especially those in nonprofits:


You don't have to carry the weight of the world. You will be better, your team will be better, your organization will be better when you take a step back to take a look at the fires - and grab your hose.

 
 
 

Comments


bottom of page