The Difference Between a Season and a Practice: Sustaining Governance Disciplines Through Spring
March 29, 2027
February was the alignment month. If your board followed the February Alignment Arc — the budget review, the first data check-in, the superintendent evaluation 90-day checkpoint, the policy audit, the listening sessions, the governance team health check — you built something that most boards never build: a connected set of governance disciplines that actually work together.
The budget review taught your board to read a budget for goal alignment. The data check-in established a decision structure for progress monitoring. The policy audit connected the board’s adopted goals to the policy framework that governs operations. The governance team health check forced the board to ask whether it was governing the way it committed to.
Those are five disciplines. And they’re impressive — for February.
Here’s the question that determines whether your board’s governance improves for the rest of the year: were those disciplines a seasonal response to budget season, or did they become a sustained governance practice?
The difference between a season and a practice
I’ve watched boards run a flawless February. The budget review was structured. The data check-in produced recorded decisions. The policy audit was thorough. The governance team health check surfaced real issues that the board committed to addressing.
Then March arrived, and the disciplines started slipping. The budget alignment review happened — but the board didn’t schedule the Q3 data review. The April budget adoption happened — but nobody set the date for the second data check-in. The governance calendar that the board adopted in January started showing blank spots in April and May. Board members who were fully engaged during budget season stopped reading advance materials. The meeting structure that produced focused February conversations started reverting to the old format.
February wasn’t a failure. February was a season. A season is a concentrated period of disciplined activity driven by an external deadline — budget submission, public hearing, adoption vote. The deadline forces the discipline. When the deadline passes, the discipline fades.
A practice is different. A practice is a discipline that continues after the deadline passes because the board has built it into how it operates. The data review that happens every board meeting, not just during budget season. The goal alignment check that the board runs even when there’s no budget on the table. The governance team check-in that the board schedules in advance, rather than running reactively when something goes wrong.
The February Alignment Arc built the disciplines. The March arc is about turning them into a practice.
The Focused Monitoring Cycle: the test of sustainability
The ESB Framework requires boards to maintain a Focused Monitoring Cycle — a regular, public, recorded review of goal progress that happens at every board meeting, not just during budget season.
The test of whether your board’s February disciplines have become a practice is simple: can your board run a data review in May, when there’s no budget deadline, no public hearing, no external pressure?
May is the hardest month on the governance calendar. Budget season is over. The superintendent evaluation feels distant. The community’s attention has shifted to end-of-year events. The board’s own members are distracted by spring schedules. The governance calendar has more empty space than any other month.
And May is precisely the month when the Focused Monitoring Cycle reveals whether your board is governing with disciplines or governing by crisis.
The boards that sustain the cycle through May share three characteristics.
1. They schedule the review cadence before budget season ends.
The board that waits until May to schedule the May data review won’t hold the May data review. The board that schedules all quarterly data reviews in January — and locks them into the governance calendar before anything else competes for the time — holds the May review because it’s already on the calendar, not because the board remembered to schedule it.
The January governance roadmap piece recommended this. The question is whether your board actually did it. If your April board meeting didn’t include a calendar review confirming the May and June data review dates, that’s the first thing to fix.
2. They maintain the same meeting structure regardless of the agenda.
The boards that sustain the Focused Monitoring Cycle through spring use the same meeting structure for every data review. The superintendent doesn’t get sixty minutes to present data in February and fifteen minutes in May. The board doesn’t ask detailed operational questions in February and skip questions entirely in May. The format is consistent because the board’s expectation is consistent.
The structure — thirty minutes, superintendent presents, board runs the three-outcome decision framework, recorded decision for each goal — is the same in every data review. The consistency of the structure, not the urgency of the content, is what sustains the discipline.
I’ve watched a board hold a May data review where none of the goals had significant movement since February. The data was flat. The board’s decisions were “stay the course” for all three goals. The meeting lasted twenty-two minutes instead of thirty. But it happened. The structure held. And when June’s data showed movement, the board had the May baseline to compare it against.
If the board had skipped May because nothing had changed, it would have lost the comparative data point and broken the cadence. The cadence is the point.
3. They discuss governance sustainability explicitly at the mid-year check-in.
The April mid-year governance check-in — if your board scheduled it — is the moment to discuss governance sustainability explicitly. The check-in should include a question that most boards never ask: are our February disciplines holding, or are they slipping?
The five indicators from the February check-in provide the framework. Meeting structure — are meetings still producing what the calendar promised? Board member contribution — is every member still participating at the February level? Calendar integrity — did the board hit every milestone it set in January? Communication discipline — has the board maintained one-voice discipline under budget pressure? Governance alignment — has three months of execution deepened or eroded the board’s shared definition of governance?
The April check-in should produce specific adjustments for sustaining the disciplines through May and June. If the board identified a meeting structure problem in February and the problem persists in April, that’s not a discovery — it’s a failure to act. The April check-in is the moment to name the gap and commit to closing it.
The Q3 dashboard review: a specific milestone
The Q3 dashboard review — typically late May or early June — is the third full data review of the governance year. It follows the February Q1 review and whatever Q2 review the board scheduled in April.
The Q3 review is significant because it’s the last data review before the year-end governance report. The data the board sees in Q3 determines what the year-end report will say. If the board skips Q3 or runs a shortened version, the year-end report will lack the comparative data it needs to show the full year’s progress.
I recommend three specific actions for the Q3 review that go beyond the standard data review structure.
1. Year-to-date trend analysis. The Q3 review should include a year-to-date trend line for each adopted goal, showing the Q1 data point, the Q2 data point, and the current Q3 data point. The trend line tells the board whether the direction of change is consistent or inconsistent. A goal that improved from Q1 to Q2 but plateaued in Q3 needs a different governance response than a goal that has steadily improved across all three reviews.
2. Resource-to-outcome check. The March budget alignment review checked whether the board’s resources matched the trajectory. The Q3 review checks whether the resources that were allocated actually produced change. If the board directed a 12% increase in reading intervention funding in March, the Q3 review asks: did the 12% increase produce the expected movement in reading proficiency? If it didn’t, the board needs to ask why — and the answer may inform the next budget cycle before it starts.
3. Year-end governance report planning. The Q3 review is the moment to set the timeline and scope for the year-end governance report. I’ll cover the year-end report in detail later in this arc. For now, the Q3 action is: the board president or designated board member should confirm the report’s due date, the data it will require, and the person responsible for assembling it. The board that plans the year-end report in Q3 will have a comprehensive report in June. The board that starts the year-end report in June will have a hasty report in July.
The year-end governance report: why spring preparation matters
The year-end governance report is the board’s annual accountability document. It tells the community: here are the goals we adopted, here’s the progress we made, here are the decisions we made that drove that progress, and here’s what we learned that will shape next year’s goals.
Most boards don’t produce a year-end governance report. They produce a superintendent’s annual report — which is the district’s operational report, not the board’s governance report. The superintendent’s report covers enrollment, staffing, programs, facilities. The board’s governance report covers goal progress, budget alignment, governance team performance, and community engagement.
If your board wants to produce a year-end governance report — and I recommend every board do this — the preparation work starts in March, not June.
March is when the board should confirm the report’s scope. April is when the board should assign responsibility for each section. May’s Q3 review generates the data that fills the progress section. June’s year-end governance check-in produces the governance team assessment.
A board that begins year-end report preparation in March will produce a report that the community can read, understand, and act on. A board that begins in June will produce a report that is either incomplete or late — and the community will notice the absence more than it would have noticed the report.
The arc ahead: March through spring
This piece opens the March Governance to Impact arc. The arc covers two connected themes: completing the spring budget cycle with discipline, and sustaining the governance practices that budget season built.
The existing pieces in this arc — the budget alignment review framework, the goal-to-budget crosswalk, the community progress report, the content guide, the trust bridge, the combined meeting design, and the April preview — all contribute to the first theme. The arc’s second theme — governance continuity — begins here.
Wednesday’s piece will address the first practical step: how to lock the Q3 data review cadence before budget season ends, including the specific board action that makes the difference between a scheduled review and a forgotten commitment.
Your board built the disciplines in February. March through June is where they prove themselves. The difference between a season and a practice is not the February work — it’s whether the work continues when no deadline demands it. That’s what this arc is designed to help your board do.
Let’s get to work.
Your free CTA: Reply to this email with the keyword Sustain and I’ll send you the Governance Sustainability Assessment — a one-page tool that measures whether your board’s February disciplines are holding or slipping, with the five-indicator framework, the mid-year check-in integration guide, and the Q3 dashboard review preparation checklist.
Your paid CTA: I offer a Spring Governance Sustainability Coaching Package — structured support from March through June, including the mid-year check-in facilitation, Q3 dashboard review design, and year-end governance report preparation. Reply to this email for pricing and availability.
This opens the March Governance to Impact arc: budget alignment and community progress reporting — and the governance sustainability disciplines that keep both running through spring. Wednesday’s piece covers locking the Q3 data review cadence before budget season ends. Subscribe at effectiveschoolboards.com to continue the series.
Backlinks: This piece builds on the February Alignment Arc — the budget review (Feb 1), first data check-in (Feb 3), supt eval 90-day checkpoint (Feb 8), policy audit (Feb 10), governance team health check (Feb 22), and the board self-assessment (Feb 24) that established the five disciplines. The Focused Monitoring Cycle concept extends the Jan 27 governance roadmap’s calendar structure. The Q3 dashboard review action steps connect to the dashboard evolution framework from Feb 19. The year-end governance report preparation timeline connects to the April preview (Mar 22) and the Jan 6 governance calendar. The sustainability framework extends the governance team check-in from Feb 22 by applying its five indicators to the spring months.