What board meetings are actually for
Most founders treat board meetings as quarterly status updates with governance attached. They arrive over-prepared on the numbers and under-prepared on the decisions. The founders who get genuine value from their boards use the meeting for something entirely different.
The status update is a waste of a board meeting.
The typical Series A board meeting runs like this: the founder presents the deck, the deck covers Q3 performance against Q2 plan, the board asks clarifying questions about metrics, there is a brief discussion about the sales pipeline, the meeting ends with a few action items that are mostly research tasks assigned to the founder. Everyone leaves with the impression that governance occurred. Almost nothing useful happened.
This is not the board's failure — it is the founder's. The founder who designs the agenda sets the quality of the meeting. And most founders design board meetings as reporting exercises because that is what they are anxious about: the judgment of people who hold their capital and, in some structures, their seat. The response to that anxiety is to spend ninety percent of the preparation time making the numbers look good in a deck. The result is a meeting that produces no value proportional to the preparation invested.
The founders who get the most from their boards — who walk out of board meetings with sharper thinking, better decisions, and stronger investor relationships — run their boards differently at a structural level. They treat the meeting as a resource to extract from, not an obligation to discharge.
What a board actually has to offer.
A board is not a reporting audience. It is a collection of people who have seen more companies at your stage than you have, who have a financial stake in your outcome, and who have agreed to give you access to their networks, their pattern recognition, and their judgment on specific questions. The operative words are "specific questions." Board members are useful in proportion to the specificity of what you bring them.
A board member who is asked "what do you think about our go-to-market?" will give you a generic answer. The same board member asked "we are choosing between a direct sales motion targeting CFOs and a channel partner strategy through accounting software platforms — we have run both for two quarters and here are the unit economics, what have you seen work in this cost range?" will give you a specific, useful answer. The difference is not the board member — it is the question.
The board offers three things that are genuinely difficult to get elsewhere: pattern recognition from companies at your stage and in your category, access to networks that you cannot cold-reach, and the particular kind of outside perspective that comes from someone who cares about your outcome but does not share your operational tunnel vision. All three of these things are only valuable if you give the board the right surface area to engage with.
The structure that produces value.
The board meeting structure that consistently produces value has four components, roughly in this order.
The pre-read, sent 48 hours in advance. This is a three-to-five page memo, not a slide deck. It covers: actual performance versus plan with honest variance explanations, the two or three external developments that most affect the company's strategic situation, and the agenda for the meeting with a clear statement of the decisions or questions you want the board to engage with. The memo does the work of status-reporting so the meeting does not have to. Any board member who shows up to a board meeting without reading the pre-read is telling you something important about how much they value the relationship. That conversation is worth having separately.
Fifteen minutes of governance. Resolutions, approvals, consent items. Fast, undramatic, done. If your governance items are requiring extended discussion, you have a structuring problem — governance decisions should be clear before the meeting, with any disagreements surfaced in the pre-read exchange, not discovered at the table.
The strategic discussion, structured around one or two real decisions. This is the meeting. Come with the one decision — maybe two — that genuinely require outside perspective. Not "we are thinking about expanding to Australia" as a status update, but "we have a decision to make about whether to pursue the Australian market in Q3 or focus capital on deepening penetration in Singapore. Here are the arguments for each, here is what we do not know, here is our current lean and why." Then open the room. Let the board disagree. Ask follow-up questions. Write down what you hear. This is the part that justifies the meeting.
The close, which is a specific ask. End every board meeting with a specific ask of each board member. "I need intros to two series B leads who have written into logistics software in the last eighteen months — can you each send me three names by the end of the week?" The close turns the meeting's goodwill into a concrete output. Board members who leave a meeting with a specific ask are far more engaged between meetings than those who leave with a warm feeling and no task.
The pre-work that makes the meeting work.
The quality of a board meeting is set three weeks before it happens, not the night before. The preparation that produces the best outcomes involves three steps that most founders skip.
One: the pre-meeting one-on-ones. In the week before the board meeting, call each board member individually. Tell them what you are planning to bring to the board for discussion. Ask them what they are thinking about. This serves two purposes: you surface any strong views that would disrupt the meeting if they emerged for the first time in the room, and you build the relationship that makes the board member willing to do the hard work of genuine engagement. A board member who has talked to you in the week before the meeting shows up to the meeting as a participant, not an audience member.
Two: the decision brief. For every decision you plan to bring to the board, write a one-page brief before the meeting. The brief has four sections: the decision to be made, the options you have considered, the criteria for making the decision, and your current thinking with its key uncertainties. The act of writing the brief forces you to have done enough thinking that the board discussion is genuinely useful — if you cannot write the brief, you are not ready to bring the decision to the board.
Three: the metrics memo. Rather than building a new metrics update for each board meeting, maintain a running document that tracks performance against plan on the three to five metrics that matter most. Update it monthly and share it with the board monthly, whether or not there is a board meeting. When the board meeting arrives, the performance context is already established. You do not spend the first hour of the meeting educating people on numbers they should already know.
- 01Send the pre-read 48 hours in advance, not the morning of. A pre-read sent the night before will not be read. A pre-read that arrives 48 hours early gets read and thought about. The quality of the meeting is directly proportional to how prepared the board members are when they walk in. You control that through your timing.
- 02Come with no more than two decisions. The board meeting that tries to get useful input on five strategic questions produces shallow thinking on all five. The meeting focused on one or two decisions produces the kind of depth that is actually useful. Triage ruthlessly. If something does not need outside perspective, it does not need board time.
- 03Never let the board learn bad news for the first time in the board meeting. If you have a significant negative development — a key departure, a missed milestone, a customer loss — your board should have heard about it from you, directly, before the meeting. Not in the pre-read memo. A personal call. The board meeting is the wrong place for the first reaction to bad news. The board meeting is where you discuss what to do about it.
- 04Close with a specific ask. Every board meeting should end with each board member leaving with something concrete to do — an introduction to make, a reference to check, a question to think about before the next meeting. The ask converts the meeting's goodwill into forward motion. Without it, board members disengage between meetings.
- 05Build the board culture you want, starting with the first meeting. Whatever norms you establish in your first three board meetings will persist. If you run the first three as status updates, you will spend years trying to convert the board to a strategic function. If you run the first three as decision-focused sessions with tight pre-reads and specific asks, the board will calibrate to that standard. Culture is set at the beginning, not corrected at the middle.
Frequently asked questions.
How long should a board meeting run?
Two to three hours for a company at seed or Series A. The board update materials — financials, metrics, progress against plan — should be sent 48 hours in advance and read before the meeting. If your board meeting is spending the first hour reviewing numbers that should have been read beforehand, you have a board culture problem, not a scheduling problem.
What should go in the board pre-read?
The pre-read has three sections: performance (actuals versus plan for the quarter, with variance explanations), context (the two or three external or strategic developments that most affect the company's situation), and the agenda for the meeting itself, including the specific decisions or questions you want the board to engage with. The pre-read should not be a slide deck — it should be a memo, three to five pages, written in prose that forces you to explain, not just report.
How do you handle a board member who is consistently unhelpful?
First, distinguish between unhelpful and uncomfortable. A board member who consistently pushes back on your strategy, asks hard questions, or surfaces risks you would rather not discuss is not unhelpful — they are doing the job. A board member who is unhelpful is one who is disengaged, who relitigates settled decisions, or whose advice is so generic it could apply to any company. For the disengaged member, a direct conversation about the value exchange helps. For the member who relitigates, the solution is more rigorous meeting structure, not a personnel change.
Should the CEO present every section of the board meeting?
No. Bringing functional leaders into the board meeting to present their area — the CFO on financials, the CPO on product — builds board-level familiarity with your leadership team, signals that the company is building management depth, and frees the CEO to focus on strategy and the decisions that require board input. It also protects against the single point of failure that comes from a CEO who personally controls all board communication.
Working on this?
If this is the problem on your desk, a 30-minute intro is the fastest way to find out whether I can help.
Request an intro →