When a board keeps getting pulled into operations, it's almost never because board members are poorly intentioned. It's because the governing work isn't defined clearly enough to hold the board's attention, the CEO hasn't established sufficient confidence in their own judgment, or both. Operational discussions fill space that governance hasn't claimed. The fix isn't to tell board members to back off — it's to give the board substantive governance work that is more compelling than the operational details that keep creeping in.

Start by diagnosing which direction the pull is coming from. Sometimes the board initiates: members with deep subject-matter expertise can't resist weighing in on decisions they know how to make. A board member who spent 20 years in healthcare operations will have opinions about how the clinic is staffed. A former CFO will want to renegotiate the audit contract. These are natural instincts, and redirecting them requires both a clear role definition and a board chair who is willing to enforce it consistently in meetings.

Other times the CEO is the source of the pull — either intentionally (seeking political cover by looping the board into decisions they should own) or unintentionally (bringing operational questions to the board out of insecurity or habit). A new CEO in particular may seek board validation on decisions that fall well within their authority. The board's job in these situations is not to take the bait, but to say clearly: "That's your call — what we care about is whether it produces the result we've agreed on."

The structural fix: a clear delegation framework

The most durable solution is a written delegation framework — sometimes called an executive limitations policy — that explicitly names what the CEO has authority to decide without board approval, and what requires board involvement. This document removes ambiguity in both directions. The CEO stops seeking permission for things that are clearly theirs. The board stops wandering into territory that clearly belongs to the CEO. When a gray-area item comes up, the board can refer to the framework rather than debating it case by case.

Example: Delegation Framework Language

CEO authority (no board approval needed): Any single operational expenditure within the approved budget, staff hiring and compensation within approved salary bands, program design decisions consistent with adopted outcomes targets.

Requires board approval: Unbudgeted expenditures exceeding $50,000, executive compensation changes, acquisition or disposal of real property, entering multi-year contracts above $200,000.

Holding the line in real time

Even with a strong framework, boards need a chair who redirects operational conversations without embarrassing the person who raised them. A useful phrase: "That's exactly the kind of decision we want the CEO to own — let's note it as a question for the CEO to address in their next report rather than making it a board discussion." This validates the concern while keeping the boundary intact.

Over time, a board that consistently stays in its governance lane develops something valuable: a CEO who brings monitoring reports that actually answer whether beneficiaries are better off, rather than operational updates that invite board second-guessing. That relationship — where the board defines required outcomes and holds the CEO accountable for producing them, while the CEO determines how — is what governing looks like. It doesn't happen by accident. It happens because someone named the problem, built the structure, and held the line.

Practical steps

  1. Diagnose which direction the pull is coming from before designing a fix. Review your last three meeting agendas: were operational items brought by board members, or by the CEO seeking approval? The intervention is different in each case.
  2. If board members are initiating operational discussions, adopt a written Executive Limitations policy that explicitly names what falls within the CEO's authority. Once adopted, the chair can redirect using the policy rather than personal judgment.
  3. If the CEO is the source — bringing items for board input that fall within their own authority — have a direct conversation: clarify that the board's role is to monitor results, not to pre-approve decisions. Ask the CEO what would help them feel confident making those calls independently.
  4. Build a monitoring calendar with scheduled outcome reviews at least four times per year. Filling meeting time with substantive governance work is the most effective way to crowd out operational drift — an agenda with no governance gaps leaves less room for operations to creep in.
  5. After each meeting for the next three cycles, ask the board chair to spend five minutes reviewing the agenda: what percentage of time was spent on governance versus operations? Track it. Naming the metric publicly tends to move it.
← Back to all Q&As