Board members evaluate two things simultaneously when a founder or executive presents to them. The first is the content: the performance of the business, the decisions made, the plan going forward. The second is the presenter: whether this person understands the business deeply, can be trusted with capital and authority, and will communicate clearly when things go wrong.
For non-native English speakers, the second evaluation is particularly susceptible to miscommunication. It doesn't take a language failure. A slightly off register, an unclear structure, an answer that doesn't lead with the conclusion — any of these can produce a small but real reduction in confidence. Over time, these reductions accumulate.
Here's what boards are actually listening for, and how to give them what they need.
What Boards Want From the CEO Update
Board members are not looking for a comprehensive report. They're looking for evidence of three things: that the CEO understands the business at depth, that they're honest about where it stands, and that they have a clear plan.
The best board updates share these characteristics:
Lead with the headline. What is the single most important thing about this period? Not the most positive thing — the most important. If the most important thing is a miss, that's the headline.
Be honest about negatives. Board members who discover problems they weren't told about lose confidence in the presenter, not just the situation. The implicit question is: what else am I not being told? Early, honest disclosure of problems is one of the most effective trust-building tools available to a CEO.
Be clear on the plan. For every significant challenge named, the board wants to understand what you're doing about it. "Here's the situation, here's what drove it, here's what we're changing" is the right structure for difficult news.
Be short. Most good CEO updates can be delivered in 15–20 minutes. Extended updates usually signal that the presenter hasn't identified what matters most — that they're reporting rather than leading.
The Language of Command
There is a specific register in English-language board settings that conveys command and ownership. It is characterised by declarative statements over hedged ones, and first-person over passive construction.
| Hedged | Commanding |
|---|---|
| "Revenue growth has been somewhat challenging this quarter." | "We missed the revenue target. Here's why and what we're doing." |
| "There are a few things we're considering on the product side." | "We made two product decisions this quarter. Here's the reasoning." |
| "We're hoping to get the partnership across the line by Q3." | "The partnership closes end of Q3. I'm confident in this." |
| "It seems like the market may be shifting." | "The market is shifting. Here's our read on it and how we're responding." |
Hedged language reads as uncertainty about the content — as if the presenter isn't fully committed to their own analysis. Declarative language reads as ownership. Even genuine uncertainty can be stated declaratively: "We don't know yet how this plays out. We'll have clarity by [date]. Here's what we're watching in the meantime."
First-person ownership matters equally. "A decision was made to..." is a passive construction that diffuses responsibility. "I decided to..." is clear and signals accountability.
Questions From the Board
Board questions are rarely purely informational. They signal concern, disagreement, or a desire to probe the depth of the presenter's understanding. Reading what the question is actually asking matters as much as answering it.
The due-diligence question: "Can you walk me through the thinking behind that decision?" — Genuine request for reasoning. Answer with the reasoning in the order you actually used it: what you knew, what you weighed, what you decided.
The challenge-as-question: "I'm wondering whether [X] might be a better approach." — Not really a question. Acknowledge the suggestion respectfully, give your position, explain your reasoning. Don't reflexively agree to avoid conflict.
The confidence probe: "How confident are you in this plan?" — asked with flat affect after a difficult section. This is a trust signal, not an information request. Answer with composure and specificity: "Very confident — here's the basis for that." The words matter less than the tone: unhesitating.
The explicit push: "I'm not sure this is working." — Rare, but when it comes, the worst response is defensiveness. "I hear that. Help me understand what you're seeing that I might be missing." Inviting the challenge is stronger than resisting it.
The Specific Difficulty for Non-Native Speakers
Two patterns come up consistently for non-native English speakers in board settings:
Summarising too much at the cost of the point. Board updates delivered by non-native speakers sometimes add more context than is necessary — a hedge against being misunderstood. The effect is a dilution of the core message. The board gets a thorough briefing and a murky conclusion. The discipline is to cut context to the minimum and trust the audience to ask questions if they need more.
Sounding uncertain about certain language. If you're unfamiliar with a specific board-context term (covenants, drag-along rights, EBITDA adjustments), it's fine to say: "I want to make sure I'm using the right term here — what I mean is [description]." This is more credible than using the term incorrectly or visibly struggling with it.
On Admitting Problems
Many founders underreport problems to boards out of a combination of optimism and anxiety about losing confidence. The paradox is that boards give more confidence to leaders who surface problems early and clearly own them.
The structure for reporting a significant problem:
"We had a difficult [quarter/month/period]. [Key metric] was [X], against a target of [Y]. Here's what drove the miss: [specific factor]. Here's what we got wrong in our original assumption: [honest assessment]. Here's what we're changing: [specific actions]."
This is harder to deliver than a positive update. It requires composure and a willingness to be accountable. But it is what boards remember as the mark of trustworthy leadership — and they notice its absence.
Frequently Asked Questions
How should I handle a question I don't know the answer to?
"I don't have that figure in front of me — I'll get it to you today." Then actually send it. Never guess at a number in a board meeting. The board can handle "I don't know"; they can't handle incorrect data presented with confidence.
How formal should board presentations be in terms of language and register?
Formal in structure, professional but not stiff in language. The register that works is the same register a confident, senior person uses in a serious meeting — direct, precise, unhurried. The formal language of written board papers is not the right register for spoken delivery.
What's the right response if a board member is consistently hostile in questioning?
Engage with the substance, not the tone. "I want to address that properly — here's my view." If the hostility is consistent and undermining, a private conversation after the meeting is the right channel. In the meeting, staying level and substantive is almost always the right play.
How do I manage board members who have very different levels of technical understanding?
Structure your updates for the least technical person in the room, and keep the technical depth available for questions. If a board member with deep domain expertise asks for more specificity, give it — but don't optimise the main update for that person at the expense of the others.
If any of this resonates, I run weekly sessions with founders and senior professionals on exactly this kind of thing. Free 10 minute fit call to see if it's a fit. Book here.