The Five Questions Every Nonprofit Leader Should Ask Before Trying to Fix Everything at Once

(And How They Help You Build Systems That Keep Your Organization From Accidentally Setting Itself on Fire)

Nonprofit leaders are known for doing heroic things with limited time, limited resources, and enough email threads to power a small city. But when it comes to building organizational systems that help their teams thrive… well, that usually gets pushed to the "when we have time” pile.

Spoiler: You will never magically have time. (If you ever do, please alert the sector. You may have discovered time travel.)

The Stanford Social Innovation Review offers a helpful framework called the five questions for scaling social innovation, and while it’s usually discussed in the context of big-picture impact, these questions are also incredibly useful for leaders trying to create systems that reduce burnout, clarify roles, and make the organization function like a coordinated unit.

Below is a nonprofit-friendly, systems-oriented spin on those five questions - with practical suggestions, real-world applicability, and just enough humor to keep you awake.

1. Where Are We Actually Right Now?

(AKA: Before you can do anything, you must locate yourself on the map.)

Think of this like a systems MRI. You cannot fix what you have not diagnosed.

Ask yourself:

• Where are goals clear?

• Where are they… interpretive? (Like abstract art?)

• Where are our biggest bottlenecks?

• What is falling through cracks?

  
  

System-Building Takeaway: Before improving anything, you need to understand what is actually happening and not what you think is happening.

Tools leaders can use:

• A simple systems audit

• Staff listening sessions

• Mapping a process from start to finish 

• A decision-making matrix (no more mystery approvals!)

  
  

This gives you the raw material to build systems that reflect reality, not systems for a fantasy version of your organization that only exists in grant proposals.

2. Where Do We Want to Go, and Why There?

(AKA: Your vision is the GPS; your systems are the roads.)

You cannot build systems until you’re clear on your North Star. Otherwise, you end up with:

• Processes that don’t match goals

• Workflows that contradict values

• Staff who spend hours on tasks that do not move the mission forward

  
  

System-Building Takeaway: Every system should be tied to a specific strategic priority. If it doesn’t move the vision forward, it’s not a system - it’s busywork wearing a blazer.

Try this: List your top 3 goals for the next 12 - 18 months, and next to each one answer:

• “What systems do we need to hit this?”

• “Who will own those systems?”

• “How will we measure whether they’re actually working?”

  
  

This step stops leaders from creating systems that look impressive but accomplish nothing (the nonprofit version of buying gym equipment and never taking the tags off).

3. What Needs to Change Internally to Support That Vision?

(AKA: Your structure, roles, and talent must match the dream - not compete with it.)

This stage is where most nonprofits struggle, because it requires hard choices:

• Who makes which decisions?

• Who owns which responsibilities?

• Do people understand the expectations of their role?

• Does the structure support the strategy, or is it held together by goodwill and caffeine?

  
  

System-Building Takeaway: Systems fail when roles are unclear. Systems thrive when people know:

• Their lane

• Their authority

• Their boundaries

• And when they should actually ask for input

  
  

Many nonprofits think they have a “capacity problem,” when they actually have a clarity problem.

4. How Will We Roll This Out Without Chaos or Mutiny?

(AKA: System change requires real change management, not one enthusiastic all-staff meeting.)

Rolling out new systems with no plan is the organizational equivalent of announcing,

“We’re switching to a new database!” and then immediately unplugging the old one.

You need:

• A phased implementation plan

• Training for staff

• Feedback loops

• A clear place to report problems

• Celebrations for small wins (pizza counts - don't listen to the internet!)

  
  

System-Building Takeaway: Change sticks when people understand why it’s happening, how it will help them, and what they need to do differently.

This is also where you fight the nonprofit curse of “We’ve always done it this way,” which is usually code for, “We’re scared to fix it because it’s held together with duct tape and vibes.”

5. How Will Leadership Communicate, Reinforce, and Model the Change?

(AKA: If leaders don’t use the systems, no one else will.)

This final question pulls everything together.

Systems don’t endure because they’re well-designed - they endure because leaders:

• Use them

• Protect them

• Reinforce them

• Communicate consistently

• Do not make exceptions every time something feels urgent

  
  

If leaders say, “We now have a project management system,” but continue sending midnight emails with vague requests… the system is already dead.

System-Building Takeaway: Culture is a system. And leaders shape it hourly.

If leaders align their behavior with the new systems, change becomes normal. If they don’t, change becomes optional - and optional systems never survive.

Bringing It All Together

Using the five questions gives nonprofit leaders a built-in roadmap to design systems that:

• Reduce burnout

• Improve retention

• Clarify roles

• Strengthen communication

• Support long-term scaling

• And eliminate inefficiencies that waste time, energy, and staff morale

  
  

Most importantly, it keeps you from doing what many nonprofits accidentally do: solve surface-level issues while the root causes quietly grow stronger.

A Realistic Place to Start (Because Yes, That Was A LOT)

If you’re still reading, congratulations you’ve just taken in enough organizational insight to qualify for an honorary degree in “Systems We Probably Should Have Fixed Three Years Ago.”

And yes, it is a lot, because leading a nonprofit is a lot. And knowing where to start can feel like staring at a messy storage closet thinking, “If I open this door, something will fall on me.”

So here’s the simplest, most doable first step:

Pick ONE process your team touches every week… and map it.

That’s it. Not five. Not everything. Not the whole organization. One.

Try:

• How a new client is onboarded

• How decisions get made

• How communication flows between programs and leadership

• How tasks get assigned and completed

  
  

Grab a whiteboard, a Google Doc, or a stack of sticky notes. Write down what actually happens, again - not what you wish happened. Then ask your team two questions:

1. What part of this process is confusing or inconsistent?

2. What (even tiny) change would make this easier?

   
   

That one mapped process will show you exactly where your first system should go. Once you fix one, you’ll build the confidence and clarity to fix the next. That’s how systems are built: one intentional improvement at a time, not one massive overhaul.