Usually, no. A superintendent who pushes back on operational micromanagement is doing their job. The right question to ask yourself is whether your board's question is about student outcomes or about operations — because those require entirely different responses, and conflating them creates the friction you're experiencing.
When the superintendent is right to push back
If your board is asking which vendor was selected for a facilities contract, which assistant principal was assigned to which school, or what the professional development agenda looks like for next Tuesday — those are operational questions. They sit squarely in the superintendent's domain. A superintendent who answers those questions without pushback is training the board to expect operational access, which leads to a dysfunctional relationship where the superintendent is effectively working for seven bosses with different operational opinions.
Pushback in these situations isn't defensiveness — it's professional boundary-setting. A superintendent who never pushes back on scope creep is either conflict-averse to a fault or doesn't understand their own role. Neither is a good sign.
When the superintendent is wrong to push back
The dynamic flips entirely when your board is asking governance questions that the superintendent is treating as overreach. A superintendent should never push back on:
- Requests for student outcome data — achievement trends, attendance, graduation rates, disaggregated by subgroup
- Questions about whether district work is aligned to the board's adopted goals
- Requests to understand how the budget connects to strategic priorities
- Questions about what happened after the board identified a goal that was off track
- Requests for transparency about the superintendent's evaluation criteria and progress against them
These are not operational intrusions. They are core governance functions. A superintendent who resists them is either confused about the board's legitimate authority or actively avoiding accountability — and your board should name that distinction directly.
How to tell which situation you're in
The cleanest diagnostic: ask yourself what your board would do with the answer. If the answer would inform a board-level decision — a policy vote, a budget allocation, a goal adjustment, a superintendent evaluation — it's a governance question and your board is entitled to it. If the answer would inform a management decision that the superintendent is supposed to be making, your board may be in their lane.
A second test: is the question traceable to a specific student outcome your board is trying to understand? Questions that can be connected to outcome monitoring are almost always appropriate. Questions that are really about how things work operationally — born from curiosity, personal interest, or constituent pressure — are often not.
What to do when you're not sure
Name the uncertainty directly, with the superintendent, outside of a board meeting. A productive conversation sounds like: "We asked about X and felt like we got some resistance. Help us understand whether that's a governance question we're entitled to press on, or whether we were drifting into your territory." Most strong superintendents will welcome that conversation. It's an opportunity to clarify the working relationship without anyone losing face in public.
If the pattern is that your superintendent consistently deflects questions that are clearly within the board's governance purview — outcome data, goal alignment, accountability information — that's a different and more serious problem. It should be addressed through the superintendent evaluation process, not through escalating conflict in public meetings.
The underlying dynamic worth naming
Friction between boards and superintendents over question scope almost always traces back to one of two root causes: a board that hasn't internalized the governance/management distinction, or a superintendent who is using "that's operational" as a shield against legitimate accountability. The answer to the first is board development. The answer to the second is a frank performance conversation. Knowing which problem you have matters — because applying the wrong solution makes both situations worse.
Practical steps
- Before raising a question with the superintendent, run the two-part test. Ask: would the answer inform a board-level decision? And: is the question traceable to a student outcome goal your board adopted? If yes to either, proceed. If no to both, consider whether the question belongs in a board meeting at all.
- Send questions to the superintendent before the meeting. Your board should share monitoring questions with the superintendent at least three working days in advance. This gives the superintendent time to prepare data-backed answers and removes the dynamic where pushback happens under public pressure.
- Have the scope conversation outside of public meetings. When pushback occurs and you're not sure whether it's warranted, schedule a direct conversation with the superintendent to work through the distinction — not to relitigate the specific question, but to build shared understanding of the boundary.
- Name persistent deflection in the evaluation process. If your superintendent consistently resists questions about outcome data or goal progress, document it and address it during the annual evaluation. Accountability-avoidance is a performance issue, and the evaluation is the right venue for it.
- Adopt written norms about question scope. Your board's working agreements should describe what kinds of questions belong in a governance meeting and what channels exist for other inquiries. This gives the board chair a neutral reference point when scope disputes arise in real time.