The October board meeting is built in September

Labour Day Classic is over. The Stamps either won or didn't, and we have all moved on accordingly. The leaves in Kananaskis are starting to turn. Downtown is fully back from August, and somewhere on every operator's calendar is an October board meeting that does not quite know what it is going to be about yet. The board meeting is built in September, but most operators don't realize that until October.

The IT read your board actually wants - and the three slides that are almost always missing from it.

(One pattern that holds across 19 years of M&A in this town: the September scramble produces October decisions that get litigated in November and reversed in January.)

Most boards get an IT update that tells them very little. Spend versus budget, a project status table, a security incident count. Useful for managing IT. Not useful for governing the business.

The board read your directors actually want is different. They want to know whether the technology backbone of the business is getting stronger, holding steady, or weakening - and whether that trajectory matches the strategy the board is being asked to fund.

If your October board pack doesn't answer that, the directors who notice will lose confidence quietly, and the ones who don't notice will keep approving things they shouldn't. Neither is what you want.

The three slides almost always missing

Concentration risk on critical systems. One slide that says: here are our top five systems by business impact, here's who runs each one, here's what happens if any of them fail for 72 hours, and here's the gap between what we'd accept and what we'd actually experience. Most boards see a vendor list and a renewal date. That isn't a risk read; it's a procurement list.

Talent depth on the technology bench. Most mid-market technology functions sit on one or two people who, if they left tomorrow, would take a year of context with them. Boards ask about CFO succession. Most don't ask the same question about the people who hold the technology in their heads. They should. The slide doesn't need names - it needs a depth chart and an honest red/yellow/green on whether the depth matches the risk.

Strategic-vs-keep-the-lights-on ratio in the IT investment mix. One pie chart. Of what we're spending this year, how much is keeping current operations running, how much is paying down past decisions (debt, in the technical sense), and how much is actually building toward what we said we were going to build? If the answer is "92% keeping the lights on," the board needs to know it before they approve the next strategy that requires technology investment to deliver.

What this isn't

This isn't a transformation slide deck. It's three working slides that tell a board what they need to know to do their job. They can sit alongside whatever standing report you already produce. The first time you put them in front of the board, the conversation gets sharper. By the third time, the directors start asking the right questions on their own.

October sits on what September builds. If your standing report is the standing report, the October meeting goes the same way the August one did. If the read sharpens between now and then, the next twelve months of governance get sharper too.

Worth a half-day of work for the next four years of board conversations.

This issue of the Operator's Brief is operator pattern recognition from Vencer Group's work with mid-market businesses across industries and geographies. Not industry-specific advice. Read accordingly.