I once watched a brilliant engineer deliver a flawless technical presentation to a board of directors. Forty-five slides. Impeccable data. Every assumption tested, every variable considered.

The board approved nothing.

Not because the analysis was wrong. Because the engineer had answered every question except the only one the board was actually asking: Should we do this, and why does it matter?

If you've spent time presenting to boards, committees, or senior executive teams as a technical professional, you'll recognise this pattern. The harder you work on the technical substance, the less traction you seem to get.

Here's why, and what to do differently.

The Fundamental Mismatch

Technical professionals and board members are not processing information the same way in that room.

You are thinking about the system. They are thinking about the decision.

You are thinking about what's true. They are thinking about what to do.

You are thinking about risk. They are thinking about which risk is worth taking.

And crucially: you have been preparing for hours, days, or weeks. They are processing your presentation cold, alongside fifteen other items on an agenda, within a time window they may already be running over.

This is not a criticism of board members. It's the reality of how senior decision-making works. The sooner you understand it, the more effective your presentations become.

Lead With the Conclusion

The single most transformative change you can make to a technical presentation for a board is this: start with the recommendation.

Not the background. Not the methodology. Not the data. The recommendation.

"We should invest £2.4 million in upgrading the X system over the next 18 months. This will reduce operational risk by 60% and deliver a return within three years. Here's why."

Engineers often resist this instinctively. It feels like you're asking the audience to accept the conclusion before you've justified it. But that's not how boards work. They need to know where you're going before they can evaluate whether the journey is worth taking.

Lead with the conclusion. Support it with evidence. Invite scrutiny.

The Three-Slide Discipline

There is almost no board presentation that cannot be made in three slides. Not because the subject isn't complex (it often is) but because the board's job is not to understand the complexity. It's to make a decision about it.

Slide 1: The situation. What is true right now, in plain language? What is the problem or opportunity? One clear, honest paragraph.

Slide 2: The options. What choices are available? (Usually two or three, including "do nothing.") What are the implications of each? No more than a paragraph per option.

Slide 3: The recommendation. What should the board decide? Why? What does success look like? What do you need from them?

Everything else (the detailed analysis, the technical underpinning, the data) lives in an appendix. The board can call it up if they want it. Most won't. The ones who do will respect that you've anticipated the question.

Translate, Don't Simplify

Here's a mistake I see often: technical professionals, trying to make their content more accessible to a board, simplify it to the point of inaccuracy.

That's not what boards need. They need translation, not simplification.

The difference is important. Simplification removes precision. Translation preserves precision while changing the language.

An engineer might describe a structural assessment as "a compliance review of load-bearing components against current regulatory standards."

Translated for a board: "We checked whether our buildings are safe under the latest regulations. They are, with one exception that needs action within six months."

The technical precision is preserved: the buildings are safe, one exception exists, there's a time-sensitive action required. But the language is accessible, the framing is risk-based, and the implication for the board is clear.

Work on translation, not simplification.

Anticipate the Questions They Actually Ask

Board members tend to ask a predictable set of questions, regardless of the technical subject matter. If you prepare for these before the presentation, you'll rarely be caught off-guard.

"What's the risk if we don't do this?" Always have a clear answer to this. Boards often make decisions based on consequences of inaction, not just benefits of action.

"Have we done this before?" If yes, what was the outcome? If no, why are we confident it will work?

"Who else has done this?" Boards like precedent. They want to know this approach has been tested somewhere before it's tested here.

"What could go wrong?" Have two or three genuine risks identified, with clear mitigations. Boards trust leaders who can see the downside honestly.

"What do you need from us?" This is the one technical professionals most often leave unanswered. Be specific. A decision? Funding approval? Agreement to proceed to the next stage?

The Relationship That Happens Before the Meeting

This is the thing most technical professionals don't do, and it is possibly the highest-leverage change you can make.

Important decisions rarely get made for the first time in the room where they're formally made.

They get made in the conversations before the room. The one-on-one with the CFO who has a concern about capital allocation. The corridor conversation with the NED who has a background in your sector. The email exchange with the board secretary that reveals what the chair actually wants to talk about.

Before any significant board presentation, invest in briefing the key decision-makers individually. Not to sell them on the decision, but to understand their concerns, to hear their questions, and to demonstrate that you've thought carefully about their perspective.

When you walk into that room, you want no one to be surprised. The best outcome for a technical professional presenting to a board is that the formal meeting becomes a confirmation of decisions that have already been reached through high-quality individual conversations.

One Final Thought

The anxiety that many technical professionals feel before board presentations often comes from a misidentification of what's at stake.

It's not your technical analysis that's being judged. It's your judgement.

The board wants to know: can this person be trusted with complex decisions? Do they understand the full context, not just the technical dimension, of what they're recommending? Are they the kind of leader we can rely on as the scope of their responsibility grows?

When you walk in with clarity, a clear recommendation, and genuine confidence in your reasoning — not defensive about the questions, but genuinely curious about them, you answer those questions in a way that your data never can.

That's the presentation that changes careers.

Randy Ekakitie is a Chartered Engineer, executive coach, and keynote speaker. If you'd like to work on your executive communication and leadership presence, book a free strategy call.