← Back to all questions

Effective governance hinges on a clear delineation between the board's policy-setting role and the superintendent's operational execution. When these lines blur, board effectiveness diminishes and operational efficiency suffers. When a fellow board member brings up specific teacher assignments or student discipline cases in a public meeting, you redirect by referring to this framework: the board sets policy, the superintendent executes it. Say something like, "That's an operational decision that falls under the superintendent's authority. Let's take that offline and discuss whether there's a policy gap we need to address."

The distinction between governance and operations is the engine that makes a board effective because it creates clarity of role — the board focuses on system-level oversight while the superintendent has the authority to make operational decisions. Governance means establishing the strategic direction, formulating comprehensive policies, and holding the superintendent accountable for results. Operations means deciding which teacher goes to which classroom, how a particular discipline case is handled, and managing the day-to-day flow of the district. When a board member asks about a specific teacher assignment, they are not governing. They are performing the superintendent's job. The mistake many boards make is treating every concern raised by a colleague as a legitimate governance question. It is not. A question about whether your district's discipline policy is being applied consistently across schools is governance. A question about what happened to a particular student in a particular classroom is operations.

Translating this principle into practice requires consistent action. When the question comes up, the chair or any board member can say, "That's an operational matter for the superintendent. We can note your concern and follow up privately." If the board member presses, the response is, "Can you point to the policy you think we're not following?" If they cannot, the matter closes. If they can, you have a governance question worth discussing. The key is that you never debate the specific case in public. You either resolve it as an operational matter taken offline, or you elevate it to a policy discussion for a future agenda. Taking a concern offline allows you to gather facts and determine whether the concern reflects a systemic issue worth bringing back to the full board as a policy discussion, rather than debating the specific case in public.

One honest complication deserves direct address: what if the board member insists their question is really about policy? This happens when someone has a genuine concern about whether the district is applying its own rules fairly. The right move is to ask them to identify the specific policy they are questioning. If they name the policy, you schedule a governance discussion about whether the policy is being followed or whether it needs revision. If they cannot name a policy, if they are simply unhappy with an outcome, you thank them for their concern, note that the superintendent has the authority to make that call, and move on. The distinction between governance and operations can be nuanced and may require careful consideration on a case-by-case basis. For ambiguous cases where the policy connection is unclear, consider a preliminary review by a governance committee to determine whether a policy discussion is warranted. The board's job is to ensure the system that produced the decision is sound, while recognizing that exceptions or unusual circumstances may require flexibility in how this principle is applied.

Here are the steps your board can take:

1. At your next board retreat, review the governance-operations distinction using your own policies. Have each board member articulate one decision that belongs to the board and one that belongs to the superintendent.
2. When the question arises in a meeting, use the same language every time: "That's an operational decision" or "Let's take that offline." Consistency signals that the rule is real, not situational.
3. If a board member repeatedly raises operational questions, schedule a private conversation. Ask directly: "Are you seeing a pattern that suggests a policy problem, or is this about a specific outcome you disagree with?" This forces clarity. If the board member continues to disregard the governance-operations distinction despite private conversation, escalate to formal board protocols or consider involving governance training to reinforce the distinction.
4. When a concern does point to a policy gap, bring it to the full board as a deliberate agenda item, not as a reaction to one board member's question, but as a governance review of the system.
5. Include in your board's annual self-evaluation a check: have we stayed within our governance role this year, or have we drifted into operations?

Your board's credibility with the public depends on this discipline. When board members routinely question individual teacher assignments or student discipline decisions, the public sees a board that cannot tell the difference between oversight and interference — the public expects board members to set policy, not to involve themselves in day-to-day decisions. When your board consistently redirects those questions while taking seriously the task of setting and reviewing the policies that govern those decisions, you model the governance the district needs. To preempt misunderstandings, communicate the governance-operations distinction publicly through board communications and meeting explanations, so the public understands why certain questions are redirected. The superintendent gains clearer authority to lead when the board stays in its lane because operational decisions rest with the superintendent, and your board gains the one thing that makes all other accomplishments possible: trust that you will govern, not manage.