When Systems Exhaust the People Who Serve Them

Before the data, a moment for the people inside it.

Forty-six percent of nonprofit CEOs now cite burnout as “very much” a concern, up from 29% just a year ago, according to the Center for Effective Philanthropy’s State of Nonprofits 2026. Fifty-six percent are leading inside atmospheres of fear and stress. These are not soft numbers. They are the daily texture of work for the people holding mission-driven organizations together.

It is tempting to read that as a story about individual resilience. A 17-point single-year jump tells us otherwise. Something has shifted in the structures holding the sector up, and structural shifts are not solved by longer weekends.

What the burden actually looks like
At the scale most of us serve (organizations with 5 to 25 staff and budgets between $500K and $2M), the executive director is often the operations leader, the finance leader, the HR leader, and the public face. The architecture concentrates risk in one seat.

Add a federal funding environment built on reimbursement (spend, wait, reconcile), grant cycles that don’t sync with payroll, board members who care deeply but oversee from a distance, and rising community need pressing against a flat resource base — and the architecture itself becomes the source of the strain.

The leader absorbing that design is not weak. She is doing exactly what the design asks of her. The design is the issue.

The cascade
What happens in the CEO seat does not stay in the CEO seat. A leader carrying too much has less to give a struggling program manager. The program manager has less to give the team. The team has less to give the clients. Boards, sensing tension without diagnosing it, sometimes add scrutiny when ballast was needed. Funders, watching from another remove, read staff turnover as instability rather than as a downstream effect of structural overload.

Burnout is not always a leadership problem. It is also a system signal traveling through people.

The hopeful part
Systems can be redesigned. Quietly, intentionally, and without a strategic plan retreat.

Three questions that open the door: Which approvals exist because we decided they were necessary, and which exist because no one has revisited them since 2019? Where is decision-making concentrated in one person when it could be held by two or three? What does the calendar say about reflection time — and does the actual week match?

These are organizational design questions, not personal-growth questions. The answers come from honest conversations with the team, the board, peer EDs at similar scale, and sometimes a trusted outside eye who can name what familiarity has rendered invisible.

A small move
This week, name one constraint you have been treating as fixed. Maybe it is the monthly board report format. Maybe it is the approval threshold for vendor payments. Maybe it is a meeting cadence that made sense two staffing structures ago. Bring it to one colleague, not to vent, but to ask together: Is this still doing the job we built it for?

One constraint, one conversation. That is the shape of structural change inside organizations that do not have the bandwidth for a full redesign.