Governing is setting direction and holding the organization accountable for results. Managing is deciding how to get there. Your board owns the first; your superintendent owns the second. When your board blurs this line, it undermines your superintendent's authority and distracts itself from the only question that actually belongs to it: are students learning? The distinction isn't bureaucratic formality — it's the structural foundation that makes effective school governance possible.
The clearest way to draw the line
A useful test: if the decision requires knowledge of what happened in a school building yesterday, it's probably a management decision. If the decision shapes what the district is trying to accomplish and whether it's succeeding, it's a governance decision. Your board owns the destination and the accountability for getting there. Your superintendent owns the route.
Governance decisions include: adopting student outcome goals, setting guardrails that define what the superintendent will not do, approving the budget, hiring and evaluating the superintendent, and monitoring results against goals. Management decisions include: which curriculum to purchase, how to schedule professional development, which staff members to assign to which schools, and how to respond to a parent complaint. Your board should be deeply interested in the outcomes those management decisions produce — but not in making the decisions themselves.
Why the blur happens
Board members cross into management for understandable reasons. They're elected because they care. They have backgrounds in education, business, or community organizing that make them feel qualified to weigh in on operational choices. And the boundary isn't always obvious — especially when management decisions seem to be producing bad results.
But feeling qualified to make a decision and being the right person to make it are different things. A board member might know a great deal about reading instruction and still be wrong to override the curriculum director's recommendation. The governance structure exists precisely because distributed, coherent organizational authority produces better results than ad hoc intervention — even well-intentioned ad hoc intervention. And critically: if your board is involved in operational decisions, it loses the ability to hold your superintendent accountable for results. You can't evaluate a decision you co-made.
What micromanagement actually costs
When your board drifts into management, several things happen — all of them bad:
- Your superintendent's authority erodes. Staff quickly learn that decisions made by the superintendent can be relitigated by going to a board member. This creates parallel power channels that breed confusion, resentment, and slow execution.
- Your board's attention fragments. Every hour spent on operational details is an hour not spent on goal-setting, monitoring outcomes, or superintendent accountability. Your most important work gets crowded out by your least important work.
- Accountability becomes impossible. If your board is involved in operational decisions, it can no longer hold your superintendent cleanly accountable for results.
- Good superintendents leave. Talented leaders do not stay in organizations where their professional authority is routinely second-guessed by a committee. Boards that micromanage tend to retain only superintendents who tolerate it.
The governance question that clarifies everything
When you're unsure whether to weigh in on something, one question cuts through most of the ambiguity: "Am I asking about the outcome, or am I asking about the method?" Asking about outcomes is governance. Asking about methods is management. A board member who wants to know whether third-grade reading scores are improving is governing. A board member who wants to know which phonics program the reading coaches are using in second period is managing — unless your board has adopted a guardrail governing curriculum selection, in which case monitoring compliance with that guardrail is governance.
When your board disagrees with a superintendent's operational decision, the right response is not to direct a different action. It's to ask a monitoring question, or to consider whether the concern represents a values issue that warrants a new guardrail. Guardrails use negation language — "The superintendent will not…" — and they keep your concern at the governance level rather than pulling your board into management.
Practical steps
- At your next board work session, list the decisions your board made in the last six months. For each one, ask: was this a goal, a guardrail, a legally required item, or something else? Anything in the "something else" column is a management decision your board shouldn't have been making.
- Adopt a written policy that defines what requires board approval versus superintendent discretion. Make it specific enough that a new board member could use it to sort incoming agenda items.
- When a community member brings a concern to your board, practice the values-versus-operational test: if it's a values issue (what we should prioritize, what we won't tolerate), consider a guardrail. If it's operational (how something is being run), refer it to your superintendent without directing the outcome.
- When your board disagrees with a superintendent decision, respond with a monitoring question or a proposed guardrail — not a directive. "We'd like to see data on outcomes from that approach" keeps you in governance. "Change the approach" does not.
- Include governance-management boundary questions in your annual board self-evaluation. Name the pattern publicly so the whole board can correct course together rather than waiting for conflict to surface it.