Redirect with a question, not a correction. When your board is about to make a management decision, the least confrontational move is to ask whether it's a governance question at all — "Is this within the superintendent's authority under our current policies?" or "What board policy requires us to approve this?" Those questions redirect attention to the governance-management boundary without accusation, and they give everyone a principled basis for stepping back rather than making it personal.
The pattern rarely improves on its own. Without intentional intervention, boards that drift into management tend to drift further. The issue isn't that your colleagues are acting in bad faith — it's usually that the boundary hasn't been clearly defined, your superintendent hasn't fully claimed the management domain, or some board members find operational decisions more comfortable than governance ones. Voting on a vendor contract feels like doing something concrete. Monitoring student outcome data requires tolerating ambiguity and holding your superintendent accountable in ways that can feel unkind.
What the boundary actually is
Your board's work is three things: student outcome goals, guardrails that define what your superintendent will not do, and legally required approvals. Everything else is superintendent work — which programs to run, which staff to assign where, which budget allocations to make, which partnerships to pursue.
When your board votes on operational decisions, it's making your superintendent's job for them. And then it can't hold your superintendent accountable for results. You co-made the decision. That accountability problem is real and it compounds over time — the more your board is in the operational mix, the harder it becomes to evaluate whether your superintendent is doing their job well.
When a community concern arrives at the board table
Many management detours start with a community concern brought to the board. The test is: is this a values issue or an operational one? If it's a values issue — something the community believes the district should always or never do — that's a signal to consider a new guardrail. Guardrails use negation language: "The superintendent will not…" They keep the concern at the governance level without your board directing operational action. If the concern is operational — how something is being run — refer it to your superintendent without prescribing the outcome.
If the pattern is persistent
A single conversation rarely changes a pattern. What changes it is a combination of structural and cultural shifts:
- A clear written policy that defines what requires board approval versus superintendent discretion — specific enough that a new board member could use it to sort incoming agenda items
- A board self-evaluation process that includes governance-management boundary questions, so the pattern gets named publicly on a regular cadence rather than only when conflict forces it
- A board facilitator or coach who can observe meetings and name the pattern when it appears — someone with no stake in the political dynamics who can redirect without creating winners and losers
The harder question underneath the pattern
If your board keeps getting pulled into management, at least some board members probably want to be there. The question isn't only "how do we redirect?" — it's "why does your board find management decisions more comfortable than governance?" That's often a question about whether your board is willing to be accountable for student outcomes, which is harder than approving a vendor contract. Governance requires sitting with uncertain data, holding a superintendent to account in a human relationship, and accepting that you may not see results for years. Management offers the comfort of visible, concrete action. Naming that tradeoff honestly, with your whole board, is often what's required before the redirecting actually sticks.
Practical steps
- Before your next meeting, review the last three months of board agenda items. For each action item, ask: was this a goal, a guardrail, a legally required approval, or something else? Bring the "something else" list to a work session and discuss it explicitly.
- Adopt a written delegation policy that distinguishes what requires board approval from what falls within superintendent discretion. Review and update it annually.
- When your board is about to act on an operational matter, use a process question to pause: "What board policy requires us to approve this?" If no one can answer, that's the answer.
- When a community concern arrives, practice the values-versus-operational test out loud before deciding how to respond. Name which category it falls into and what your board's appropriate response is in each case.
- Schedule a board self-evaluation that includes governance-management boundary questions. Do it annually, not only when a problem surfaces.