Board or Staff? Clarifying Who Owns What

When a board and an executive director are in conflict, the diagnosis offered is usually about people. The board is too involved, or not involved enough. The director is defensive, or not transparent. Occasionally that is true. Far more often, two reasonable groups are operating from different unstated assumptions about who decides what.

The remedy is not a better relationship. It is a written agreement about roles, which a board and a director can usually produce in a single working session.

The boundary, stated simply

The board owns what and whether. Staff own how.

The board is responsible for the organization's purpose, its direction, its financial health, its legal and ethical compliance, and its chief executive. Staff are responsible for designing and delivering the work that pursues that direction, and for managing the people who do it.

The board hires, supports, evaluates, and if necessary replaces one employee: the executive director. Everything below that line is the director's to manage. A board member who directs a program manager has stepped outside the governance role, however helpful the intention.

Who owns what, specifically

The following split works for most organizations and is worth adopting explicitly rather than assuming.

• Mission and strategic direction. Board approves. Staff propose, inform with evidence, and implement. The board should not be drafting the plan; it should be interrogating and approving it.
• Annual budget. Board approves and monitors. Staff build it and manage within it. The board's job is whether the budget reflects the strategy and whether the organization can sustain it, not the line-item detail.
• Program design and delivery. Staff own it. The board's legitimate question is whether programs advance the mission and produce results, not how intake is sequenced.
• Hiring and personnel below the executive. Staff own it entirely. The board sets personnel policy; it does not participate in staff hiring decisions.
• Executive director hiring, evaluation, and compensation. Board owns it, without exception.
• Fundraising. Shared, and worth being explicit. Staff run the strategy and the operation. Individual board members have personal responsibilities: giving, opening doors, and thanking donors.
• Financial oversight and audit. Board owns oversight. Staff produce the statements and manage the controls. The board reviews, questions, and engages the auditor.
• Legal and regulatory compliance. Board holds ultimate responsibility. Staff maintain the filings and the calendar.
• Policy. Board approves policy. Staff write the procedures that implement it. The distinction matters: policy is what we will and will not do; procedure is how.
• Vendor selection and contracts. Staff own it, within an approval threshold the board sets.

Where it usually goes wrong

Three patterns account for most of the trouble.

The board that manages. Common in organizations that recently had no staff, or where a founder still sits on the board. Board members give direction to staff, weigh in on operational decisions, and treat committee meetings as management meetings. The director cannot manage against multiple competing directives, and good staff leave.

The board that rubber-stamps. Materials arrive the night before. Votes are unanimous and unexamined. The director effectively sets direction and the board ratifies. This feels comfortable and leaves the organization without genuine oversight, which is a real fiduciary problem and often surfaces only when something has already gone wrong.

The board that oscillates. Disengaged until a crisis, then intensely operational, then disengaged again. Whiplash for staff, and it generally means the board's standing role was never defined, so it defaults to either absence or emergency.

Committees: fewer, with charters

Committees that exist without a written charge tend to drift into operations, because operational questions are concrete and governance questions are abstract.

Give each standing committee a one-page charter: its purpose, what it decides versus what it recommends to the full board, who sits on it, how often it meets, and what it reports. Most organizations need finance and audit, governance and nominating, and an executive committee with tightly limited authority. Beyond that, use time-limited task forces with a defined end date rather than permanent committees looking for a purpose.

The questions a board should be asking

Role clarity does not mean a passive board. It means a board asking the right questions rather than the operational ones. A strong board asks: Are we achieving the outcomes we committed to? Is the organization financially sustainable over the next three years, not just this year? What are the three risks most likely to damage us, and what are we doing about them? Is the executive director supported and performing? Are we compliant? And does our strategy still fit the environment we are operating in?

Those questions are harder than asking why the newsletter went out late. They are also the ones only the board can ask.

Make it routine

Review the role agreement annually, and cover it in every board member's onboarding. New members arrive with expectations from other boards they have served on, and those expectations vary enormously. An hour of orientation prevents a year of friction.

When roles are written down and agreed, disagreements become easier rather than harder, because the conversation shifts from who has the right to decide this to what is the right decision. That is the conversation worth having.