Governance

There is a meeting most technology executives encounter in their first year in a senior role, and almost none are prepared for it. Nobody is hostile. The analysis is sound, the recommendation is clear, the presentation is structured correctly — and yet something does not land. The board keeps returning to the same concerns, slightly reworded. The meeting ends not because the question was resolved but because time ran out.

A technical career builds a specific relationship with expertise: the person who answers the hardest questions with the most precision is the most credible. A board does not work this way, and this is Capability Inversion operating at the level of Governance.

A board is evaluating something harder to perform than correctness: whether the executive's judgment can be trusted across a domain the board cannot independently check.

What Governance actually asks for

Projected certainty on genuinely uncertain questions does not read as competence to a board — it reads as naivety about the complexity, or as someone who has already decided and is now performing rather than advising. What a board wants, and almost never says directly, is an executive who understands the problem well enough to be honest about what they don't know, with a recommendation built on that honesty.

This includes leading board papers with the decision rather than the analysis, holding accountability discipline even when it's personally uncomfortable, negotiating from genuine understanding rather than accepting the first position offered, and building governance structures that flex under real exceptions rather than either rigid rules or none at all.

Where to start

• Before your next board paper, write the single question you're most afraid they'll ask — and answer it on the first page, not buried in the appendix.
• Practice naming what you don't yet know, specifically, rather than smoothing over uncertainty with confident language. Boards trust the honesty faster than the polish.