A governance board and an operational board are not two versions of the same thing. One builds organizations. The other buries them in fence repairs.
I once sat through a board meeting where we spent fifteen to twenty minutes discussing a broken fence. Not the budget. Not the mission. Not whether the organization was actually serving the people it existed to serve. A fence. Which section needed replacing. Who we might know that could fix it. And then — because this particular organization ran a ranch — a detailed conversation about horse feed prices and where to source them.
I'm a city boy. I didn't understand a word of it. I sat there for fifteen minutes completely zoned out, waiting for someone to remember we were supposed to be governing a nonprofit.
Nobody did.
That is an operational board in action.
An operational board is hands-on in all the wrong ways. Board members are directly involved in managing facilities, fundraising, communications — things that should belong to staff and the executive. Decisions that should be made by the people running the organization day-to-day get pulled up to the board table instead.
The meetings reflect this. Agenda items are operational. Conversations go deep into execution details. Board members are effectively functioning as a second layer of management over an executive director who is already supposed to be doing that job.
It feels productive. It isn't. What's actually happening is that the most important governance work — ensuring the organization is on mission, financially sound, and legally protected — is getting no airtime because the board is too busy talking about fences.
A governance board operates at 30,000 feet.
Its job is to ensure the mission, vision, and values of the organization are aligned with everything the organization is actually doing. It sets the direction. It defines the outcomes the organization exists to achieve for its beneficiaries. And then it gets out of the way and lets the executive do their job.
The board has one employee: the executive director. That is the only person they manage.
They set empowered boundaries — clear expectations, financial authorities, defined limits — and then they trust the executive to operate within them. They don't second-guess every expense. They don't sit in on staff interviews. They don't contact volunteers directly with instructions or pressure.
If a board member is also a volunteer in the organization, they take their board hat off completely when they step into that role. No authority. No pressure. No board member energy in an operational space. Those are two entirely separate hats and they cannot be worn at the same time.
Here is the cycle that operational boards get stuck in. They spend their meeting time on operational details. That means the real governance work doesn't get done. Because the real governance work doesn't get done, the organization drifts — unclear on its mission, unclear on its boundaries, unclear on who is actually responsible for what.
That drift creates more problems that pull the board back into operational firefighting. And the cycle continues.
Good board members won't join this kind of board. And if they do join, they won't stay. Their time is not being respected. They came to govern, not to debate horse feed prices.
Almost every young nonprofit starts as an operational board — and that's not always wrong. In the early years, the board may genuinely need to roll up its sleeves. But governance must never get permanently bypassed just because the organization is too busy to stop and build it. Busy is how operational boards justify staying operational. And busy is exactly how organizations stay stuck.
Moving from an operational board to a governance board is real work. It starts with the documents — constitution, bylaws, existing policies — going through all of it to make sure everything is aligned with the mission, vision, and values.
Often that process reveals something important: the original vision was never clearly defined to begin with. So before anything else can be fixed, you have to do that foundational work. Define the language. Define the mission. Define the values. Identify who the organization actually belongs to and who it exists to serve. Then make sure the bylaws support that — and rewrite them where they don't.
That work is significant. But it's not the hard part.
The hard part is the culture.
You have to give up control. You have to hand operational authority to your executive and actually mean it. At Shiloh we stopped going through expenses line by line every month. We gave the executive full authority over staffing decisions. The board no longer automatically had a seat at the interview table.
That was uncomfortable. It felt like losing something. But what we were actually losing was the habit of not trusting the person we hired to lead.
You have to let them run. You give the empowered boundaries, you extend the trust, and you stay true to the framework — even when it's uncomfortable. Especially when it's uncomfortable.
The transition feels like strain. That's because it is strain — the same kind you feel lifting weights, where the muscle tears a little before it rebuilds stronger.
You won't feel it working right away. But one day you'll show up to a board meeting that runs ninety minutes, covers what matters, and ends with everyone feeling like their time was well spent. You'll realize the executive has grown into the role in ways they couldn't when the board was hovering.
That's not an accident. That's what governance does when you give it the chance to work.
Without it, you're still driving with a windshield so dirty you can only see a few feet ahead — making decisions without the clarity to see where you're actually going. The transition is hard. The alternative is harder.
If you're ready to make the shift from operational to governance — or you're not sure where your board actually sits on this spectrum — reach out to book a discovery call. We'll figure out where you are and what the path forward looks like.
Book a Discovery Call