Your board can adopt student outcome goals over the superintendent's formal objection, subject to state law and your district's bylaws, which typically grant the board authority over goals while the superintendent manages implementation. Goals define what results you want for students. That authority sits with the board, subject to state law and your district's bylaws. The superintendent's job is to achieve those goals, and to recommend honestly what it will take—so the question isn't whether you may act, it's whether you should act the way you're planning to.
Here is the principle worth holding onto, with an important caveat. In most governance frameworks, the board sets direction and the superintendent operationalizes it. When you say "our students will read on grade level by third grade," you're naming an end. When the superintendent decides which reading program, which staffing, which schedule, that's means. But ends and means are not always cleanly separable, setting a specific end can implicitly constrain what means are available, and the superintendent's input on ends often reveals practical constraints. Treat this principle as a useful starting framework, not a rigid rule. A formal objection to a goal is your superintendent telling you something about feasibility, resources, timeline, legal compliance, or alignment with other district priorities. That's valuable information. It is not a veto.
The common mistake is treating the objection as a wall or as noise. Some boards back off entirely, and a real goal dies. Other boards steamroll ahead, adopt the number, and never ask what the objection was about. Both responses waste the moment. The effective move is to separate the things buried in most objections. One part is "this goal is unwise"—it conflicts with other priorities, raises legal or ethical concerns, or doesn't reflect the district's values. The other part is "this goal is unachievable with what I have"—the timeline is too tight, the resources don't exist, or the target ignores constraints you control. There may be other valid concerns too, including situations where the superintendent's objection reflects their own preferences or political calculations rather than objective constraints. You handle those differently.
If the objection is about wisdom, that's a governance conversation you lead. Your superintendent gets a voice, not a vote, on what the district values. You'll want to hear the reasoning fully, then decide as a board. If the objection is about achievability, you've learned something concrete. Maybe the timeline is too tight. Maybe the target ignores a resource gap you control. That's not a reason to abandon the goal. It's a reason to sharpen it, adjust the timeline, or fund what's needed. If the superintendent cannot articulate specific needs or constraints, treat that as its own useful signal about their planning.
Now the honest complication. Adopting a goal your superintendent has formally opposed creates a real risk, and you should name it out loud. You may be setting a target that fails, then holding the superintendent accountable for a failure they predicted. That's a trap for both of you. If you proceed over the objection, you're also accepting shared ownership of the risk. The monitoring reports will show whether the goal was unrealistic or the execution fell short. Be prepared to read that data honestly, including the possibility that the superintendent was correct.
There's also the practical matter of the vote itself. A goal adopted 4-3 over the superintendent's written objection lands differently than one adopted 7-0. The legal authority is identical. But a split board signaling disagreement with an opposed superintendent creates political fragility—a multi-year target needs broader consensus to survive leadership changes, budget pressures, and shifting priorities. You can still proceed. Just know you'll be spending trust you may need later.
Here's how to work through it.
- Before you vote, ask your superintendent to put the objection in writing, with the reason named. Request one sentence: is this about whether the goal is worth pursuing, whether it can be achieved with current resources, or something else like legal compliance or competing priorities? That single answer changes everything that follows.
- If the objection is about achievability, ask directly in your next meeting or one-on-one: "What would you need from the board to make this goal achievable?" Then listen for the answer that lives in your control—budget, timeline, a competing priority you can drop. Write down what you hear. If the superintendent cannot articulate specific needs, that itself is useful information about their planning or willingness to engage.
- Adjust the goal or the timeline based on what you learn, then bring the revised version back to the full board. A goal your superintendent can commit to is worth more than a bolder number they've disowned, because commitment increases the likelihood of serious effort and honest assessment. Don't confuse ambition with a target that no one owns.
- If you still choose to adopt over a standing objection, name the shared risk in the meeting record. Say plainly that the board is accepting responsibility for a goal the superintendent flagged. This protects your future self when the monitoring data comes in, and it keeps the accountability conversation honest.
- Set the first monitoring checkpoint sooner than usual—within a semester, not a year. Watch the early data with genuine openness. You're testing two things at once: whether the goal was set right, and whether the district is moving toward it.
That last point is the one you'll keep returning to. Adopting a goal over an objection isn't a one-time act of authority. It starts a relationship you have to tend, meeting after meeting, report after report. The boards that do this well don't win the argument and move on. They keep asking, at every checkpoint, whether the data is telling them something they didn't want to hear.