Governance vs. Management: Where Should the Board Stop and Staff Begin?

One of the most frustrating dynamics in a nonprofit can sound something like this:

Or maybe:

Sometimes, oddly enough, both can be true. A board can be deeply involved in the wrong things while remaining disengaged from the things that actually require governance. This is where the distinction between governance and management becomes incredibly important.

At DVLP, we believe the goal isn't to create a board that does less. It's to create a board that does the right work.

Governance Is Not Management

At its simplest:

Governance is about direction, oversight, accountability, and stewardship.

Management is about execution, operations, and day-to-day leadership.

The board should help answer:

Staff leadership generally answers:

The lines aren't always perfectly clean.

But when those lines become consistently blurred, problems usually follow.

What Belongs on the Governance Side?

Board-level work generally includes things such as:

Mission

Is the organization still fulfilling its purpose?

Strategy

What are the organization's priorities and long-term direction?

Financial Oversight

Are finances being managed responsibly?

Legal & Ethical Accountability

Are we meeting our obligations and protecting the organization?

Executive Leadership

Is the executive director supported, evaluated, and held accountable?

Risk

What could threaten the organization's mission, reputation, finances, or sustainability?

Resource Development

How can board members help strengthen the organization's resources and relationships?

Organizational Health

Do the people, systems, programs, and structure support the mission?

This is governance.

It requires thoughtful questions, healthy debate, oversight, and strategic decision-making.

What Belongs on the Management Side?

Staff generally handles the day-to-day execution of the organization's work.

That can include:

• Managing staff

• Running programs

• Creating social media posts

• Coordinating volunteers

• Planning routine events

• Managing vendors

• Responding to everyday operational issues

• Implementing strategic priorities

• Handling internal workflows

• Managing communications

• Carrying out fundraising activities

• Maintaining systems

• Solving routine operational problems

That doesn't mean the board can never discuss these things. It means the board shouldn't become the management team.

The Gray Area Is Where Things Get Interesting

Here's the reality:

Nonprofit governance is rarely black and white.

Consider fundraising. A board should absolutely support resource development. But should a board member approve every fundraising email? Probably not. Should a board member help introduce the organization to potential supporters? Absolutely!

Consider programs. A board should understand program performance and impact. But should board members tell program staff how to run every program? That's management.

Consider employees. The board should generally oversee the executive director. But should individual board members directly supervise staff? That can quickly create confusion.

The question isn't:

The better question is:

A Simple DVLP Test: Direction, Oversight, or Execution?

When you're unsure whether something belongs with the board or staff, ask three questions.

1. Is this about direction?

If you're deciding where the organization is going, that's generally governance.

2. Is this about oversight?

If you're determining whether the organization is operating responsibly and effectively, that's generally governance.

3. Is this about execution?

If you're deciding how the work gets done, that's generally management.

This isn't a rigid legal test. It's a practical conversation starter. And it can prevent a lot of unnecessary board/staff friction.

What Micromanagement Actually Looks Like

Micromanagement isn't simply a board asking questions. Healthy boards should ask questions.

Micromanagement happens when board members move from oversight into control of routine execution.

Examples might include:

• Requiring approval of routine communications

• Directing individual staff members

• Rewriting staff work

• Making operational decisions outside board authority

• Assigning tasks directly to employees

• Second-guessing routine management decisions

• Attempting to manage volunteers individually

• Creating unofficial reporting relationships

The problem isn't just annoyance. It can create conflicting instructions, undermine staff leadership, slow decisions, and make accountability unclear.

But “That's Staff's Job” Isn't a Get-Out-of-Governance Card

There is an equal and opposite problem. Staff should not be able to shut down legitimate board oversight by saying:

If the board is responsible for governance, it needs enough information to govern.

A board should understand:

• Financial condition

• Program performance

• Strategic progress

• Fundraising health

• Organizational risks

• Major operational concerns

• Leadership capacity

• Compliance issues

• Major changes affecting the organization

The board doesn't need to run the work. It does need to understand the organization well enough to oversee it.

Committees Can Make This Even Trickier

Committees can be incredibly useful but they can also become miniature management teams. A finance committee, for example, should help the board understand financial performance and oversight. It shouldn't necessarily become the organization's unofficial accounting department.

A development committee can help open doors, support fundraising strategy, and engage donors. It shouldn't become a team that dictates every fundraising task.

A program committee can help monitor impact and provide strategic insight but it shouldn't run the program.

Every committee should have a clear purpose, authority, and relationship to the full board and staff.

Create a Board/Staff Responsibility Map

If your organization struggles with this distinction, don't just tell everyone to “communicate better.” Create something concrete.

Build a simple table with four columns:

Your exact structure will depend on your organization. The important thing is that people aren't guessing.

What a Healthy Relationship Looks Like

A strong board/staff relationship usually has three things:

Clear authority

People know who makes which decisions.

Healthy challenge

Board members can ask hard questions without becoming operational managers.

Mutual trust

Staff trusts the board to govern.

The board trusts staff to lead.

Neither assumes the other should disappear.

That's the sweet spot.

Your DVLP Quick Win

Take your next board meeting agenda and look at every item.

For each one, label it:

G = Governance | M = Management | B = Both

Then ask:

If the agenda is 80% staff reports and operational updates, that's a clue. If the board is making routine staff decisions, that's a clue too. Your board meeting should be a place where the organization thinks, not simply where staff reports.

The DVLP Takeaway

A healthy board isn't one that stays out of everything and it isn't one that gets involved in everything. It's one that understands its role well enough to know when to lean in and when to step back.

Good governance creates the conditions for good management. Good management gives the board the information it needs to govern. The goal isn't separation - it's clarity, trust, accountability, and partnership.