What Your Board Learned This Spring — and What to Carry Forward

May 3, 2027


The governance year that runs January through June is nearly complete. Your board adopted goals, set a budget, conducted data reviews, evaluated a superintendent, engaged the community, and closed out a full governance cycle. Whether the board realizes it or not, that cycle produced institutional knowledge — specific lessons about what worked, what didn’t, and what the board should do differently when the next governance year begins.

Most boards skip the lesson-capture step. They finish June, scatter for summer, and reconvene in August or September without having documented what they learned. The result is a governance year that starts fresh in name only — the same patterns, the same blind spots, the same unexamined practices that produced the same outcomes.

This piece is the spring lesson-capture framework. Use it before the summer break.

Three questions every board should answer before summer

The lesson-capture framework has three categories. Each category has one question. Answer each question as a board — not as individual members, but collectively, in a work session or study session before the final June meeting.

Category one: Data and decision-making. The board conducted at least two full data reviews this governance year — one in February and one in May. The May review included budget-to-actual data for the first time. What did the board learn about how it uses data to make decisions?

Some boards discover that they look at outcome data but not resource data together. They make a decision about reading proficiency without checking whether the literacy budget is producing the result. Some boards discover that they look at trajectory data but not variance — they see improvement month over month but don’t ask whether the improvement rate is fast enough to reach the annual target. Some boards discover that they spend more time on data presentation than on decision-making — the presentation takes forty-five minutes and the decision takes five.

Write it down. That’s a lesson the board should carry into the fall goal-setting process.

Category two: Community engagement. The board conducted at least one community testimony cycle this governance year — the spring budget hearings, the community progress report, or both. What did the board learn about how it listens and responds?

Some boards discover that they hear from the same people every time — the regular speakers who attend every meeting. The board’s engagement reach is narrower than the board thought, and the community voices the board isn’t hearing may be the ones that matter most. Some boards discover that they respond to testimony but don’t close the loop — a parent testifies about bus routing, the board directs staff to investigate, and the parent never learns what happened. Some boards discover that the community engagement calendar is disconnected from the board’s decision calendar — the board solicits input after the decision is already made.

Write it down. The fall governance year should start with a community engagement plan, not just a hearing schedule.

Category three: Board culture and operations. The board operated on a governance calendar from January through June — meeting schedules, agenda protocols, decision recording, board member preparation discipline. What did the board learn about how it operates as a team?

Some boards discover that the meeting schedule works but the preparation timeline doesn’t — board members receive agenda packets two days before the meeting, which is enough time for reading but not enough for thoughtful review. Some boards discover that decision recording has improved but follow-through hasn’t — the board records a decision but has no system for tracking whether the decision was implemented by the agreed deadline. Some boards discover that the governance model works when every board member participates but breaks down when one or two members miss meetings — the board has no continuity protocol.

Write it down. The fall governance year is the opportunity to fix what didn’t work.

What to do with the lessons

Capture them in a one-page governance lessons document. Three categories, three answers, three action items. The board reviews this document at the first board meeting of the new governance year — before setting goals, before approving a calendar, before anything else. The lessons from the spring become the input for the fall decisions.

A board that doesn’t capture its lessons enters the fall governance year with the same practices that produced the same results. A board that captures its lessons enters the fall with an improvement plan already written.


Your free CTA: Reply to this email with the keyword SeasonReview and I’ll send you the Spring Governance Lessons Capture Template — a one-page framework covering the three categories, the three questions, the board conversation facilitation script, and the action-item format that feeds directly into fall goal-setting.

Your paid CTA: I offer a Governance Year Retrospective Facilitation — a ninety-minute board work session covering the spring lesson-capture framework, the documentation format, and the integration of lessons into the fall governance calendar design. Reply to this email for pricing and availability.


This opens the Summer Launchpad and Transition to Next Governance Year arc: spring lessons, board self-evaluation, summer professional development, and goal-setting timeline. The arc flows from the April infrastructure arc and the May “Governance to Impact” execution arc. Wednesday’s piece covers board self-evaluation — using the mid-year check-in data to evaluate governance effectiveness before the summer break. Subscribe at effectiveschoolboards.com to continue the series.

Backlinks: This piece builds on the lesson-capture theme previewed in the Apr 26 community testimony closeout piece and the May 3 spring sprint arc opener. The three-category framework extends the board self-evaluation methodology from the Feb data review methodology. The community engagement reflection connects to the Mar community progress report piece and the Apr community testimony reflection piece. The decision recording follow-through connects to the decision recording protocol from the Feb 3 and May 5 data review pieces. The governance lessons document format aligns with the governance closeout framework from the May “Governance to Impact” arc.