Reporting engineering progress to your board, with evidence behind every line

Your board wants to know what the AI money bought, and the answer has to survive the follow-up question. An update that keeps the board’s confidence carries the momentum of what the team got done, and every claim in it holds up when someone asks how you know. It takes a clear structure and a hard line between what runs today and what’s still a plan.

A structure with a job for each part

Start with the hard problem the team solved and why it matters to the business, then show what runs in production today and what it changed. Cover the team next: who joined, who left and what works better than it did. Close with what comes next: the roadmap, each item marked as scoped or still an idea, and anything the roadmap needs from the board, stated plainly. Before you draft, settle two things: what can be shown working, and which parts of the roadmap are scoped. Board members who don’t read code get what the work does for the business, and the plumbing stays out.

What counts as done

Report as done only what runs today and what you measured. Everything else goes in as a plan, with the time, money or start date it still needs. For the AI spend, set delivery against a baseline from your own systems and leave seat counts and lines of code out of it, which I wrote about in what to bring when your board asks if AI is paying off.

The easiest line to blur is the one between a foundation and a product. A backend can be running and used by the team every day while the product customers will touch still needs work to finish, and a good update keeps those two apart. A date for something nobody has started becomes a window counted from when the work begins. “Just needs polish” gets called out, because it shrinks real work, and a number that undersells the work is a mistake too, so every figure gets checked against what’s actually built.

The last check before it goes out

Before the update goes to the board, your CTO or the engineer who built each piece confirms every claim, and the numbers come from your own systems. The engineers’ own account of their breakthrough carries the story, so the update still reads like people who are proud of their work. It’s the same standard my team holds the board readout to, which the CEOs we work with take to their boards once the improvements we agree on are live.

Read next

Testing a product bet before your customers do

All writing