How to Run a Board Meeting That Doesn't Waste Everyone's Time

By Kent Fenwick, Runner co-founder — 2026-03-06

You know that feeling on the Sunday before a board meeting when you are still stitching together slides, Slack threads, and half-finished numbers? In my experience that is usually the moment the meeting already went wrong. The room has not happened yet, but the quality of the room has already been set.

A board meeting is not a status meeting

A good board meeting is a place to create clarity, make decisions, and pressure-test the hard parts of the business. It is not the best place to read 40 slides out loud. If the meeting becomes a narrated recap of facts everyone could have read beforehand, you are burning your most expensive room.

• Update items belong in the pre-read.
• Discussion items belong in the room.
• Decision items should be explicit and few.
• Anything vague enough to become a ramble should be tightened before the meeting starts.

The meeting starts a week before the meeting

The best board meetings I have seen were mostly won in the prep. That means locking the agenda early, collecting the real numbers early, and deciding in advance where you want board attention. If you do not do this, the last forty-eight hours become an archaeology project.

• Seven days out: lock the agenda and identify the actual decision topics.
• Five days out: gather the metrics, owner updates, and the draft narrative.
• Three days out: circulate a real pre-read, not a placeholder deck.
• One day out: tighten the open questions and align on who owns each discussion topic.
• Day of: walk into the room ready to discuss tradeoffs, not to figure out what happened.

Write from the system, not from memory

This is where founders lose a surprising amount of time. The story of the quarter is spread across inboxes, docs, dashboards, product notes, hiring plans, and side conversations. If you try to reconstruct it from memory, you end up with a smooth version of the truth. Board meetings get better when the materials are assembled from the systems where the work actually happened.

What should be in the pre-read

• A short narrative of what changed since the last board meeting.
• The handful of metrics that actually explain the business right now.
• A clear summary of wins, misses, and surprises.
• The decision areas where you want advice, pressure, or approval.
• Background material in appendices so the main deck stays clean.

The pre-read should do most of the updating. The live meeting should do most of the thinking.

A simple agenda that usually works

• Opening and framing: what matters most in this meeting.
• Quick review of company performance: what changed and why.
• Deep dive one: the biggest strategic issue on the table.
• Deep dive two: the operational or financial issue that needs board attention.
• Decision block: the specific asks for the board.
• Wrap-up: owners, dates, and what happens before the next meeting.

Run the room with a little tension

I think a useful board meeting should have a little tension in it. Not theater. Not combat. Just enough honesty that the hard questions actually surface. If everyone is too comfortable, you often end up with a friendly deck review instead of a working session.

• Do not use the first twenty minutes for silent reading.
• Name the hard question plainly instead of circling it.
• Ask the board where they disagree, not only where they agree.
• Separate information from recommendation so the discussion stays sharp.

Common ways founders waste the room

• Too many slides and not enough decisions.
• Metrics without interpretation.
• A deck written too late to be challenged properly.
• Asking the board vague questions that produce vague answers.
• Ending without owners, dates, or a record of what was decided.

What should happen in the next 24 hours

The meeting is not done when everyone leaves the Zoom or the room. Within a day, you want decisions captured, follow-up items assigned, minutes drafted, and any promises reflected in the operating system of the company. If that does not happen, the meeting fades into institutional fog.

Board meetings should create clarity. If everyone leaves with more ambiguity than they walked in with, that is not governance. That is theater. This is part of why we built Runner. I wanted the machine to gather the context and help shape the materials so the founder could spend the real energy on judgment.