It is one of the most common dilemmas in nonprofit organizational life, and it surfaces with remarkable regularity: a staff member, deeply concerned about the behavior or performance of an executive director, wonders whether to bring those concerns to the board of directors.
The conventional wisdom, shared freely among nonprofit professionals who have been around long enough to have opinions about it, tends toward caution: "Don't do it. Boards protect their EDs. You'll be dismissed as a disgruntled employee. Your reputation will suffer. Get out and move on." That advice is not wrong, exactly. But it is incomplete. And the decision deserves more careful examination than a blanket "no" provides because the circumstances that produce the question vary enormously, and so do the stakes.
Why the Conventional Wisdom Exists
The caution embedded in that advice is grounded in real experience, and it would be dishonest to dismiss it.
Boards have a complicated relationship with their executive directors. They hired the person. They negotiated the contract. In many cases, they have publicly championed the hire and staked some portion of their own credibility on it. Admitting that the hire was a mistake, or that the person they selected and continue to oversee is falling short, requires a level of institutional self-examination that governance bodies do not always manage gracefully.
There is also a structural reality worth acknowledging: boards and executive directors are often more aligned with each other than boards and staff are. They occupy a similar stratum of organizational authority. They interact in formal settings where the ED has significant control over what information reaches the board and how it is framed. A staff member who goes to the board with concerns about an ED is, in effect, going around the person who controls their day-to-day work environment, their performance review, and in some cases their continued employment, to an oversight body that may be receiving a very different picture of organizational reality.
The risk of being perceived as a disgruntled employee is real. So is the risk of retaliation, however carefully worded the organizational policies against it may be. And in a sector where professional networks are tight and word travels, the reputational dimensions of the decision extend beyond the immediate organization.
For a staff member in this situation, particularly one without significant institutional standing or documentation of their concerns, the calculus is genuinely unfavorable. The conventional wisdom did not emerge from nowhere.
Where the Conventional Wisdom Falls Short
And yet. There are circumstances in which the answer to this question is not "no," and in which the advice to simply leave and move on carries its own significant costs.
The most obvious is illegality. Financial fraud, discrimination, harassment, misuse of grant funds, falsification of reporting; these are not situations where the appropriate response is quiet departure. They are situations where the board has both a legal obligation and a fiduciary responsibility to act, and where staff members who have direct knowledge of wrongdoing may have legal protections, and in some cases obligations, that the "just leave" advice entirely ignores.
But the threshold for going to the board does not have to be criminal. There is a meaningful category of organizational harm (serious enough to damage the mission, the staff, or the communities being served) that falls short of illegality but still warrants escalation. Systematic mismanagement that is destroying program quality. Behavior that is driving out the organization's most effective staff. A pattern of decisions that is jeopardizing the organization's financial sustainability or donor relationships. These are things boards are supposed to know about. The fact that they often do not is partly a failure of governance structure, and partly a consequence of staff who have concluded that raising concerns is too risky to attempt.
There is also a question of who pays the price for the advice to stay quiet and leave. The staff member who exits cleanly may well be the right outcome for that individual. But the colleagues left behind, the clients still being served, and the mission still at stake do not exit with them. The "move on" framing treats organizational dysfunction as primarily a personal problem to be escaped rather than an institutional problem to be addressed. Which is understandable from a self-protective standpoint and genuinely insufficient from a sector-health standpoint.
What Boards Need to Understand About How They Are Perceived
This conversation has a dimension that boards themselves rarely hear, and it is worth stating plainly.
The conventional wisdom that staff should not go to the board reflects, among other things, a widespread belief that boards will not respond well. That they will circle the wagons. That they will prioritize the comfort of their relationship with the ED over the substance of the concern being raised. That the staff member will be dismissed, managed out, or quietly made to regret the attempt.
The fact that this belief is so widespread, and so often confirmed by experience, is an indictment of board culture in significant portions of the sector.
A board that has created conditions, intentionally or not, where staff believe it is career-damaging to raise legitimate organizational concerns is not functioning as an oversight body. It is functioning as a shield. And the organizations most likely to experience serious governance failures are precisely those where the gap between what leadership knows and what the board knows has been allowed to grow unchecked.
Boards that want to be the kind of oversight body that staff can actually approach, that want early warning of organizational problems rather than late-stage crises, have to actively create those conditions. That means clear, confidential reporting channels. It means board members who make themselves genuinely accessible, not just nominally available. It means taking concerns seriously enough to investigate rather than reflexively defending the status quo. And it means understanding that the staff member willing to raise a difficult concern is often doing the organization a service, not causing it a problem.
A Framework for the Decision
For staff members navigating this question, a few considerations are worth working through deliberately before acting, or deciding not to.
What is the nature of the concern? Illegality, financial impropriety, or serious ethical violations are categorically different from management style, strategic disagreement, or interpersonal conflict. The former category warrants escalation almost regardless of the risks. The latter category probably does not, and is better addressed through direct conversation, HR processes, or ultimately departure.
What is the evidence? A board that takes a concern seriously will want specifics: documented incidents, patterns over time, concrete impact on programs or staff. A concern that can be clearly articulated and supported by evidence is more likely to be heard than one that is primarily impressionistic. Building that documentation before escalating is not about building a legal case, it is about being taken seriously.
What are the realistic outcomes? This requires honest assessment of the board's likely response, the organization's culture, and the staff member's own position and risk tolerance. The optimistic scenario, board engages seriously, investigates thoroughly, takes appropriate action, is possible. It happens. But so does the pessimistic scenario. Knowing which is more likely in a specific organizational context is important information.
Are there other avenues? In some cases, a trusted board member, someone with genuine independence from the ED and a reputation for taking governance seriously, may be a more viable first contact than the board as a whole. A conversation with an employment attorney, or with the organization's HR function if one exists, may clarify options and protections before any escalation occurs.
What is the cost of not acting? This question tends to get less attention than the risks of acting, and it should get more. If the concern is serious enough to be worth asking about, it is serious enough to consider what happens if nothing is said and nothing changes.
No Clean Answer
The question of whether to go to the board does not have a clean universal answer, and anyone who offers one (in either direction) is oversimplifying a decision that depends heavily on context, evidence, organizational culture, and individual circumstance.
What can be said with confidence is this: the reflexive "almost always no" deserves to be examined rather than accepted. It protects individuals in ways that are often appropriate and sometimes essential. It also, in aggregate, protects organizational dysfunction in ways that cost the sector more than most people acknowledge.
The staff member weighing this decision deserves a fuller picture than conventional wisdom typically provides. And the boards whose cultures have made "don't go to the board" the obvious advice deserve to know what that says about them.
Nonprofit Snapshot publishes perspectives from across the nonprofit sector. Views expressed are illustrative of common organizational dynamics and do not represent any single organization or individual.