What Your Board Actually Needs to Hear About Technology

Technical accuracy is worthless if the people who fund it can't make a decision with it.

Most technology reports to boards fail in one of three ways. They're too long, so nobody reads them. They're too technical, so nobody understands them. Or they're always green, so nobody believes them - right up until the quarter something goes badly wrong.

The fix isn't a better template. It's remembering who's reading, and what they're there to do.

What the board is there to do

Board members aren't technology experts, and they don't need to be. Their job is to understand the risks to the business, make sure there are enough resources to manage them, hold leadership accountable, and ask good questions.

So the report's job is to give them what they need to do that - and nothing else.

Lead with the decisions

If the board only reads one part of your report, it should be what you need them to decide.

Put it first. For each decision: what it is, why it matters to the business, the options, your recommendation, and when you need an answer. "Approve $60,000 to finish the customer portal, because two renewals depend on it. We recommend funding it now with a smaller first release." That's a decision a board can make in a meeting.

Burying the ask on page six, after the project updates, is how decisions get deferred to the next quarter.

Risks in business terms

Every technology risk can be described two ways.

"We have unpatched vulnerabilities in our ERP environment" is accurate, and means nothing to most boards.

"Our order system is out of support. If it fails, we can't ship, and a replacement takes six months" is the same risk, and the board can act on it.

For each of your top risks: what it would mean for the business, how likely it is, whether it's getting better or worse, who owns it, and what you're doing about it. Five risks is plenty. If everything is a top risk, nothing is.

Projects: outcomes, not activity

Boards don't need to know a project is "60% complete". They need to know whether it will deliver what it was approved to deliver, when, and for what it was meant to cost.

For each significant project: the business outcome it's for, whether it's on track, and whether the spending is running ahead of the progress. That last one is the early warning most reports miss.

The money

A simple view: what you spent this quarter against budget, and the year to date, by category. Anything more than a few percent over, with one line of explanation.

No surprises is the goal. A board can accept a number that's higher than hoped. What it can't accept is a number that was fine last quarter and badly wrong this one.

Be honest with the color

Every report has a status: green, amber, red. The temptation is to keep it green.

Resist it. A report that's always green isn't believed, and the first red one will be a shock - to the board and to your credibility. An honest amber, with a plan, builds more trust than a green that turns out to be wrong.

Keep it short

Two pages is enough for most quarters. Send it three days ahead, so the meeting is for questions and decisions, not reading. Keep the detail in an appendix, or with you.

A short report also forces the right discipline: if it doesn't fit, you have to decide what really matters.

Translate, every time

A few swaps that help:

• Instead of "We need extended detection and response," try "We need to spot attackers before they shut down operations for a week."
• Instead of "We're exploring AI use cases," try "Forty people use AI tools today. We need to decide what customer data they can see."
• Instead of "The project is 60% complete," try "The project is on track to go live in March, within budget. Here's the one thing that could change that."

The bottom line

A good board report is short, honest and leads with what you need. It turns technology from something the board worries about into something it can govern.

Want a head start? The Quarterly Tech Board Report builds a two-page report from your decisions, risks, projects and spending, ready to print, with a guide to presenting it.

Free guide: The 45-Minute Tech Spend Checkup - a one-page meeting agenda for finding out whether your technology spending is working.

Related reading

• The Security Questions Every Executive Should Be Able to Answer
• Status Maintains Motion. Decisions Create Momentum.

Reporting to a board and not sure it's landing? Let's talk. Getting the board report right changes the whole conversation about technology.